Home › Exact Online and Power BI
How do you connect Exact Online to Power BI without losing records?
Through the Exact Online REST API with OAuth. A direct connection is fine for a first report, but Exact enforces call limits and a full pull hits them quickly, which is why records go missing. Load incrementally into your own layer with a checkpoint per division and period, and let Power BI read from there.
Three approaches, and when each fits
| Approach | Fits | Limit |
|---|---|---|
| Standard connector | A first look | Runs into call limits on volume |
| Direct API calls | One subject, modest volume | Loads the source during office hours |
| Own data layer | Daily use, several subjects | Needs a setup up front |
The mapping is the real work
A general ledger is not a balance sheet and a chart of accounts is not a profit and loss statement. The translation between them is where the value sits, and it belongs in a table outside the report code. In one engagement that meant 242 accounts across four levels, so a controller can reclassify an account without waiting for a developer.
Half an hour is enough to know whether we fit
No slide deck and no quote at the end. We walk through your sources, your definitions and your biggest frustration.
Book half an hourFrequently asked questions
How do you connect Exact Online to Power BI?
Through the Exact Online REST API with OAuth. For a first report a direct connection works, but Exact enforces call limits and a full pull hits them quickly. Once it becomes serious you load incrementally into your own layer and let Power BI read from there.
Why do records go missing?
Almost always because of paging and call limits. A full extract runs into the limit halfway and stops, and what you get back looks like a complete file. Incremental loading with a checkpoint per division and per period prevents that, and it makes gaps visible instead of silent.
A general ledger is not a balance sheet. How do you bridge that?
With a mapping table outside the report code. In one engagement that meant 242 general ledger accounts mapped to balance sheet and profit and loss across four levels. Because the mapping sits in a table, a controller can reclassify an account without a developer.
How do you handle multiple divisions?
As a dimension, not as separate reports. One model with division as an attribute, so consolidated and per-entity views come from the same source. Separate copies per division drift apart within months.
How long does a first connection take?
For one subject, general ledger or revenue and margin, 6 to 10 weeks to figures you can steer on. That includes the connection, the model underneath and the definitions. After that it costs you around 30 minutes per 2 weeks.