ABA billing software that bills what the auth allows

Why ABA billing is not general medical billing

Most billing software assumes a visit: one encounter, one or two codes, a claim. ABA does not work that way. A single client generates several sessions a week against a grant of 15-minute units, delivered by staff at different credential tiers, under a payer that may or may not permit a supervisor to bill concurrently with the technician they are observing.

That produces three failure modes a general system does not even model. Units that exceed what was authorized. A modifier that matches the person who delivered the service but not the tier that payer recognises. A rendering NPI reported for a technician-delivered session where the payer wanted the supervising provider.

Each one is a clean denial, and each one is only visible after submission.

Units come from the session, not from a form

The charge is computed from the session record — the code, the delivering staff member’s credential, the start and stop times already captured for the note — rather than entered separately by whoever does billing.

That is a small architectural decision with a large audit consequence: the units on the export and the minutes in the documentation cannot disagree, because there is only one number. When a payer asks for the record behind a billed unit, the record is the thing the unit was derived from.

Because the same session record also decrements the authorization balance, the burn-down on the parent page and the charge on the export are two views of one fact rather than two systems that must be reconciled monthly.

Payer rules are settings, not assumptions

Each payer record carries its own answers: which credential-tier modifiers apply, whether the rendering or the supervising provider is reported on a technician-delivered session, whether concurrent supervision billing is permitted alongside direct service, which places of service are accepted, and how rates resolve per code and modifier.

None of it is hard-coded, because a system that encodes one payer’s rules as universal generates denials for every other payer quietly and at scale. No table of “what payer X allows” is published here either — those policies change, and each agency confirms them against its own contracts. What the software does is make a confirmed rule into a setting rather than knowledge held by one biller.

What your biller receives

A per-session export carrying codes, units, modifiers, diagnosis pointers and the NPI resolved under that payer’s rule — in the format your biller asks for, not a format they have to convert.

Claims are not transmitted to payers from here, and that is a deliberate scope decision rather than a missing feature. Agencies that already submit electronically should read it as the gap it is. Agencies that keep a biller — most of this market — get the part that was actually slow: the assembly of clean charge data. A biller’s seat costs nothing, so they can work in the system rather than from emailed spreadsheets.

Superbill and CMS-1500 PDF output follows completion of AMA CPT licensing.

Where these fields land on the actual claim is covered box by box in the CMS-1500 field guide — Box 23 for the authorization, Box 24J for the rendering provider, Box 33 for who gets paid. For the authorization side, the authorization tracker is the spreadsheet this replaces.