Finance opens the income statement in Fortnox. Sales opens Power BI and sees a different revenue figure for the same month. The finance report may be showing posted revenue while the sales report adds up invoices issued. Connecting the systems alone won't reconcile those figures.
Pick one Fortnox report you trust and one question it doesn't answer today. Those two things make a better starting brief than a long list of fields to import.
Choose the records that answer your question
A profit report by cost centre starts with ledger entries, accounts, periods and allocations. A report on what a customer bought needs invoice lines. If some entries have no cost centre, keep them visible in a separate group so finance can trace the total.
| Question | Records to check | Compare with |
|---|---|---|
| What did we earn this month? | Posted entries for the accounts and periods in scope | Income statement for the same entity and period |
| What did we invoice by product? | Invoice and credit lines with products and net amounts | Total invoiced excluding VAT on the same date basis |
| How much was unpaid at month end? | Invoices and payments through the cut-off date | Aged receivables or open-items list as at the same date |
Trace a credit note across a month end
Suppose you invoice SEK 100,000 excluding VAT in March and issue a credit note for SEK 20,000 in April. Net invoicing by document date shows SEK 100,000 in March and minus SEK 20,000 in April. Across both months, the total is SEK 80,000.
Apply the credit to the original invoice in March and the March figure becomes SEK 80,000. That's a useful lifetime view of the sale. Finance still needs to see how much was invoiced during March itself. Give those two views different names and agree which one will appear on the monthly report.
Test the numbers before choosing the connection
An export from a closed period is often enough to test the calculation. For a recurring feed, check which fields an existing integration or the Fortnox API can supply for your company. Fortnox ties API access to both the authorised permissions and the licences held by the company. Check these against the records the report will use.
Start with one company, one figure to reconcile and someone in finance who can sign it off. Run the same import twice and check the total holds. Then add a late correction and verify that it changes the report exactly once. Show when data was last retrieved successfully so users can distinguish old figures from current ones.
Common questions
Do we need API access for a first prototype?
An export can be sufficient to build and validate a draft. For a recurring report you'll also need a dependable way to get the next month's data. Compare the work of producing that file with the cost of operating an automated connection.
Can one report cover several Fortnox companies?
Yes, given access to the required records in each company. Keep the entity on every row and agree how accounts and cost centres map before combining figures. Eliminating intercompany transactions requires separate consolidation rules.