Integration: Fortnox
From payment to voucher. Automatically.
memberio transfers your CRM payments straight to Fortnox as finished vouchers. Payments marked for transfer are picked up, booked and confirmed – no manual entry, no spreadsheets, no month-end catch-up.
✓ Built for NPOs ✓ since 2007 ✓ Finnish EU Data centres
Why this integration
Your bookkeeping, without the busywork
Every payment your organisation receives eventually has to reach the books. Doing it by hand is slow, error-prone and nobody’s favourite task. This integration makes it someone else’s job – and that someone is software that never forgets.
Always up to date
The service runs on a schedule and checks for payments marked for transfer. New payments are picked up and booked without anyone lifting a finger.
Correct by design
You choose if you want the vouchers or the invoices to flow and match your accounting process. The books match what was actually sold and paid.
Nothing gets lost
Every payment gets its result written back to memberio. Success or error, you can always see exactly what was transferred and what needs attention.
How it works
This is how Fortnox works in memberio.
Set it up once. It just keeps booking. The integration runs as a background service – no buttons to press, no exports to import. Here is what happens on every cycle.
Connect
Customer configurations and Fortnox access tokens are loaded and refreshed automatically when needed.
Find
memberio payments marked for transfer to Fortnox are collected – nothing is moved without your mark.
Build
Voucher rows are assembled from payment, invoice, contact, account and product data.
Send
The finished voucher / invoices is sent to Fortnox and booked in your accounting.
Two scenarios, one flow
However the payment was made, it gets booked
Members pay in different ways. The integration handles both common cases – with the same automatic result.
Scenario 1
Payment with invoice
When the payment is linked to an invoice, the voucher is built directly from the invoice rows.
- Voucher rows mirror the invoice, line by line
- Accounts and amounts come from the invoiced products
- Books match exactly what was invoiced and paid
Included
This is what the integration takes care of
Scheduled transfers – payments are picked up continuously, not in batches you have to remember
Automatic Fortnox token refresh – connections stay alive without manual renewals
Voucher rows from invoice or product – both scenarios handled in one flow
Status written back to memberio – every payment shows its transfer result
Error handling with clear status – failed transfers are flagged, never silently dropped
Support for multiple customer configurations – one service, many organisations
Full data basis – payment, invoice, contact, account and product data all used
Runs as a reliable Windows service – always on, unattended
Need to know more?
View our FAQs.
It transfers payments from memberio to Fortnox as bookkeeping vouchers. The service runs on a schedule, finds payments marked for transfer, builds the voucher rows from your payment and invoice data, sends the voucher to Fortnox, and writes the result back to the payment in memberio.
No. Once a payment is marked for transfer in memberio, everything else is automatic. The next scheduled run picks it up, books it in Fortnox and updates the payment with the result.
Donations and other payments without an invoice are booked through the product linked to the payment, using its debit and credit accounts. If anything is missing, the payment isn’t sent to Fortnox and you’ll see the error in the CRM.
You see it in memberio. Every payment is updated with the outcome of its transfer – success or error. Failed payments keep a clear error status, so nothing disappears silently and your team knows exactly what to follow up.