Product
Denials are where we start.
The remittance is where the money is.
A denied claim is the most visible way to lose money on a claim that was earned, so it is the one everyone sells against. But a single remittance usually carries three separate problems: a denial, an underpayment the payer never told you about, and occasionally a payment you should not have received at all. Hypex works all three, from the same file.
What gets produced
Six documents, chosen per claim. Not always an appeal.
The engine reads the remittance and decides which instrument the claim actually calls for. Sending an appeal for a claim that needed a corrected submission is a fast way to lose it, so the routing decision is made before a word is written.
Appeal letter
The denial is disputable and the evidence is on file.
A letter addressed to the payer's appeals department by name, built on the appeal guidance we hold for that payer's denial code, quoting the chart sentences that answer each criterion.
Not a form letter. If no criterion is provable, it says so instead of asserting one.
Request for retrospective authorization
A service was rendered and authorization was required but never obtained.
A formal request asking the payer to authorize after the fact, rather than an appeal arguing a denial that was never issued.
These are two different documents and payers treat them differently. Sending the wrong one loses the claim.
Corrected claim
The claim was coded wrong, or the payer asked for a corrected submission.
A corrected 837 with the corrected CPT and ICD-10, submitted through your existing clearinghouse path.
It refuses to generate without real corrected codes. A corrected claim with an assumed code is a false claim.
Coordination of benefits redirect
The payer paid and believes another carrier is primary.
A redirect to the correct primary payer with the remittance evidence, so the claim is not written off by a payer who simply will not answer for it.
Only raised when the remittance shows the balance still outstanding, so it cannot chase a patient who has already paid.
Patient responsibility confirmation
The balance went to the patient and was never collected.
A confirmation request to the patient, with the amount and the reference the office needs to close the balance.
Written for the payer or the contract owner, not for a clinical reviewer - wrong recipient, and the dispute stalls.
Contractual review
The denial is not a clinical disagreement but a payment or edit issue.
A written review of the contract terms against what was actually allowed, for the cases where appealing is the wrong instrument.
Appealing a payment edit wastes the filing window and hardens the payer's position on a claim that was never denied.
The rest of the remittance
Two kinds of loss produce no denial notice at all.
An underpayment is silent. There is no letter from the payer to chase, so it never enters a denial queue and never gets worked - it simply becomes a write-off that nobody can explain. These are the findings a recovery audit usually turns up first.
Underpayments
Paid, but paid wrong.
A claim that pays at the wrong rate is not a denial - it produces no denial notice, so it never enters a denial queue and never gets worked. Hypex compares what was allowed against what the contract allows, and drafts the dispute letter where the difference is worth disputing.
Rate variance detected against contract, dispute drafted with the variance quantified
Overpayments
Paid twice, or paid after the fact.
An 835 can be a payment event or a restatement of an earlier one, and the difference decides whether you have been double-billed or have overpaid. Hypex tells them apart before it reports a variance, so the number it shows you is a real one and a real refund is not filed against a payment that never happened.
Event vs. restatement resolved before reporting, refund or report, whichever the record actually calls for
Eligibility
Paid by the wrong carrier.
Eligibility and benefit responses (277) are read alongside the remittance, so a claim paid by a payer who was never primary is caught and routed to the carrier who is.
277 ingest, primary-payer mismatch detected at remittance
What it refuses to do
A letter that oversells gets overturned.
The fastest way to lose an appeal is to assert something the record does not support. A reviewer reads one unsupported claim and discounts the rest. So the engine is built to hold back, and every limit below is enforced in code rather than left to whoever is operating the account that day.
It will not invent a criterion
If a criterion cannot be traced to a specific sentence in your record, the letter does not claim it. The gap goes to your reviewer as a worklist instead, naming what to fetch.
It will not invent a payer policy
Criteria are only quoted as a payer's own when a person has transcribed and verified that payer's policy document. Everything else is labelled as derived and offered for the reviewer to confirm - never dressed up as the payer's rule.
It will not file a corrected claim it had to guess
A corrected claim is refused outright until the real corrected CPT and ICD-10 are supplied. Generating one with an assumed code would be a false claim, so the engine blocks rather than produce one.
It will not address a letter to a number
Letters go to the payer's appeals department by name. Where a payer is not recognised, the letter says so in words rather than printing a clearinghouse ID into the salutation - an ID there reads as machine output to the reviewer who has to decide it.
The free audit tells you which of these you have.
Send one remittance file. You get back the denials, the underpayments, the overpayments and the deadlines, with what each one is worth and which instrument it needs. No account, no commitment, and you keep the findings either way.