By Randy Kardas, CPA, CITP, CGMA, MBA, Managing Partner, Campbell Technology Advisors
LinkedIn: Randy Kardas, CPA
LinkedIn: Campbell Technology Advisors
A healthcare organization can have a functioning EHR, billing platform and accounting system, yet still struggle to explain how a month of patient activity became a reported financial result. Each system answers a different question. Clinical records show care delivered. Billing systems track charges, claims and payments. The general ledger records financial activity under the organization’s accounting policies. A reliable report needs a defined path between them and a person responsible for investigating exceptions.
The missing control is often an agreed reconciliation process. It should identify the source and timing of each number, explain expected differences and make unresolved differences visible before leaders rely on the results. Technology can move data, but finance and operational teams must agree on what that data means.
Start with a shared definition
Take “monthly revenue.” A clinical team may mean services performed during the month. A revenue cycle team may report charges posted or claims submitted. Finance may report revenue recognized under its accounting policies. Those measures can all be valid while producing different totals. Before comparing them, document the reporting period, included entities and locations, transaction status, adjustments and accounting basis for each measure.
For every transfer between systems, name the source field, destination field, transformation rule and owner. A short mapping document is more useful than a dashboard whose totals no one can trace. It also gives finance and IT a common reference when a new service line, payer arrangement or location changes the data.
Separate timing differences from errors
Consider an illustrative encounter completed near month-end. The clinical record shows the visit in September, the charge is entered in October and the payment arrives later. A September activity report, an October charge report and a subsequent cash report will not match. That difference may be expected. A charge sent to the wrong location or account, however, requires correction. Treating both as an unexplained variance makes it harder to find the actual problem.
A reconciliation should classify differences by cause: timing, missing or duplicate records, mapping, adjustments, or accounting treatment. Set a threshold for investigation, but retain a record of smaller recurring exceptions. Repeated small differences can reveal a process defect even when no single month appears material.
Give exceptions an owner and a deadline
A useful exception log identifies the source record, amount, affected period, suspected cause, assigned owner, resolution and review date. Revenue cycle staff may need to correct a charge. IT may need to repair an interface or mapping rule. Finance may need to document why a valid operational number differs from the ledger. Assign the work to the team that can resolve the cause, and have finance review the effect on reporting.
Review open exceptions before the close is finalized. For unresolved items, record the potential financial effect and whether a temporary estimate or other accounting action is required under the organization’s policies. The goal is an explanation leaders can inspect, not a forced match between reports that measure different things.
Make the control repeatable
Begin with one material flow, such as encounter activity through charge posting and ledger entry. Document the definitions, test a sample of records end to end and record the reasons totals di(er. Then assign owners, review exceptions each month and update the mapping when workflows change. Once that routine is dependable, extend it to other locations and service lines.
The test of an integration is not whether two systems exchange files. It is whether a finance leader can follow a reported number back to the underlying activity, explain expected differences and see who is resolving the rest. That visibility makes financial reporting more useful to the people making operational decisions.