FreeToolHub

Data Corrections & Change Log

Last updated: September 1, 2026

We keep a public record of corrections

Being open about mistakes is part of being trustworthy. When we find a data error — whether through our own automated freshness checks, a manual re-verification, or a report from a user — we fix it and record it below. Hidden fixes and silent edits are against our policy.

Correction log

Corrections & Updates (6)
✏️
Corrected progressive state income tax bracket boundaries was wrong for several states after a re-verification against each state Department of Revenue portal. Flat-rate states clarified, and the 9 no-income-tax states (AK, FL, NV, NH, SD, TN, TX, WA, WY) were explicitly recognized.
2026-06-18 · State Departments of Revenue
correction
✏️
Clarified that avgLocal/maxLocal sales-tax fields represent pure local rates (not combined with state rates) to prevent a common double-counting mistake in the sales-tax tool.
2026-08-17 · Sales Tax Institute / Avalara
correction
✏️
RMD calculator switched to the IRS Uniform Lifetime Table (2022 R2) and updated the insufficient-distribution excise tax messaging to reflect the SECURE Act 2.0 reduction from 25% to 10%.
2026-07-11 · IRS Pub 590-B
correction
✏️
Fixed a rounding bug in the long-term capital gains tool that mis-bracketed income exactly at a 0%/15% boundary. No data-source change; a formula correction.
2026-01-15 · Internal QA
correction
🔄
Applied the 2026 EU VAT rate table across all 27 member states following the annual EU Council publication.
2026-01-01 · EU Council
update
🔄
Bumped the 401(k) contribution limit dataset to the 2025 IRS figure ($23,500; $31,000 for age 50+) as published by the IRS.
2025-11-01 · IRS Newsroom
update

How we detect data problems

  • Automated freshness checks — each dataset has a freshness threshold; anything past it is flagged and re-verified.
  • Validation rules — datasets carry range and required-field checks to catch malformed or implausible values automatically.
  • Manual review — tax and legal datasets are re-checked against primary sources on a set schedule.
  • User reports — corrections noticed by visitors are logged here after they are confirmed.

How to report a problem

Found a wrong rate, a broken calculation, or a value that doesn't match an official source? Please tell us. Include the tool page, the value you expected, and a link to the authoritative source if you have one. Email [email protected] or use the contact form. We aim to respond within 48 hours.

Correction process

  1. We verify the report against the cited primary source.
  2. If confirmed, we correct the dataset and update its last-verified date.
  3. We add an entry to this log with the date, type, and source.
  4. The relevant tool page reflects the fix on its next verification date.

See how our data is classified and verified in the Methodology page, and how we handle your privacy in our Privacy Policy.