Same-Day Claim Settlement: What Actually Settles, and When It Can Be Taken Back

Search "same day claim settlement" and you will get pitches from four different kinds of company. A clearinghouse, a bank, a factoring firm, and a payments platform will all use the phrase, and they are describing four products that expose you to four different risks.

The word doing the work is settlement. In payments, settlement is a property of money: funds have moved and cannot be pulled back. In billing, "settled" colloquially means the payer has decided what it owes. A product can be same-day on one of those and completely silent on the other — and the gap is where practices get hurt.

This article separates the four products, traces one synthetic payer deposit — two claims and a recoupment — through the arithmetic that tells you which one you actually bought, and ends with the five questions to put to any vendor using the phrase.

Four products, one phrase

A. Real-time adjudication. The payer returns a decision synchronously instead of on a batch cycle. This is the only one of the four that compresses the decision. It exists, it is payer-specific, and coverage is uneven — treat it as a per-payer capability question, not an industry norm [verify which of your payers and your clearinghouse support real-time claim adjudication, and for which claim types].

B. Instant transit of an already-adjudicated payment. Once the payer knows what it owes, the money moves over an instant rail (FedNow, RTP) instead of a one-to-two-day ACH cycle. Real, and irrevocable at the rail — but it starts only after adjudication finishes, so it shortens the tail, not the wait.

C. An advance against a submitted-but-unadjudicated claim. Money on day one, before anyone knows what the claim is worth. This compresses nothing. It moves the wait onto a lender's balance sheet and charges you for the accommodation. That is a legitimate product — it is also a credit product, and it should be priced as one.

D. Same-day collection of the patient share. The moment the 835 posts, you know the exact PR-group total, and you can request it over an instant rail that same hour. This is the one an independent practice can turn on unilaterally, with no payer dependency and no borrowing.

A, B, and D shorten real intervals. C converts an interval into a fee. Any vendor that will not tell you which letter it is selling has told you which letter it is selling.

Why the standard path isn't same-day

The delay is structural, and it stacks in three places.

Adjudication runs on a cycle. Most payer systems adjudicate in batches and pay on a separate schedule, so a claim that finishes adjudicating on Tuesday can still wait for the next payment run [verify with your specific payers]. On the Medicare side there is also a statutory payment floor — clean electronic claims cannot be paid before a minimum interval after receipt, which is a legal minimum, not a processing artifact [verify the current CMS provision]. State prompt-pay statutes cap the far end but do not compress the near end [verify your state's statute].

ACH is a batch, store-and-forward, reversible rail. Reversibility is why it settles on a banking calendar. You cannot have same-second finality and a multi-day return window in one system.

The money and the explanation travel separately. The EFT arrives through your bank; the 835 arrives through your clearinghouse. Reassociation is a distinct operational step — the CAQH CORE EFT/ERA rule exists because this leg breaks routinely [verify current CORE rule version]. A deposit you cannot post is not collected revenue; it is an unidentified credit sitting in a suspense account.

And there is a fourth thing, which no rail addresses at all.

Worked example: one deposit, two claims, one recoupment

Commercial payer, two established-patient claims, one EFT. All values below are synthetic and contain no patient data.

BPR*I*170.00*C*ACH*CCP*01*011000015*DA*9876543*1234567890**01*021000021*DA*5555555*20260807~
TRN*1*0805117433*1234567890~
CLP*PCN-77105*1*195.00*112.00*25.00*12*ICN-2026-0723-4410*11~
SVC*HC:99213*175.00*112.00**1~
CAS*CO*45*38.00~
CAS*PR*3*25.00~
SVC*HC:36415*20.00*0.00**1~
CAS*CO*97*20.00~
CLP*PCN-77219*1*260.00*148.00*30.00*12*ICN-2026-0723-4415*11~
SVC*HC:99214*260.00*148.00**1~
CAS*CO*45*82.00~
CAS*PR*2*30.00~
PLB*1234567890*20261231*WO>ICN-2026-0512-0455*90.00~

Every service line balances — `SVC02` = `SVC03` + the sum of that line's `CAS` amounts:

• 99213 — 175.00 = 112.00 + 38.00 (CO-45) + 25.00 (PR-3 copay) ✓
• 36415 — 20.00 = 0.00 + 20.00 (CO-97, bundled into another service) ✓
• 99214 — 260.00 = 148.00 + 82.00 (CO-45) + 30.00 (PR-2 coinsurance) ✓

Each claim ties out the same way. PCN-77105: CLP03 − CLP04 = 195.00 − 112.00 = 83.00, which is 38.00 + 25.00 + 20.00, and CLP05 = 25.00 — the PR total. PCN-77219: 260.00 − 148.00 = 112.00 = 82.00 + 30.00, and CLP05 = 30.00.

Billable to patients: $55.00. The $140.00 in CO-45 and CO-97 is contractual — putting it on a statement is balance billing under a participating-provider agreement. Note the 36415 specifically: charged, allowed at zero, bundled, and owed by nobody.

Now the segment most same-day pitches never mention. Claim payments total 112.00 + 148.00 = 260.00. The deposit is BPR02 = 170.00. The difference is the PLB:

`Σ CLP04 − Σ PLB adjustments = BPR02` → `260.00 − 90.00 = 170.00` ✓

WO is overpayment recovery. A positive PLB amount reduces the payment [verify against the current X12 835 TR3]. The payer is clawing back $90.00 on ICN-2026-0512-0455 — a claim from three months earlier that was already paid, already posted, and, if it moved over an instant rail, already irrevocably settled.

That is the point. Finality at the payment rail is not finality of the receivable. The rail cannot reverse a FedNow credit; the payer does not need it to. It nets the recovery out of the next deposit. Any product that funds you early has to answer for this, and the four products answer very differently.

The four products against that deposit

Five questions, in order:

1. Which letter is this? Make them say it. If the answer is C, the rest of the pitch is a rate sheet.
2. What triggers the money — an 835, or a submitted claim? Funding before adjudication means funding before the amount is known.
3. Who eats the recoupment? Ask them to walk through a PLB WO on a claim they already funded. If it is recourse to you, that is not settlement; it is a loan with a collateral test.
4. What reconciliation artifact do I get? A lump deposit with no line detail rebuilds the reassociation problem on a faster rail. You need SVC-level posting or the speed buys you nothing.
5. What happens to the patient balance? It must be derived from the PR group — $55.00 here, never charges-minus-payments, never the CO amounts.

FAQ

My clearinghouse advertises same-day claim settlement. Is that real? Probably, for some definition — ask which. If they mean real-time adjudication with a specific payer list, that is product A and it is genuinely valuable for the payers on the list. If they mean they will fund you on submission and collect from the payer later, that is product C, and the "settlement" is between you and them, not you and the payer. The tell is question 2: what triggers the money. A product that pays you before the payer has priced the claim cannot know what it is paying you for.

How do I price an advance against a claim? Convert the fee to an annualized rate against the days you actually gained. If a funder advances against a $260.00 claim for a flat fee and the payer would have paid on day 21 anyway, the cost is (fee ÷ amount advanced) × (365 ÷ 21). Run it with your own median days-to-payment from BPR16, not the funder's assumed timeline. Then add the recoupment exposure from question 3, which is not in the fee. Vendor-published ROI figures will not reflect your payer mix [verify against your own data].

What part of same-day can I turn on without a financing product? Two things, both unilateral. First, close the reassociation gap: retrieve and post the 835 at the service-line level the day it lands, PLB segments included, so the 170.00 deposit reconciles to 260.00 minus a $90.00 recovery instead of sitting unidentified. Second, route the PR-group total to a request for payment the same day — no stored card credential, no NSF or chargeback exposure, and irrevocable when the patient accepts. On the HIPAA question, ask for the mechanism, not the assurance: the payment instruction should reference an opaque encounter token, PHI stays in your system of record, and remittance parsing touches only the financial segments. Then confirm the compliance layer separately — executed BAA, documented payload policy, your own configuration. All three are required.

Run the tie-out on your own 835

The shteg.ai sandbox takes a de-identified 835 and returns the arithmetic above on your data: SVC02 = SVC03 + CAS validated on every line, claim-level tie-out against CLP03 − CLP04, the PR-group total isolated as the billable patient amount, and — the one most postings miss — the deposit reconciliation Σ CLP04 − Σ PLB = BPR02, with every WO recovery matched back to the original ICN it is being taken from.

Bring one 835 where the deposit didn't match what you posted. The PLB block is usually the whole explanation, and it is also the answer to question 3 for every same-day vendor you talk to.

[Open the shteg.ai sandbox →](/sandbox) [verify link target before publish]

Educational content for physicians, practice administrators, and revenue-cycle staff. Not legal, billing, coding, compliance, or financial advice. All segment values, claim identifiers, control numbers, dates, and dollar figures in this article are synthetic illustrations and contain no patient data. X12 835 specifications (including `PLB` adjustment conventions), CAQH CORE operating rules, Nacha rules, CMS payment provisions, and FedNow and RTP network capabilities and limits change over time — verify current specifications with your clearinghouse and financial institution before making operational decisions. Advances against receivables are credit products; terms, recourse provisions, and total cost vary by agreement. Payment timing obligations, patient billing, and balance-billing restrictions are governed by your payer contracts and by applicable state and federal law; consult counsel for your jurisdiction.

Draft notes: ~1,690 words. H1 + 6 H2s (4 body + FAQ + CTA). Angle divergence: fast-payment-1 decomposes AR into four clocks; fast-payment-2 covers FedNow network mechanics and the enrollment chain. This draft is a product-taxonomy piece — the query "same day claim settlement" returns four distinct products, one of which is credit — and it is the only one of the three built on PLB / BPR02 deposit reconciliation, i.e. the argument that rail finality ≠ receivable finality. No overlap in worked-example segments, table axes, or FAQ questions. Worked example carries the required SVC02 = SVC03 + CAS form on all three lines with per-claim tie-out (CLP05 = PR total on both), plus the deposit-level identity Σ CLP04 − Σ PLB = BPR02 (260.00 − 90.00 = 170.00). Comparison table is four-product on trigger, funded amount, amount-known-at-funding, line detail, recoupment incidence, product type, and availability. Ten [verify] flags: real-time adjudication payer support, payer batch/payment cycles, CMS payment floor, state prompt-pay, CORE rule version, 835 TR3 PLB sign convention, vendor advance terms, payer-side instant rail support, own-data ROI, sandbox link. No statistics asserted — all figures belong to one labeled synthetic deposit; the advance cost is given as a formula, not a rate. PR-vs-CO balance-billing guardrail stated at the point the patient amount is derived, with the CO-97 bundled line as a second instance. HIPAA answered with mechanism plus BAA/configuration caveat. Primary-source pointers: X12 835 TR3, CAQH CORE EFT/ERA reassociation rule, Nacha operating rules, CMS Medicare claims processing manual, FedNow and RTP operating rules. Blocking before publish: §5 requires a named physician or revenue-cycle reviewer — currently unassigned.

Want me to save this as examples/seo-presence/workspace/drafts/fast-payment-3-<id>.md to match the pipeline convention? The other drafts use a short base-36 timestamp slug (msr7cpec) — give me an ID in that format, or say the word and I'll generate one.

<!-- generated_by: claude-draft-1 -->