Reconcile a BaaS program's internal ledger, Treasury Prime transaction feed, and bank-generated account statement into a three-way break report
domain: banking · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Pull program transactions for the period via the Treasury Prime List Transactions endpoint, scoped by account and date range
Generate or fetch the corresponding account statement via the Fetch/Generate a Statement endpoint, built from a configured Statement Configuration
Subscribe to transaction.create and transaction.update webhooks to catch late-posting or reversed entries close to real time, using them as triggers rather than the source of truth
Match each entry by transaction id, effective date, and amount across the internal ledger, the Treasury Prime transaction list, and the bank statement
For any account with an attached Reserve Account (overdraft coverage), pull its separate transaction history and reconcile it manually — Treasury Prime does not auto-replenish reserve funds
Age and escalate unmatched items past a defined threshold, distinguishing timing differences from true breaks
Known gotchas
Reserve Account overdraft coverage is not auto-replenished by Treasury Prime — the reserve amount field must be manually reset and the funds manually reconciled via ACH or book transfer, or it silently drains
Webhook delivery is a convenience trigger, not a guaranteed exactly-once feed — the List Transactions endpoint must remain the authoritative source when reconciling
Treasury Prime documents that responses may include undocumented fields beyond the published schema — matching logic should tolerate extra fields rather than fail on them
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?