Charge capture

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

A charge sits between service evidence and a claim

Finni uses charge capture here as an editorial term for a version-controlled internal charge created from reviewed records. Systems may call all or part of it charge entry or service charge capture. A charge alone establishes neither coverage, authorization, claim acceptance, adjudication, nor payment.

Keep seven events separate:

The CMS electronic billing page collects Medicare claim, status, remittance, and payment resources. The broader CMS claim page defines electronic claim and encounter transactions. Neither defines internal charge capture.

The record should show where every field came from

A charge commonly identifies the client and funding path; service date; actual time or supported units; rendering and billing providers; place and modality; code and modifiers; diagnosis and authorization links; amount and rate version; source IDs; creator; time; status; and version. Exact fields vary.

Map each field to a source effective on the service date. The schedule shows intent; attendance and the authenticated clinical record show actual events. Authorization records a decision and parameters without establishing coverage or payment. Check provider and location enrollment or roster status for the payer, product, and service date. Use the current licensed code source, payer policy or guide, contract, and qualified reviewer for code and rate mapping.

The authorized author owns clinical content and amendments within scope. A qualified coding or billing reviewer maps supported facts. Assign and log authority to create, release, hold, or override charges. Software may compare fields and route conflicts; it must not rewrite clinical content.

The current BACB Ethics Code covers BCBAs, BCaBAs, and applicants for either certification. Standard 2.06 requires accurate service identification, required billing and reporting information, and timely correction and documentation of discovered inaccuracies. BACB has no separate organizational jurisdiction, so practices need controls for every role.

Build the workflow around release gates

A practical process has seven gates:

1. Define eligibility. Use mature delivered services; retain exclusions and unresolved records with reasons.
2. Confirm evidence. Reconcile client, date, actual time, setting, participants, provider, attendance, and clinical record.
3. Confirm prerequisites. Check payer, member, authorization, provider, location, modality, contract, service-date status, and filing deadline.
4. Create the charge. Apply current documented code and unit rules through the qualified role.
5. Run checks. Test required signatures, duplicates, overlaps, units, dates, provider, setting, authorization fit, and source consistency.
6. Release or hold. Record decision, approver, time, rule version, exception, owner, and due date.
7. Reconcile downstream. Link exact claim versions, acknowledgments, adjudication, remittance, payment, adjustments, and balances.

Trace both directions. Service-to-charge finds completed services with missing charges; charge-to-record finds unsupported charges. Claim-to-charge verifies that transmitted lines map to approved charges and that splits, combinations, or payer-specific transformations are authorized and documented.

The voluntary, nonbinding HHS OIG guidance supports auditing, monitoring, investigation, reporting, and correction. It approves no ABA service, code, unit, charge, or claim.

Corrections need a controlled path

Before transmission, use a versioned correction that preserves values, source, reason, user, approver, and time. Afterward, use the payer's corrected, replacement, or void process for wrong submitted data. Use reconsideration or appeal to dispute adjudication of accurate data. Link every action to the original charge and claim.

A documentation amendment stays under the authorized author's scope; billing staff cannot rewrite clinical facts. CMS's July 2025 Medicare guidance permits a record's author to attest to a missing signature on medical documentation other than an order, subject to limits, and forbids using attestation to backdate a plan of care. A signature log identifies an illegible signature. Neither supplies missing service facts. Apply this only to Medicare; follow applicable requirements elsewhere.

The CMS EFT and ERA page defines ERA as the payer's claim-payment explanation and EFT as the funds-transfer order. An ERA may report zero payment; one deposit may cover several claims. Charge capture ends before adjudication. End-to-end control continues through claim result, ledger disposition, and deposit when paid.

A fictional audit uses mature denominators

A fictional practice schedules 12 encounters: one cancellation, one no-show, and 10 delivered. At its one-day cutoff, eight have required evidence and pass other eligibility gates; two are overdue documentation holds. Documentation readiness is 8 of 10, or 80%.

Seven eligible encounters have charges. Completeness is 7 of 8, or 87.5%. Delivered-to-charge conversion is 7 of 10, or 70%, keeping documentation holds visible. The uncharged eligible encounter retains an owner and due date.

Reverse review finds six of seven charges supported. One used scheduled instead of actual time. First-pass supported-charge rate is 6 of 7, or 85.7%. The practice holds it, preserves the error, corrects it validly, and checks other exposed records.

Readiness finds mature services on hold; completeness finds missing eligible charges; supported-charge rate finds defects. None predicts payer acceptance, adjudication, or payment.

Measure completeness, support, and lag

Useful measures include:

• readiness and hold aging: documented mature services divided by mature delivered services, plus holds by reason and age
• charge completeness and missed value: timely charges divided by eligible services, plus supported value of missing charges
• supported-charge rate: charges passing every named source check divided by charges tested
• charge lag: time from the defined service or record-completion event to approved charge
• duplicate and recurrence rates: defects divided by records exposed to the same check and rule version
• downstream reconciliation: adjudicated lines linked to correct remittance, ledger disposition, and deposit when paid divided by lines due for posting

Define maturity, clock, exclusions, rule version, and tested fields. Segment meaningful cohorts when samples permit. Pair speed with accuracy, record integrity, client-balance safeguards, and audit results.