CRITICAL story-accounting-system-export-and-integration-organization-admin-003 8 pts

User Story

As a Organization Administrator
I want to securely configure and test the connection between the app and our organization's accounting system
So that exported claims reach the correct Xledger or Dynamics environment without manual IT involvement for each export

Acceptance Criteria

  • Given a coordinator opens the integration setup wizard, when they select an integration type (Xledger or Dynamics), then the wizard presents the appropriate credential fields for that system
  • Given credentials are entered, when the coordinator taps Test Connection, then the system performs a lightweight authenticated call to the accounting system and reports success or failure with a human-readable message
  • Given a successful test, when the coordinator saves the configuration, then credentials are encrypted and stored in the accounting-credentials-vault and are never displayed in plaintext again
  • Given an existing integration is configured, when a coordinator opens the integration dashboard, then they see connection status, last successful sync, and options to edit field mappings or rotate credentials
  • Given invalid credentials are saved and an export is triggered, when the export fails due to authentication, then the coordinator is directed to the credential management form with an explanatory error

Business Value

Without a self-service credential configuration flow, every integration setup requires developer intervention, creating bottlenecks and support overhead. Empowering coordinators to configure and validate their own connections reduces onboarding time from days to minutes and eliminates the security risk of credentials being shared over email or chat.