Apply Employer Retirement Matching as Marginal Bands, Not One Flat Rate — Free
A plan saying '100% on the first band, then 50%' is not offering a 50% match on every dollar. Keep marginal bands visible before comparing a payroll contribution with the employer amount described in the plan.
The proof surface
Offer-perk comparisons list benefits, and family savings caps model a flat promise. This matrix performs a different reconciliation: contiguous marginal retirement-match bands with an explicit employee contribution percentage and unmodeled eligibility and true-up rules.
InputBand code | employee lower % | employee upper % | employer match % in band; employee contribution as percent of eligible pay
Rare deviceOffer-perk comparisons list benefits, and family savings caps model a flat promise. This matrix performs a different reconciliation: contiguous marginal retirement-match bands with an explicit employee contribution percentage and unmodeled eligibility and true-up rules.
Output artifactModeled employer contribution percentage with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Core band | 0 | 3 | 100; Stretch band | 3 | 5 | 50. Employee contribution as percent of eligible pay = 6. Modeled employer contribution percentage: 4 % eligible pay matched. All records are invented.
Before using the match-band matrix
Copy the band's lower and upper contribution percentages and the employer's marginal match rate from the actual plan explanation. Use percent of eligible pay, not gross pay unless the plan defines them as equal. This tool reports an employer percentage only; it does not infer a currency amount, annual tax limit, entitlement or investment return. Bands must start at zero, be ordered, touch exactly and have increasing endpoints up to 100%. A zero-rate band can explicitly represent an unmatched interval. If contribution extends above the final band, the excess is reported as outside the entered match schedule. Confirm whether actual matching occurs per paycheck, annually or with a true-up before comparing the model with a pay statement.
Why the flat version breaks
Applying the last rate to the entire contribution
The upper band rate applies only to employee percentage points inside that interval. At six percent with three points fully matched and two half matched, the modeled employer rate is four, not three. Read each marginal working rather than substituting one average-looking rate.
Allowing unexplained gaps or overlaps
A missing interval cannot be assumed to have the rate of its neighbor, and overlapping intervals can count the same contribution twice. The parser rejects both. Enter an explicit zero-rate band if the written plan truly leaves an interval unmatched, or ask the administrator to clarify the schedule.
Treating modeled match as vested money or tax advice
Contribution calculation, eligibility, vesting and tax treatment are separate questions. A percentage can reconcile arithmetically while no payment is yet due or while a yearly true-up applies. Keep those limitations with the result and have the plan administrator confirm the actual benefit before using it in a consequential decision.
How to work the match-band matrix
Obtain the marginal schedule and pay definition
Ask HR or the plan administrator for the written band schedule and the definition of eligible pay. A summary such as up to four percent can hide several bands and conditions. Do not reverse-engineer the schedule from one payroll deposit or assume that every employee is eligible for the same rates.
Enter every interval, including zero-rate bands
Use a lower percentage, a greater upper percentage and a non-negative marginal match percentage for each band. Begin at zero and continue without gaps or overlaps. A 50 in the match-rate cell means half of the employee contribution within that band, not half of eligible pay. Keep benefit identifiers and payroll account numbers out of row labels.
Clamp the employee contribution within each band
For lower L, upper U and employee rate E, the used employee percentage points are max(0,min(E,U)-L). Multiply those points by the band's match rate divided by 100. Add employer percentages across bands only after this marginal calculation. Report employee contribution beyond the final upper boundary separately so no undefined rate is silently extended.
Reconcile with a qualified plan explanation
Take the visible band workings to HR or the administrator and ask about eligibility, eligible-pay exclusions, annual limits, timing, true-up and vesting. Those conditions may explain a mismatch with actual payroll. Do not change retirement elections solely from the matrix; a qualified adviser can help place contribution choices in the person's wider financial context.
What the match-band matrix separates
Question
Before
Inspect this instead
Applying the last rate to the entire contribution
The upper band rate applies only to employee percentage points inside that interval. At six percent with three points fully matched and two half matched, the modeled employer rate is four, not three. Read each marginal working rather than substituting one average-looking rate.
Enter every interval, including zero-rate bands
Allowing unexplained gaps or overlaps
A missing interval cannot be assumed to have the rate of its neighbor, and overlapping intervals can count the same contribution twice. The parser rejects both. Enter an explicit zero-rate band if the written plan truly leaves an interval unmatched, or ask the administrator to clarify the schedule.
Clamp the employee contribution within each band
Treating modeled match as vested money or tax advice
Contribution calculation, eligibility, vesting and tax treatment are separate questions. A percentage can reconcile arithmetically while no payment is yet due or while a yearly true-up applies. Keep those limitations with the result and have the plan administrator confirm the actual benefit before using it in a consequential decision.
Reconcile with a qualified plan explanation
This match-band matrix replaces a manual count or calculation, not source verification or the responsible person’s review.
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.
Plan-schedule arithmetic only, not retirement, tax or employment-law advice or proof of benefits owed. Ask HR or the retirement-plan administrator to confirm eligible pay, timing, limits, eligibility and vesting; consult a qualified adviser before changing elections.
Data note: The match-band matrix processes Band code | employee lower % | employee upper % | employer match % in band locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a scored comparison matrix
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the match-band matrix reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The match-band matrix answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Plan-schedule arithmetic only, not retirement, tax or employment-law advice or proof of benefits owed. Ask HR or the retirement-plan administrator to confirm eligible pay, timing, limits, eligibility and vesting; consult a qualified adviser before changing elections.
What this is built on
Method: For lower L, upper U and employee rate E, the used employee percentage points are max(0,min(E,U)-L). Multiply those points by the band's match rate divided by 100. Add employer percentages across bands only after this marginal calculation. Report employee contribution beyond the final upper boundary separately so no undefined rate is silently extended.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: a headline match rate blurred marginal bands and benefit conditions. After: each used band contributes a visible percentage of eligible pay.
Three worked readings, with different inputs
Sample A — typical inputs
Core band | 0 | 3 | 100
Stretch band | 3 | 5 | 50
Setting: Employee contribution as percent of eligible pay = 6. Expected summary: 4 % eligible pay matched.
At an employee contribution of 6% of eligible pay, the first three percentage points receive a 100% match, producing 3% employer contribution. The next two receive a 50% match, adding 1%. The total is 4% of eligible pay. The final employee point above 5% lies beyond the entered bands and is explicitly unmatched in this model; the 50% top-band rate is not applied to the whole contribution.
Sample B — changed plan
First band | 0 | 4 | 50
Additional band | 4 | 8 | 25
Setting: Employee contribution as percent of eligible pay = 6. Expected summary: 2.5 % eligible pay matched.
The first four points at 50% produce 2%. Only two of the four available points in the next band are used because the employee contributes 6%, so that band contributes 0.5%. Total modeled employer contribution is 2.5% of eligible pay. An upper band endpoint of eight does not mean the employee contributes eight, and unused band space creates no employer payment.
Sample C — boundary convention
No-match band | 0 | 6 | 0
Setting: Employee contribution as percent of eligible pay = 6. Expected summary: 0 % eligible pay matched.
An explicit 0% match across the employee's six-point contribution produces zero employer contribution. Zero is a stated rate, not an omitted band. A schedule with a gap, overlap or nonzero starting boundary would be rejected rather than inventing a policy for that interval. Even a fully reconciled schedule leaves eligibility, vesting and pay-period true-up rules unresolved.
Optional AI formatting, never the calculation
Manual entry completes this match-band matrix 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 match-band matrix. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Band code | employee lower % | employee upper % | employer match % in band; the setting is Employee contribution as percent of eligible pay. 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.