Skip to main contentSkip to navigation
SeniorCRE Logo

Operator playbook

Data Quality and Reconciliation: Getting Systems to Agree on a Fixed Calendar

How operators improve data quality and reconciliation across census, billing, payroll and accounting with a system of record and a close calendar.

Download the checklist

Operators improve data quality and reconciliation by naming a system of record for each governed field, stating which other systems must agree with it and within what tolerance, and comparing them on a fixed calendar. Every break is assigned to a steward with a due date and fixed at the source record. Reconcile once under governed rules, then stop re-reconciling downstream.

SeniorCRE’s Operator-Controlled Operating Record is designed and not yet implemented in any community. These educational templates do not establish product implementation, operator outcomes or legal compliance. Bracketed values require the operator’s approval.

Part of How Operators Govern Data Across Multiple Systems, the six-step operator data governance playbook.

Section 01

Why it matters

Every operator reconciles. The question is whether reconciliation is a governed process or a monthly scramble. In the scramble version, analysts pull reports from each system, line them up in a spreadsheet, adjust the differences and send the result. Next month they do it again, because nothing upstream changed.

Governed reconciliation changes three things. Each field has a named system of record, so the comparison has a reference point. Breaks are routed to the people who can fix the source, so they do not recur. And the calendar is fixed, so owners, lenders and boards know when figures are final.

The result is not a world without discrepancies. Systems will always disagree at the edges. The result is that disagreements are found early, settled by rule and recorded, so the reported figure can be defended.

Section 02

How to do it

  1. Step 1

    Choose the fields that matter most

    Start with the figures that appear in owner, lender and board reporting: census, billed days, hours worked, agency hours, care level. A short list governed well is worth more than a long list governed loosely.

  2. Step 2

    Name a system of record for each field

    Decide which system's value governs. The choice belongs to the domain owner and is recorded in the data dictionary. It may differ by field even within one domain.

  3. Step 3

    Set tolerances and cadence

    State how closely each comparison system must agree, and how often to check: daily for census, per pay period for labor, monthly for revenue. Tolerances are placeholders until owners approve them: [tolerance].

  4. Step 4

    Route breaks to stewards

    Each break goes to the field's steward with a due date. The steward fixes the source record, or documents why the difference is valid, and closes the break.

  5. Step 5

    Publish a close calendar

    Set dates when each period's figures are final. After close, changes go through a documented adjustment with an approver, so final means final.

  6. Step 6

    Measure the process

    Track open breaks, average days to close and repeat breaks by field. A rising repeat rate signals a definition or workflow problem upstream.

Worked example: fictional Operator 1

Operator 1 compares a fictional physical-census assertion with a billing assertion for a proposed reporting period. The steward checks the entity crosswalk, extraction times and approved definitions before calculating anything. A departure recorded after [approved cut-off] explains a timing difference, while an unmatched residency episode remains a separate identity exception. Both original assertions stay available. The owner decides whether the late event belongs in the current close or a later approved adjustment; the steward does not select whichever file arrived last.

The exception packet identifies the cause, applicable rule, authorized correction and retained report reference. A reviewer checks the corrected source through a fresh readback and confirms that unresolved items remain provisional. If the assertions answer different questions, each measure keeps its own label rather than being forced to agree. This fictional exercise uses no real totals and promises no savings; acceptance depends on the operator actually performing the comparison and retaining the determination.

How to start in the first 30 days

Select a field tied to a recurring decision and agree its meaning, population and reporting boundary with the owner. Preserve sample source assertions, draft the comparison rule and leave tolerances as [approved tolerance]. Rehearse missing, late and mismatched records, then assign a correction and escalation path for each state. Close the initial exercise with the comparison, unresolved register and report version. Advance only after the authorized reviewers can explain the acceptance; the first-month sequence is planning guidance, not a guaranteed close schedule.

Distinguish disagreement from legitimate differences

Before opening a break, compare the field meaning, population, period and reporting purpose. Physical resident days and billed resident days can differ legitimately. Scheduled agency hours and approved invoice hours can also describe different stages of work. A difference becomes a reconciliation exception when records that should agree under the operator’s approved rule do not. Classify whether the cause is a definition mismatch, a timing delay, an identity mismatch or an incorrect assertion. That classification determines whether the next action belongs to the owner, the integration team, the identifier steward or the source-record custodian.

Build the comparison from preserved source assertions. Record the extraction time, the reporting cut-off, the source record identifiers and any filters applied. Match the period and entity keys before computing a variance. Leave thresholds and timing windows as [approved tolerance] and [approved cut-off] until the owner approves them. A missing record should remain visibly missing; replacing it with zero can turn a failed extraction into an apparently valid result. Retain the original competing values even when the final determination accepts one of them. The disagreement is part of the evidence, not a nuisance to delete.

Route a break through a defined resolution path

Use a synthetic census discrepancy to rehearse the process. The steward identifies the matching entity and period, checks the approved definition, and determines whether a late update explains the difference. If the source is wrong, the authorized source custodian makes the correction and the steward reads it back. If both assertions are valid for different purposes, retain both and label the reporting measure correctly. If no existing rule decides, escalate to the domain owner. Do not choose the largest value, the newest file or the most familiar vendor as an unstated authority rule.

Every closure should identify the resolution category, the accepted representation, the approving authority and the evidence used. Record whether the source was corrected or an authorized adjustment was retained separately. Not every source record should be overwritten: clinical, payroll and financial records may have protected correction procedures. Apply those procedures rather than forcing agreement through an informal edit. A break can also remain unresolved. In that case, mark the affected figure provisional and identify the decision it cannot yet support. Closing the ticket solely to meet a reporting deadline does not make the value governed.

Separate the close calendar from later adjustments

The close calendar should specify when source extracts arrive, comparisons run, exceptions are reviewed and the reporting period is accepted. Name a delegate for an absent approver and a route for late evidence. Preserve the report version accepted at close so a later adjustment does not silently change what the board or lender received. A revised report should identify the changed field, the reason, the approval and the version it supersedes. The operational target is a repeatable process with visible exceptions, not a promise that every period will contain no differences.

Review repeat breaks by root cause and field. Distinguish extraction failure from incomplete mapping, a recurring timing problem from an unresolved definition, and an unauthorized edit from an approved adjustment. Use that evidence to choose the next improvement. Test the process again with a missing record, a late record and an out-of-tolerance value; each should reach the correct state. Retain the comparison, the exception record, the closure and the accepted report reference. These checks demonstrate an operator’s own reconciliation process only when actually performed; educational examples do not establish production operation or measured outcomes for SeniorCRE.

Section 03

Working template

Exhibit 1. Break log fields
FieldPurpose
Field and periodWhat disagreed, and for which period
Systems comparedSystem of record and the system that differed
DifferenceSize of the break against the approved tolerance
Steward and due dateWho will resolve it, and by when
ResolutionSource fixed, valid difference documented, or escalated to owner

Source: SeniorCRE illustrative template.

Section 04

Common failure modes

  • Fixing the report, not the source. Adjusting the spreadsheet makes this month's report right and guarantees the same break next month.
  • No system of record. Without a named reference, every reconciliation becomes a negotiation between departments.
  • Re-reconciling downstream. When each report team reconciles again, figures diverge between reports. Reconcile once, upstream, and have reports read the governed result.
  • A clean comparison uses a mismatched period. Matching totals conceal different cut-offs. Fix: verify entity keys, population and period before comparing values; preserve the failed comparison, rerun with the approved boundary and retain the accepted version separately.

Section 05

Frequently asked questions

Section 06

Continue the playbook

Next step

Scope a governance program around the systems you run today.

Request a 30-Minute Assessment

SeniorCRE · Operator playbook · Guide 3 of 7 · Updated October 20, 2026

Stay up to date

The Senior Housing Journal, in your inbox

Perspectives on governed operating truth, capital and operating developments across senior housing & care, and platform updates from SeniorCRE.

By subscribing, you agree to receive the Senior Housing Journal newsletter. Unsubscribe at any time. See our Privacy Policy.