Is TargetFlo billing live?

Yes. Charge capture, the claim scrubber and review queue, 837P submission through Stedi, 277CA acknowledgments, claim status checks, corrections and voids, 835 ERA posting, manual and unmatched payments, the denials work queue, and the revenue view are all live.

Where do charges come from?

From the session itself. A therapist collects data on the scheduled session and submits it, then signs the session note. Signing is the billing gate: only then does TargetFlo capture a charge, with units computed from the actual session minutes using the payer's rounding rule.

Do we have to switch every payer at once?

No. Each payer starts in Shadow mode, where claims are built and scrubbed but never sent. Compare them with your current biller's output, then go live payer by payer when the numbers match.

Which codes can we bill?

97151–97158, 0362T, 0373T, and H0032, with credential modifiers (for example HM, HN, HO) and the telehealth modifier your payer expects. Rates and unit rounding are set per payer.

What happens when a session is voided after it was billed?

If the claim has not been sent, the line is removed and the claim is re-scrubbed. If it was already sent, the charge is flagged on the claim so your team can send a correction (frequency 7) or void (frequency 8).

Do we need a separate clearinghouse?

TargetFlo submits through Stedi and receives acknowledgments and ERAs from it. Payers that don't send ERAs can be paid with manual payments that post to the same claims and lines.

Only the billing roles your organization grants. Every claims screen and API checks access and records denied attempts in the audit log; tax IDs and payment details are encrypted.

Is TargetFlo billing live?

Yes. Charge capture, the claim scrubber and review queue, 837P submission through Stedi, 277CA acknowledgments, claim status checks, corrections and voids, 835 ERA posting, manual and unmatched payments, the denials work queue, and the revenue view are all live.

Where do charges come from?

From the session itself. A therapist collects data on the scheduled session and submits it, then signs the session note. Signing is the billing gate: only then does TargetFlo capture a charge, with units computed from the actual session minutes using the payer's rounding rule.

Do we have to switch every payer at once?

No. Each payer starts in Shadow mode, where claims are built and scrubbed but never sent. Compare them with your current biller's output, then go live payer by payer when the numbers match.

Which codes can we bill?

97151–97158, 0362T, 0373T, and H0032, with credential modifiers (for example HM, HN, HO) and the telehealth modifier your payer expects. Rates and unit rounding are set per payer.

What happens when a session is voided after it was billed?

If the claim has not been sent, the line is removed and the claim is re-scrubbed. If it was already sent, the charge is flagged on the claim so your team can send a correction (frequency 7) or void (frequency 8).

Do we need a separate clearinghouse?

TargetFlo submits through Stedi and receives acknowledgments and ERAs from it. Payers that don't send ERAs can be paid with manual payments that post to the same claims and lines.

Only the billing roles your organization grants. Every claims screen and API checks access and records denied attempts in the audit log; tax IDs and payment details are encrypted.

Billing & Claims

Live today

ABA billing that starts from the signed session note

Authorization → scheduled session → session data → signed note → claim → payment. Every claim line traces back to the session that earned it, and every denial points to the step that broke.

Book a Demo See data collection

What is TargetFlo Billing & Claims?

TargetFlo Billing & Claims is ABA billing and claims software built on the records your team already keeps in TargetFlo: the client's insurance and eligibility, the authorization lines, the scheduled session, the session data and signed note. Charges are captured when a note is signed, claims are checked before they leave, and payments post back to the line they pay.

The ABA revenue path

Five steps, one chain, no re-keying

The biller never types a session from a paper log. Each step is created by the one before it.

01
Authorization
Approved units per CPT code
02
Scheduled session
Calendar event drawing on the authorization
03
Session data
Collected on a tablet, submitted
04
Signed note
The billing gate
05
Claim & payment
837P out, 277CA and 835 back

Capabilities

Everything between the signed note and the deposit

All live in the product today.

Billing settings & payer rules

Billing NPI, taxonomy, and EIN once per organization. Per payer: contracted rate per code, unit rounding (CMS 8-minute, exact 15, or round down), credential modifiers, telehealth modifier, place of service, and timely filing.

Charge capture from signed notes

A session becomes a charge only after its note is signed. Units, rate, modifiers, place of service, authorization, and supervising provider are filled in automatically.

Held charges with reasons

No insurance, no authorization, authorization used up, missing NPI, rate, or diagnosis, past timely filing — each charge says why it is held. Fix the source and recheck, or release with a note.

Claim scrubber & review queue

Charges group into claims weekly or per session. Every claim is checked before it can be approved: errors block, warnings need acknowledgment, duplicates are caught.

837P submission through Stedi

Approved claims go out as 837P. 277CA acknowledgments come back and mark each claim accepted or rejected; status checks follow up on the quiet ones.

835 ERA payment posting

Remittances post to the right claim and line with CARC/RARC adjustments. Anything that doesn't match lands in an Unmatched queue; payers without ERA get manual payments.

Denials work queue

Every denial becomes a work item with category, amount, assignee, and due date. Correct (7), void (8), resubmit, appeal, or write off — the chain stays linked.

Revenue view

Billed vs collected by month, days in AR, AR aging by payer, held charges by reason, and denial trends — with monthly collections split Medicaid vs commercial.

Shadow mode before go-live

Run each payer in Shadow first: claims build and scrub but nothing is sent. Upload your current biller's CSV to compare line by line, then go live per payer.

Trace every claim

Live today

A claim you can explain line by line

Open any claim and walk back through it: the payment, the acknowledgment, the charge with its units and modifiers, the signed note, the session data, the calendar event, and the authorization line it drew from.

Units come from actual session minutes with the payer's rounding rule
Authorization utilization is checked when the charge is captured
Claim events record every scrub, approval, send, acknowledgment, and payment
Corrections and voids stay linked to the original claim

Read the authorization-to-claim workflow

app.targetflo.com · Claim · Lucas H. · NC Medicaid

1
Authorization
97153 · 240 units · through 06/30
2
Scheduled session
Wed · 3:00–6:00 PM · RBT S.C.
3
Session data
7 targets · 46 entries · submitted
4
Signed note
Signed 6:42 PM · billing ready
5
Charge
97153 HM × 12 units · $180.00
6
Claim
Accepted (277CA) · ERA posted $180.00

Paid — every step traceable164 units left

Held charges

A held charge tells you what to fix

Charges that can't be billed yet wait with a reason. Fix the source and recheck — or, for reasons that allow it, release with a note.

Common held-charge reasons and the fix
Reason	Fix
No primary insurance	Add or date the client's insurance
No authorization / used up	Record the authorization line or its extension
Rendering NPI missing	Add the provider's NPI in Workforce
Missing diagnosis	Add a primary ICD-10 code on the client
Missing rate	Set the contracted rate on the payer rule
Appointment not completed	Complete the calendar event
Past timely filing	Review before releasing

Revenue

Live today

Billed vs collected, AR aging, and denials in one view

Owners and billing leads see the month's billed and collected totals, what payers still owe and for how long, which charges are held and why, and where denials cluster.

Billed vs collected by month, with a monthly collections rollup
Days in AR and AR aging buckets by payer
Held charges by reason, so the biggest fix comes first
Denials by category with assignees and due dates

app.targetflo.com · Revenue · last 4 months

Jul

Aug

Sep

Oct

Days in AR

Owed by payers

$38.7k

Held charges

Codes

ABA codes TargetFlo bills (97151–97158, 0362T, 0373T, H0032)

Each code carries a typical rendering provider. Scheduling uses it to check credentials; billing applies the matching modifier and the payer's rate.

ABA CPT codes in TargetFlo with typical rendering provider
CPT code	Service	Typical provider
97151	Behavior Identification Assessment	BCBA
97152	Supporting Assessment	RBT
97153	Direct ABA Therapy (by protocol)	RBT
97154	Group ABA (technician)	RBT
97155	Protocol Modification / Supervision	BCBA
97156	Family / Caregiver Guidance	BCBA
97157	Multiple-Family Group Guidance	BCBA
97158	Group ABA (BCBA-led)	BCBA
0362T	Supporting Assessment — Severe Destructive Behavior (multi-technician)	RBTs, BCBA on site
0373T	Treatment — Severe Destructive Behavior (multi-technician)	RBTs, BCBA on site
H0032	BIP/POC Development (NC Medicaid)	BCBA

Rates and unit rules vary by payer and state; TargetFlo stores them per payer and code. Read the ABA CPT codes guide.

Start in Shadow, go live per payer

Shadow builds and scrubs real claims without sending them. Upload your current biller's export to see matches and differences by date, client, code, units, and charge. When a payer matches, switch it live.

Billing data stays in the billing team

Claims screens are limited to the roles you choose. Tax IDs and payment details are encrypted, and every access — including denied attempts — is in the audit log.

FAQ

Billing & claims FAQs

How charges, claims, payments, and denials work in TargetFlo.

Related features

Data Collection & Session NotesTablet data collection, target graphs, and signed session notes.Live Scheduling & AuthorizationsTeam and client calendar that draws on authorized units per CPT code.Live Insurance & EligibilityReal-time 270/271 eligibility checks and payer context.Live ABA CPT Codes Guide97151–97158 and H0032 explained for ABA billing and authorization teams.Plan of Care & BIPGoals, behavior plans, caregiver training, NC CCP 8F checklist alignment.Live Intake & Referrals9-stage referral intake pipeline with checklists and leads.Live

See a session become a paid claim

Book a demo. We walk one session from the calendar to the signed note, the claim, the acknowledgment, and the posted payment.

ABA CPT codes guide

ABA billing that starts from the signed session note

What is TargetFlo Billing & Claims?

Five steps, one chain, no re-keying

Authorization

Scheduled session

Session data

Signed note

Claim & payment

Everything between the signed note and the deposit

Billing settings & payer rules

Charge capture from signed notes

Held charges with reasons

Claim scrubber & review queue

837P submission through Stedi

835 ERA payment posting

Denials work queue

Revenue view

Shadow mode before go-live

A claim you can explain line by line

A held charge tells you what to fix

Billed vs collected, AR aging, and denials in one view

ABA codes TargetFlo bills (97151–97158, 0362T, 0373T, H0032)

Start in Shadow, go live per payer

Billing data stays in the billing team

Billing & claims FAQs

Is TargetFlo billing live?

Where do charges come from?

Do we have to switch every payer at once?

Which codes can we bill?

What happens when a session is voided after it was billed?

Do we need a separate clearinghouse?

Who can see billing?

Related features

See a session become a paid claim