Accuracy record
Where widely-published reference values are wrong, and where ours were. Every finding names the governing instrument and tells you how to check it without trusting us.
This exists because provenance is the product. Anyone can publish a number. The claim worth making is that a number was read from the instrument that creates it, on a date, and is re-checked — and that claim is only worth anything if we also publish what we got wrong.
Findings come from reading primary sources, not from comparing one aggregator against another. Where a discrepancy could not be reproduced from a public document, it is not listed. We name instruments, not vendors.
Where commonly-published values are wrong
6 findings.
Belize — public holidays do NOT all shift to Monday
Commonly published: That Belize holidays falling on a weekday other than Monday are observed on the following Monday, applied as a blanket rule. This appears on Wikipedia and is reproduced by multiple commercial holiday APIs and calendar libraries.
What the source actually says: There is no such blanket rule. Checking six consecutive official notices, the dates gazetted do not follow it: holidays are listed on their actual dates in years where the supposed rule would have moved them. The rule is a plausible-sounding generalisation that the primary source contradicts.
Instrument: Belize Statutory Instruments declaring public and bank holidays, read across six successive years rather than one
Check it yourself: Take any year's Belize public-holiday Statutory Instrument and compare the gazetted dates against what the Monday rule would predict. They diverge. One year could be an exception; six is a refuted rule.
Malta — 5% is not the corporate tax rate
Commonly published: That Malta's effective corporate tax rate is 5%, often stated flatly as though it were the rate a company pays.
What the source actually says: The statutory rate is 35% and it is genuinely paid by the company. Under full imputation, shareholders receiving distributions from specified tax accounts may then claim a REFUND — commonly six-sevenths on active trading income, giving a 5% net outcome, or five-sevenths on passive interest and royalties, giving 10%. Those are shareholder-level outcomes claimed after distribution, not the corporate rate. A payroll or provisioning calculation using 5% as the company's rate is wrong by 30 points.
Instrument: Income Tax Act, Cap. 123, read with the Income Tax Management Act
Check it yourself: Look for who claims the refund. If it is the shareholder and only after a distribution, it is not the company's tax rate.
Slovenia — the '7% minimum effective corporate rate' is out of date
Commonly published: That Slovenia has a minimum effective corporate tax rate of about 7%.
What the source actually says: The rule is a 63% cap on aggregate reductions of the tax base (ZDDPO-2 Art 59.a), leaving a minimum taxable base of 37%. 7.03% was 19% × 37% — correct only while the headline rate was 19%. The rate has been 22% since 2024, so the figure is 8.14%. Separately, the 22% is not in ZDDPO-2 at all: Art 60 still reads 19%, and the 22% is an override in ZORZFS Art 64 enumerated for 2024–2028 only, reverting to 19% for tax year 2029.
Instrument: ZDDPO-2 Arts 59.a and 60; ZORZFS Art 64 (Uradni list RS 131/2023)
Check it yourself: Multiply the current headline rate by 37%. If a published 'minimum effective rate' does not move when the headline rate moves, it is stale.
Cyprus — the late-payment law is N. 123(I)/2012, not 73(I)/2012
Commonly published: That Cyprus transposed the Late Payment Directive by Law 73(I)/2012.
What the source actually says: 73(I)/2003 was the repealed predecessor, transposing the earlier Directive 2000/35/EC. The instrument in force is N. 123(I)/2012 as amended by N. 227(I)/2022. Citing the repealed law points a reader at superseded payment terms.
Instrument: Ν. 123(Ι)/2012 as amended by Ν. 227(Ι)/2022
Check it yourself: Check which Directive the cited law transposes. 2000/35/EC means you have the repealed one.
Slovenia — payment terms are not '30 days by default, 60 by agreement'
Commonly published: That Slovenian B2B payment terms default to 30 days and may be extended to 60 by agreement.
What the source actually says: Three distinct rules are being collapsed into one. The B2B cap is 60 days by ordinary agreement (ZPreZP-1 Art 10(1)); beyond 60 days requires writing and must not be grossly unfair (Art 10(2)); 30 days is the gap-filler when nothing was agreed (Art 12), and separately the cap where the debtor is a public authority (Art 11(1)).
Instrument: Zakon o preprečevanju zamud pri plačilih (ZPreZP-1), Uradni list RS 57/2012
Check it yourself: Read Arts 10, 11 and 12 together. They answer three different questions.
Luxembourg — 3% is the broad rate, 8% is the narrow one
Commonly published: An assumption, carried over from how most member states are structured, that the higher reduced rate covers the essentials basket.
What the source actually says: Luxembourg inverts the usual pattern. The 3% super-reduced rate carries food, non-alcoholic drinks, books, pharmaceuticals, hotels, restaurants and passenger transport. The 8% rate is narrow: hairdressing, gas and electricity, bicycle and shoe repair, cleaning. Applying 8% to food would overcharge by five points.
Instrument: Loi modifiée du 12 février 1979 concernant la taxe sur la valeur ajoutée
Check it yourself: Look up which annex food sits in, rather than assuming the higher reduced rate is the general one.
Where we were wrong
5 errors found in data or code we had already shipped. All are fixed; each is listed with what caused it.
Colombia — we were missing a holiday created mid-year
What was wrong: Ley 2578/2026 created a public holiday on Monday 13 July 2026, effective on promulgation. We had served Colombia's 2026 calendar without it. Confirmed observed by the Cámara de Representantes. A working-day count spanning that date would have been one day out.
Instrument: Ley 2578/2026
Check it yourself: Compare our /v1/co/public-holidays against the law's promulgation date.
Namibia — we were missing Genocide Remembrance Day
What was wrong: 28 May was declared by Proclamation 19/2024 (Government Gazette 8373). We had not carried it. Same class of failure as Colombia: a holiday created by an instrument issued after we first built the calendar.
Instrument: Proclamation 19/2024, Government Gazette 8373
Check it yourself: Compare our /v1/na/public-holidays against the proclamation.
Angola — we modelled a repealed article
What was wrong: We were missing 23 March and were applying the pre-2018 Artigo 6.º weekend-transfer rule, which had been amended. Two errors compounding: a missing day, and a transfer rule that moved other days incorrectly.
Instrument: Lei that amended Artigo 6.º (post-2018 text)
Check it yourself: Compare our /v1/ao/public-holidays against the consolidated law currently in force.
Papua New Guinea — we added two days that do not exist
What was wrong: Building PNG's 2027 calendar we added Somare Remembrance Day and Easter Sunday. Neither is statutory: the Remembrance observances rest on one-off s.5 declarations with no recurring basis, and s.1(1)(b) covers only Good Friday and the following Saturday and Monday. Caught by a cross-year name-set comparison against our own 2026 data and removed.
Instrument: Public Holidays Act (PNG), ss. 1(1)(b) and 5
Check it yourself: Read s.1(1)(b). Easter Sunday is not in it.
We returned HTTP 500 on two countries for part of a day
What was wrong: A guard added to stop working-days selling wrong answers past our calendar coverage did not account for holiday entries with a deliberately null date (ungazetted placeholders). Sorting put null last and the coverage computation threw. Trinidad and Guyana returned 500 until it was fixed. The guard itself was correct and necessary; the null-handling was not.
Instrument: (internal — commit 8087e21 through d4dc14b)
Check it yourself: POST /v1/answers/working-days for tt or gy. It now refuses or answers, never 500s.
What changed so these are caught sooner
The Colombia, Namibia and Angola errors share one cause: a value that was correct when written and was invalidated later by a new instrument. Freshness checking cannot catch that, because the value never changed — what changed was the world. Two things now run against it:
- A weekly holiday-integrity audit that compares calendars across years, flags expired placeholder dates, and catches regional days duplicating national ones. It is what caught the Papua New Guinea additions.
- Daily source provenance — every cited source is fetched, hashed and re-checked, so if the document behind a value is amended or disappears, that surfaces rather than sitting silently. See /provenance.
Neither is sufficient. Both are better than a last_confirmed date that only says someone looked.
Found something wrong?
Send the instrument. api@3l-groupconsulting.co.za — corrections with a primary source are acted on and credited here.