Validate an ABA Payer Payment Reported to the Member

Define Olivia's payer payment reported to the member control

Olivia's record separates payer adjudication, payment to the provider, payment reported to the member, and patient responsibility. It preserves what the 835 communicates and what must come from a payer, member, contract, or bank source. Collection and claim follow-up wait for verified authority.

Build the member-payment verification record

Record payer and product; person and member; provider and payee; claim and line; service date; ERA; patient-paid amount; responsibility; BPR and TRN; provider payment; member-payment indicator; payer explanation; member receipt evidence; assignment or contract treatment; provider balance; secondary coverage; communication; owner; dispute; hold; and closure. 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 Olivia's workflow

Olivia matches the remittance to the claim, determines the named payee, and reviews the patient-paid or responsibility fields in context. She checks contract and payer instructions, then uses a respectful, authorized communication path if member confirmation is needed. Posting and collection decisions follow the verified result.

Assign decisions to qualified owners

TRN02 identifies the payer-to-payee remittance relationship and is not necessarily the number on a payment sent separately to a member. A patient-paid indicator does not by itself prove receipt, authorize collection, or establish a provider's contract rights.

Work through Olivia's fictional example

Olivia reviews 16 fictional claim episodes. Ten show provider payment, three report payment to the member, one shows patient responsibility without payment, one has a mismatched payee, and one is unclear. Thirteen have complete claim, remittance, contract, and payment evidence. Two repair. One remains held. 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 Olivia's measures

Initial verification is 13 of 16 episodes, or 81.3%. Fifteen reach verified provider, member, responsibility, or final hold status, or 93.8%. Members, payees, claims, payments, indicators, and balances remain separate units.

Address the main payer payment reported to the member risk

Treating a member-payment indicator as confirmed cash can trigger inappropriate collection. Treating it as provider payment can overstate deposits and close the claim incorrectly.

Test the member-payment verification record against exceptions

Olivia tests provider paid, member paid, patient responsibility, no payment, wrong payee, secondary coverage, disputed receipt, assignment difference, duplicate payment, and remittance correction. 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 collection, posting, statement, or close when payee, payment, contract treatment, or member balance is unclear. Avoid requesting sensitive financial evidence beyond the purpose and authorized route.

Hand off open work with evidence

Olivia's handoff includes the claim, remittance, payee, payment indicators, contract source, member communication, balance, open question, owner, and deadline. The receiver confirms actual money movement separately from adjudication.

Verify Olivia's release evidence

The final record states which source supports adjudication, which supports receipt, and which supports the remaining balance. Olivia documents any unresolved member report without treating it as dishonesty or as proof that the payer record is complete.

Maintain Olivia's control over time

Olivia reviews member-payment episodes after payer, contract, assignment, statement, or COB changes. She samples communication for clarity and privacy, verifies that provider receipts and member reports remain separately sourced, and checks later remittances for corrections. Recurring member-payment patterns receive a payer-specific workflow and family-facing explanation.

Run Olivia's independent review

Olivia assigns a reviewer who did not build the member-payment verification record. The reviewer reconstructs the payer payment reported to the member 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. Olivia records payer, product, route, transaction version, sender, receiver, and artifact before using either source in the member-payment verification record.

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. Olivia keeps those levels distinct and verifies the non-Medicare payer's current instructions before applying the payer payment reported to the member 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. Olivia 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. Olivia 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. Olivia retains original and adjudicated lines, amounts, identifiers, and mapping instead of generalizing that one scenario into a universal payer payment reported to the member 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. Olivia 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. Olivia distinguishes interchange, transaction set, clearinghouse claim, payer claim, adjudication, remittance, and payment evidence when resolving payer payment reported to the member.

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. Olivia keeps clinical, payer, privacy, accounting, and legal decisions with qualified owners.

Related resources

• Reconcile Negative ABA Remittance and Posting Amounts.
• Resolve Conflicting ABA Claim Status and Remittance Evidence.
• Allocate an ABA Multi-Claim Remittance Payment Reproducibly.
• Roll Out ABA CARC and RARC Code-List Updates Safely.

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.