Getting started in 2 minutes guide

Generate a test dataset

Use this generator for synthetic issued invoices and bank data that match how your files arrive. Every pack has 10 commercial counterparties, 1 Internal counterparty, 20 invoices, 4 credit notes, and 11 out-of-scope bank lines. Dates fall between 20 days ago and today. You choose identifiers, payment process, shared or custom amounts, credit, refund, or a mix, the payment mix, and file formats.

Browse documentation

Use this questionnaire to build a synthetic import pack for a sandbox tenant. It does not connect a bank and it does not upload anything to Invunion. You download a zip, then import the files in the product.

The generator always produces issued (customer) documents. Supplier bills are not included.

What every pack contains

  • 10 commercial counterparties (CLI-001…CLI-010). Five have full identity (VAT, external reference, national ID, e-invoicing address, postal address). Five are thin: name and a customer code, without those extra keys.
  • 1 Internal counterparty (INT-001, Demo Entity). Its row in counterparties.csv includes the own-account payment method: code PM-OWN-001, name, bank, IBAN FR7610011000201234567890189, BIC, and is_own_account.
  • 20 issued invoices and 4 credit notes in the same file — two invoices per commercial counterparty, plus two credit notes for Alpha Industries (CLI-001), one for Beta Commerce, and one for Gamma Solutions. Each credit note has a documentary origin invoice (origin_invoice_number). Credit notes are not pre-applied onto invoices.
  • Credit notes follow your answer. If you keep them as credit on the next invoices, there are no refund bank lines and all four stay open to apply in Overview. If you choose a refund, the pack adds four outbound refunds, one full refund per credit note, each in its own file: AV-2026-001 (36), AV-2026-002 (24), AV-2026-003 (30), and AV-2026-004 (48). A mix fully refunds AV-2026-001 (36) and AV-2026-003 (30), each in its own file, and leaves AV-2026-002 and AV-2026-004 open. A credit note is never partially refunded: once refunded, it shows as Refunded, and its origin invoice shows Partially refunded (or Refunded when the credit note covers the whole invoice).
  • Invoice amounts follow your answer. Mostly the same amount uses 120.00 on each customer’s first invoice and 360.00 on the second. Mostly customized gives every invoice its own total. Mixed keeps 240.00 on Alpha, Gamma, Epsilon, and Eta, and a distinct total on the other customers. Customer payments use those same totals.
  • Dates generated on download. Invoice dates and bank line dates fall between 20 days ago and today. They are never later than today. Due dates stay 30 days after the invoice.
  • Bank lines for your payment mix in the main transactions file, booked on that same bank account, plus 11 transactions that should not be matched:
    • 1 incoming internal transfer toward INT-001 (rejected from matching because the other party is the Internal own-account IBAN);
    • 8 outbound lines (payroll, tax, bank fees, loan, rent, supplies) for the default outbound exclusion rules;
    • 2 lines that stay in view until you add a reconciliation rule (described in README.txt inside the zip).
  • Credit-note refunds in separate files. When you choose a refund or a mix, each refund is its own file under transactions-credit-notes/, imported after the invoice file. A credit on the next invoices adds no refund files.

IBANs are never written on invoices, including EN 16931 UBL and CII files.

After you download

  1. Open a sandbox tenant. Do not use real customer or bank data.
  2. Follow the import order in README.txt. counterparties.csv carries Internal INT-001 and its own-account payment method on that row. When you chose customers first, the commercial customers are in that file and you import it before the invoices. Otherwise import it before the transactions file. Import the invoice file (invoices and credit notes together) and the transactions file in the order you chose. Import each file in transactions-credit-notes/ after the invoice file.
  3. Map Issuer IBAN and Recipient IBAN. The issuer sends the money and the recipient receives it. On a customer payment the counterparty is the issuer and your account is the recipient. When you chose a refund, that direction is reversed: your account is the issuer, and the counterparty — for example Alpha Industries on AV-2026-001 — is the recipient. JSON uses issuer_iban and recipient_iban the same way. camt.053 keeps your account on Stmt/Acct/IBAN and records the counterparty as debtor or creditor according to the direction.
  4. In Settings → Reconciliation, add the two description rules named in the README so the last two noise lines leave matching.
  5. Open Match inbox and Issued invoices. The incoming internal transfer should already be out of matching. One-to-one payments with an invoice number should confirm when evidence is unique. Several invoices sharing one payment stay in review: Invunion does not split one remittance across invoices. In an invoice Overview, apply open credit notes to later invoices. When the pack includes refunds, match those outbound lines to the credit notes.

Expected result

You can import the pack without real ERP or bank credentials and see a mix of confirmed matches, review items, credit notes with origin invoices, excluded outbound lines, and one rejected incoming internal transfer. Refund lines appear when you chose a refund.

Edge cases

  • If the mix does not sum to 100%, or the several-invoices slice is not a multiple of 10%, the download is blocked.
  • EN 16931 UBL packs contain one XML file per invoice and per credit note under invoices-ubl/. EN 16931 CII packs do the same under invoices-cii/. Each file carries the invoice number, dates, amounts, the line description, and the buyer name. When the customer has them, it also carries the SIREN, VAT number, e-invoicing address, and email. No IBAN is written on the document.
  • camt.053 packs replace the transactions CSV with transactions.camt053.xml. Each credit-note refund is its own camt.053 file under transactions-credit-notes/.

Security and sandbox notes

All names, IBANs, and amounts are invented. Keep the files out of production workspaces. Generating a pack does not prove that a live bank, ERP, or e-invoicing connection is ready.

Next step

If you have not connected a test bank yet, follow Getting started in 2 minutes with a demo environment. When the files are imported, continue with Complete your first reconciliation.

Generate your pack

Answers stay in your browser. The zip is synthetic French B2B data for a sandbox tenant.

Can you link your invoices to a customer number?
Would you rather migrate your customers and invoices at the same time, or migrate your customers first and then your invoices?
In the transactions that you receive, do you usually know the IBAN of your customer?

IBANs are never placed on invoices. Issuer IBAN sends the money. Recipient IBAN receives it.

How is your payment process?

Credit notes travel with the invoices. Each refund is a separate transaction file.

Do invoice amounts differ a lot from one customer to another?
If a credit note happens, will you emit a credit to the customer for their next invoices, or will it be a refund?
How do customer payments split?

Use 10% steps. The three values must sum to 100%.

Invunion will not split one payment across invoices. Those lines go to Match inbox.

How do you want to simulate the invoices?

This chooses the invoice format you will import.

How do you want to simulate the transactions?

This chooses the bank format you will import.

Updated

Was this article helpful?

Feedback helps us improve the next version of this guide.

Tell us what is missing