The 835 file nobody wants to open — parsed into readable EOB output and organized for review.
Remit Forge reads ANSI X12 835 remittance files, creates readable EOB output, and uses the configured doctor identity to propose the output path. The operator reviews the run summary and any exceptions before the files become downstream work. On our own billing floor it runs every remit, every week.
The jobs Remit Forge removes
- Reading raw 835s — deciphering segment-by-segment remit files by eye, or paying a portal to do it slowly
- Rebuilding EOBs by hand — retyping remit data into something a poster or follow-up person can actually work from
- Sorting and filing — figuring out which practice belongs to which doctor and dragging documents into the right folders
- Remit spreadsheet wrangling — the parallel spreadsheet someone maintains just to know what arrived and what got processed
Built to run remits all day, not to demo well.
835 → finished EOB documents
Each remit file is parsed and rendered as a payer-style, fixed-width EOB document — the familiar printed-report layout your posters and follow-up team already know how to read.
Batch queue with resume
Add individual 835 or ZIP files, or refresh to pull in everything waiting in your company’s 835 intake folder. Click Convert / Resume and let it work — the queue picks up exactly where it left off, even across sessions.
Automatic doctor routing
Finished EOB documents file themselves into the right doctor’s folder from your routing table — one row per doctor, their 835 folder and their EOB output folder.
Teach-once practice aliases
When a practice name isn’t recognized, an Unmatched window asks you once. Your answer becomes an alias, and that practice routes itself on every future run.
Mapping Review lane
Anything that still needs a human decision waits safely in a review queue — work through pending mappings on your schedule, then convert again. Nothing is ever silently dropped.
Company-wide routing sync
Admins publish doctor paths, practice mappings, and aliases to the whole company, and can push or pull the tables against the company workbook — every workstation stays in step.
Run totals & reports
Every run ends with the count of 835 files processed and EOB documents saved. Admin Reports & Analytics keep run history, volumes, and your own team’s measured time numbers.
Local conversion engine
The conversion itself runs entirely on your computer — no network calls, no APIs, no remit data sent anywhere. Company sync carries settings, never your 835 files.
Five-minute team installs
A first-run wizard walks each workstation through setup. Team members sign in and go — only the company admin’s very first install takes longer, once, ever.
From raw remit files to filed EOB documents in four moves.
Load the batch
Add 835 or ZIP files, or hit Refresh to sweep your company’s 835 intake folder into the queue.
Convert / Resume
Remit Forge parses each file and builds the finished EOB documents, one after another.
Teach it once
Unrecognized practice? Pick the right doctor one time — the alias sticks forever after.
Filed and totaled
Documents land in the right doctor folders, and the results window totals the whole run.
$97 a month. Two for the price of one.
Remit Forge
- Benefit Beacon desktop included free — itself a $97/mo tool
- Two installations included; extra installations $27/mo each
- Automatic updates, every improvement from our own floor
- Guided self-setup free; assisted setup available
- Annual option: pay for 10 months, get 12
Or take the suite
- All five ClaimVolt tools, mixed however your floor works
- Benefit Beacon Plus intake portal included
- White-glove personal setup
- Running three tools? The suite already costs less
Questions offices ask about Remit Forge
Does patient data leave our office?
No. The 835-to-EOB conversion engine runs entirely on your computer — no network calls or APIs are part of the conversion itself. License activation sends only the key, the product name, this workstation’s fingerprint, and the app version — never patient data, 835 files, or folder contents.
What happens when it doesn’t recognize a practice name?
An Unmatched window asks you to pick the right doctor (or create a new one), and your answer is remembered as an alias — the same practice routes itself from then on. Anything still needing a decision waits safely in the queue; nothing is lost between sessions.
Do team workstations need Google credentials?
No. Team installs read everything they need from the company’s shared setup — no Google credentials ever live on a team machine. The admin configures the company connection once; everyone else just signs in.
What does it run on?
Shipped, signed installers for Windows, with automatic updates — when an approved release is ready, the app offers it and your team accepts it in place. No re-installing, nothing to maintain.
Can we add more tools later?
Yes — every ClaimVolt tool is $97/month, and they share one sign-in and one company setup. By the time you’re running three, the Starter suite already costs less than the singles.
Bring a week of remits. We’ll show you the after.
Tell us how remits run in your office today, and we’ll show you exactly which jobs Remit Forge takes over — with honest numbers from our own floor, where it runs every remit, every week.
Request my workflow review