Skip to content
Novus Examples
edi1 KB

Juniper Fitness and Clinic Administration: X12 837 claim whose service lines do not add up to the claim total

X12 837 claim whose service lines do not add up to the claim total for Juniper Fitness and Clinic Administration. The same single-claim interchange with one element changed: CLM02 reads 225.00 instead of 205.00. The two SV102 amounts are untouched at 120.00 and 85.00, so they still sum to 205.00 and disagree with the claim total by 20.00 USD. Segment counts, envelope control numbers and every other element are correct, so a structural validator passes the file and only the balance rule catches it.

edi

application/edi-x12

1 KB
Document Set
healthcare
Industry
fitness-clinic-administration
Source Kit
appointment-capacity
Entity
Juniper Fitness and Clinic Administration
Synthetic
true
As Of
2026-09-08

Binary edi: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
healthcare
Industry
fitness-clinic-administration
Source Kit
appointment-capacity
Entity
Juniper Fitness and Clinic Administration
Synthetic
true
As Of
2026-09-08
Transaction Set
837
Claims
1
Service Lines
2
Segment Count
27
Service Line Total
205.00
Declared Claim Total
225.00
Difference
20.00
Structurally Valid
true

Testing contract

Expected to fail
Scenario
Validate the envelope and segment counts first, then sum SV102 and compare with CLM02.
Expected result
The envelope is well formed and SE01 matches the 27 segments present, so a structure-only check reports the file as clean. SV102 sums to 205.00 against a CLM02 of 225.00, an overstatement of 20.00 USD on the CLM segment.

What is a .edi file?

EDI (Electronic Data Interchange), in the ANSI X12 family, is a structured plain-text format for exchanging business documents like purchase orders (850) and invoices (810) between trading partners. It is built from segments (ISA, GS, ST, …) separated by delimiters, with tightly specified element positions. It underpins much of B2B supply-chain and retail commerce.

How to use this file

Use an example X12 EDI file to test EDI parsers and translators, segment/element extraction, and mapping from EDI to JSON or XML. The parties and values here are synthetic.

How to use this file for testing

“Juniper Fitness and Clinic Administration: X12 837 claim whose service lines do not add up to the claim total” is a deterministic Novus Examples fixture for Data import, Schema validation, Error handling. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: EDI · 1,036 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

from pydifact.segmentcollection import Interchange  # EDIFACT

inter = Interchange.from_file("claim-837p-CLM-0006-service-line-total-mismatch.edi")
for seg in inter.segments:
    print(seg.tag, seg.elements)

Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.