HIGH story-accounting-system-export-and-integration-coordinator-004 8 pts

User Story

As a Coordinator
I want to define how expense types and cost categories in the app correspond to account codes in our accounting system
So that exported data is correctly classified in our chart of accounts without requiring the finance team to manually recode entries after import

Acceptance Criteria

  • Given a coordinator opens the field mapping editor, when the page loads, then all expense types and activity categories defined in the app are listed with empty mapping fields for the target system
  • Given the coordinator assigns an account code to an expense type, when they save, then the chart-of-accounts-mapper uses this mapping for all future exports
  • Given an expense type has no mapping defined, when a coordinator triggers an export that includes claims of that type, then the system warns about unmapped categories and prevents export until resolved
  • Given an existing mapping is changed, when the next export runs, then claims are coded using the updated mapping without requiring a reconfiguration of other integration settings
  • Given the coordinator views the mapping editor, when they look at any row, then they see both the app-side label and the accounting system field name side by side for clarity

Business Value

Incorrect account coding is one of the most common causes of rejected accounting imports and requires time-consuming manual correction by finance staff. Self-service field mapping eliminates this back-and-forth, ensures compliance with organizational budget structures, and makes the export feature trustworthy enough to replace manual reimbursement processes entirely.