What can you already see in Moneybird itself?

Moneybird is built for bookkeeping and invoicing, and it does that well. It shows your profit and loss statement, your balance sheet, outstanding invoices and your bank position. For a business owner with one administration who checks the numbers once a month, that is often enough.

It starts to pinch when your questions get broader. For example:

  • You want revenue per customer or per product over two years, not just this year's position.
  • You have several administrations (a holding and two operating companies) and want to see them side by side.
  • You want to combine Moneybird figures with your CRM, time tracking or online shop.
  • Several people need to see the same numbers, but not everyone should have access to the bookkeeping.

Then a dashboard in Power BI is a logical next step. Still unsure whether it is worth it? Read Excel or Power BI first.

Which Moneybird data do you need for a financial dashboard?

Moneybird's public API gives access to most of the data you see in the package. For a first financial dashboard you broadly need:

  1. Sales invoices and invoice lines. Amounts, dates, status, customer and, per line, the product or ledger account. The basis for revenue and margin.
  2. Contacts. Customers and suppliers, so you can show revenue and outstanding items per relation.
  3. Payments and financial mutations. When something was paid and what happens on the bank account. Needed for payment terms and a cash flow picture.
  4. Ledger accounts. Moneybird uses RGS codes (the Dutch standard chart of accounts). They make it easier to group costs and revenue consistently, also across several administrations.
  5. Purchase invoices and receipts. If you want to track costs and margin alongside revenue.

If you use hours, projects or subscriptions in Moneybird, you can add those later. Start small. Exactly which fields are available depends on your plan, the modules you use and the permissions of the connection. Our page on the Power BI Moneybird integration explains how we map that out per administration.

Connect directly or via a data layer?

There are two routes to get Moneybird data into Power BI.

Directly from Power BI. With Power Query you can call the API directly with an API token. That works for a quick test with a few hundred invoices. But you have to handle pagination yourself (the API returns at most 100 records per request), your token sits inside the report, and every refresh fetches everything again.

Via your own data layer. A small process fetches the data, stores it in a database and afterwards refreshes only what is new or changed. Power BI reads from that database. It is a bit more work upfront, but:

  • you build up history, even when something is changed or deleted in Moneybird;
  • you don't run into the API limits;
  • you can easily add a second administration or another source;
  • the token lives in one managed place, not in a report file.

For daily use we recommend the second route. What such a data layer is and how heavy it needs to be is explained in what is a data foundation.

Which five KPIs belong on your Moneybird dashboard?

Keep the first dashboard small. Together, these five numbers give a good picture of where your business stands financially:

  • Revenue per month versus last year. Excluding VAT, by invoice date. That shows seasonal patterns and whether you are really growing.
  • Outstanding receivables and their age. How much is outstanding, and how much of that is more than 30 or 60 days past due?
  • Average payment term per customer. The number of days between invoice date and payment. A customer who gradually pays later and later shows up here before it shows in your bank account.
  • Gross margin per month. Revenue minus direct costs, grouped by ledger account. Only possible if purchases are booked properly.
  • Customer concentration. What share of your revenue comes from your five largest customers? Useful for making risk visible.

Write down how each KPI is calculated: which date leads, how credit notes count and whether amounts include or exclude VAT. More on choosing core metrics in the 10 KPIs every SME dashboard needs.

What does that look like in practice?

A fictional example to make it concrete. An installation company with twelve employees uses Moneybird for the operating company and a separate administration for the holding. Every month the owner asks the bookkeeper for an overview of outstanding invoices and revenue to date. By the time it is discussed, that overview is already a week old.

In Power BI that becomes one report with three pages:

  • Overview: revenue per month against last year, gross margin and total outstanding receivables, with a filter per administration.
  • Receivables: per customer what is outstanding, how old it is and the average payment term over the past twelve months. The office team uses this list to make targeted calls.
  • Customers: revenue per customer over two years and the share of the largest customers.

The data refreshes every night. The owner opens the report on Monday morning and no longer has to ask anyone for an export.

Step by step: connecting Moneybird to Power BI in five steps

  1. Choose the questions and set the definitions. What do you want to see every week or month, and who uses it? Pick three to five KPIs and write down how they are calculated.
  2. Arrange API access. Moneybird supports a personal API token and OAuth. A token is fine for your own administration; preferably put it on a separate or shared admin account, not in the name of one employee. Only grant the permissions the dashboard needs.
  3. Fetch and store the data. First load the history (for example two years of invoices), then only the changes each day. For invoices, among other things, Moneybird offers a synchronization endpoint that returns an id and version per record, so you only need to fetch records that changed.
  4. Build the data model and reconcile with Moneybird. Compare revenue per month and outstanding items with the reports in Moneybird itself. If they match, move on. If not, the difference is usually in VAT, credit notes or the chosen date.
  5. Build the report and arrange ownership. Show the first version to the people who will use it. Set up a daily refresh and make sure someone gets an alert when it fails. To share the report you need Power BI licences; which ones is explained in Power BI licensing in 2026.

Where does it usually go wrong?

  • API limits. According to Moneybird's documentation (checked on 30 October 2026) you can make 150 requests per 5 minutes, and 50 per 5 minutes for the report endpoints. Plan your first full history load accordingly. If you go over the limit, you get an error that tells you when you can continue.
  • VAT and credit notes. The biggest source of "the dashboard is wrong". Decide whether you report including or excluding VAT and in which month a credit note counts.
  • Messy contacts. The same customer twice in Moneybird means two rows in your dashboard. Clean that up once, in the source.
  • Shifting ledger accounts. If the bookkeeper merges or renames accounts halfway through the year, your margin calculation changes. Group by RGS code where possible, and agree that changes are communicated.
  • A token in one person's name. If that person leaves or the account is cleaned up, the refresh stops without anyone noticing.

For more general tips on accounting integrations, read connecting Power BI to your accounting software.

Need help with your Moneybird dashboard in Power BI?

Want your revenue, receivables and margin from Moneybird up to date in one dashboard every morning, without exports? We are happy to look at your administration and what you want to see. Read more on our page about the Moneybird integration with Power BI, see what we do in dashboarding and data engineering, or read how we work.