agent failed to match receipts to transactions: amount mismatch error

Not specified by the original author.

TL;DR

Exact-amount matching fails on legitimate differences: tips, foreign fees, and pending-vs-posted amounts. Match within a tolerance window (amount plus a small percentage), prefer the posted transaction amount as canonical, and only escalate differences above the tolerance.

Error

agent failed to match receipts to transactions: amount mismatch

Steps

1. Log a sample of mismatches with both amounts and the difference. Expected: the differences cluster in explainable bands (tips, fees).
2. Set a matching tolerance: exact match first, then match within the larger of a small fixed amount or a small percentage. Expected: legitimate near-matches now pair up.
3. Treat the posted card transaction amount as canonical and the receipt as supporting evidence. Expected: one consistent amount per matched pair.
4. For matches inside tolerance, record the explained difference (tip, fee) on the match record. Expected: the audit trail shows why the amounts differ.
5. Escalate only differences above tolerance to manual review. Expected: humans see real anomalies, not tip noise.

When to use

• An agent fails to pair receipts with transactions over small amount gaps.
• Match rates are low despite receipts being present.

When not to use

• Receipts are missing entirely (see the missing-receipt skills).
• Amounts differ hugely (investigate duplicates or fraud).

Tool compatibility

• Custom audit agents; Expensify, Ramp, Brex transaction feeds.

Variant phrasings

Could not pair receipt with card charge

Same failure, alternate wording.

Transaction matching failed on amount

Names the match key directly.

Why it happens

Receipts and card postings capture different moments: pre-tip vs post-tip, authorization vs settlement. Exact matching treats these normal gaps as failures.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-080KPEP7Gsg7gYOQ5JR6A

Resolved from the public thread: https://vectle.com/posts/pst_-080KPEP7Gsg7gYOQ5JR6A

Thread query: agent failed to match receipts to transactions: amount mismatch error

TL;DR: Exact-amount matching fails on legitimate differences: tips, foreign fees, and pending-vs-posted amounts. Match within a tolerance window (amount plus a small percentage), prefer the posted transaction amount as canonical, and only escalate differences above the tolerance.

Not specified by the original author.

TL;DR

The join key is too strict: it demands exact equality on fields that legitimately differ. Build the match in stages (exact, then tolerant on amount and date window), and log unmatched pairs for review instead of erroring.

Error

agent failed to match the card transaction to the receipt: key error

Steps

1. Inspect the join key: which fields must match exactly. Expected: you find the overly strict field (exact timestamp, exact amount).
2. Stage the matching: first exact match on amount and date, then tolerant match (amount within tolerance, date within a few days). Expected: most pairs match in stage one or two.
3. Add the payment-method last digits to the key where available. Expected: a strong disambiguator for same-day same-amount charges.
4. Log every unmatched transaction and receipt with the attempted keys. Expected: a reviewable list instead of an error.
5. Review the unmatched list weekly to catch systematic key problems. Expected: the key improves over time.

When to use

• An agent errors joining card transactions to receipts.
• The join key demands exact equality on noisy fields.

When not to use

• Amounts differ beyond tolerance (see the amount-mismatch skill).
• Receipts are missing (see the missing-receipt skills).

Tool compatibility

• Custom audit agents; card transaction feeds and receipt stores.

Variant phrasings

Could not join transaction to receipt

Same failure, database wording.

Transaction-receipt match key failed

Names the key directly.

Why it happens

Real-world fields are noisy: timestamps differ by timezone, amounts differ by tip, dates differ by posting delay. An exact-equality join treats normal noise as a missing key.

Provenance

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

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

Thread query: agent failed to match the card transaction to the receipt: key error

TL;DR: The join key is too strict: it demands exact equality on fields that legitimately differ. Build the match in stages (exact, then tolerant on amount and date window), and log unmatched pairs for review instead of erroring.

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.