Frequently asked questions

Invunion gets your bank transactions in six ways: a bank connection through open banking, statement downloads from your bank over EBICS, a statement file you import (CSV, JSON, camt.053, MT940 or BAI2), statement files delivered automatically over SFTP, the API, or one line added by hand. Whatever the source, the transactions end up in the same Transactions list and Invunion matches them with your invoices.

Way	When it fits	Where to start
Bank connection	Your bank is in a country the connection covers, and you want new transactions without exporting files.	Connect bank on the Dashboard. You sign in on your bank’s own page.
EBICS	Your bank offers EBICS (common in France, Germany, Austria and Switzerland) and you have, or can get, an EBICS T contract.	Developer > Import data > EBICS: an admin adds the contract, sends the keys and signs the initialisation letter. Invunion then downloads your statements on a schedule.
Statement file	You already export statements from your bank.	Developer > Import data > Transaction import: save a mapping once per account, then import.
Automatic statements (SFTP)	Your bank or your ERP can drop statement files on a server every day.	Ask support. Invunion sets up the SFTP delivery with you.
API	Your own system already holds the bank lines.	The Ingest transactions endpoint, with an API key.
By hand	One missing line.	Add on the Transactions page.

When you connect a bank, the first sync asks for the previous 90 days. The bank may return less history. After that, Invunion keeps fetching the new transactions of the connected accounts.

EBICS is used only to download statements: Invunion never sends payments through it.

Whatever the source, the IBANs and account numbers on your transactions are stored encrypted and shown masked. See How does Invunion protect IBANs and account numbers?

Excel workbooks and PDF statements are not accepted. Export them to CSV first.

Read more: Use Open Banking demo connection · EBICS: download bank statements from your bank · Transaction import · Automatic statements · Transactions

Invunion takes the invoices you sent from a file you import (CSV, JSON, or electronic invoice XML in EN 16931 UBL or CII), from invoice files delivered over SFTP, from the API, or from an invoice you add by hand. It does not read PDF invoices or Excel workbooks, and it has no ready-made connector to an accounting tool.

Way	When it fits	Where to start
Invoice file	You export invoices from your accounting or billing tool.	Developer > Import data > Invoice import: map the format once, then every later file is read the same way.
Invoice files over SFTP	Your tool can drop UBL or CII files on a server.	Ask support, then set an SFTP file prefix so Invunion knows which files are invoices.
API	Your billing system should push each invoice as it is issued.	The Create invoice endpoint, with an API key.
By hand	One invoice or credit note.	Add on the Invoices Issued page.

Invunion works on the invoices you sent to customers, and on your credit notes. Supplier invoices are out of scope.

If your tool only exports PDF or Excel, export a CSV instead. One mapping covers every later file of that format.

Read more: Invoice import · Automatic statements · Invoices issued

Yes. Besides the IBAN of every country that uses one, Invunion recognises three domestic account formats: a UK sort code and account number, a US routing number (ABA) and account number, and a Canadian transit, institution and account number. You can enter them on a payment method, and Invunion reads them on the bank lines of camt statements to find who paid.

Country	Account format	Example
Countries with an IBAN	IBAN, with its length and check digits checked	FR76 3000 6000 0112 3456 7890 189
United Kingdom	Sort code (6 digits) and account number (8 digits)	20-00-00 12345678
United States	Routing number (ABA, 9 digits, check digit checked) and account number (4 to 17 digits)	021000021 123456789
Canada	Transit (5 digits), institution (3 digits) and account number (7 to 12 digits)	12345-003-1234567

On a payment method, type the account in IBAN or account number and set the Bank country. Invunion reads the format and shows the parts it found.

A UK sort code and account number and the matching GB IBAN are the same account for Invunion: a payment from either finds the same payment method.

Domestic account numbers are protected like IBANs: stored encrypted and shown masked. Company accounts use an IBAN or an identifier for now.

Other countries without an IBAN, such as Australia or Singapore, are not recognised yet. Their payments are still imported and matched; to tell Invunion who paid, use an identification rule or pick the counterparty on the transaction. If you need a country, tell us.

Read more: Payment methods · Transactions · Identification rules

Invunion works only with the data you bring in: your bank transactions, from a bank connection, EBICS, a statement file, SFTP or the API, and the invoices you sent. It uses them to find which payment paid which invoice. It cannot make payments or move money, it does not send invoices, and it does not handle supplier invoices or replace your accounting system.

What Invunion does

• It reads the transactions you bring in, whatever the source: a bank connection, EBICS, a statement file, SFTP or the API. See How can I retrieve bank transactions?
• It reads the invoices and credit notes you sent. See How can I retrieve invoice data?
• It proposes matches. It confirms the ones that leave no doubt and leaves the others to your team, who can correct any match.

When you connect a bank

A bank connection is one way among others, and it is optional. If you use it:

• You approve the access on your bank’s own page. Your bank login never goes through Invunion.
• The access covers the accounts you choose, and Invunion fetches their transactions.
• It lasts up to 180 days. After that, you connect the account again with your bank login. The bank may end it sooner.

When you use EBICS

• You need an EBICS T (transport) contract with your bank. Invunion only downloads statements: it does not need, and does not use, a contract that allows payments.
• The keys that identify you to the bank are created by Invunion, stay sealed on our side and are never shown.
• The bank decides which accounts and statement files the contract covers.

How your bank details are protected

• IBANs and other bank account numbers are stored encrypted and shown masked.
• Only admins can see a full number, and each time they do it is recorded in the audit log.

What Invunion does not do

• It does not make payments or move money.
• It does not create or send invoices to your customers.
• It does not handle supplier invoices or general expenses. Those bank lines are kept, but they are not matched.
• It does not replace your accounting system. Your organisation stays responsible for its records and approvals.

Read more: What is Invunion? · Use Open Banking demo connection · Match levels

The bank connection is offered in 16 European countries: Austria, Belgium, Croatia, Denmark, Estonia, Finland, France, Germany, Italy, Latvia, Lithuania, the Netherlands, Slovenia, Spain, Sweden and the United Kingdom. The list of banks for each country comes from our open banking provider when you connect, so check that yours appears in the connect dialog.

To see whether your bank is offered:

1. Select Connect bank on the Dashboard.
2. In Connect your bank account, choose the Bank country and the account type (Business or Personal).
3. Select Select your bank. The list shows the banks the provider offers for that country.

A new account starts in a sandbox Entity. There, the list shows test banks, so you can try the whole flow with invented data. Your real bank is connected in a production Entity, which we set up with you.

We do not publish a list of banks: banks join and leave the provider’s list, and a bank may offer business accounts and not personal ones, or the reverse. If your bank is missing, or your country is not listed, contact us. Statement files, SFTP and the API work with any bank.

Read more: Use Open Banking demo connection · What Is Open Banking? · Open Banking for Reconciliation

Yes, but not through a bank connection. Open banking in Invunion covers European countries only. For a bank elsewhere, bring its transactions as statement files (CSV, JSON, camt.053, MT940 or BAI2, the format of US banks), over SFTP, or through the API. Invunion then matches them like any other bank line, including payments in USD, AUD, CAD, SGD and NZD.

Most banks outside Europe can export statements as CSV or MT940, and many can deliver them over SFTP. US banks usually send BAI2 files: Invunion reads them as they are, including files that cover several accounts. Once the file mapping of that account is saved, each later file is read the same way.

Bank accounts do not need an IBAN. Besides the IBAN, Invunion recognises a UK sort code and account number, a US routing number (ABA) and account number, and a Canadian transit, institution and account number, on payment methods and in camt statements. See Does Invunion work with bank accounts that have no IBAN?

When the payment and the invoice are in different currencies, Currency conversion converts the amount with the European Central Bank daily reference rates. These are reference values, not the rate your bank applied. Conversion covers EUR, USD, GBP, CHF, CZK, DKK, HUF, PLN, RON, SEK, ISK, NOK, TRY, AUD, CAD, SGD and NZD.

We do not offer a bank connection outside Europe today, and we do not announce a date for one. If you need a specific country, tell us.

Read more: Transaction import · Automatic statements · Currency conversion

Yes. With an EBICS T (transport) contract from your bank, Invunion downloads your camt.053, camt.052, camt.054 or MT940 statements on the schedule you set, imports their transactions and runs matching. It supports EBICS 3.0 and 2.5. Invunion only downloads statements: it never sends payments through EBICS.

EBICS is the file exchange standard of banks in France, Germany, Austria and Switzerland. Setting it up takes four steps, in Developer > Import data > EBICS:

1. Ask your bank for an EBICS T contract. It gives you a server address, a Host ID, a Partner ID and a User ID.
2. Add the contract in Invunion. For many banks, the server address and Host ID are filled in for you.
3. Send the keys and sign the initialisation letter. Invunion creates your keys and sends them to the bank; you print, sign and send the letter. The bank activates your access once it has checked the letter, which can take a few days.
4. Confirm the bank’s keys against the ones your bank published. Downloads then start on the schedule.

Only admins can set up EBICS. The keys stay sealed on Invunion’s side and are never shown. If EBICS is not in your menu, it is not available for your Entity yet: contact us.

The full walkthrough is in the Guide: EBICS.

Read more: EBICS: download bank statements from your bank · What Is EBICS? · Automatic statements · Transaction import

IBANs and other bank account numbers are stored encrypted in Invunion, on payment methods, counterparties, transactions and the original bank files. Everywhere else they are shown masked, for example FR76 •••• 0189. Only admins, and API keys given a specific permission, can see a full number, and each time they do it is recorded in the audit log.

Where	What Invunion does
Storage	IBANs and account numbers are encrypted in the database, whatever their source: bank connection, EBICS, statement file, SFTP, API or typed by hand.
On screen	Masked: an IBAN keeps its country and check digits (FR76 •••• 0189), any other account keeps its last four digits (•••• 6789).
Full number	An admin selects Show the full number (admins only, logged). Each reveal is recorded in the audit log.
API and webhooks	Masked by default. An API key sees a full number only with the Reveal full account numbers permission, which is in no profile, and each read is logged.
Changes	Bank details are locked once a payment method is used, and every change to a payment method is recorded in the audit log.
Alerts	The event counterparty.bank_account_linked can notify you, or your systems, when a bank account starts identifying a counterparty.

Matching, identification rules and merges still use the full number inside Invunion, so masking does not change how payments are matched. To search for an account, type its whole IBAN or account number, or its last four characters.

The same protection applies to UK, US and Canadian account numbers.

Read more: Payment methods · Audit log · API keys · Members

Not with a ready-made connector. Invunion has no built-in link to Pennylane, QuickBooks, Xero, Sage or other accounting tools. You connect it through files exported from your tool, through the REST API, and through webhooks that tell your systems when an invoice is paid or a match is confirmed.

The usual setup has three parts:

1. Invoices in. Export invoices from your tool as CSV, JSON, UBL or CII, or have your developers send them through the API.
2. Matches out. Subscribe a webhook to the events you need, such as a paid invoice or a confirmed match, and update your accounting tool from them.
3. Your records stay yours. Invunion keeps the matches and their history. Your accounting system stays the place where entries are booked and approved.

Read more: Invoice import · API keys · Webhooks

No, only the clear ones. Invunion gives each bank line and invoice pair a match level. Certain (the payment cites the invoice) and Strong (the exact amount from the right payer) are confirmed for you. Possible pairs wait in the Match inbox for a person to decide. You can tune how matches are confirmed in Match levels.

Some cases always come back to your team:

• One payment for several invoices. Invunion does not split a payment on its own. You allocate it in the Match inbox.
• An amount that is close but not exact, or an exact amount from a sender Invunion does not know.
• Two invoices that fit equally well. When two invoices of the same customer are Strong for one payment, neither is confirmed.

A pair you reject is not proposed again. Administrators can tune the levels in Match levels, for example to stop confirming Strong pairs.

Read more: Match levels · Matching · Invoice-to-Payment Reconciliation Explained

Yes. Every new account starts in a sandbox Entity with sample data. There you can connect a test bank through open banking with test credentials, import sample invoices and see matches in the Match inbox. Nothing in the sandbox touches a real bank account.

The Open Banking demo connection walks through the test bank step by step, with the credentials to use. When you are ready for real data, the going-live checklist lists what to set up in your production Entity.

Read more: Use sample setup · Use Open Banking demo connection · Going-live checklist