Complete your first reconciliation

Reconciliation links a bank transaction to the issued document that it settles. In Invunion v1, the supported business scope is:

• an incoming customer payment reconciled to an issued invoice; and
• an outgoing refund reconciled to an issued credit note.

Payables and automatic many-to-many matching are not promised in v1. Although records can store allocated amounts and the manual interface can work with more than one compatible item, do not assume that the automatic matcher will discover a batch payment covering several invoices.

UI wording and navigation can change. The confidence thresholds below describe current product behavior.

Prerequisites

• At least one bank transaction imported through a banking connection or supported transaction import.
• At least one issued invoice or issued credit note with an open amount.
• Access to transaction or counterparty reconciliation controls.
• Source evidence such as the bank description, invoice record, remittance reference, and customer identity.

For a safe first exercise, choose a transaction and document with the same currency, exact amount, and a clear invoice reference.

Steps

1. Choose the correct cash direction. For a normal issued invoice, select an incoming transaction. For a refund of an issued credit note, select an outgoing transaction. Do not reconcile an outgoing supplier payment to an issued customer invoice.

2. Open the transaction or counterparty context. Locate the transaction in the reconciliation-scoped transaction list or from the relevant counterparty detail. Open the available match or reconcile action.

3. Review any proposed match. Matching assigns a score from 0 to 100. A score of 80 or more is automatically confirmed, 50–79 is placed in review, and below 50 is ignored as a candidate. An automatic confirmation is still an accounting result that your team should inspect under its control process.

4. Verify currency and amount. The candidate filter expects matching currency and a broadly compatible amount. Confirm the bank amount against the invoice’s open amount, not only its original total. For a partial payment, allocate no more than the available transaction amount or the document’s open amount.

5. Verify dates. Compare the transaction date with the invoice date and due date. The matcher considers candidates near those dates, but proximity alone does not establish that the payment belongs to the invoice.

6. Verify references. Give the strongest weight to an exact invoice number, external reference, or structured payment reference. Then check the bank description and customer or counterparty association.

7. Confirm or create the match. If a review candidate is correct, use the available confirmation control. If no suitable suggestion is visible, open manual reconciliation, search for the invoice number or transaction code, select the compatible record, and inspect the proposed allocated amount.

8. Adjust the allocation if needed. For a partial settlement, enter the amount actually applied. Never increase an allocation merely to make the invoice appear paid. The product validates compatibility and available balances.

9. Submit the reconciliation. Complete the action and wait for the data to refresh.

10. Check both sides. Verify that the transaction’s remaining amount and the invoice’s open or settled amount reflect the allocation. For a fully settled invoice, confirm that its displayed status is consistent with the resulting balance.

Expected result

The chosen transaction and issued document are linked by a recorded match with an allocated amount. The remaining amount is reduced on the transaction, and the issued invoice’s open amount is reduced accordingly. For an issued credit note refund, the outgoing transaction settles the credit note itself, not the original invoices to which the credit note may have been allocated.

Edge cases and troubleshooting

• No candidate is shown: check direction, currency, date, amount, document type, open amount, and whether the transaction was ignored or is outside the settlement view.
• The correct record has a medium score: review it manually. Medium confidence means 50–79, not that the match is wrong.
• A low-scoring pair is absent: scores below 50 are ignored by the automatic candidate result. Use manual reconciliation only after independent verification.
• The invoice is paid or cancelled: it is not available as an open manual candidate.
• The transaction was ignored: an ignored transaction cannot be matched until its reconciliation state is changed.
• One payment covers several invoices: handle allocations carefully through available manual controls. Automatic N:N discovery is not a promised v1 capability.
• An outgoing payment has no candidate: normal supplier payables are outside v1. Only an outgoing refund with a compatible issued credit note belongs in the supported settlement scope.

Security and sandbox notes

Treat reconciliation as a financial control. Do not confirm a match based only on similar amount or timing, especially when different customers can pay identical totals. Restrict reconciliation permission appropriately and retain source evidence under your organization’s procedures.

In sandbox, use synthetic transactions and invoices. Mock ASPSP data is not evidence of a real payment. Sandbox results are for evaluation and controlled operation; UI and scoring behavior can change.

Next step

Read Review match confidence to understand why a suggestion may be confirmed, queued, or omitted. For a transaction with no suitable candidate, continue to Resolve an unmatched transaction.

Updated 10 August 2026

Was this article helpful?

Feedback helps us improve the next version of this guide.

Yes Not yet Tell us what is missing