Settlement versus Reconciliation
How “settlement” language relates to Banking Reconciliation in MasteryHive — objectives, files, categorisation, currency, chargebacks, and audit.
Purpose
Prevent finance stakeholders from treating settlement and reconciliation as interchangeable products when the AI package implements reconciliation, with settlement appearing mainly as a matching mode and data fields.
Different objectives
|
Reconciliation |
Settlement (in this product) |
| Objective |
Prove GL and bank (or holdings and custodian) lines agree for a period |
Often: allocate a payment-provider or clearing total across many lines |
| In MasteryHive AI |
End-to-end product: ingest → match → unmatched → exceptions |
Bulk Settlement is a matching method / template label inside reconciliation |
| Separate settlement product |
— |
UNVERIFIED as a standalone product in this documentation source tree |
A legacy request flag is_settlement is deprecated and ignored. Classification uses customer type and template service, not that flag.
Required files
| Flow |
Typical files |
| Money reconciliation |
GL extract URL(s) + bank statement URL(s) |
| Asset reconciliation |
Holdings / custodian extracts via asset ingestion |
| Bulk settlement-style matching |
Same money file pattern; template selects bulk matching behaviour |
Inputs are object-storage file URLs, not a verified “source connection” product object.
Transaction categorisation
| Mechanism |
Role |
| Template / settings |
Chooses matching method (including bulk settlement) |
| Customer type / service |
Routes ETL (for example NIP vs other commercial paths) |
| Narration / name prep |
Prepares counterparties for fuzzy compare |
Wrong template selection surfaces as user-facing errors (for example selecting Bulk Settlement when the data shape does not fit).
Currency handling
| Behaviour |
Notes |
| Narration hygiene |
Common currency codes can be stripped from narrations before name compare |
| Amount matching |
Driven by template rules and charge bands where enabled |
| Multi-currency policy |
Confirm programme expectations with MasteryHive — do not assume automatic FX conversion |
Chargebacks
| Capability |
Status |
| Chargeback detection / tagging on matches |
Coded on supported paths |
| Separate chargeback task / publish |
Coded where the path emits it |
| Full chargeback case desk |
Part of broader ops UX — treat durable UX as environment / app dependent |
Advisement matching
UNVERIFIED — no advisement-matching product capability was found in the Banking Reconciliation AI package. Do not claim it.
Exports
| Topic |
Status |
| Accepted input formats |
CSV, Excel, PDF (as enforced by ingestion validation) |
| Operator export of results API in the AI package |
UNVERIFIED — results are persisted and may be shown or exported by the banking application |
Audit expectations
| Trail |
What it covers |
| Exception resolution audit |
Append-only record of approve / reject / escalate / reopen / reconcile decisions |
| Match / unmatched tables |
Analytical record of session outcomes |
| Full institutional audit pack |
May include banking-application logs — confirm outside this AI package |