IREMIT · Remittance visibility
See your deposits before they land.
Matching a remittance to a deposit takes two halves, and the bank detail is often the harder half to get. IREMIT starts with what you already have: your 835 files.
Payer A · expected Tue$ illustrative
Payer B · expected Wed$ illustrative
Payer C · expected Thu$ illustrative
Denials by reasonGrouped
Cash outlookExportable
Illustrative

Today
Half of reconciliation is the half you don't have.
The 835You already receive it
The bank detailOften the harder half to get
Waiting and searchingWhere is the deposit?
With IREMIT
The deposit date is already in the 835.
1
835 files inThe files you already receive.2
Parsed and validatedEvery file, as it arrives.3
Deposit dates surfacedThe date the payer wrote into each file.4
Reporting outKnow when each payment should land. No bank file needed.What you get
More than dates, from the same files.
Expected deposits, by payer and by day
Payments, adjustments and patient responsibility
Denials grouped by reason, so repeat causes surface
A forward view of cash you can export
Fits what you haveNeeds only the 835s you already receive. When you are ready to match against the bank, IERA picks up from there.
What is actually in the file
One month of 835 activity, fully accounted for.
Every remittance file already carries this breakdown. Most teams never see it, because nothing reads it back to them.
Paid as contracted68%
Contractual adjustments21%
Denied7%
Patient responsibility3.2%
Recoupments and offsets0.8%
A single remittance
Where did the other $1,250 go?
An 835 reports $48,000 in payments and a net payment of $46,750. IREMIT reads the adjustment detail in the file and names the difference.
$46,750Net payment, per the 835
$1,250
$785Prior overpayment recovery
$465Forwarding balance
Illustrative figures. The actual mix varies by payer, specialty and contract.
ONE-PAGERAdd what you need next
See it run on your own files.
A short conversation is all it takes to find out where IntelEDI fits.





