## TL;DR

Reconciling Stripe payouts against the wrong bank account happens when entities share one reconciliation flow without scoping: payouts from entity A get matched to entity B's bank feed. Scope every reconciliation run by entity and by Stripe account, matching each payout to the bank account actually configured for that entity. Add a pre-run check that the entity, Stripe account, and bank account triple is consistent.

```text
agent reconciled stripe payouts against the wrong bank account: multi-entity mixup
```

## Use this when

- Stripe payouts were reconciled against the wrong bank account
- Multiple entities share one Stripe or bank setup
- Reconciliation mismatches cluster by entity

## Not for this skill when

- A single entity's payouts do not match (timing or fee issue)
- The bank feed itself is missing transactions
- You are debugging payout creation rather than reconciliation

## Steps

1. Identify the mis-reconciled payouts and the bank account they were wrongly matched to.
   Expected: The scope of the error is known.
2. Reverse the incorrect matches and re-run reconciliation scoped to the correct entity.
   Expected: The books are corrected.
3. Map every Stripe account to its entity and to the exact bank account receiving its payouts.
   Expected: The triple mapping is explicit.
4. Add a pre-run consistency check: entity, Stripe account, and bank account must align or the run aborts.
   Expected: Mis-scoped runs cannot execute.
5. Require the mapping to be reviewed by finance when entities or accounts change.
   Expected: Changes are human-approved.
6. Monitor for unmatched payouts per entity; a growing unmatched pile signals a scoping drift.
   Expected: Drift is caught early.

## Tool compatibility

Stripe payouts and bank feed reconciliation; multi-entity accounting setups.

## Variant phrasings

### stripe payout reconciled wrong bank account

The error phrased directly.

### multi-entity reconciliation scoping

The structural fix phrasing.

### agent reconciliation entity mixup

The agent-operations angle.

## Why it happens

In multi-entity businesses, Stripe accounts, legal entities, and bank accounts form a mapping that humans hold in their heads: entity A settles to bank account A. An agent reconciling payouts without that mapping will match on amount and date alone, which works until two entities have similar payouts, and then it silently cross-matches. The resulting books are wrong in a way that compounds: tax, FX, and intercompany balances all inherit the error. Explicit per-entity scoping with a triple-consistency check turns the implicit human knowledge into an enforced invariant.

## Edge cases / pitfalls

- Payout timing differs by entity and currency; do not assume one settlement calendar.
- Intercompany transfers between the entities' bank accounts can look like payouts; exclude them explicitly.
- When an entity changes its payout bank account, the mapping update and the reconciliation cutover must be synchronized.

## Provenance

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