Data Quality & Integrity Controls
Trust in the figures rests on what happens before they are published. GeoBusinessIQ enforces a set of deterministic, build-time controls: data is validated against typed schemas, references must resolve, prose is checked for hype and invented dates, and the whole build fails if any check fails. The controls are code, not a style guide.
Last updated:
Quick answer
Every figure is typed and schema-validated at build, every source and cross-reference must resolve, marketing language and invented dates are rejected by tests, and the static build fails if any check fails — so nothing ships unvalidated.
Validated at build, not at runtime
Every dataset entry is parsed through a typed schema when it loads. A field of the wrong type, an over-length meta description, or an unknown enum value throws immediately and stops the build — invalid data cannot reach a page.
Referential integrity
Each source, ranking, calculator, country, comparison, structure, and sibling-topic reference is checked against its registry at load. An unknown identifier is a build error, so there are no broken citations or dead internal links in production.
Tone and honesty checks
Tests scan content for banned marketing phrases and for exact calendar dates in cadence-only fields, and they enforce unique titles and meta descriptions. The aim is to make over-claiming and date-rot fail the build rather than rely on review.
| Control | Enforces | Failure mode |
|---|---|---|
| Schema validation | Field types, lengths, enums | Build throws at module load |
| Reference integrity | Sources, rankings, calculators, countries, topics resolve | Build error on unknown id |
| Banned-phrase scan | No marketing or guarantee language | Test fails |
| Cadence-only dates | No exact filing dates in deadline prose | Test fails |
| Metadata uniqueness | Unique titles + meta descriptions | Test fails |
| Freshness audit | Valid, non-future ISO dates | Test fails |
Integrity controls and what they enforce
Methodology notes
- These controls are enforced by the same test suite that must pass before any deploy; a failing check blocks the static export.
- Numeric rates live once on the country record and are never restated in prose, so a figure cannot disagree with itself across pages.
Data limitations
- Controls verify structure, references, tone, and dates — they confirm a figure matched its source at review time, not that the underlying law is unchanged today.
FAQ
- What happens if a source reference is wrong?
- The loader throws at build time and the static export fails, so a page with an unresolved source or cross-reference cannot ship.
- Do these controls verify the underlying tax law?
- No. They enforce structure, references, tone, and date consistency. Accuracy against the law is maintained through sourcing and the review dates shown on each page.
Related
Sources
- OECD — OECD — economic and tax statistics (accessed ; reviewed )Covers: Comparable corporate tax, statutory rate, and economic indicators across member and partner economies.Does not cover: Effective tax rates, deductions and incentives, local surtaxes, and personal residency rules.Why it matters: Used as a cross-country baseline to sanity-check rates against primary tax-authority figures.Review cadence: Annual, plus on major statutory changes.
- European Commission — European Commission — policy and country information (accessed ; reviewed )Covers: EU policy framework including the VAT One-Stop-Shop and single-market rules.Does not cover: Member-state-specific reduced rates, national thresholds, or non-EU jurisdictions.Why it matters: Used for EU/EEA market-access and VAT-OSS framing referenced across rankings and guides.Review cadence: On policy change; re-checked each data review.
Last updated: