Billing reconciliation
Find the gap between delivery and billing.
AI & integrations
The problem
A service recorded in one system does not prove that it was billed in another. Identifiers, service dates, procedure codes and billing statuses must be related before an apparent gap can be treated as work needing attention.
The integration also has to distinguish a reliable match from an unresolved mapping. A plausible join between records is not enough when the result will inform billing review.
The solution
The project investigates and develops a reconciliation workflow that normalises records, establishes cross-system mappings and compares delivered services with billing information. Exception categories make unmatched and uncertain items available for review.
Connector and matching work remains in research and development. The intended result is a reviewable set of differences, with uncertain matches separated from items that can be confidently reconciled.
The decisions behind it
- Matching is a domain problem
- A shared name or date alone does not identify the same service. The comparison needs explicit identifiers and service-level matching rules.
- Uncertainty needs a review path
- An unmatched record may mean missing billing, missing source data or an incomplete crosswalk. Those cases should not collapse into one confident answer.
- Cross-system record mapping
- Reconciliation workflow design
- Exception review planning