The deposit is real, but it was applied to the wrong invoice. Deleting the commercial document or recording another receipt does not fix that relationship. Identify what reconciliation actually did: it may have created a payment, linked an existing transaction, or recorded a movement without a document. The correction needs to address that specific effect while retaining the bank evidence that remains valid.
Record the problem before changing anything
Note the account, date, amount, bank reference, and selected document. Inspect the payment record and current invoice balance. Keep the explanation showing why the link is incorrect. This helps avoid changing the wrong movement when there are equal deposits or when a customer has made several payments during the same week. Identify the actual records rather than relying on a summary count.
Confirm who can make the correction and whether the period is open. Read access is not authority to alter accounting records. For a closed period, ask the person responsible for closing and follow the authorized procedure. Do not change dates to move the event into another month or bypass a restriction by creating an unsupported compensating entry.
Hypothetical example: two invoices with the same amount
A company received CRC 80,000 from customer A. The movement was mistakenly applied to customer B's invoice F-610, which also had CRC 80,000 outstanding. The correct document is customer A's invoice F-608. The receipt and remittance details identify F-608. The equal amounts explain the confusion, but they do not establish that B made the payment.
If reconciliation created the incorrect receipt and no other activity affects the documents, the corrected result is straightforward: F-610 has CRC 80,000 outstanding again, F-608 is paid, and the bank still shows one CRC 80,000 deposit. There are not two deposits. This calculation is illustrative; earlier payments, notes, or corrections require checking actual balances instead of assuming the same result.
Any collection communication sent to B during the error also deserves attention. Tell colleagues that the balance was restored and explain the change if an inaccurate statement was shared. Review does not finish when a status badge changes. Prevent someone from continuing to work with the previous information or recording another receipt to solve a communication misunderstanding.
Detaching a link is not always reversing a payment
Consider a different case: A's receipt was recorded correctly before the statement import, but the bank line was linked to another existing transaction. Correcting that bank relationship does not require deleting the valid receipt. Distinguish an entry created by reconciliation from an earlier record that merely gained a link. That distinction determines what should remain after undoing the relationship.
- Identify whether reconciliation created a payment or linked an existing record.
- Confirm the correct invoice using the receipt and remittance advice.
- Check period restrictions and permissions before correcting anything.
- Inspect the pending line and affected documents after undoing.
- Apply the correct relationship once and verify bank and document balances.
Tario's bank flow distinguishes those cases. Undo reverses what reconciliation created or detaches the relationship with a record that already existed, returning the movement to review. When a payment to an invoice or bill is involved, correction uses the shared payment service. This is not the same as editing the commercial document's amount or making the real deposit disappear from the bank.
Review the scope of the action
Correcting one line and reversing a complete import have different scopes. If only F-610 is wrong, inspect the movement-specific option before reversing a batch containing other correct receipts. For an entirely incorrect import, examine all associated records and the available preview. Get help if you cannot identify which operations the proposed action will affect.
An internal transfer can connect two bank lines to the same transaction. Tario's undo flow accounts for that relationship and returns associated lines to review when it reverses a transfer created by reconciliation. Inspect the counterpart account as well as the account where the mistake was discovered. Check that no unexplained combination of a confirmed side and pending side remains.
Xero's documentation distinguishes removing a reconciliation from removing and redoing a transaction, and notes locked-period restrictions. It is cited to illustrate why correction scope matters, not to provide Tario button instructions. Do not extrapolate fiscal procedures from another product or country. This article addresses the bank relationship and does not provide advice on correcting fiscal documents.
Inspect the result before applying again
Reopen the line and review its suggestions. When equal amounts match several documents, do not repeat the automatic selection that caused the mistake. Identify the correct document by customer, number, and evidence. If a valid receipt already exists, locate it for linking. If a new payment is appropriate, inspect the amount and available balance before confirming.
Do not repeat an action simply because the screen took time to respond. First check whether the operation was recorded or the movement became pending. Acting again without reviewing the outcome can create another confusion. If an error appears, preserve its message and inspect the movement and document states rather than assuming everything failed or everything was saved.
For the original example, inspect both customers after applying the correct relationship. A should have the payment against F-608, while B still owes F-610. Check that the bank record represents just one incoming amount. If any result differs, stop making additional changes to the case and investigate which earlier action is still affecting the balances.
Leave an explanation another person can follow
A useful note identifies what happened: deposit applied to F-610 because the amount matched; customer A's advice identifies F-608; relationship corrected and balances checked. Notes such as fixed or system error do not explain the event. A brief factual record helps answer internal questions and explains why a previously paid document became outstanding again.
Finally, identify a check that would prevent the same selection: obtain remittance details, compare invoice numbers, or avoid confirming ambiguous matches in bulk. Every correction does not need an extensive procedure. The next operator does need to know which evidence was missing and what additional comparison to make before accepting another movement of a similar amount.