837P and 837I: why almost nobody actually mails a paper claim anymore.
Under HIPAA's electronic transaction standard, the CMS-1500 and UB-04 are, for almost every practice, no longer something anyone actually prints and mails. Claims travel as the 837P or the 837I — the electronic transaction sets built around exactly the same fields as their paper equivalents — and that isn't just a convenience. It's faster, and it catches far more before a claim ever becomes a denial.
Key takeaways
- Electronic submission is the default under HIPAA, not a preference. The 837P and 837I are what almost every claim actually travels as.
- Paper survives only in narrow exceptions. A limited group of small-volume or non-standard submitters, plus certain payer-specific situations.
- Electronic scrubbing catches errors in seconds, before submission. Paper's first real review happens inside the payer's system, weeks later.
- The paper form's field structure never disappeared. Box numbers and form locators are still how payer correspondence describes a problem, even on claims that were never printed.
What the 837P and 837I actually are
The 837P and 837I are the electronic transaction formats defined under the HIPAA electronic transaction standard for submitting healthcare claims, built on the ANSI X12 data interchange format used across US healthcare administrative transactions. They are not a different, competing way of billing — they carry the same underlying information as the paper CMS-1500 and UB-04, organized into the electronic data segments a payer's adjudication system reads directly, rather than a printed page a human would have to key in by hand. The 837P mirrors the CMS-1500 and carries professional claims: physicians, non-physician practitioners, and most outpatient practices billing for services they personally performed. The 837I mirrors the UB-04 and carries institutional claims: hospitals, skilled nursing facilities, home health agencies and other facility-type providers billing for the facility side of an episode of care.
In practice, almost no practice builds or transmits an 837 file by hand. A practice management system generates the transaction from the same data entered for billing purposes, and a clearinghouse sits between the practice and the payer, validating the transaction's structure, routing it to the correct payer, and very often applying its own layer of pre-submission edits before the claim is ever accepted for adjudication. That clearinghouse layer is a large part of why electronic submission behaves so differently from paper in practice, and it's covered in more depth in our guide on what a clearinghouse actually does.
Because HIPAA's electronic transaction standard applies to the transaction, not to the payer's internal processing, the 837P and 837I are used the same way across Medicare, Medicaid, and commercial payers alike. A practice billing a mixed payer panel submits the same transaction type to every payer that accepts assignment of the standard, rather than learning a different submission format payer by payer — a standardization that paper claims, submitted under whatever cover process each individual payer happened to require, never offered.
Electronic submission as the default, not the exception
HIPAA's Administrative Simplification provisions require covered healthcare providers above a small-volume threshold to submit claims electronically as the standard transaction, rather than on paper, and that requirement is why electronic submission functions as the practical default across the industry rather than simply the more popular option. For the overwhelming majority of practices, this isn't a choice weighed each time a claim goes out — the practice management system generates an 837 transaction as a matter of course, and paper is not part of the normal workflow at all.
The exceptions that remain are genuinely narrow, and it matters to understand them as exceptions rather than as a live alternative most practices could reasonably choose. A limited category of small-volume or non-standard submitters — providers who fall under a recognized exception to the electronic filing requirement — may still submit on paper. Certain payer-specific situations also still call for a paper form in particular circumstances, where a specific payer's own processes or a particular claim scenario falls outside the standard electronic transaction. Neither category represents a meaningful share of total claim volume industry-wide, and neither should be read as evidence that paper submission remains a viable default workflow for a typical practice weighing its options. Confirm your own status against the current exception criteria directly with your Medicare Administrative Contractor or payer rather than assuming either general description applies to your specific situation.
| Electronic (837P / 837I) | Paper (CMS-1500 / UB-04) | |
|---|---|---|
| Who uses it | The overwhelming majority of practices and claim volume | A narrow group of small-volume or non-standard submitters, plus limited payer-specific situations |
| Pre-submission validation | Field-level logic checked by the clearinghouse or scrubbing engine before the payer ever sees the claim | None until the payer's own system processes it |
| When an error surfaces | Within seconds to minutes of submission | Weeks later, as a rejection or denial letter, while the filing clock keeps running |
| Field structure | Same fields as the paper form, organized as electronic data segments | Numbered boxes (CMS-1500) or form locators (UB-04) |
Why electronic submission catches more before it becomes a denial
Speed is the obvious advantage of electronic submission, but it isn't the one that actually protects revenue. The real advantage is that an electronic claim gets checked before anyone outside the practice ever sees it. A clearinghouse or a scrubbing engine can apply field-level logic edits to an 837 transaction in seconds — confirming a diagnosis pointer actually resolves to a diagnosis listed elsewhere on the claim, confirming a Type of Bill frequency digit doesn't contradict what the payer already has on file for that claim, confirming a rendering provider's NPI is reassigned to the billing group named on the same claim. None of that checking is possible on a paper claim before it's mailed; the first real review a paper claim gets happens inside the payer's own adjudication system, and that means the first time anyone learns about a field-linking error is a rejection letter that can arrive weeks after the claim was sent.
That gap matters more than it might seem, because the clock on a claim doesn't pause while it's in transit or while a rejection letter is being generated and mailed back. A claim's timely filing deadline keeps running regardless of how the claim was submitted, so a paper claim that bounces for a fixable, field-level error has simply burned weeks of its filing window before anyone even knows there's a problem to fix. An electronic claim carrying the identical error gets caught and corrected inside the same business day, often before the claim has even left the clearinghouse, which is the specific mechanism behind why practices that moved fully to electronic submission see materially fewer of exactly the kind of late, preventable timely-filing losses covered in our timely filing guide.
This is also why "electronic" and "scrubbed" tend to travel together operationally, even though they're technically separate steps. A clearinghouse's baseline validation catches structural problems — a transaction that doesn't parse, a required segment that's missing entirely. A dedicated claims-scrubbing layer on top of that catches the more specific, payer-aware logic errors: the diagnosis pointer, the modifier combination, the units against a Medically Unlikely Edit. A practice relying only on the clearinghouse's baseline check is still catching far more than a paper submission ever would, but it's leaving a second, more specific layer of protection on the table that our claims scrubbing service is built to add.
What the paper form's field structure still explains
Electronic submission being the default doesn't make the paper form's layout irrelevant, and this is the part of the electronic-versus-paper picture that trips up billing staff who came up entirely inside a clearinghouse dashboard. The 837P and 837I are organized around the same fields the CMS-1500 and UB-04 define — box 24E's diagnosis pointer, form locator 4's Type of Bill — and payer remittance advice, denial correspondence and even some clearinghouse error messages routinely reference those box numbers and form locator numbers by name, regardless of whether the specific claim in question was ever printed on paper at all.
That means a biller who only knows the electronic side of the workflow, without ever learning what box 24E or form locator 4 actually represent, is at a real disadvantage the moment a denial reason code references one of them directly. The field structure defined by the paper forms is, in effect, the shared vocabulary the entire system — electronic and paper alike — still speaks, which is exactly why our CMS-1500 vs. UB-04 guide and the two field-level guides underneath it are worth knowing cold even for a practice that hasn't handled a physical paper claim in years.
If your practice believes it qualifies for a small-provider or non-standard-submitter exception to electronic filing, confirm that status directly and in writing with your Medicare Administrative Contractor or the specific payer before building a workflow around paper submission. The exception criteria are narrow and specific, and assuming eligibility without confirming it is a common way practices end up submitting claims that don't meet either the paper exception's requirements or the electronic default — and get rejected on a technicality that has nothing to do with the underlying billing.
Still handling any claims on paper?
We move every claim through electronic submission with pre-submission scrubbing built in, so field-level errors get caught in seconds, not weeks.
Frequently asked questions
Is paper claim submission still allowed?
In narrow circumstances, yes. HIPAA's electronic transaction standard requires most claims to be submitted electronically as the 837P or 837I, but a limited group of small-volume or non-standard submitters qualify for a recognized exception, and certain payer-specific or claim-type situations still call for a paper form. For the overwhelming majority of practices and the overwhelming majority of claims, electronic submission through a clearinghouse is not optional in practice even where a narrow exception exists on paper.
What's the difference between the 837P and the 837I?
They are the electronic equivalents of the two paper claim forms. The 837P carries the same information as the CMS-1500 and is used for professional claims — physicians, non-physician practitioners and most outpatient practices. The 837I carries the same information as the UB-04 and is used for institutional claims — hospitals, skilled nursing facilities, home health agencies and other facility-type providers. Which transaction applies follows the same provider-type rule that decides which paper form would apply.
Why does electronic submission catch more errors before a claim is denied?
Because a clearinghouse or scrubbing engine can validate field-level logic on an electronic claim in seconds, before it ever reaches the payer — things like a diagnosis pointer that doesn't resolve, or a Type of Bill frequency digit that contradicts what's already on file. A paper claim gets none of that pre-submission checking. Its first real review happens inside the payer's own system, and any error only comes back as a rejection or denial letter weeks later, after the filing clock has already been running the entire time.
Confirm before you rely on this. Claim form requirements, electronic transaction rules and payer-specific field rules change. The process information on this page reflects standard industry practice as of August 2026 and is provided for general education — verify current requirements against the current NUCC CMS-1500 and NUBC UB-04 instructions, and your own electronic filing exception status, before relying on it.