Automate X12 837 claim submission and 835 remittance posting between the billing system and your clearinghouse or payers — with acknowledgment tracking and a denial work queue that closes the loop.
Claims and Remittance Automation
Objective: Claims leave the billing system and disappear into a clearinghouse portal. Nobody can say which claims were acknowledged, which were rejected before they ever reached the payer, or why cash posted three weeks late. This plan automates 837 submission and 835 remittance posting, tracks every acknowledgment in between, and turns denials into a work queue instead of a PDF someone opens on Friday.
What's Getting Built
- Claim Assembly and Scrub (Process API) — extracts the billing batch, scrubs claims, and assigns a submission control number ·
SCHEDULER submit ready batch, POST /claims/scrub, POST /claims/submit
- X12 Trading Partner Gateway (System API) — sends 837P/837I over AS2 or SFTP and receives TA1, 999, 277CA, and 835 back ·
AS2 SEND 837P/837I, SFTP PUT 837, RECEIVE TA1/999/277CA, RECEIVE 835
- Acknowledgment Tracker (Process API) — records TA1, 999, and 277CA against the originating claim with an overdue SLA timer ·
CONSUME TA1/999/277CA, PATCH /claims/{controlNumber}/ack, SCHEDULER ack overdue check
- Remittance Posting and Denial Queue (Process API) — parses 835 at service-line level, posts payment, and routes CARC/RARC denials by category ·
PARSE 835, POST /remittance/post, POST /denials/queue
- Billing System (target) — source of the claim extract and destination for service-line payment write-back ·
GET /claims/ready, POST /payments/post
- X12 Dead-Letter Queue (Object Store) — retains raw unparseable X12 payloads with correlation for replay ·
PUT /dlq/{controlNumber}, GET /dlq/{controlNumber}
This plan covers the claim-out and payment-in half of the revenue cycle. Front-end verification is covered separately by Benefits and Eligibility Verification and Prior Authorization: CRD, DTR, and PAS — run those first, because most denials are created before the claim is ever built.
Prerequisites
- Anypoint Platform org with the X12 EDI connector licensed and an AS2 or SFTP channel to your trading partner.
- MuleSoft Accelerator for Healthcare X12 assets imported from Exchange as the transaction-set foundation.
- Clearinghouse or direct payer trading partner agreement, companion guides, and sandbox endpoints.
- Billing system or EHR revenue cycle module access for claim extract and payment posting write-back.
- Test payer IDs, member IDs, and a claim set that exercises professional and institutional formats.
Choose your path
- Clearinghouse — Choose for breadth. One connection reaches hundreds of payers, the clearinghouse normalizes companion-guide differences, and onboarding a new payer is a configuration change. You pay per transaction and you inherit their outage.
- Direct payer connectivity — Choose for your highest-volume payers where the economics or turnaround justify a dedicated connection. Faster acknowledgments and no intermediary, but you own every companion guide variation yourself.
Architecture
1. Business requirements
- Submit 837P (professional) and 837I (institutional) claims on a schedule the billing team controls.
- Track every claim through acknowledgment — TA1, 999, and 277CA — so no claim is silently lost.
- Post 835 remittance automatically against the originating claim, including adjustments and patient responsibility.
- Route denials and rejections to a work queue with the reason code translated into something a biller can act on.
- Reconcile deposits to remittance to claims, and report on anything that does not tie out.
2. Claim assembly and scrubbing
- Extract claims in a batch the billing system marks as ready — never scrape a work-in-progress table.
- Scrub before submission: required loops present, NPI and taxonomy valid, diagnosis-to-procedure linkage sound, service dates inside the coverage period.
- Fail a claim locally with a specific message rather than letting the payer reject it two days later; a local scrub failure costs minutes, a 277CA rejection costs a week.
- Assign your own submission control number and keep the mapping to the billing system claim ID — this is how you correlate everything downstream.
3. X12 transaction set and acknowledgments
- Build 837 envelopes per trading partner using their companion guide; the differences are real and they are not in the base standard.
- Consume TA1 (envelope), 999 (syntax), and 277CA (payer-level claim status) and record each against the claim, with the timestamp.
- Treat a missing acknowledgment as an exception with an SLA timer, because silence from a clearinghouse is indistinguishable from success until the cash does not arrive.
- Support corrected and voided claims with the right frequency code rather than resubmitting a duplicate original.
4. Remittance posting and denial management
- Parse 835 into claim, service line, adjustment, and payment detail; post at the service-line level so partial payments are not rounded into a single number.
- Translate CARC and RARC codes into a categorized denial reason and route by category — coding, eligibility, authorization, timely filing — to the team that can fix each one.
- Split contractual adjustment, patient responsibility, and true denial; posting all three as one write-off is how revenue quietly disappears.
- Match the EFT trace number in BPR/TRN to the bank deposit so finance can reconcile without a spreadsheet.
5. Error handling and operations
- Make submission idempotent on the submission control number — a retried batch must never create duplicate claims at the payer.
- Never partially post a remittance: post the 835 as a transaction, or fail it whole into a queue for review.
- Route unparseable files to a DLQ with the raw payload retained; X12 rejects are usually one bad segment in an otherwise good file.
- Alert on batch not sent, acknowledgment overdue, remittance not received within expected days, and denial-queue depth.
6. Security and compliance
- Encrypt PHI in transit and at rest.
- Audit-log every access to and modification of patient data.
- Enforce minimum-necessary access for integration operators and support users.
For additional HIPAA controls, API policies, and reference security patterns, see the MuleSoft Accelerator for Healthcare on Anypoint Exchange.
Sample payload — X12 835 remittance (payment with a contractual adjustment)
ST*835*0001~
BPR*I*1250.00*C*ACH*CCP*01*011000015*DA*1234567890*1512345678**01*021000021*DA*9876543210*20260203~
TRN*1*EFT20260203001*1512345678~
DTM*405*20260203~
N1*PR*EXAMPLE HEALTH PLAN~
N1*PE*NORTH MEDICAL GROUP*XX*1234567893~
LX*1~
CLP*ACCT10045*1*2000.00*1250.00*250.00*12*PAYERCLM00987*11~
NM1*QC*1*DOE*JANE****MI*MEMBER12345~
SVC*HC:99214*250.00*180.00~
DTM*472*20260115~
CAS*CO*45*70.00~
AMT*B6*180.00~
Testing and validation
- Submit a clean 837P batch to the partner sandbox and confirm TA1, 999, and 277CA all post against the originating claims.
- Submit a claim with a deliberately invalid NPI and confirm the local scrub catches it before transmission, with an actionable message.
- Resend an already-transmitted batch and confirm idempotency — no duplicate claims at the payer.
- Post an 835 containing a contractual adjustment, a patient-responsibility amount, and a denial; confirm all three land in the right buckets at service-line level.
- Withhold an acknowledgment past the SLA and confirm the overdue exception fires rather than the claim sitting as submitted forever.
Phased rollout
Phase 1 — Connect
- Establish AS2 or SFTP connectivity to the sandbox trading partner, exchange certificates, and prove a TA1 round trip.
- Import the X12 assets and configure envelope and companion-guide settings per partner in externalized properties.
Phase 2 — Map and test
- Map 837P for one specialty and payer; run parallel with the existing process and compare claim-for-claim before cutting over.
- Enable 835 posting in read-only mode first — produce the posting file and have a biller verify it before it writes to the billing system.
Phase 3 — Production
- Cut over payer by payer, highest volume last; monitor acknowledgment SLA and first-pass acceptance daily during ramp.
- Hand the denial queue, reconciliation report, and partner-outage runbook to the revenue cycle team before go-live.
Success metrics
- First-pass claim acceptance ≥ 95% at 277CA, measured before any resubmission.
- Auto-posted remittance ≥ 90% of 835 lines, with manual posting reserved for genuine exceptions.
- Days in accounts receivable reduced against the pre-integration baseline the finance team already reports.
- Zero duplicate claim submissions, and every submitted claim carrying a recorded acknowledgment within SLA.
Configuration checklist
Before first sandbox deploy, complete the shared Healthcare integration configuration checklist — secure property keys, TLS, OAuth, and credential naming conventions are documented once for all Exchange use cases.
7. Implementation starting point
Import the X12 assets from the MuleSoft Accelerator for Healthcare on Anypoint Exchange and start from the 837 and 835 transaction-set definitions rather than hand-rolling segments.
Build the acknowledgment tracker first, before submission volume grows — retrofitting claim correlation onto a running pipeline is painful.
Keep companion-guide variations, payer routing, and envelope IDs in an externalized table so onboarding a payer is configuration, not a redeploy.
Post 835 remittance to a staging structure a biller reviews before writing to the billing system, at least through the first month.
Troubleshooting
- 999 returns with IK5 rejection on every claim — Likely cause: an envelope or loop structure that does not match the partner companion guide. Fix: Diff your 837 against the partner's sample file segment by segment; the base standard is not enough on its own.
- Payment posted but claim still shows outstanding — Likely cause: the 835 claim control number does not match the submission control number sent on the 837. Fix: Correlate on your own control number carried through CLP07 and keep the cross-reference to the billing system claim ID.
- Duplicate claim denials from the payer — Likely cause: a batch retried after a timeout that had actually succeeded. Fix: Make submission idempotent on control number and confirm transmission status before any resend.
- Remittance total does not match the bank deposit — Likely cause: multiple 835 files settled under one EFT, or a reversal in a later file. Fix: Reconcile on the BPR/TRN trace number across files rather than per file, and handle reversals explicitly.
Deliverable: An automated 837 submission and 835 posting pipeline with full acknowledgment tracking, service-line posting, and a categorized denial work queue.