Reconciliation report templates guide¶
How operators should interpret reconciliation results: unmatched items, matched records, charges, identifiers, and where “side-by-side” fits.
Purpose¶
Give finance and operations a shared vocabulary for what the platform produces after a session — and what is not verified as a dedicated report product.
Template configuration vs report output¶
| Concept | Meaning |
|---|---|
| Matching template / settings | Request configuration that drives how lines are matched (method, bands, services) |
| Session results | Stored matches, unmatched, summaries, and exception clusters after the run |
| Named report-template catalog | Downloadable starter “report packs” as a CMS — UNVERIFIED as a product catalog |
Operators usually care about session results in the banking application UI. Integrators pass template/settings when starting ingestion.
Unmatched reports¶
| What you see | How to interpret |
|---|---|
| Unmatched GL lines | Ledger entries without a bank counterpart under the matching rules used |
| Unmatched bank lines | Statement lines without a GL counterpart |
| Persistence after resolve | Some resolve paths remove items from unmatched reporting; others leave history — follow the exception contract |
Unmatched does not always mean “error in the bank file.” It can mean timing differences, missing counterpart files, charge lines, or template mismatch.
Side-by-side reports¶
| Claim | Status |
|---|---|
| Operators compare GL and bank lines visually in a UI | May exist in a banking application — UNVERIFIED in MasteryHive AI reconciliation sources |
| Dedicated side-by-side API in the AI package | Not verified |
Do not treat “side-by-side” as a guaranteed MasteryHive AI report type until the application that owns the UI is documented from source.
Reconciled records¶
| Output | Meaning |
|---|---|
| Matched / reconciled rows | Lines paired under the session’s matching method |
| Summary counts | Aggregates for the session (including narrative summaries where configured) |
| Session status | Whether matching completed, stalled, or failed |
Bank charges¶
| Behaviour | Meaning |
|---|---|
| Charge-band matching | Optional matching that tolerates fee amounts within configured min/max bands |
| Narration exclusions | Some payment-line engines exclude bank-charge narrations from certain match paths |
Confirm whether charge-band matching is enabled for your environment and template.
Session IDs and reference numbers¶
| Identifier | Meaning |
|---|---|
| Session id | Id of the reconciliation run (caller-minted). Use it for status, support, and reruns. |
| Reference number | Bank/payment identifier on a line (transaction id, cheque number, etc.) |
| Settlement session id (data field) | Payment-rail join key on some lines (for example NIP) — not the same as the recon run’s session id |
When opening a support ticket, send the reconciliation session id first; include reference numbers for specific lines.
Expected operator interpretation¶
- Confirm the session completed (or note the failure stage).
- Review matched counts vs unmatched.
- Open exception clusters before manually editing source files.
- Prefer controlled resolve / reprocess / overwrite over ad-hoc spreadsheet edits.
- For settlement-style templates, see Settlement vs Reconciliation.