If your billing team has ever stared at a rejected claim and wondered which message told you what, you are not alone. California workers’ compensation EDI involves a handful of transaction types that sound similar, arrive at different times, and mean very different things. A claim can be technically accepted and still be unpaid. A file can be rejected before anyone ever looks at the medical bill. And a payment message can arrive with adjustments that need a closer look.
This guide explains workers’ comp EDI billing in plain English. You will learn what the 837, 999, 277 and 835 transactions do, how they fit together, where California’s own requirements come into play, and how to handle the errors that cost teams the most time. It is written for billing managers, practice administrators and providers who want to understand the full journey from submission to payment.
What Is EDI in California Workers’ Compensation Billing?
EDI, or electronic data interchange, is the standardized exchange of business data between computer systems. In medical billing, it means claims, acknowledgments, status updates and payments move electronically in a fixed format instead of on paper or by phone.
What electronic data interchange means in medical billing
Instead of mailing a form and waiting, your billing system sends a structured file that the receiving system can read automatically. The receiver sends structured responses back. Each message type has an identifier, such as 837 or 835, defined by the X12 standard used across U.S. healthcare.
Why electronic billing matters for California workers’ comp
California workers’ comp electronic billing gives teams faster feedback and a cleaner paper trail. Errors surface within hours instead of weeks, payments can be posted from data instead of typed in by hand, and every step leaves a record you can audit later. For high-volume practices, that difference adds up quickly.
The role of providers, clearinghouses, payers, and claims administrators
Four parties usually take part. The provider creates the bill. A clearinghouse, if one is used, checks and routes the file. The payer or claims administrator receives it, reviews it and issues payment. Each party can send back its own responses, which is why one claim can generate several messages. The exact path depends on your trading partners, so never assume two payers behave the same way.
Understanding the Workers’ Compensation EDI Workflow
The common sequence is easy to describe, even if the details vary by payer and clearinghouse.
Step | Transaction | What happens |
1 | 837 | The provider or billing system submits the claim |
2 | 999 and validation responses | The receiver confirms the file was readable and reports any structural errors |
3 | 277, when applicable | The payer or clearinghouse reports claim acknowledgment or status |
4 | 835 | The payer sends payment and adjustment details for reconciliation |
Responses and sequencing vary. Some trading partners send extra acknowledgments, some skip certain messages, and some route everything through a clearinghouse. Treat this table as the typical pattern, not a guarantee.
Preparing and submitting the electronic claim
The workflow starts with clean data. Patient details, claim numbers, provider identifiers, procedure codes and dates of service all need to be accurate before the file leaves your system. Fixing a problem at this stage takes minutes. Fixing it after rejection takes days.
Receiving technical acknowledgments
Within a short time of submitting, you should receive acknowledgment that the file arrived and could be read. This tells you the transmission worked, not that the claim is approved.
Monitoring claim status and processing updates
After the file is accepted, status messages tell you whether individual claims were accepted into the payer’s system, are pending, or were rejected. Teams that watch these updates catch problems while there is still time to act.
Reviewing remittance information and payment adjustments
Finally, the remittance arrives with payment amounts and adjustment reasons. This is the step that closes the loop and drives your accounts receivable.
What Is an 837 EDI Transaction?
The 837 EDI transaction is the electronic healthcare claim. It carries everything a payer needs to evaluate a bill: who the patient is, who provided the service, what was done, when, why, and how much was charged.
What information an 837 claim contains
A typical 837 includes billing and rendering provider information, patient and claim identifiers, diagnosis codes, procedure codes, modifiers, dates of service and charge amounts. In workers’ comp, it also needs the correct claim and employer details so the payer can match the bill to the right injury.
837P versus 837I
The 837P is used for professional claims, such as those from physicians, therapists and other clinicians. The 837I is used for institutional claims, such as those from hospitals and facilities. Most outpatient workers’ comp providers deal with the 837P, so 837P claim submission is the workflow most billing teams manage day to day.
Common claim data and formatting errors
The usual suspects are missing or mismatched claim numbers, invalid diagnosis or procedure codes, incorrect provider identifiers, formatting problems in dates, and fields that exceed length limits. None of these are exotic, and almost all are preventable.
How pre-submission validation can reduce avoidable rejections
Checking a claim before it goes out is the cheapest form of EDI claim rejection management. Validation rules can flag missing fields, bad codes and format problems while the claim is still in your hands. BillGenix, for example, describes an 837P validation workflow that checks claims before submission so teams can correct issues early.
What Is a 999 EDI Acknowledgment?
A 999 acknowledgment in medical billing is an implementation-level response that tells the sender whether a submitted file met the required structure. Think of it as a delivery receipt with a quick inspection, not a decision on the claim.
What the 999 acknowledgment confirms
It confirms that the receiving system could read the transaction and that it followed the expected format. It can report that the file was accepted, accepted with errors, or rejected.
It does not confirm that the claim has been approved or that payment is coming. This is the single most common misunderstanding about the 999. A clean 999 only means the file was well formed.
Common structural and implementation errors
Typical problems include missing required segments, invalid data elements, incorrect control numbers and values that do not follow the implementation guide. These are usually software or mapping issues rather than billing judgment calls.
What to do when a 999 reports errors
Read the error details, identify which transaction or segment was affected, correct the underlying data or mapping, and resubmit. If the same error keeps appearing, contact your clearinghouse or trading partner, because the issue may sit in how your files are built.
Why acknowledgment tracking matters
An unnoticed rejected file is a claim that was never really submitted. If nobody reviews the 999, a whole batch can sit idle while everyone assumes it is moving. Tracking every acknowledgment, and flagging the ones that never arrive, protects your cash flow.
What Is a 277 EDI Transaction?
The 277 claim status transaction carries information about where a claim stands. Depending on the implementation, it can respond to a status inquiry or acknowledge that a claim was received and passed initial checks.
Claim status responses and claim acknowledgment use cases
There are two related uses worth separating. A 277 claim status response answers a status question, usually one you asked through a claim status inquiry. A 277CA, or claim acknowledgment, reports whether individual claims were accepted or rejected at the payer or clearinghouse front end. The exact purpose depends on the applicable implementation and your trading partner, so confirm which one you will actually receive.
How to interpret a status update
Status messages use category and status codes that describe what happened, such as accepted, pending, or rejected, along with a reason. Read the codes alongside the claim identifiers so you know exactly which bill the message refers to. A status update is information about processing, never confirmation that payment has been made.
What to do when a claim is pending, rejected, or requires follow-up
Pending claims need a follow-up date, so they do not drift. Rejected claims need the cause identified, the data corrected and a documented resubmission. Claims that need more information should be routed to whoever can supply it, along with a clear deadline.
How to track outstanding claims
The simplest approach is to track every claim by its next expected event. If a claim was submitted and no acknowledgment or status has arrived within your normal window, it belongs on a follow-up list. Doing this manually in spreadsheets works for a short while, then breaks as volume grows.
What Is an 835 Electronic Remittance Advice?
The 835 electronic remittance advice is the transaction that explains payment. It tells you what was billed, what was allowed, what was paid, and why any amounts were adjusted.
How the 835 communicates payment and adjustments
For each claim and service line, the 835 reports the billed amount, the paid amount and any adjustments, along with codes that explain them. It is designed so a billing system can read it and update the account without someone retyping numbers.
Understanding claim adjustment reason codes (CARCs)
Claim adjustment reason codes explain why an amount differs from what was billed. They can indicate contractual reductions, fee schedule adjustments, denials, or amounts that remain open for follow-up.
Understanding remittance advice remark codes (RARCs)
Remittance advice remark codes add detail. Where a CARC gives the main reason, a RARC often supplies the supporting explanation or the next step the provider may need to take.
Reconciling billed amounts, adjustments, and payments
Good EDI 835 payment posting matches each payment to the original claim, accounts for every adjustment, and leaves a clear balance. When the numbers do not reconcile, the discrepancy should be visible rather than buried.
Identifying underpayments and possible second-review needs
Compare the paid amount with what you expected under the applicable fee schedule, then read the adjustment codes to see why they differ. If the explanation does not hold up, the claim may qualify for a second review. In California workers’ comp, the EDI remittance can serve as the Explanation of Review (EOR) for applicable electronic billing workflows, which makes careful reading of the 835 especially important.
837 vs. 999 vs. 277 vs. 835: Key Differences
These four transactions cover submission, acknowledgment, status and payment. None of them replaces another.
Transaction | Main purpose | Typically sent by | Typically received by | Timing | Recommended next action |
837 | Submits healthcare claim information | Provider or billing system | Clearinghouse or payer | At submission | Validate claim data and submission format |
999 | Reports implementation-level acknowledgment | Receiving system | Sender of the file | Shortly after submission | Review errors and correct the transaction when necessary |
277 | Communicates claim status or acknowledgment, depending on implementation | Payer or clearinghouse | Provider or billing system | After acknowledgment, and during processing | Review status and determine the next follow-up action |
835 | Communicates claim payment and remittance details | Payer or claims administrator | Provider or billing system | After adjudication and payment | Post payments, reconcile adjustments and investigate discrepancies |
Timing and senders vary by trading partner, so use this table as a general guide. The key point is that a 999 is not an approval, a 277 is not a payment, and an 835 is not a submission receipt. Treating them as interchangeable is how claims get lost.
California Workers’ Compensation EDI Requirements
California has its own rules layered on top of the national standards, so it helps to know where to look.
California DWC electronic billing guidance
The California Division of Workers’ Compensation publishes electronic billing guidance and FAQs. Claims administrators must accept electronic medical bills, while providers may choose electronic billing or compliant standardized paper billing. Providers who choose EDI must be able to receive electronic responses, including acknowledgments and remittance advice.
Medical Billing and Payment Guide and Companion Guide
The DWC’s Medical Billing and Payment Guide and its Companion Guide describe how electronic bills and responses are expected to work in the state. Use them as primary references rather than relying on secondhand summaries.
WCIS medical bill reporting versus payer billing
This is the distinction that trips up many teams. California WCIS medical bill reporting is a separate process from the billing you exchange with payers and clearinghouses. WCIS, the Workers’ Compensation Information System, receives medical bill data reported to the state, and that process uses X12 837 files and 999 acknowledgments.
The payer-facing workflow can involve 837P submissions, 999 acknowledgments, 277 status messages and 835 remittances, depending on the trading partner and implementation. Both sides use some of the same transaction names, but they serve different purposes and should never be treated as the same workflow.
Why trading-partner requirements matter
Every payer, clearinghouse and claims administrator publishes its own companion guide or implementation rules. Required fields, accepted code values and response behavior can differ. Before you go live with a new trading partner, read their documentation and test with sample files.
Common EDI Errors and How to Resolve Them
Most EDI problems fall into a few repeating patterns.
Invalid claim data or transaction formatting
Bad codes, missing fields and malformed dates are the most frequent causes of early rejection. Validate before submission and keep your code sets current.
Missing or inconsistent identifiers
Claim numbers, provider IDs and patient identifiers must match across the claim, the acknowledgment and the remittance. A small inconsistency can make a payment impossible to match later.
Unnoticed 999 errors
If no one reads the acknowledgement, a rejected file looks the same as a successful one. Assign someone to review every 999 and set alerts for batches that receive no response.
Unresolved claim status messages
Pending and rejected statuses are easy to ignore when volume is high. Give every status message an owner and a follow-up date.
Payment discrepancies in the 835
When paid amounts do not match expectations, compare the claim against the fee schedule and read the CARC and RARC codes before deciding how to respond.
Establishing a documented correction and resubmission process
Write down who fixes what, how corrections are approved, how resubmissions are tracked and when an issue escalates. A documented process turns firefighting into routine work, and it makes training new staff far easier.
How EDI Software Improves Workers’ Compensation Billing
Managing four transaction types across spreadsheets, portals and inboxes is possible, but it gets harder every month. Workers’ comp EDI software helps by keeping the whole lifecycle in one place and giving every message a home.
Validate 837P claims before submission
Built-in validation catches data problems before the claim leaves your system, which supports better EDI claim rejection management from the start.
Track 999 and 277 responses in one workflow
When acknowledgments and status messages land in the same view as the original claim, nobody has to hunt through separate portals to understand what happened.
Connect 835 remittance to the original case
Linking each remittance back to its case makes EDI 835 payment posting faster and makes underpayments easier to spot.
Route errors to the right team
Rejections and discrepancies can be assigned to the person best placed to fix them, instead of sitting in a shared inbox.
Improve reporting, accountability, and follow-up visibility
When every transaction is tracked, managers can see what is waiting, what is stuck and what needs attention today. This is where medical billing EDI automation earns its place, by taking repetitive tracking work off people and leaving them time for judgment calls.
BillGenix offers workers’ compensation EDI software built around this idea. Its published EDI capabilities include 837P validation, 999 acknowledgment tracking, 277 status updates, 835 reconciliation, rejection routing and resubmission tracking. It also supports workers’ comp clearinghouse integration, so your existing submission path can feed into the same tracked workflow. You can read more about its billing, EDI, and payment workflows and how they fit within the wider connected workers’ compensation operations platform.
Ready to see it in action? Book a BillGenix Demo and walk through a claim from submission to payment. Or start with a closer look at the product by choosing Explore EDI Capabilities.
Frequently Asked Questions
What is EDI in workers’ compensation billing?
EDI is the electronic exchange of claims, acknowledgments, status updates and payment information between providers, clearinghouses and payers using standardized formats. In California, it is one of the ways providers submit workers’ comp medical bills and receive responses.
What is the difference between an 837 and a 999?
An 837 is the claim itself. A 999 is the acknowledgment that tells you whether the file you sent was readable and correctly structured. One carries the bill, and the other reports on the transmission.
Does a 999 acknowledgment mean a claim has been approved?
No. A 999 is an implementation-level acknowledgment. It shows the file met structural requirements, but it says nothing about approval, adjudication or payment.
What is the difference between a 277 and a 277CA?
A 277 can serve as a claim status response, while a 277CA is a claim acknowledgment that reports acceptance or rejection at the front end. Which one you receive depends on the implementation and your trading partner.
What is an 835 in medical billing?
An 835 is the electronic remittance advice. It reports payment amounts, adjustments and the reason codes behind them so your team can post payments and reconcile accounts.
Can an 835 explain why a claim was underpaid?
Often, yes. The adjustment reason codes and remark codes describe why amounts were reduced or denied. In California workers’ comp, the EDI remittance can serve as the Explanation of Review for applicable electronic billing workflows, so it is the first place to look when a payment seems low.
How does California WCIS use 837 and 999 transactions?
The WCIS medical bill reporting process uses X12 837 files and 999 acknowledgments to collect medical bill data reported to the state. This is separate from the billing you exchange with payers, even though some transaction names overlap.
Can EDI software help manage claim rejections?
Yes. Good software validates claims before submission, surfaces rejections quickly, routes errors to the right person and tracks corrections through resubmission.
Does BillGenix replace an existing billing system?
BillGenix is designed to connect EDI activity with your workers’ comp operations. If you are wondering how it would sit alongside your current setup, a demo is the best way to confirm what fits your workflow.
Improve Your Workers’ Compensation EDI Workflow With BillGenix
The real value of understanding the 837, 999, 277 and 835 is seeing them as one connected story. A claim is submitted, acknowledged, tracked and paid, and every step either moves it forward or flags what needs to happen next. When that story lives in one place, your team spends less time searching and more time resolving.
Tracking transactions from submission through payment also makes the next action obvious. A rejected 999 points to a correction. A pending 277 points to a follow-up. An 835 with unexpected adjustments points to a review. That clarity is what keeps claims from slipping through the cracks.
If you want to see how that looks in practice, Book a BillGenix Demo and see how connected EDI tracking can support your billing team. You can also learn more about BillGenix to understand the platform behind it.