835 · ERA · CARC and RARC
Charles Trinh — X12 835 Remittance | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

The 835 is where the money is explained: a payment, an adjustment reason, and a remark code for every line the payer did not pay in full. Read properly, it is the richest operational dataset in the revenue cycle.
What this is
An 835 remittance carries the payment, the claim-level and line-level adjustments, and the codes that say why. Claim Adjustment Reason Codes explain the money — contractual obligation, patient responsibility, COB, denial. Remittance Advice Remark Codes add the detail, and the two together are the difference between a denial a team can fix and a denial a team writes off because the reason is unintelligible.
Most organisations post the payment and ignore the rest. The 835 is treated as a financial document when it is also an operational one: the same file that says a claim paid less than expected says which edit fired, which code was wrong and which payer applied a rule the provider did not know about. That information is lost if the reason codes are not parsed into something a person can act on.
Auto-posting is the usual goal and the usual failure. A system that posts payments but maps adjustment codes with a default bucket produces a denial rate that looks stable while the underlying reasons shift. The correct design maps each CARC and RARC combination to a category, an owner and an action, and refuses to post a combination it does not recognise rather than silently bucketing it.
Provider level adjustments — PLB segments — are the third trap. They carry interest, penalties, prior balance recoveries and other movements that are not claim payments, and a posting process that treats them as payments produces a reconciliation that never balances.
There is a second audience for the 835 that is usually ignored: the patient. A remittance that assigns a balance to the member becomes a statement, and a statement whose explanation does not match the explanation code on the remittance produces a call to the billing office. Parsing the reason codes properly is what makes the patient-facing explanation honest, and honest explanations are the cheapest reduction in billing calls available.
Finally, the remittance is a contract check. The allowed amount on the 835 is what the payer says the contract permits, and a provider that never compares the allowed amount to the contracted rate has no way to identify an underpayment. That comparison is a simple join between the remittance and the fee schedule, and it is the one audit that pays for itself almost immediately.
How I do it
I start with a month of real remittances and a full parse: payments, adjustments, PLBs, and the code combinations actually seen. That inventory is usually smaller than feared — a few dozen combinations account for most of the money — which makes the mapping work tractable.
Each combination gets a category, an owner and an action, and the unrecognised ones go to a review queue rather than a default bucket. The queue is the control that keeps the mapping honest as payers change meaning.
Then the balancing test. Every remittance must reconcile: payment plus adjustments must equal the billed amount minus the allowed amount, and PLBs must reconcile separately. A file that does not balance is rejected and investigated, not posted.
The underpayment check runs monthly: every paid line is compared to the contracted rate for its procedure and payer, and any line paid below contract is flagged with the difference. Disputes are raised from that list, with the remittance line as the evidence.
Artifacts you keep
- A parsed inventory of CARC/RARC combinations by dollar impact
- A code mapping with a named owner and action per combination
- An unrecognised-combination review queue
- A balancing test applied to every remittance before posting
- A denial trend report by cause, not by count
The 835 is the only source of truth for what was paid
Everything upstream of the remittance advice is a claim about intent. The 835 is the payer stating what it actually did: what was billed, what was allowed, what was paid, what was adjusted, and the reason codes behind each adjustment. Any system whose revenue figures are not derived from the 835 is reporting an estimate.
The practical consequence is that posting is where accuracy is won or lost, and posting errors are silent. A denial posted against the wrong encounter produces a work item that gets worked twice and a denial that never gets worked at all. Both look like normal activity in the day's totals.
Reconcile posted remittances against expected amounts weekly rather than annually. The drift is continuous and invisible until somebody reconciles, and by then the window for correcting the underlying claims has usually closed.
CARC and RARC mapping is a control, not a config
Claim adjustment reason codes and remittance advice remark codes combine to describe an adjustment, and the mapping from that combination to a posting outcome is where money quietly reconciles to the wrong claim. The mapping is usually maintained by one person, undocumented, and never reviewed.
Audit it quarterly against actual remittances. Pull a sample of 835s, apply the mapping by hand, and compare to what the system posted. Every divergence is either a mapping defect or a code combination nobody anticipated, and both are cheap to fix and expensive to leave.
Version the mapping and record which version was in force for each posting period. When a payer changes its code usage, the release note should tell you which postings are affected rather than leaving you to discover it through a reconciliation gap.
What to build around the 835
An ingestion path that is idempotent, because remittances get re-sent. A posting table that records the source file, the transaction, the claim and the adjustment, so any figure can be traced back to a received artefact. A reconciliation job that compares posted totals against the file totals per payer per day and fails loudly on mismatch.
And a queue for the codes the mapping does not recognise, worked weekly. Unmapped codes are the leading indicator that a payer changed something, and a queue that nobody works means you find out at the quarterly audit instead of the day it happened.
The underpayment check
Every paid line compared against the contracted rate for its procedure and payer. Any line paid below contract is a dispute with the remittance line as its evidence, and the comparison is a join between two tables you already hold.
Run it monthly. The recoverable amount is usually larger than the cost of the exercise by an order of magnitude, and it is recoverable only inside the payer's dispute window, which is why the cadence matters more than the sophistication.
The number that matters
Cash posted within thirty days of service, by payer, compared to the contracted expectation. Every other revenue-cycle metric is a leading indicator for that one, and organisations that can produce it weekly find their leaks in weeks rather than quarters.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Where this work is delivered
Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — x12 835 remittance — the scope, the failure modes it prevents and how the work is measured. It sits in the X12 and EDI category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.