Implement a complete Modern Treasury reconciliation workflow using expected payments and reconciliation results
domain: docs.moderntreasury.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Configure a reconciliation rule set in Modern Treasury by defining matching parameters: match on remittance_information, amount range, direction, and date window; assign the rule set to your internal account
For each outbound or inbound payment, create an expected payment with all known attributes; link it to the relevant counterparty and internal account
When bank transactions arrive (via your bank feed, BAI2, or SFTP statement), Modern Treasury attempts to match them against open expected payments using your rule set; view reconciliation candidates via GET /api/transactions?status=partially_reconciled
Review transactions with status=unreconciled in your operations dashboard or via the API; provide manual match decisions via POST /api/reconciliations for items your rule set could not match automatically
Retrieve the reconciliation result via GET /api/reconciliations or the expected_payment.reconciled webhook; the result includes the matched transaction ID, the expected payment ID, and the match_method
Close the reconciliation period by confirming all expected payments are either reconciled, manually resolved, or explicitly written off; export the reconciliation ledger to your ERP for period-close
Known gotchas
Modern Treasury's automatic matching runs on a schedule after transactions arrive from your bank feed; there is inherent latency between transaction arrival and reconciliation completion — do not build synchronous user-facing flows that depend on immediate reconciliation
Expected payments set with exact amounts will fail to match if the counterparty deducts a bank fee from the incoming wire; use amount_lower_bound and amount_upper_bound to accommodate common fee deductions
Reconciliation rules are evaluated in priority order; if two rules can match the same transaction, the higher-priority rule wins — test rule ordering carefully in the sandbox before deploying to production
Give your agent this knowledge — and 15,600+ 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?