Accounting Export Screen
Component Detail
Description
Main administrative screen where coordinators and org admins initiate accounting system exports. Displays available export configurations per organization (Xledger or Dynamics), allows date range selection, and shows a summary after export completion including claim count and any skipped records.
accounting-export-screen
Summaries
The Accounting Export Screen eliminates manual data transfer between the platform and organizations' financial systems by providing coordinators and administrators with a self-service export workflow. By supporting both Xledger and Microsoft Dynamics integrations, the platform accommodates the accounting infrastructure already in use by client organizations, reducing the cost and friction of adoption. Post-export summaries with skipped-record warnings give finance teams confidence in the accuracy of exported data and surface discrepancies before they reach the accounting system. This directly reduces administrative overhead for finance operations and strengthens the platform's value proposition for mid-to-large organizations with formal accounting requirements.
The Accounting Export Screen is a medium-complexity frontend and mobile component with three direct dependencies: the date range picker, the confirmation dialog, and the accounting exporter service. All three must be available before end-to-end testing of the export flow can begin. The dual-exporter requirement (Xledger vs Dynamics) introduces conditional rendering logic that must be tested independently for each org type — avoid assuming shared test data covers both paths. Role-based access enforcement must be validated in QA to confirm non-authorized roles cannot trigger exports.
The skipped-claims warning UI should be reviewed with product stakeholders early, as the definition of 'skipped' may vary and affect backend contract design. Mobile layout testing is required given the dual execution context.
Accounting Export Screen is a frontend and mobile UI component orchestrating the export workflow through three dependencies. `buildExportScreen()` renders the initial state, dynamically showing the correct exporter label via `renderOrgExporterLabel(orgType)` based on the organization's accounting system configuration fetched from context or props. `onExportTriggered(dateRange, orgId)` delegates to `accounting-exporter-service` after the confirmation dialog resolves positively; ensure the async call is guarded against double-submission with a loading state. `showExportSummary(result)` and `showSkippedClaimsWarning(skippedList)` render post-export feedback — skipped claims should be displayed with enough detail (claim ID, reason) for coordinators to act.
Access control must be enforced at the component mount level by checking the user's role against an allowlist of coordinator and org_admin roles, not just hidden via UI conditionals. The mobile execution context requires responsive layout handling and touch-friendly date range input.
Responsibilities
- Render org-specific exporter configuration (Xledger vs Dynamics)
- Allow coordinators and org admins to trigger export runs
- Display post-export confirmation with included and skipped claim counts
- Enforce role-based access so only authorized users see the export action
Interfaces
buildExportScreen()
onExportTriggered(dateRange, orgId)
showExportSummary(result)
showSkippedClaimsWarning(skippedList)
renderOrgExporterLabel(orgType)
Relationships
Dependencies (3)
Components this component depends on