To reconcile payer split or consolidated ABA remittance lines, start from the original submitted claim lines and map every adjudicated line by service, date, code, modifiers, units, charge, payer identifier, and adjustment. Preserve payer-created splits, consolidations, bundled results, and zero-charge lines as remittance evidence. Recalculate totals without inventing service units, duplicating adjustments, or rewriting the source record.
Define Keiko's payer-split or consolidated line reconciliation control
Keiko's crosswalk permits one submitted line to map to several adjudicated lines and several submitted lines to map to a consolidated payer result. Each relationship records its basis and financial allocation. A transformed line remains a payer representation rather than a new clinical service.
Build the submitted-to-adjudicated line crosswalk
Record claim and version; submitted line; service date; provider; code; modifiers; units; charge; payer claim and line ID; adjudicated line; split, consolidated, bundled, or zero-charge state; allowed, paid, and adjusted amounts; group code; CARC; RARC; mapping basis; remainder; patient balance; reviewer; exception; and close. Structured fields preserve identity, source, transaction level, version, clock, comparison, access, action, hold, calculation, correction, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, family communication, privacy, legal deferral, and the responsible owner's rationale.
Run Keiko's workflow
Keiko locks the outbound lines, imports the raw remittance, and builds a many-to-many map. She balances charges, payments, and adjustments at claim level while preserving line detail. Unsupported transformations receive payer inquiry; system workarounds cannot manufacture a source line.
Assign decisions to qualified owners
A payer line transformation can affect payment representation without changing the care delivered. It cannot authorize new units or clinical documentation. A zero-charge payer line can carry financial meaning and should not be discarded solely because its charge field is zero.
Work through Keiko's fictional example
Keiko reviews 18 fictional claims with 41 submitted and 47 adjudicated lines. Twelve claims map exactly. Two have payer splits, one is consolidated, one has a zero-charge line, one duplicates an adjustment, and one cannot reconcile units. Five claims resolve and one remains held. Across the 47 adjudicated lines, 45 have supported mappings or line-level dispositions; two lines inside the held claim remain open. This synthetic cohort tests control logic and arithmetic only. It creates no coding, coverage, authorization, payment, patient-balance, disclosure, privacy, accounting, recovery, or legal conclusion for a real person, provider, plan, claim, remittance, or deposit.
Calculate Keiko's measures
Initial claim mapping is 12 of 18 claims, or 66.7%. Forty-five of 47 adjudicated lines have supported mappings or line-level dispositions, or 95.7%; two remain open. Claims, submitted lines, adjudicated lines, units, adjustments, and dollars remain distinct.
Address the main payer-split or consolidated line reconciliation risk
Posting payer-created lines as new services can inflate utilization or duplicate patient balances. Collapsing all adjudicated lines into one result can hide the reason a particular service was reduced or denied.
Test the submitted-to-adjudicated line crosswalk against exceptions
Keiko tests one-to-many split, many-to-one consolidation, bundled result, zero-charge line, negative adjustment, changed identifier, duplicate line, unit mismatch, and corrected ERA. Each fixture retains source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, quarantined, and held items remain in the predeclared cohort.
Document the stop condition
Hold posting when submitted and adjudicated line relationships, totals, units, or adjustment ownership cannot be reproduced. Preserve raw files and request payer clarification where needed.
Hand off open work with evidence
Keiko's handoff includes outbound lines, payer lines, mapping edges, financial allocation, remainder, patient-balance effect, exception, and owner. The receiver rebuilds one transformed claim from raw evidence.
Verify Keiko's release evidence
Before release, Keiko proves that every submitted and adjudicated line appears exactly once in the crosswalk or has a documented exclusion. Claim totals balance independently from unit counts, which prevents financial reconciliation from masking a service-line defect.
Maintain Keiko's control over time
Keiko maintains a fixture library for each payer transformation pattern and parser version. Monthly review samples split, consolidated, zero-charge, and corrected remittances, compares mappings with original claims, ages unresolved remainders, and verifies that patient statements and utilization reports use the supported line interpretation rather than the payer display alone. She records the tested payer route.
Run Keiko's independent review
Keiko assigns a reviewer who did not build the submitted-to-adjudicated line crosswalk. The reviewer reconstructs the payer-split or consolidated line reconciliation source, state, calculation, action, and close from retained evidence. Earlier versions, failed tests, unknowns, and holds remain available. Hidden exceptions, unexplained values, overwritten history, missing population, or unauthorized decisions fail review.
Anchor claim identity to the adopted standard
Current 45 CFR 162.1102 identifies the adopted professional-claim standard. The CMS claims-status page identifies the 276 request and 277 response. Keiko records payer, product, route, transaction version, sender, receiver, and artifact before using either source in the submitted-to-adjudicated line crosswalk.
Read remittance levels before taking action
The CMS Medicare remittance page separates claim, service-line, and provider-level adjustments and explains group codes, CARCs, RARCs, PLB, and payment in Medicare scope. Keiko keeps those levels distinct and verifies the non-Medicare payer's current instructions before applying the payer-split or consolidated line reconciliation workflow.
Use current code lists and effective dates
The X12 external-code-list index defines adjustment, remark, status, and provider-adjustment list scopes. Its code-update page shows the July 1, 2026 release and August 3 correction to a RARC effective date. Keiko stores code status and source-check time rather than overwriting historical remittance meaning.
Interpret corrected identity in transaction context
X12 RFI 2227 explains corrected patient or insured reporting in a specific 835 scenario and preserves the distinction between submitted patient and insured information. Keiko uses that interpretation for the transaction field while independent identity, coverage, privacy, and master-record sources govern their own decisions.
Preserve payer line transformation evidence
X12 RFI 2165 addresses a payer line-splitting example and shows why line representation and financial balancing need exact evidence. Keiko retains original and adjudicated lines, amounts, identifiers, and mapping instead of generalizing that one scenario into a universal payer-split or consolidated line reconciliation rule.
Scope member-payment and reassociation fields
X12 RFI 2600 explains that TRN02 supports payer-to-payee reassociation and need not carry the number of a separate payment sent to a member. X12 RFI 2075 describes the one-payment-to-one-835 relationship with a nonpayment exception. Keiko verifies the actual payee and money movement separately.
Keep transaction-set receipt narrow
X12 RFI 2099 says 999 acceptance does not necessarily establish carrier receipt date. Keiko distinguishes interchange, transaction set, clearinghouse claim, payer claim, adjudication, remittance, and payment evidence when resolving payer-split or consolidated line reconciliation.
Protect payment data and qualified authority
HHS payment guidance and minimum-necessary guidance apply only when their HIPAA conditions are met. The CASP public summary, BACB Ethics Code, and voluntary OIG GCPG retain their limited scopes. Keiko keeps clinical, payer, privacy, accounting, and legal decisions with qualified owners.
Related resources
- Separate Informational ABA RARCs From Adjustment Actions.
- Review Corrected Patient or Insured Data on an ABA Remittance.
- Roll Out ABA CARC and RARC Code-List Updates Safely.
- Handle Payer-Initiated ABA Claim Reprocessing.
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, Health Care Claims Status.
- Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
- X12, External Code Lists.
- X12, Code Updates Listing.
- X12, RFI 2227, Use of NM1 74 on X12 835.
- X12, RFI 2165, Line Splitting Versus Unbundling.
- X12, RFI 2600, Payment Made to Patient and TRN02.
- X12, RFI 2099, 999 Confirming Claim Receipt.
- X12, RFI 2075, 835 Relationship to Payment.
- 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.