Connecting Moneybird

Prerequisites

• An active Moneybird account
• At least one administration (company) in Moneybird
• You must be the owner of the administration you want to connect — Moneybird checks this during authorization, so a regular (non-owner) user cannot complete the connection. If bookkeeping is normally handled by an accountant or colleague, the account owner still needs to be the one who authorizes.

Steps

1. Click Authorize to start the OAuth flow
2. Log in to your Moneybird account (if not already logged in)
3. Grant access to the requested scopes
4. You'll be redirected back — the connection will show as Connected
5. The Administration dropdown will be automatically set to your first company
   • If you manage multiple companies, select the desired one from the dropdown
   • Click Save to confirm

Permissions

The integration requests access to:

• Sales invoices & contacts — Read and manage invoices and customer data
• Documents — Read and manage purchase invoices and receipts
• Bank — Read bank account information
• Settings — Read administration and ledger account configuration

Multi-Company Support

If your Moneybird account manages multiple administrations (companies):

• The default administration is set automatically on first connection
• Change it anytime via the Administration dropdown in connection settings
• Each connection targets one administration at a time

Troubleshooting

Issue	Solution
"Not Connected" after authorization	Refresh the page — the administration may still be loading
Authorization fails or is rejected immediately	Confirm you're logged in as the owner of the administration, not a regular team member. Moneybird requires the owner to authorize the connection.
Administration dropdown empty	Ensure your Moneybird account has at least one active administration
Unexpected 429 / throttling errors	Moneybird rate-limits per IP address, not per application or administration — activity from anything else sharing your integration's outbound IP can throttle your requests too. Retry using the Retry-After value on the response.
"Invalid configuration"	Delete and re-create the connection