Your Tech Club
INTEGRATIONSMONEYBIRD

Moneybird integration

Once Moneybird is connected, nobody retypes orders, customers and payments any more. Invoices are ready sooner, payments get matched and your VAT overview is right without manual work. Below you'll read which data you exchange, how the API works and when an existing integration will do.

All integrations
4.8 from 127 reviews
ISO 9001 & 27001
MoneybirdAccounting and ERP · Moneybird B.V.
  • Sales invoices and external invoices goes back and forth with Your other systems
  • Contacts goes back and forth with Your other systems
  • Products goes back and forth with Your other systems
  • Payments and bank transactions goes back and forth with Your other systems
Your other systemsSuch as Shopify, WooCommerce, Mollie

Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman

What you exchange

This is the data organisations most often let flow between systems. Which of it matters to you depends on where work is getting stuck today.

Sales invoices and external invoices

Orders from an online store or platform become an invoice that Moneybird sends itself, or an external sales invoice: an invoice created elsewhere that Moneybird only posts. That choice determines who issues the invoice number and who emails the customer.

Contacts

Customers and suppliers. Moneybird has a customer_id field where you store the customer number from the other system. That way, on the next order you find the same customer instead of creating a duplicate contact.

Products

Items with price, VAT rate and general ledger account. Useful if you invoice from a CRM or quoting tool and every line needs to land on the right revenue account straight away.

Payments and bank transactions

Bank lines and payments that are linked to invoices. If the money comes in through a payment provider, you post the payout to a clearing account and match the individual payments against it there.

Purchase invoices and receipts

Documents that come in by email, through Peppol or through the app. Moneybird reads them itself and recognises supplier, amount and VAT. An integration mainly adds context here, such as the project or order an expense belongs to.

Off the shelf or custom

Not always. If an existing integration for Moneybird does exactly what you need, we'll tell you.

What already exists

Moneybird doesn't build integrations itself. It offers an open API and shows, in an integrations overview, what other parties have already built: for online stores, payment providers, payroll and time-tracking packages, stock management, tills and a few CRM packages. For Shopify, WooCommerce and Mollie there are several.

A standard integration like that is often enough if you have one online store, your products have ordinary VAT treatment and every order becomes exactly one invoice. The maker of the integration also provides the support, and you don't have to build anything.

What Moneybird does provide itself is an AI integration through MCP. It lets you connect an AI assistant of your choice to your administration, with read-only access or with read and write access.

When you need custom work
  • You sell through several channels and want different general ledger accounts, number series or VAT rules per channel.
  • Your own platform or customer portal needs to create invoices, for example for subscriptions or monthly usage.
  • Your CRM or planning package isn't in the integrations overview.
  • You want discrepancies to be held back and put to someone, instead of everything being passed on unseen.
  • You have several administrations that need the same logic, such as a holding company with operating companies.
How it works technically

REST API with OAuth or a personal token

The Moneybird API is a REST API that uses JSON and XML, with the administration ID in the path. You authenticate with OAuth 2.0 or with a personal API token. With scopes such as sales_invoices, documents and bank you limit what an integration can see and do.

Signed webhooks

Moneybird sends a POST to your URL when something happens, for example when a contact is created or an invoice changes status. Your endpoint must reply with status 200, or Moneybird retries up to ten times. Every push has an Idempotency-Key and a Moneybird-Signature, so you can prevent double processing and verify the sender.

Limits

Per IP address you may make 150 requests per five minutes, 50 for the reporting endpoints. Above that you get status 429 with a Retry-After header. Lists return at most 100 rows per page.

Sandbox administration

Moneybird offers free sandbox administrations with all features, so you can test an integration without touching your real books. Invoices from a sandbox get a watermark.

Two details that save time

IDs in Moneybird are large numbers; read them as text to avoid rounding errors. And because GET requests are cached, Moneybird advises against checking a change by reading it back immediately. Look at the status code of your request.

AI in between

An integration moves data. In between, AI can read, sort and prepare a suggestion. Where it matters, a person decides.

Purchases with context

Moneybird already reads purchase invoices itself. AI can add a step: for each invoice, find which project, order or customer the costs belong to, and prepare that as a suggestion. You approve, and only then is it posted.

Flagging open items

AI checks open invoices daily and spots which customers are paying later than usual. You get a short list with a draft reminder per customer. You send them yourself.

Asking your administration questions

Through Moneybird's MCP integration you can ask an AI assistant questions such as: which quotes are still open? Start with the read-only version. Only let an assistant write once it's clear which actions a person approves first.

Where it goes wrong

The limit on a large import

If you want to read in a year of orders in one go, you quickly hit 150 requests per five minutes. Because the limit applies per IP address, integrations on the same server share that headroom. Use a queue and spread the import.

Wrong VAT rates

Every invoice line refers to a VAT rate in the administration. If you sell to consumers in other EU countries, create those country rates first. You file the OSS return itself outside Moneybird; the VAT overview does split the amounts by country.

Duplicate contacts

Without a fixed key, every order creates a new contact. Store the customer number from the source system in customer_id, or search by email address before creating a contact.

Webhooks processed twice

Moneybird retries a webhook if your endpoint doesn't return status 200. If you don't store and check the Idempotency-Key, you end up posting the same entry twice.

How we build an integration

  1. What goes where

    Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Sales invoices and external invoices, Contacts, Products, Payments and bank transactions, Purchase invoices and receipts.

  2. Fields and rules

    For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: REST API with OAuth or a personal token, Signed webhooks, Limits, Sandbox administration, Two details that save time.

  3. Testing with real cases

    In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.

  4. Live, with logging and monitoring

    Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.

The Your Tech Club team at the office in Amsterdam
Amsterdam
Who you'll talk to

No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.

Joey van VlietJoey van VlietFounder
Yassine SeghrouchniYassine SeghrouchniFounder
  • Office on the Duivendrechtsekade in Amsterdam
  • ISO 9001 and ISO 27001, certified by Kiwa
  • 500 projects delivered
  • 4.8 from 127 reviews
Frequently asked questions

Does Moneybird have an API?

Yes. Moneybird has a public REST API, version 2, that supports JSON and XML. You use it to read and write contacts, sales invoices, external invoices, purchase documents, products and bank transactions, among other things. Access runs through OAuth or a personal API token.

Can I test a Moneybird integration without my real administration?

Yes. With a Moneybird account you can create a free sandbox administration with all features. Invoices from that sandbox get a watermark, so they can't be used as a real invoice by mistake.

How many API requests can I make to Moneybird?

Moneybird allows 150 requests per five minutes per IP address, and 50 per five minutes for the reporting endpoints. If you go over, you get status 429 and a Retry-After header. Partners with widely used OAuth apps can request a limit per administration.

Does Moneybird build integrations itself?

No. Moneybird doesn't develop integrations itself and offers an open API for that purpose. The integrations in the overview on the Moneybird site are made by other parties, who also provide the support. Moneybird does offer the AI integration through MCP itself.

Can I connect Moneybird to an AI assistant?

Yes. Moneybird has an MCP integration that you switch on under Settings, in the section for external applications and AI integrations. You choose between read-only or read and write, and copy the URL into your AI tool. Think beforehand about which data you want to share with that AI service.

My package isn't in the integrations overview. Can I still connect Moneybird?

Yes. On the Moneybird side, everything the API supports is accessible, and on the other side there is almost always an API, export or file to work with. We can integrate any system, even when no standard integration exists.