Erply Books data for your finance model

Reporting across Erply Books organisations starts with access and account mappings for each organisation. We scope the accounting data first; adding data from the Erply sales system is a separate decision.

Status: Previous Power BI experience. Fabric connection scope is established in the finance review.

How does data reach Fabric?

We plan loading from the Erply Books API into Fabric. Its API token is tied to a user and organisation. Erply Books and the Erply point-of-sale system are distinct sources.

Which data will we use?

We select the required accounts, transactions and reports, and map each organisation’s accounts to shared report lines.

What will the output look like?

For example, an overview of selected organisations using shared report lines. Each organisation’s balances are checked before combining them and comparing the result with the agreed budget. Inspect the worked example.

What is checked before implementation?

We check permissions, API access terms and request limits for each organisation, and agree token storage and rotation with your IT team.

Your finance team approves account mappings and balances for a sample period. We agree the environment, access and processing boundaries with your IT team. No API keys are needed for the first call.

What needs a separate agreement?

Currency treatment, intercompany eliminations and statutory consolidation. Accounting-system changes, unlimited history and writeback to the source also require separate scope. A management view is not automatically a consolidation solution.

How will you accept the work?

We check balances for the agreed period and entities, report-line mappings and refresh logs. Gaps are recorded before you decide on the next stage. Planning and ongoing management have separately agreed scope.

First step

Finance review: options, cost assumptions and implementation scope. Price on request. View services.

Book a call

Technical source, checked 9 October 2026: Erply Books: API. The source describes vendor capabilities, not the readiness of a Future Finance connection.