How it works
Every remittance, read against the claim.
A claim says what your practice asked to be paid. A remittance says what the payer decided. Liquidity Health links the two, explains the difference, and organizes the follow-up.
- Your practiceSubmits the claim837
- The payerDecides and pays835 / EOB
- Liquidity HealthReads it against the claimevery remittance
- Your teamActs on the next stepwork queue
Step by step
From what the payer sent to what came back.
Three real cases, with names removed, show what Liquidity Health finds and what your team does with it.
What do we send?
Step 1: Your claims and your remittances.
Upload 837 claim batches and 835s, ERAs or EOBs through separate lanes. Liquidity Health extracts the data in the background, and nothing is saved to a claim until it has been reviewed. A remittance received twice is not counted twice.
UploadIllustrativeEDI 837 files
Batch details / claim batches
EDI 835 files
ERA, EOB, or payment-advisory documents
Select the correct uploader; extraction schemas are intentionally separate.
Background document extraction
- Uploaded
- 0/2
- Extracted
- 0/2
- Reviewed
- 0/2
Claims saved after review
What does LH find?
Step 2: What was billed, allowed, owed and paid.
Every payment is matched to your own claim number, with the payer's claim ID kept beside it. The difference between what the payer owed and what it paid becomes visible. For Claim C, the remittance alone shows $611.00 due from the payer and $199.00 paid.
Underpaid claimClaim C · remittance short payShortfall−$412.00Provable from the remittanceThe arithmetic
- Billed
- $810.00
- Allowed
- $611.00
- −Patient responsibility
- $0.00
- =Expected from payer
- $611.00
- −Paid
- $199.00
- =Shortfall
- $412.00
Allowed $611.00 − patient responsibility $0.00 = $611.00 owed by the payer, but $199.00 was paid.
What happens to a denial?
Step 3: Understand the payer's reason. See what to check next.
Liquidity Health reads the reason and remark codes, explains them in plain English and suggests a next step for your team to confirm. For Claim A, the remark code N211 rules out an appeal, so the suggestion is a corrected claim instead.
Selected denialClaim A · denial correctionSelected denial
••••9674
Payer A · 99454, 99457, 99458
Denial reason
N382Remittance Advice Remark (RARC)
Missing/incomplete/invalid patient identifier
Something on the claim is missing, invalid, or internally inconsistent, so it could not be adjudicated as submitted.
N211 explains the denial above
Alert: You may not appeal this decision
N211: this decision may not be appealed. Correct and resubmit instead.
Recommended action
Read the accompanying remark code - it names the exact field. Correct that element and submit a corrected claim rather than an appeal.
In practice: The remark code (N or M) tells you what is wrong. Fix it and resubmit as a corrected claim, not an appeal.
Responsibility: Provider. Appeal: No - correct and resubmit.
Work queue stage
1. New denial · step 1 of 4
Who does the work?
Step 4: Your team acts. The stage follows.
Your billers record what they did, and the claim moves through New denial, Working / On hold, Resubmitted or Appealed - Payer pending, and Resolved, with its filing window in view.
Recovery queueClaim A · denial correction1. New denial: 130 claimsat stake $34,892.152. Working: 9 claimsat stake $3,574.003. Payer pending: 31 claimsat stake $6,720.014. Resolved: 125 claimsrecovered $8,510.72••••9674Payer A · 99454, 99457, 99458
Work queue stage
1. New denial · step 1 of 4
Correct the flagged issue and resubmit.
Record what happened
Start workResubmittedFiling window: on track.
What about payments that are too low?
Step 5: Compare the payer's allowance with your contract.
Underpayments follow their own track. When a claim matches a loaded contract, Liquidity Health compares each line with the contracted rate. For Claim B, Payer B allowed $96.55 where the contract allows $144.83.
Underpaid claimClaim B · below contractAllowed below contract−$48.28Contract match, high confidenceThe arithmetic
Swipe the table for all columns →
Code Contract rule Contract allows Payer allowed 99214-25 × 1 Fixed 133.26 per unit $133.26 $87.07 95117-59 × 1 Fixed 11.57 per unit $11.57 $9.48 - Billed
- $255.00
- Contract allows
- $144.83
- −Payer allowed
- $96.55
- =Allowed below contract
- $48.28
On what it did allow, the payer paid $91.55 and assigned $5.00 to the patient. At that same split, about $45.78 of the gap is owed by the payer and about $2.50 would be added to patient responsibility. A deductible or flat copay changes this split.
Primary contract, Payer B Fee Schedule · in force 4/1/2026 – 3/31/2027
Priced at the non-facility rate from the claim's place of service.
Recovery stage
- 1. New / Review
- 2. Confirmed / Dispute in preparation
- 3. Disputed / Payer pending
- 4. Resolved / Payment
How do we know it worked?
Step 6: Track what came back, and what still needs work.
The claim journey keeps every submission and payer response on the same claim. Claim A came back as $121.39, 16 days after the denial. Money counts as recovered only when the payer actually pays.
Claim journeyClaim A · denial correctionRecovered-Recovered via payer reprocessed16 days after the denialClaim journey1 events
01Claim submittedBatch date 09/08
837 claim batch
Illustrative examples based on real dashboard records. Names, claim numbers and dates are changed.
It starts with a conversation.
Send your business contact details and a short note. Our team replies, talks through your practice and explains how claim files are shared securely. The analysis follows that conversation. No claim or patient data goes through this website.
01
Tell us about your practice
Business contact details and a short note. No claim or patient data on this website.
02
Our team reaches out
We talk through your practice and explain how claim files are shared securely.
03
Then the analysis
Liquidity Health reviews your claims after that conversation. It is not an instant result.














