Accounting API
Feature Detail
Description
This feature provides API-level integration between the Meander Admin Web Portal and external accounting systems, specifically Xledger (Blindeforbundet) and Microsoft Dynamics (HLF). The integration automates transmission of expense and financial data, replacing manual export-and-import workflows. A pluggable abstraction layer supports multiple accounting backends through a unified interface, so each organization configures their preferred system without requiring platform code changes.
Sources & reasoning
Line 72 documents explicit per-org accounting system requirements (Xledger and Dynamics) for HLF and Blindeforbundet. Line 354 places this under Fase 3, mapping to v1.1. The need for a shared API abstraction across two different accounting backends with org-specific credentials directly motivates this feature.
-
docs/source/likeperson.md · line 72API-integrasjon mot regnskapssystem (Xledger for Blindeforbundet, Dynamics-portal for HLF).
-
docs/source/likeperson.md · line 354Regnskapsintegrasjon (Xledger for Blindeforbundet, Dynamics accounting for HLF)
Analysis
Expense reimbursement and financial reporting currently require manual data entry into separate accounting systems, creating administrative burden and error risk. Automating this data flow eliminates double-entry, reduces processing time, and ensures financial records are accurate and timely. For HLF and Blindeforbundet - the two organizations with explicit accounting integration requirements - this directly reduces staff hours spent on reconciliation. The unified API abstraction means future organizations with different accounting systems can be onboarded without code changes, supporting the platform's multi-tenant scalability goals.
The integration uses a pluggable AccountingApiGateway infrastructure component accepting a provider configuration per organization. Each provider (Xledger, Dynamics) implements a shared interface, with organization-specific credentials stored as encrypted tenant configuration. AccountingApiClient handles authentication, request signing, and error handling. AccountingIntegrationRepository persists sync state and transaction IDs to support idempotent retries. All outbound calls are recorded in the audit trail for compliance. The gateway implements retry logic with exponential backoff for transient failures.
Components (7)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.