For billing teams
Work exceptions, not spreadsheets

Held charges, scrub results, denials and unmatched payments queue up with reasons, so billers work the exceptions.
What do ABA billers need from software?
Billers need to know why a charge is held, which claims need attention and what the payer said. TargetFlo billing turns each into a queue with a reason. See why ABA charges get held and claims history import.
What you get
A biller's queues
Held charges
With reasons and rechecks.
Scrub results
Errors and warnings in a review queue.
Sent and acknowledged
837P and 277CA status.
Payments
835 posting with exceptions.
Denials
A worklist with actions.
Revenue
Billed, collected and AR aging.
How it works
A biller's day
- 01
Release holds
Fix and recheck.
- 02
Approve claims
Clear the review queue.
- 03
Post payments
Handle unmatched.
- 04
Work denials
Correct, appeal or write off.
FAQ
ABA Software for Billing Teams: frequently asked questions
Related features
ABA Billing SoftwareThe charge comes from the note, the scrubber checks the claim, the payment posts itself, and every denial becomes a work item.ABA Denial ManagementEach denied claim lands in a worklist with its reason, an owner and the next action, instead of sitting in a payer portal.ABA ERA Payment PostingThe 835 arrives, matches the claim, and posts with adjustments. What it cannot match is queued for a person.ABA Claim ScrubberEighteen checks run on every claim. Errors block, warnings need an acknowledgment, and a person approves what is sent.ABA Revenue DashboardBilled against collected, days in AR, aging by payer and the charges being held, in one view built from your own claims.