# Unmatch
> A match can be wrong: the wrong payment, the wrong amount, or a line that is not a customer payment. Open the match, choose Remove match and say why. Invunion computes the invoice and the transaction again and keeps the removed match in the history. Worked examples show the status before and after each correction.
Source: https://www.invunion.com/knowledge-base/unmatch/
Last updated: 2026-10-16
A match can be wrong, whether Invunion or a person made it. You can remove it at any time. Nothing is lost: Invunion keeps the removed match in the history, with who removed it, when and why.
## Where to remove a match
| From | How |
| --- | --- |
| **Counterparty overview** | Select the arrow at the start of a line, then **Edit Match**. See [Overview page](https://www.invunion.com/knowledge-base/counterparty-overview/#invoices). |
| The edit panel of an **invoice** or a **transaction** | Select next to a linked line, then **Save**. |
| **Transactions** | **Ignore from reconciliation** removes every match of the line, after asking you. |
**Edit Match** gives you the most choice: the buttons below and the reasons.
## Remove one match
In **Edit Match**, select **Remove match**. Invunion asks **Remove this match?** and says which allocation goes: only this one. The other matches of the invoice and of the transaction stay.
Then choose **Why is this payment wrong?**
| Reason | When | What happens next |
| --- | --- | --- |
| **Wrong transaction: this movement did not pay the invoice** | The payment belongs to something else. This is the default. | Invunion will not suggest this payment for this invoice again. |
| **Right transaction, wrong amount** | The payment is right, the allocated amount is not. | You can match the pair again with the right amount. |
| **Duplicate** | The same payment was matched twice. | |
| **Other** | Anything else. | |
**Note (optional)** keeps a sentence with the removal, for your team and your integrations.
With any reason other than **Wrong transaction**, the payment is free again, and Invunion can match the same pair on its next run. To keep it from coming back, choose **Wrong transaction**.
Removing a line with in an edit panel does not ask for a reason. It is saved as **Other**.
### Undo a Wrong transaction
**Not a match** in the Match inbox works the same way as **Wrong transaction**. To bring a pair back, open the invoice in the Match inbox and select **Show me all the transactions**. The pair is listed there; select it to restore it.
## Remove all matches
**Remove all matches** removes every match at once. What it does depends on where you started:
- **From an invoice**: every payment is removed from this invoice. Credit notes applied to it stay. You choose a reason, as above.
- **From a transaction**: every invoice is removed from this payment. Then choose:
- **Remove only**: the transaction becomes Unmatched, ready for another match.
- **Remove and ignore**: the transaction becomes Ignored and leaves matching. Use it for a line that is not a customer payment.
## Fix an amount without removing
When only the amount is wrong, you do not need to remove the match. Open the edit panel of the invoice or of the transaction, change the **Allocated amount** of the line, then select **Save**.
## Change the counterparty
In **Edit Match**, you can also change the counterparty of the transaction. Invunion warns you first: this removes the other matches of the transaction, because they belonged to the previous counterparty.
## What changes after a removal
- **The invoice**: its **Settled**, **Amount due**, **Recovery** and status are computed again. A Paid invoice can become Partially paid, Unpaid or Overdue.
- **The transaction**: its **Remaining** and status are computed again. A Matched line becomes Partially matched or Unmatched.
- **The Dashboard**: the numbers follow at the next refresh.
- **The history**: the [Audit log](https://www.invunion.com/knowledge-base/audit-log/) records the removal, with who did it, when and the reason.
- **Your integrations**: [Webhooks](https://www.invunion.com/knowledge-base/webhooks/) send **Match cancelled** and **Invoice settlement changed**. A **Wrong transaction** also sends **Match rejected**.
## Example: a wrong payment
Invoice **FAC-2026-019**, Kappa Retail, **480,00 €**, was paid by two payments of 200,00 and 280,00 (see [the example](https://www.invunion.com/knowledge-base/match-from-invoice/#example-an-invoice-paid-in-two-parts)). The 280,00 payment was in fact for another invoice.
You open the match and select **Remove match**, with the reason **Wrong transaction**.
| | Invoice FAC-2026-019 | Amount due | Transaction of 280,00 | Remaining |
| --- | --- | --- | --- | --- |
| Before | Paid | 0,00 | Matched | 0,00 |
| After | Partially paidOverdue · 3 days | 280,00 | Unmatched | 280,00 |
The due date has passed, so the invoice is overdue again. The 280,00 payment is free to be matched to its real invoice, and Invunion will not suggest it for FAC-2026-019 again.
## Example: a wrong amount
A payment of **280,00** was matched to FAC-2026-019 with an allocated amount of **200,00** instead of **280,00**.
| | Invoice FAC-2026-019 | Amount due | Transaction of 280,00 | Remaining |
| --- | --- | --- | --- | --- |
| Before | Partially paid | 80,00 | Partially matched | 80,00 |
| After you set **Allocated amount** to 280,00 and select **Save** | Paid | 0,00 | Matched | 0,00 |
No removal needed: the match stays, with the right amount.
## Example: not a customer payment
A transfer of **1 200,00 €** between two of your own accounts was matched to an invoice of **1 200,00** by mistake. From the transaction, you select **Remove all matches**, then **Remove and ignore**.
| | Invoice | Amount due | Transaction | Remaining |
| --- | --- | --- | --- | --- |
| Before | Paid | 0,00 | Matched | 0,00 |
| After | Unpaid | 1 200,00 | Ignored | 1 200,00 |
The invoice is open again and waits for its real payment. The transfer no longer counts in **Transactions considered** on the Dashboard. With **Remove only**, it would be Unmatched instead.