Output Examples

These files were generated from the same public 835 sample using the conversion engine shared by the desktop app and CLI. The sample contains one adjudicated claim with seven service lines. Download the source EDI file to try the conversion yourself.

The previews below show selected columns and the first two service lines. Downloads contain the complete output.

Single file; header on first row

Choose this mode to keep the claim and its services in one table without repeating every claim field. Claim identifiers remain on later rows.

Download CSV with claim values on the first row.

The empty claim amounts on the second row do not mean zero: the amounts are already shown on the first row.

Single file; header repeats all rows

Choose this mode when you want to sort or filter service lines while keeping the claim context on every row.

Download CSV with claim values repeated.

The claim charge is still 384, not 384 multiplied by the number of services. Use one row per claim for claim totals, or sum line amounts when calculating service-line totals.

Separate files for header and lines

Choose this mode to work with claim totals and service lines independently. Match the tables using Id.

Claims table:

Service-line table:

Download the claims CSV and service-lines CSV, or the Excel workbook to view the tables on separate sheets.

Additional 835 tables

All three CSV modes also produce a remittances table, containing payment-level information such as the check or EFT trace number, date, and total payment. A remittance can contain multiple claims, so its total can differ from an individual claim’s paid amount.

Provider-level adjustments are written to a -ProviderAdjustments.csv file. The sample above has no provider adjustments, so that file contains only column headings. See this provider-adjustments CSV example for populated rows.

JSON

Select JSON under Format to preserve nested objects and lists. This shortened excerpt shows the claim-level amounts from the same sample:

[
  {
    "objectType": "PAYMENT",
    "patientControlNumber": "7722337",
    "chargeAmount": 384.0,
    "paymentAmount": 238.0
  }
]

Download the complete JSON, including the patient, payer, adjustments, transaction, and all seven serviceLines. This example leaves the three JSON options unchecked. Enabling them adds validation or control objects, or moves transactions to the top level.

NDJSON uses the same record structure, with each object on its own line instead of wrapping the records in a JSON array.

More transaction types

For 837 claims, 834 enrollment, and other JSON examples, see the CLI Output Examples. The desktop app produces the same output when the same conversion options are selected.

See the CSV Data Dictionary for column definitions and the JSON Schemas for JSON fields. Optional values may be blank, and repeating lists in CSV use a fixed number of numbered columns; JSON preserves nested lists.