Welcome to Invunion
Invunion helps finance teams compare bank transactions with issued invoices and review the evidence behind suggested matches. This introduction explains what the product covers today, what you need before you start, and the safest path from a sandbox trial to a controlled reconciliation decision.
Browse documentation
What Invunion helps you do
Invunion helps finance teams reconcile bank activity with issued invoices.
It brings bank transactions and invoice data into one place, suggests likely matches when the evidence is strong enough, and leaves unclear cases for someone on your team to review.
The goal is to automate as much reconciliation as possible, while keeping a clear path for someone on your team to review exceptions by hand. In practice, that means aiming for the routine cases (about 95%) to clear automatically, and making the remaining 5% easy to resolve. That last share is usually where most of the time goes.
The current focus is customer payments against issued invoices, and customer refunds against issued credit notes.
What Invunion does not decide for you
Supplier invoices, general outgoing expenses, and complex many-to-many matching are outside the current scope. Do not force an unsupported transaction into an invoice match just to clear an exception.
Who should use this documentation
- Finance teams can follow the task guides to connect test data, import invoices, and review reconciliation outcomes.
- Controllers and reviewers can use the confidence and exception guidance to understand controls and limits.
- Developers & Integration partners can use the terminology and data-flow explanations while the API reference is being prepared.
Recommended path
- Read How Invunion works for the full data and review flow.
- Complete Getting started in 2 minutes with a demo environment without real bank credentials or customer data.
- Generate a test dataset if you want invoices and bank lines that match how your files arrive, then import them in sandbox.
- Learn the core records in Key objects: start with Quick overview, then Counterparties, Payment methods, Transactions, and Invoices issued.
- Learn how to review match confidence.
- Use the troubleshooting section when a connection or transaction does not produce the expected result.
Before using live financial data
New workspaces start in sandbox mode. Completing the test-bank exercise only confirms that the sandbox workflow works. It does not prove that a particular production bank is available, or that your production setup is ready.
Before you move beyond sandbox data, confirm the workspace mode, which data you are allowed to use, user roles, provider setup, and your organisation’s reconciliation controls.
Next step
Continue with How Invunion works, or open the bank reconciliation glossary if you want to review the terminology first.
Updated
Was this article helpful?
Feedback helps us improve the next version of this guide.