Import Mollie transactions into Visma eAccounting

For many Dutch webshops, freelancers and associations, Mollie is the payment service provider for iDEAL, credit card, Bancontact and PayPal. The payments run smoothly; the bottleneck is in the bookkeeping. Mollie pays out your balance to your business account in bundled form, while Visma eAccounting wants to see every transaction separately in order to book debtors, revenue and transaction costs correctly. In this guide you will read how to import Mollie transactions cleanly into Visma eAccounting.

Why Mollie needs special attention

A Mollie payment goes through two steps before it appears on your bank statement:

1. Customer pays — the amount is added to your Mollie balance, less transaction costs.
2. Mollie pays out — Mollie transfers the balance periodically (daily, weekly or on request) as a single amount to your business bank account.

On your bank statement you only see that payout: a single line with, for example, Mollie payout 16062026 of € 2,945.80. If you only book that line, outstanding invoices in Visma eAccounting remain wrongly open and you lose insight into transaction costs and chargebacks. The solution is to import a statement with the underlying transactions — not just the payout.

Which export should you choose from Mollie?

The Mollie Dashboard offers several exports. For Visma eAccounting two are relevant:

• Settlement export — per payout, a breakdown of all payments, refunds and chargebacks included in that payout. Available as CSV.
• Transaction export — all payments in a period, regardless of the payout.

For Visma eAccounting the settlement export works best: you split the export per payout, so that the sum of the transactions exactly matches the bank line you receive on your business account. The difference between total payments and the payout — namely the transaction costs — you book to a separate general ledger account (for example Payment service costs).

Which format does Visma eAccounting process?

Visma eAccounting supports CAMT.053 (the preferred format) and MT940. For a clean import with individual transactions, both are suitable: the file contains, per transaction, its own line with date, amount and description. CAMT.053 is preferred because of its richer transaction data. Do you choose MT940? Then note that the file must have the .txt extension. Unsure? Read MT940 vs CAMT.053: what is the difference?

Approach in outline

1. Create a separate bank account with a clearing/intermediate account for Mollie in Visma eAccounting.
2. Download the settlement CSV per payout from the Mollie Dashboard.
3. Convert the CSV to CAMT.053 or MT940 with StatementBridge.
4. Import the file under the Mollie bank account.
5. Book the payout as an internal transfer between the Mollie clearing/intermediate account and your bank account.
6. Book transaction costs to the correct general ledger account.

Step 1 — Create a Mollie bank account in Visma eAccounting

1. In Visma eAccounting, go to Settings > Bank accounts and add a new account.
2. Give it a recognisable description, for example Mollie clearing account.
3. Link the account to a general ledger account in the liquid assets class, for example 1080 Mollie clearing account.
4. Enter a fictitious IBAN — a recognisable sequence that no real bank issues, such as NL00MOLL0000000000.
5. Save the bank account. Do not activate a bank link (Autopay) for this account; otherwise you cannot import files manually.

This account becomes the ‘intermediate station’ where Mollie transactions arrive before the payout is booked to your real bank.

Step 2 — Download the settlement CSV from Mollie

1. Log in to the Mollie Dashboard (my.mollie.com).
2. Go to Revenue → Payouts.
3. Click the payout you want to process.
4. Open the Transactions tab and click Export at the top right.
5. Choose CSV as the format and save the file in a fixed location (for example \Mollie\Settlements\2026\).

Step 3 — Convert the CSV to CAMT.053 or MT940

Visma eAccounting reads CAMT.053 and MT940 by default, but not a Mollie CSV. With StatementBridge you convert the file in a few seconds:

1. Open the conversion app.
2. Upload the Mollie settlement CSV.
3. Select Mollie as the source and choose CAMT.053 (preferred) or MT940 as the target.
4. Enter the fictitious IBAN that you linked to the Mollie bank account in step 1.
5. Download the converted file. If you choose MT940, give the file the .txt extension.

More background can be found in Convert CSV to CAMT.053 and Convert CSV to MT940.

Step 4 — Import into Visma eAccounting

1. Log in to Visma eAccounting and go to Cash and bank transactions.
2. Click the arrow next to New bank transaction and select Read in bank file.
3. Click Select bank file or drag the CAMT.053 or MT940 file into the window.
4. Check that Visma recognises the Mollie bank account based on the fictitious IBAN.
5. Review the transactions and click Import.

For the general import procedure, see Importing bank statements into Visma eAccounting. The procedure with payment service providers such as Mollie, Stripe and PayPal is identical; see also AMEX, PayPal, Stripe import into Visma.

Step 5 — Book the payout and transaction costs correctly

Under the Mollie bank account there are now all the individual transactions. In your business bank ledger there is a single line: the payout from Mollie. Process this as follows:

• Payout line on the business bank → book it as an internal transfer between 1080 Mollie clearing account and your bank account.
• Transaction costs → book to a general ledger account Payment service costs or Bank charges.
• Refunds and chargebacks → book against the original debtor or a separate general ledger account Chargebacks.

At the end of each period, the balance on 1080 Mollie clearing account is zero, apart from any payout that is still outstanding. An unexplained balance points to a missing or duplicated settlement.

Common pitfalls

• Booking the bank line directly to debtors. First split the payouts into individual transactions; only then do debtors stay correct.
• MT940 without the .txt extension. Visma only reads in MT940 if the file has the .txt extension; rename the file if necessary.
• Leaving transaction costs in revenue. Book the costs to a separate general ledger account; that keeps your revenue figure clean for VAT and reporting.
• Foreign currencies. For multi-currency settlements, use a separate Mollie bank ledger with its own clearing account per currency.

File not accepted by Visma?

Do you get an error message such as File not recognised or Bank account not found? Check that MT940 files have the .txt extension. With StatementBridge you can still convert the Mollie export to a Visma-friendly CAMT.053 or MT940 file with the correct IBAN.