Accounting System Integration

Manual reconciliation between Meander's expense records and external accounting systems creates duplicated data entry work for finance staff and coordinators. For HLF, the Dynamics portal is also being redesigned in parallel, making tight integration coordination essential to avoid overlap or conflict between platforms. For Blindeforbundet, Xledger integration removes a manual export-import workflow that is error-prone and time-consuming. From a sales perspective, offering accounting system integration makes Meander a more complete operational platform, increasing its value proposition for larger organizations with established financial workflows. This feature has a narrower initial audience but high impact for the organizations that require it.

The integration layer should be implemented as a configurable adapter pattern on the backend, with organization-level integration configs stored in the integration_configs table referencing the target system type (xledger, dynamics, etc.) and credentials. Each adapter implements a common interface for pushing approved expense data. OAuth or API key authentication should be supported depending on the target system's requirements. The Integration Config Repository in the mobile app stores per-org settings. HLF's Dynamics portal coordination requires careful scoping to avoid feature overlap - the integration should be limited to data sync, not UI duplication. Initial implementation should target one system (likely Xledger) as a reference implementation, with Dynamics following the same adapter pattern. All credential storage must use encrypted fields.