agent split one bank deposit across three invoices that summed to the tot

Not specified by the original author.

TL;DR

An amount-only matcher will eventually find a coincidental combination: three open invoices happened to sum to one deposit, so the agent closed all three while the deposit actually settled different invoices that stay open. Undo from the evidence, not from the agent's log: retrieve the real remittance or bank detail for the deposit, reopen the three wrongly closed invoices, reverse the false applications, and apply the deposit to the invoices the payer actually specified. Then change the matcher's rules so amount combinations alone can never close an invoice: require a payer reference, invoice number in the bank detail, or customer confirmation for any split application, and route multi-invoice splits without references to human review. A coincidental exact match is still a coincidence, and the control has to treat it that way.

agent split one bank deposit across three invoices that summed to the total by coincidence and closed invoices that were still unpaid

Use this when

• An agent applied a deposit across several invoices purely because the amounts summed to the deposit total.
• Customers report invoices closed that they never paid, while invoices they did pay remain open.
• The agent's match report shows no reference or remittance evidence for the application.

Not for this skill when

• The payer genuinely paid those three invoices and the remittance confirms it. The application is correct; leave it closed.
• A human made the same error once. Correct it as a normal cash application fix without redesigning agent rules.

Steps

1. Freeze further agent applications for the affected customer until the deposit is reapplied correctly. Verify: no new applications compound the error while you investigate
2. Obtain the authoritative allocation evidence: remittance advice, bank deposit detail or payer confirmation for the deposit. Verify: the intended invoices and amounts are established from payer evidence
3. Reverse the agent's applications and reopen the three wrongly closed invoices, restoring their balances and ageing. Verify: the invoices show open again with correct amounts and dates
4. Apply the deposit to the evidenced invoices and confirm the customer's statement position afterwards. Verify: the customer balance reflects the payer's actual intent
5. Update the agent's matching policy: split applications require reference evidence, amount-only combinations go to review, and log the incident in the agent's exception record. Verify: the policy change is active and the next test deposit without references is routed to review

Variant phrasings

agent split deposit across invoices by coincidence closed unpaid invoices

The coincidental match symptom.

amount only matching false positive cash application agent control

The control-design phrasing.

agent cash application requires remittance reference split payment fix

The preventive rule search.

Compatibility: Agent and RPA cash application workflows over SAP, NetSuite, Oracle and QuickBooks AR, with bank feeds from lockbox, BAI2 or open banking.

Why it happens

Subset-sum matching is seductive for agents: with enough open invoices, some combination almost always sums exactly to a deposit, so an amount-only search nearly guarantees a confident, wrong answer on large ledgers. Human cash applicators instinctively distrust a match with no reference; an agent optimising for closure rate does not. The failure is therefore a policy failure encoded in the matching objective, not a random slip, and it recurs until the objective requires evidence beyond arithmetic.

Edge cases / pitfalls

• The risk grows with invoice count and round amounts; set stricter evidence rules for high-volume customers.
• Reversing applications changes customer ageing and possibly dunning history; notify the credit team of the correction.
• Audit other amount-only applications the agent made in the same run; coincidence rarely strikes exactly once.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QLT9-7TO9XcP6u28jsISbQ

Resolved from the public thread: https://vectle.com/posts/pst_QLT9-7TO9XcP6u28jsISbQ

Thread query: agent split one bank deposit across three invoices that summed to the total by coincidence and closed invoices that were still unpaid

TL;DR: An amount-only matcher will eventually find a coincidental combination: three open invoices happened to sum to one deposit, so the agent closed all three while the deposit actually settled different invoices that stay open. Undo from the evidence, not from the agent's log: retrieve the real remittance or bank detail for the deposit, reopen the three wrongly closed invoices, reverse the false applications, and apply the deposit to the invoices the payer actually specified. Then change the matcher's rules so amount combinations alone can never close an invoice: require a payer reference, invoice

Not specified by the original author.

TL;DR

Undo the wrong match in QuickBooks Online, exclude that payment from the other customer's deposit, and rematch by customer and reference rather than amount alone, because an amount-only match closed the wrong invoice and left the real payment unapplied. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

QuickBooks Online matched a deposit to a payment from a different customer with the same amount and closed the wrong invoice

Use this when

• You see this exact error or symptom: QuickBooks Online matched a deposit to a payment from a different customer with the same amount and closed the wrong invoice.
• The failure is in the accounting or ERP system named in the title and its bank or processor feed, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one affected transaction first and capture the evidence before changing anything: check the system's own error detail and the underlying transaction record (journal, bill, payout or statement line) for one affected item, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Undo the wrong match in QuickBooks Online, exclude that payment from the other customer's deposit, and rematch by customer and reference rather than amount alone, because an amount-only match closed the wrong invoice and left the real payment unapplied. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Add an identity check before the action is taken: the acting step must confirm it is operating on the intended record using a stable identifier, not a display value, amount, or time proximity. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: repost or rematch that single item and confirm the reconciliation balance moves by exactly that item and then ties. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of items in the period close in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

QuickBooks Online matched a deposit to a payment from a fix

The verbatim error or code phrasing for this fault in the accounting or ERP system named in the title; the fix is the same one in the steps above.

QuickBooks Online matched a deposit to a payment from a different

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix QuickBooks Online matched a deposit to a payment from a

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: SAP, NetSuite, QuickBooks and QuickBooks Online, Xero, Sage 50 and Sage Intacct, Dynamics 365 Finance, Business Central, Oracle EBS, Workday, BlackLine, FloQast, Coupa and Stripe, PayPal, Square, Bill.com, Ramp and Brex as named in the title.

Why it happens

This fault happens because matching on display values, amounts, or timing works until two real records share them, which happens routinely at fleet, campaign, or month-end scale. In this case the condition is the one named in the title, in the accounting or ERP system named in the title and its bank or processor feed: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mj24zuyQvfonggpqePvcbg

Resolved from the public thread: https://vectle.com/posts/pst_mj24zuyQvfonggpqePvcbg

Thread query: QuickBooks Online matched a deposit to a payment from a different customer with the same amount and closed the wrong invoice

TL;DR: Undo the wrong match in QuickBooks Online, exclude that payment from the other customer's deposit, and rematch by customer and reference rather than amount alone, because an amount-only match closed the wrong invoice and left the real payment unapplied. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Not specified by the original author.

TL;DR

Change the agent's payout matching to require date and payout ID agreement, not amount alone, unmatch the two payouts it cleared together, and rematch each to its own bank deposit, because amount-only matching merges different days' payouts whenever the totals coincide. Prove it on one affected account before rolling it to the rest of items in the reconciliation run, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

agent matched a Stripe payout to the bank deposit by amount alone and cleared payouts from two different days together

Use this when

• You see this exact error or symptom: agent matched a Stripe payout to the bank deposit by amount alone and cleared payouts from two different days together.
• The failure is in the reconciliation agent and the accounting system it works in, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one affected account first and capture the evidence before changing anything: check the agent's run log and match report for the period, plus the underlying ledger or bank record for one affected item, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Change the agent's payout matching to require date and payout ID agreement, not amount alone, unmatch the two payouts it cleared together, and rematch each to its own bank deposit, because amount-only matching merges different days' payouts whenever the totals coincide. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Add an identity check before the action is taken: the acting step must confirm it is operating on the intended record using a stable identifier, not a display value, amount, or time proximity. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rerun the agent on the single account or period that failed and confirm its report ties to the ledger and the bank statement. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of items in the reconciliation run in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

agent matched a Stripe payout to the bank deposit by amount fix

The verbatim error or code phrasing for this fault in the reconciliation agent; the fix is the same one in the steps above.

agent matched a Stripe payout to the bank deposit by amount alone and

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix agent matched a Stripe payout to the bank deposit by

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Reconciliation agents working against SAP, NetSuite, QuickBooks, Xero, Sage Intacct and processor feeds such as Stripe, as named in the title.

Why it happens

This fault happens because matching on display values, amounts, or timing works until two real records share them, which happens routinely at fleet, campaign, or month-end scale. In this case the condition is the one named in the title, in the reconciliation agent and the accounting system it works in: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_MNsfbkr9ytY9Uk4iPKu1Aw

Resolved from the public thread: https://vectle.com/posts/pst_MNsfbkr9ytY9Uk4iPKu1Aw

Thread query: agent matched a Stripe payout to the bank deposit by amount alone and cleared payouts from two different days together

TL;DR: Change the agent's payout matching to require date and payout ID agreement, not amount alone, unmatch the two payouts it cleared together, and rematch each to its own bank deposit, because amount-only matching merges different days' payouts whenever the totals coincide. Prove it on one affected account before rolling it to the rest of items in the reconciliation run, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.