MyTherapyWizard Book demo
Insurance, Private-Pay & Contract Billing TEAMS

ERAs posted, denials flagged, appeals ready.

ERA posting and remittance reconciliation for therapy billing. Electronic remittance posting. Auto-match EOBs to claims, flag denials, and trigger appeal workflows. Payment reconciliation across payers.

Watch video Book a demo →
Feature walkthrough

ERAs, product walkthrough

VIDEO EMBED · REPLACE WITH <iframe>

Overview

ERAs arrive, get parsed, and post to the patient ledger automatically. No PDF reading, no manual allocation, no copying adjustment codes from one system to another.

ERA retrieval runs through /services/eralist/ with an ERAID cursor, identical pattern to the claims response poll. Each new ERA pulls its full detail via /services/eradata/ (structured XML or JSON) or /services/erapdf/ (Base64 PDF for archiving). MyTherapyWizard parses the benefit response, matches line items to claims by claimmd_id, and posts the adjudication to the ledger: billed, allowed, insurance paid, patient responsibility, adjustments.

Every payment field is non-destructive. Edits don't overwrite, they create a new entry in the era_payment_revisions table with revision_number, field_changed, old_value, new_value, revised_by, and revised_at. The Note chip on each row captures context without touching the data underneath. Denied line items drill down into CO-group codes (CO-4, CO-97, CO-16, etc.) and surface Appeal and Resubmit actions directly from the row.

See it in action

Product screens, workflow diagrams, and example outputs. Replace each slot with a real screenshot or illustration.

IMG 01 · HEROPrimary product shot
IMG 02Workflow detail
IMG 03Output example
IMG 04Data / chart view
IMG 05Mobile / tablet view
How it works

Under the hood.

The technical architecture, API integration points, and data model that make this feature work the way it does.

01

/services/eralist/ + /services/eradata/ with cursor pattern.

First call uses ERAID=0. Save last_eraid from each response. Next poll retrieves only new ERAs. Same mechanics as claim status polling, drop-in cursor model across the integration.

02

Benefit code parsing for allied health.

MyTherapyWizard parses the response XML into its internal schema. Surfaces OT-relevant codes (96), PT (physical therapy), UC (urgent care), 50 (home health) alongside copay, deductible, out-of-pocket, and coverage status.

03

era_payment_revisions table: revision-based, never destructive.

Columns: era_record_id, revision_number, field_changed, old_value, new_value, revised_by, revised_at. Full audit log accessible via 'View' on any ERA row. '▼ History' expands a per-row inline list.

04

COB secondary claim submission after primary posting.

When a patient has a COB-IN flag and the primary ERA is posted, admin initiates the secondary claim. MyTherapyWizard submits to ClaimMD with crossover_id populated from the primary claim, no manual rebuild of the 1500 form.

Why it matters

01

Posting becomes review, not data entry.

ERAs post themselves. Your biller reviews exceptions, logs denial reasons, and initiates appeals, they don't hand-enter payments.

02

Full revision history on every payment.

Corrected a miskeyed adjustment? The old value is still there. Every edit adds a row; nothing is ever lost. Auditable by default.

03

Denied claims drill down inline.

CO-group denial codes surface per line, with Appeal and Resubmit actions at hand. No hunting through PDFs to find why a claim came back zero.

See eras inside MyTherapyWizard.

Book a 30-minute walkthrough with our clinical team. We will show the exact workflow for your discipline and caseload.