Compare Embedded and Aggregate Deductible Accumulation Across Claims — Free
A family deductible can mean two different accumulation structures. Model the same ordered eligible claims both ways before asking a plan administrator how the actual plan credits each member.
The proof surface
One procedure against a deductible does not model member-specific embedded thresholds versus a shared aggregate family threshold across ordered claims.
InputClaim code | member code | deductible-eligible dollars | individual deductible dollars; shared family deductible ($)
Rare deviceOne procedure against a deductible does not model member-specific embedded thresholds versus a shared aggregate family threshold across ordered claims.
Output artifactAggregate minus embedded allocation plus complete labeled working
Cost$0 local core · no account, card, paid key or subscription · filing proposal has no checkout
Sample, not your facts: Invented records: Maple visit | Cedar | 1200 | 1000; Oak visit | Willow | 1500 | 1000; Pine visit | Cedar | 700 | 1000. Shared family deductible ($) = 3000; expected Aggregate minus embedded allocation: 1000 $ deductible difference. These are not quotations, verified observations or personal evidence.
Before using the embedded-deductible comparison slip
Use fictional member codes and only amounts already identified as deductible-eligible by a responsible source. Both scenarios start with zero year-to-date accumulation; neither is a replacement for a benefit statement. The embedded scenario caps each member at the entered individual amount and also caps the family total. The aggregate scenario uses only the family cap. Both consume claims in the order entered and exclude premiums, coinsurance, copays, covered-versus-denied determinations and out-of-pocket maximums. The tool compares structures; it does not determine which structure a plan legally or contractually uses, and it cannot tell you what to pay a provider.
Why the flat version breaks
Individual thresholds are added as guaranteed bills
An individual threshold is a cap on modeled deductible allocation, not an amount automatically owed by every family member. Claims below it only use their eligible amount. Adding all member thresholds without claims invents liability. This slip instead shows exactly which row consumed which portion of a cap, and a member with no eligible claim contributes nothing to the entered comparison.
The family cap disappears after a member is capped
An embedded model has two limits, not one. If the family pool is exhausted first, remaining members can add no more modeled deductible dollars even if their individual pools have headroom. Omitting that second minimum overstates embedded allocation. The same eligible claim stream is used for both scenarios so the difference can be attributed to accumulation structure rather than different medical use.
Deductible arithmetic is sold as a coverage decision
Eligibility, network status, benefit exceptions and coinsurance are outside this model. A smaller deductible allocation is not a verified cheaper plan or a guarantee of a lower actual bill. The slip deliberately does not label one plan a winner. Keep the policy and explanation of benefits as authoritative source documents and have the administrator resolve any discrepancy before you rely on the numbers.
How to work the embedded-deductible comparison slip
Choose one accumulation period
Take claims from one modeled plan year and put them in the intended processing order. Do not mix an old deductible balance with a fresh zero-start illustration. Give repeated member claims the same non-sensitive code. The same code must carry the same individual threshold on every row, otherwise the parser refuses an internally inconsistent plan. The claim code is a unique reference for the arithmetic, not a medical record identifier that should be pasted into a public sharing link.
Separate eligible amounts from the total bill
Transcribe the amount that is supposed to enter the deductible, not the sticker price or every component of a statement. Keep dollars to at most two decimal places. A service with no deductible-eligible amount may be represented by zero, but it still may have other liability outside this slip. The family setting is shared across all rows. Neither threshold is a recommended benefit choice; both are reader-supplied terms for a controlled comparison.
Apply the two remaining-cap calculations
For the embedded scenario, allocate the smaller of the eligible claim, that member’s remaining individual deductible and the remaining family deductible. For the aggregate scenario, allocate the smaller of the claim and the remaining family deductible. Track those pools separately; an embedded member reaching a threshold does not automatically meet the family total. Cents are represented as integers, so a cap is never exceeded by floating-point drift. Row differences reconcile to aggregate total minus embedded total.
Ask a narrow question with the slip
Read the two accumulator totals and the member-specific notes, then ask the plan administrator whether those are the correct structures, amounts and period for the actual policy. Do not make treatment timing, provider choice or payment decisions from a hypothetical deductible difference. A full benefit comparison needs much more than this slip. The printable or CSV prototype preserves assumptions; it does not turn your inputs into confirmed coverage or a bill payable.
What the embedded-deductible comparison slip keeps distinct
Question
Before
Check this working
Individual thresholds are added as guaranteed bills
An individual threshold is a cap on modeled deductible allocation, not an amount automatically owed by every family member. Claims below it only use their eligible amount. Adding all member thresholds without claims invents liability. This slip instead shows exactly which row consumed which portion of a cap, and a member with no eligible claim contributes nothing to the entered comparison.
Separate eligible amounts from the total bill
The family cap disappears after a member is capped
An embedded model has two limits, not one. If the family pool is exhausted first, remaining members can add no more modeled deductible dollars even if their individual pools have headroom. Omitting that second minimum overstates embedded allocation. The same eligible claim stream is used for both scenarios so the difference can be attributed to accumulation structure rather than different medical use.
Apply the two remaining-cap calculations
Deductible arithmetic is sold as a coverage decision
Eligibility, network status, benefit exceptions and coinsurance are outside this model. A smaller deductible allocation is not a verified cheaper plan or a guarantee of a lower actual bill. The slip deliberately does not label one plan a winner. Keep the policy and explanation of benefits as authoritative source documents and have the administrator resolve any discrepancy before you rely on the numbers.
Ask a narrow question with the slip
The embedded-deductible comparison slip replaces this named manual reconciliation, not source verification or the responsible human's decision.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Illustrative benefit arithmetic, not medical, insurance or legal advice and not a bill. Verify deductible eligibility, accumulation period and actual plan structure with the insurer or plan administrator before changing care or paying a claim.
Data note: This embedded-deductible comparison slip calculates in the tab from Claim code | member code | deductible-eligible dollars | individual deductible dollars. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.
Go deeper: the companion app files the same reading as a till receipt with a tear-off foot
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the embedded-deductible comparison slip reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
Keep the complete embedded-deductible comparison slip answer free; optional filing proposes its boundary-preserving print, row-and-summary CSV and five local reading summaries. The $4 one-time prototype is not for sale; another calculation remains free in the article demo.
Illustrative benefit arithmetic, not medical, insurance or legal advice and not a bill. Verify deductible eligibility, accumulation period and actual plan structure with the insurer or plan administrator before changing care or paying a claim.
What this is built on
Declared local method: For the embedded scenario, allocate the smaller of the eligible claim, that member’s remaining individual deductible and the remaining family deductible. For the aggregate scenario, allocate the smaller of the claim and the remaining family deductible. Track those pools separately; an embedded member reaching a threshold does not automatically meet the family total. Cents are represented as integers, so a cap is never exceeded by floating-point drift. Row differences reconcile to aggregate total minus embedded total.
Every sample code, measurement, date, price, fingerprint and scenario is invented. Artifact checks do not verify reader data, policies, actual files, tickets, votes or health/accessibility outcomes.
Google’s official Gemini pricing page, fetched 2026-10-01, lists AI Studio access in its Free section, limited model access and free input/output tokens. Free-tier content may be used to improve products. Optional external formatting may require an account; limits/access can change. Manual local entry needs none. Do not send sensitive records.
Before: one family deductible number hid two accumulation rules. After: the same eligible claims have separate member and family pools with visible caps.
Three worked readings, with different inputs
Sample A — typical inputs
Maple visit | Cedar | 1200 | 1000
Oak visit | Willow | 1500 | 1000
Pine visit | Cedar | 700 | 1000
Embedded accumulation assigns Cedar 1,000 on the first claim, Willow 1,000 on the second, and Cedar zero on the third because that member threshold is already met. Total modeled deductible dollars are 2,000. An aggregate-only model instead accumulates 1,200, 1,500 and the remaining 300 to reach the 3,000 family threshold. The 1,000 difference concerns deductible allocation only; none of the excluded copays, coinsurance or network rules has been verified.
Both members remain below the 1,000 individual figure, and their combined 1,700 is below the 3,000 family cap. Each model therefore allocates the same deductible dollars. A zero difference does not prove these plans have identical patient bills. This input supplies only eligible amounts and thresholds; premiums, out-of-pocket caps, services excluded from deductibles, benefit limits and post-deductible liability could still differ substantially.
A zero deductible-eligible amount adds nothing to either modeled accumulator. It is included to show that an entered service can be outside this calculation, not that the real service is free. If an explanation of benefits has a copay or denied amount, that figure is not silently recast as deductible-eligible. Ask the plan administrator which amount belongs in this model and preserve the actual benefit document separately.
Optional AI formatting, never the calculation
Manual entry completes this embedded-deductible comparison slip for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a embedded-deductible comparison slip. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Claim code | member code | deductible-eligible dollars | individual deductible dollars; the setting is Shared family deductible ($). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.