The bank shows the right deposit, but a customer says their invoice remains unpaid. A review reveals an allocation to another invoice from that customer. Recording a second payment might remove the warning while duplicating money. The correction needs to reassign the existing payment, retain its transaction, and explain the changing document balances.
Establish the error first
Find the payment using reference, date, bank account, currency, and amount. Open the invoice that received it and the intended destination. Confirm whether the customer paid one invoice or several. An aging difference alone does not prove an allocation error: partial payment, a pending note, or another cutoff may explain it.
When the deposit is correct and only document allocation changes, no new money movement is needed. Duplicate payment is another problem. Returned goods may require corrective documents and refunds too. Identify the cause so reassignment does not hide a return or remove a debt that still exists.
Two invoices, one deposit
Assume two CRC 100,000 invoices. A CRC 60,000 payment was allocated to A, but evidence points to B. Before correction, A owes CRC 40,000 and B owes CRC 100,000. After reassignment, A owes CRC 100,000 and B owes CRC 40,000. The bank still contains the same CRC 60,000 deposit.
That before-and-after comparison is what needs approval. If both become fully paid, something is wrong. If another deposit or changed bank account appears, check the workflow. Record a specific reason linked to supporting evidence without adding unnecessary personal information to free text.
Review reassignment in Tario
Tario displays linked payments and offers reassignment where permissions and state allow. Choose destination documents, distribute the amount, and state the reason. The review shows source and destination balances before confirmation. Use it to check conservation of the original amount and the available capacity.
A destination must have capacity to receive the allocation. Do not force more than its current balance. Another user may collect while the preview is open, requiring an updated review. Approval based on old figures can create an excess even when the original allocation looked correct.
Different currencies mean different amounts
Bank and document amounts may use different currencies. A colones deposit applied to a dollar invoice needs both figures and support for conversion. Do not copy the same number between currencies or assume today's exchange rate applies. Inspect the values proposed for this specific operation.
For several destinations, follow each allocation and total bank amount used. The distribution must preserve original money and respect document balances. If a difference remains unexplained, stop and request detail. Reallocation cannot create an unsupported customer credit or another collection.
What the assistant can prepare
Tario's assistant can prepare a proposal after identifying the exact payment and reading documents. It needs a system-calculated preview with authoritative before-and-after balances. The approval card must represent that proposal. A generic instruction to fix everything does not replace a person's click on this reassignment card.
If confirmation returns an uncertain outcome, reopen the review and inspect the result first. Blind repetition may intervene again on a payment already corrected. Check its bank relationship and correction history. A later reviewer should be able to follow origin and destination without relying on memories of a chat.
Finish with a receivables check
Open both documents after confirmation and verify their balances. Review the customer statement or aging at the same cutoff and confirm the deposit remains recorded once. Tell collections staff what changed if a reminder was wrong. A technical correction is incomplete while administration still uses an old export.
Bring the A-and-B example to a Tario demo and inspect the proposal before real execution. Check the CRC 60,000 allocation against the intended destination and the reopened source balance. Find the saved reason afterward. These small checks make the correction understandable to someone reviewing it next week.