reconciliation-match

Schedule a monthly cron run that reads the reconciliation sheet for the period boundaries, pulls Stripe charges, payouts, and fees plus the Plaid bank feed for the same period, then matches each line against invoices. Clean matches tie out silently while exceptions are escalated with both records attached.

A deposit matches within tolerance when the shortfall equals Stripe's disclosed fee or a recurring fee already explained in the sheet's notes, or when the timing lag stays within the standing allowance, defaulting to 3 business days. Anything outside these rules is classified as a mismatch and escalated.

Yes, reading a specific bank account's feed requires a per-account Plaid Item access token stored as the PLAID_ACCESS_TOKEN secret. A human must complete the Plaid Link flow once beforehand; the agent never runs Link itself and stops with an escalation if the token is missing.

No, the agent is strictly read-only on Stripe and the bank feed. Its only write target is the reconciliation sheet, and any correction needed outside the sheet is described in an escalation for a human to action.

Unmatched transactions are checked against the sheet's explained-mismatch notes first. Recurring explained items are tied out with a reference to the prior explanation, while new mismatches are escalated individually with both the Stripe and bank references attached, never force-fit or written off.