Accounting API

Manual re-entry of approved expenses into accounting systems is a significant source of administrative overhead and transcription errors for both HLF and Blindeforbundet. Automating this transfer directly reduces staff workload, accelerates reimbursement cycles, and eliminates a category of human error that creates reconciliation problems downstream. For Meander as a product, native accounting integration is a strong differentiator when selling to organizations that already rely on Xledger or Dynamics, making the platform a credible end-to-end solution rather than an isolated activity tracker. It also strengthens compliance posture by creating a reliable audit trail from expense registration through to accounting entry.

The accounting integration should be implemented as an event-driven service that listens for expense approval events and dispatches formatted payloads to the configured accounting API endpoint. Organization-specific configuration (API base URL, credentials, expense type-to-account-code mappings) is stored in the integration_configs table with encrypted credential fields. The service must support at-least-once delivery with idempotency keys to prevent duplicate postings. Retry logic with exponential backoff is required for transient failures. Both Xledger and Dynamics have REST APIs; the adapter pattern should abstract provider-specific serialization behind a common interface to allow future accounting systems to be added. All sync attempts and outcomes must be written to audit_logs.