Purchase Reconciliation
Match manually →Card charges match purchases exactly, to the penny, inside a 3-day posting window (7 for Private Tabs), on any card (Reed, Oct 10). Low-confidence matches surface first — confirm or reject. Know a combo the matcher can't see? Use manual match.
Where does this data come from?
- Card charges — pulled automatically from the business credit cards (via Plaid, a bank-connection service) and from imported statements
- Purchases (POs) — pulled from Skybox — every time the team buys tickets, Skybox records a purchase order
TicketLedgers pairs each card charge with the purchase it paid for, so every dollar that left a card has a documented reason. The matcher pairs the obvious ones automatically and scores its confidence; anything it isn't sure about waits here for a human decision.
What to do here: Review the suggested pairs — confirm the right ones, reject the wrong ones. For combos the matcher can't see (like six charges funding one purchase), use Manual Match.
Bank deposits ↔ marketplace payouts1 awaiting review
Exact-amount matches. Descriptor-verified ones auto-confirm; amount-and-date-only matches need a human yes.
| Bank deposit | Amount | Payout | Status | Action |
|---|---|---|---|---|
STUBHUB MARKETPLACE PAYOUT PO-MWV8YA75U3 9/30/2026 | $2849.64 | stubhub PO-MWV8YA75U3 · 9/30/2026 | suggested |
PO queue0 purchase orders still owe charges · $0.00 outstanding
Each PO lists the charges it expects (an Intake PO's captured amounts; a bulk PO's slices; otherwise its total). Charges match exactly, inside a 3-day window (7 for Private Tabs), on any card. The PO moves to History only when every line is confirmed.
Every purchase order in the window is fully reconciled.
Card charges ↔ purchases
| Card charge | Amount | Purchase ref | Purchase amt | Confidence | Status | Action |
|---|