Reconcile ABA Accounts Receivable to the General Ledger

Define Farah's accounts-receivable-to-general-ledger reconciliation control

Farah treats reconciliation as a set of bridges rather than one total. Payer receivables, client receivables, unapplied cash, credits, refunds, recoveries, and contractual adjustments each retain their own population and accounting destination.

Build the AR control-account reconciliation

Record period and cutoff; source-system snapshot; entity; location; payer or client; claim and line; service date; posting date; beginning balance; charge; contractual adjustment; other adjustment; payment; deposit; refund; recoupment; transfer; ending balance; general-ledger account; variance; owner; evidence; and certification. Structured fields preserve identity, source, version, authority, state, clock, calculation, money movement, action, hold, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, accessibility, family communication, legal deferral, and each accountable owner's rationale.

Run Farah's workflow

Farah freezes extracts, proves each subledger rollforward, maps approved transaction classes to ledger accounts, and compares both directions. Billing resolves claim meaning, treasury resolves bank evidence, accounting owns ledger treatment, and clinical staff answer only attributable record questions.

Assign each decision to its proper authority

A balanced general ledger can coexist with a wrong client balance or unsupported claim. A clean claim subledger can still differ from cash or accounting because of timing, mapping, duplicate postings, or an unresolved credit.

Work through Farah's fictional example

Farah locks a fictional month with a 410,000 dollar beginning receivable, 290,000 dollars of charges, 96,000 dollars of contractual adjustments, 214,000 dollars of payments, 8,000 dollars of other approved adjustments, 3,000 dollars of refunds, and 385,000 dollars ending receivable. The rollforward is 410,000 + 290,000 - 96,000 - 214,000 - 8,000 + 3,000 = 385,000. One 1,200 dollar mapping difference remains inside the balanced total and stays open. This synthetic scenario tests control logic and arithmetic only. It creates no coding, coverage, authorization, payment, client-balance, refund, reserve, accounting, disclosure, contract, or legal conclusion for a real person, provider, payer, claim, or entity.

Calculate Farah's measures

Population completeness is 8 of 8 source registers. Rollforward balance is a dollar equality, while item reconciliation is 127 of 128 mapped entries, or 99.2%. Report both because a net zero variance can conceal offsetting errors.

Address the main accounts-receivable-to-general-ledger reconciliation risk

Netting payer and client balances, or posting unsupported plug entries, can make totals agree while preserving the wrong obligation. A later refund or recoupment then exposes the hidden mismatch.

Test the AR control-account reconciliation against exceptions

Farah tests late ERA, split EFT, client payment, returned refund, payer recoupment, corrected claim, duplicate posting, transfer between entities, prior-period adjustment, and offsetting errors. Every fixture retains the source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, quarantined, pending, excluded, and held items remain in the predeclared cohort.

Document the stop condition

Withhold certification when a population, control account, material bridge, mapping, approval, or ownership record is missing. Preserve the prior certified snapshot while the exception is investigated.

Hand off open work with evidence

Farah sends finance the signed rollforwards and billing the item-level exceptions. Every item includes the source system, identifiers, amount, dates, prohibited shortcut, accountable owner, and expected evidence of closure.

Communicate the current state accurately

Leadership sees gross and net receivable, cash, credits, refunds, open variances, and aging by meaningful class. Families receive only verified account information through the approved channel.

Verify Farah's acceptance evidence

An independent reviewer recreates the arithmetic from locked extracts, samples each bridge to source evidence, and confirms that every manual journal entry has authority and a reversible link to detail.

Maintain Farah's control over time

Farah version-controls mappings and cutoff rules. New payer routes, locations, accounts, products, integrations, and adjustment types require boundary fixtures before the next close.

Monitor Farah's operational results

Trend close lag, unmatched entries, manual journals, postclose corrections, credit age, recoupment age, and unexplained variance by source version. Investigate improving totals alongside rising manual work because the mix can signal hidden reconciliation effort.

Make the AR control-account reconciliation implementation-ready

Build separate control totals for record count, unique claim count, service-line count, and dollars. A file can balance in dollars while losing rows. Hash or otherwise identify each locked extract, record its generated time and filters, and retain the mapping version used for the close. When a prior-period correction arrives, post it through the approved accounting route and link it back to the original claim history rather than rewriting the certified package.

Run Farah's independent review

Farah assigns a reviewer who did not build the AR control-account reconciliation. The reviewer reconstructs the accounts-receivable-to-general-ledger reconciliation source, state, calculation, money movement, action, and close. Earlier versions, failed tests, unknowns, credits, exclusions, pending items, and holds remain available. Missing authority, unexplained amounts, overwritten history, concealed exceptions, or unsupported action fail review.

Anchor claim transactions to the adopted standard

Current 45 CFR 162.1102 identifies the adopted professional-claim standard. Farah preserves the relevant claim identities and versions throughout the AR control-account reconciliation. Internal financial, migration, or ownership labels never replace the actual transaction and source evidence.

Separate claim processing, remittance, and money

The CMS electronic-claims page illustrates front-end Medicare claim processing, while the CMS remittance page separates claim, line, adjustment, and payment information. Farah uses those examples within their scope and verifies every payer's current route before deciding accounts-receivable-to-general-ledger reconciliation.

Use published rates within their stated scope

The CMS PFS overview says its tool provides Medicare payment information and directs users to the MAC for official definitive files. The 2026 national payment file page provides versioned Medicare files. Farah does not treat either source as a commercial contract, accounting rule, or universal ABA rate.

Classify credit recipients before financial action

The CMS-838 instructions define a Medicare credit-balance reporting mechanism and distinguish amounts due to Medicare, another insurer, or a patient. Farah carries that classification discipline into the AR control-account reconciliation while verifying the actual program, contract, entity, state, recipient, and accounting duties.

Escalate potential overpayments through current authority

Current 42 CFR 401.305 governs specified Medicare overpayments and includes identification, investigation, deadline, reporting, and lookback provisions. Farah keeps that Medicare scope visible and routes other payer, client, credit, refund, and accounting conclusions through their own controlling sources.

Interpret adjustment codes with complete context

The X12 external-code-list index defines code-list scopes. Farah reads group codes, CARCs, RARCs, provider adjustments, payer messages, claim history, and payment evidence together before assigning a financial or operational meaning in the AR control-account reconciliation.

Protect payment and account information

HHS payment guidance and minimum-necessary guidance apply when their HIPAA conditions are met. Farah limits access and disclosure to approved purposes and recipients while preserving the evidence needed for accounts-receivable-to-general-ledger reconciliation.

Keep professional and compliance authority visible

The CASP public summary and BACB Ethics Code retain their stated scopes. The voluntary OIG GCPG supplies a compliance framework rather than a payer, contract, coding, or accounting rule. Farah routes clinical, billing, payer, finance, privacy, compliance, and legal decisions to qualified owners.

Related resources

• Build an ABA Contract Variance Reserve Without Hiding Claim Work.
• Build an ABA Billing Control Ownership Matrix.
• Investigate Unapplied ABA Payer Cash.
• Reconcile Legacy ABA Claims After a Payer Product Migration.

Sources

• Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
• Electronic Code of Federal Regulations, 45 CFR 162.1102, standard for health care claims.
• Centers for Medicare and Medicaid Services, Electronic Health Care Claims.
• Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
• Centers for Medicare and Medicaid Services, Physician Fee Schedule Look-up Tool Overview.
• Centers for Medicare and Medicaid Services, Physician Fee Schedule National Payment Amount File.
• Centers for Medicare and Medicaid Services, Medicare Credit Balance Report, Form CMS-838 instructions.
• Electronic Code of Federal Regulations, 42 CFR 401.305, reporting and returning overpayments.
• X12, External Code Lists.
• U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
• U.S. Department of Health and Human Services, Minimum Necessary Requirement.
• U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.