Revenue cycle
Ninety-five lines, one pass.
Read the ERA, match the lines to the claims, post the payments and adjustments, and route what didn't match to the denials queue. A week of manual posting becomes a coffee break.
835 and paper EOBs. Scanned remittances are read and matched too.
One posting run
Ninety-five lines in, four exceptions out.
The file arrives, the lines match against the original claims, the payments and contractual adjustments post, and only what genuinely needs a person reaches one.
Lines in the 835 file, imported automatically from the clearinghouse.
Matched to the original claim on claim number, patient, date of service, and amount.
Denials and partial payments routed straight into the denials work queue.
Payments and contractual adjustments applied, patient responsibility calculated.
Manual posting
What this used to be
- Open the remittance in a clearinghouse portal
- Find each claim in the billing system
- Type the payment, the adjustment, and the patient portion
- Note the denials somewhere else to work later
- Roughly a week per month of one person's time
One pass
What it is now
- The 835 imports itself
- Line-level matching against the original claim
- Adjustments and patient responsibility calculated
- Exceptions land in a queue with the reason attached
- A review, not a re-entry
Paper too
Not every payer sends an 835.
Smaller plans and some state programs still mail an explanation of benefits. Scan it and the same matching engine reads it, so the paper payers do not become the ones nobody posts until quarter end.
Partial payments
The dangerous remittance is the one that pays eighty percent and looks fine.
A claim paid below the contracted rate posts as a paid claim in most systems. Matching each line against the contract is what turns a quiet underpayment into a visible variance you can appeal.
Questions
Common questions.
How does automated ERA / 835 posting work?
The 835 imports itself from the clearinghouse, each line matches the original claim on claim number, patient, date of service and amount, payments and contractual adjustments post, and patient responsibility is calculated. In the reference run, 95 lines import and only 4 exceptions reach a person — a review, not a re-entry.
Can it post paper EOBs, not just electronic remittances?
Yes. Smaller plans and some state programs still mail an explanation of benefits — scan it and the same matching engine reads it, so the paper payers don’t become the ones nobody posts until quarter end.
What happens to denials and underpayments during posting?
They’re the exceptions: denials and partial payments route straight into the denials work queue with the reason attached. Because each line is matched against the contract, an 80%-of-rate underpayment that posts as "paid" elsewhere shows here as a visible variance you can appeal.
Works with
It runs on the same record as the rest of the platform.
Revenue cycle
Denials work queue
Every denial and underpayment lands in a queue with the reason, the dollar amount, the deadline, and the person responsible.
Read more →Revenue cycle
Claim scrubbing
Validation runs before the claim leaves, highlights the exact field that will get it kicked back, and says why in plain language — not a rejection code you have to look up.
Read more →Revenue cycle
Patient balances & pay links
Balances calculated from the remittance, statements the patient can actually read, and a payment link that works from a phone — plus payment plans for the balances that need one.
Read more →Get started
Start today, or take a look first.
Create your workspace in minutes and try the whole platform free for 14 days — no credit card. Or book a one-hour walkthrough first.