Banking Reconciliation¶
Documentation status
Last verified: 26 Sep 2026. Readiness uses the single rubric and status vocabulary.
Automates matching of bank statements to general ledger (and asset holdings to custodian reports), with exception handling for finance operations.
Purpose¶
Help finance operations reconcile money and asset positions faster: ingest files, match lines, surface unmatched items and exceptions, and record operator decisions with an audit trail.
Users¶
| Audience | How they use it |
|---|---|
| Finance / reconciliation operators | Upload or trigger sessions; review matches, unmatched items, and exceptions |
| Finance managers | Interpret completion, reruns, and exception decisions |
| Partner / client engineers | Start ingestion via the API; exception decisions reach the service through the agreed messaging channel (HTTP resolve is a manual/fallback path) |
Business problem¶
Manual spreadsheet matching does not scale. Teams need consistent ingestion of statement and GL extracts, multi-stage matching (including fuzzy and model-assisted steps), clear unmatched states, and controlled exception resolution — without silently dropping failed work.
Capabilities¶
| Capability | What it does |
|---|---|
| Ingestion | Start money or asset reconciliation from file URLs |
| Matching | Fan out and match windows (exact, fuzzy, bulk settlement-style methods as configured) |
| Exception handling | Exception clusters are detected automatically after matching; operators resolve them with approve / reject / escalate / reopen / reconcile |
| Reports / results | Persist matches, unmatched, summaries; surface status for operators via the banking application |
| Correction / rerun | Overwrite or merge modes; reprocess unmatched; resume fields — see Product semantics |
| Completion | Session finalisation when matching batches complete (including recovery paths for stalled work) |
End-to-end workflow¶
flowchart LR
ingest[Ingest_files]
prepare[Name_and_prep]
match[Match_windows]
results[Matches_and_unmatched]
except[Exceptions]
ingest --> prepare --> match --> results --> except
- Ingest — supply GL and bank (or asset) file URLs with session and scope identifiers.
- Prepare — platform runs name extraction / reversals / ETL as configured.
- Match — engine and workers reconcile windows.
- Results — matches and unmatched records are stored; session status updates.
- Exceptions — the platform detects clusters after matching; operators resolve them through the exception resolve contract (Pub/Sub primary, HTTP manual/fallback).
Detail for operators: Report templates guide · Settlement vs Reconciliation.
Inputs¶
| Input | Notes |
|---|---|
| File URLs | Cloud-storage URLs for GL / bank (or asset) extracts |
| Session id | Caller-minted id for the reconciliation run |
| Scope | tenant_id, partner_id, and related identifiers |
| Template / settings | Matching configuration for the session |
| Mode | Merge, overwrite, or stop when data already exists |
Outputs¶
| Output | Notes |
|---|---|
| Matched records | Lines considered reconciled |
| Unmatched GL / bank | Items still requiring attention |
| Session / pipeline status | Progress and completion signals |
| Exception decisions | Append-only audit of operator resolve actions |
| Chargeback-related publishes | Where the matching path produces them |
Integrations¶
- Banking application / finance UI (uploads, status, exception UX)
- Object storage for input files
- Analytical warehouse for matches / unmatched / audit
- Event infrastructure for fan-out and resolve (platform-operated)
Partner APIs: Reconciliation API · Exception resolve.
Readiness¶
Rated with the single readiness rubric. Reasons for each rating are on that page.
| Gate | Rating |
|---|---|
| Code | PARTIAL |
| Integration Verified | UNKNOWN |
| Ops Ready | PARTIAL |
| Security Approved | NOT MET |
| GA | NOT MET |
Exception resolve carries the same ratings.
See Product readiness summary.
Limitations¶
- Treat live OpenAPI on the target environment as authoritative when inventories differ.
- Exception resolve has side-effect constraints — follow the external contract.
- Local and cloud execution modes can differ (for example sequential vs fan-out).
- In-repo scheduler for “scheduled” runs is not claimed;
is_scheduledis a request flag — see Product semantics. - Side-by-side comparison as a dedicated product API is not verified.