Domain scope
Read taxpayer context, compliance and payment records while keeping assessments and completed payments distinct.
Read the published guide →Nairobi · Government & public services
Read taxpayer context, compliance and payment records while keeping assessments and completed payments distinct.
Public sample available
Published domain facts
Read taxpayer context, compliance and payment records while keeping assessments and completed payments distinct.
Read the published guide →Public sample available
Preview samples & fields →Only four of eight catalogue levies produce assessments. Counts reflect full-population generation across 1940–2026, rather than a bounded sample. Ward context is modeled metadata, not an enforced relationship to a current ward.
Review the source limits →Trace taxpayer accounts, assessments and recorded payments. Amounts assessed, collected and reversed remain distinct; budget spending belongs to Public Finance.
Inspect the published scope and deployment boundaries.
FCTE models the revenue-collection half of the fiscal cycle: a TaxAccount belongs to exactly one real Citizen or Business, a TaxAssessment is raised against it for a real levy type and year, and a TaxPayment settles some, all, or none of it — on a real payment channel, sometimes reversed.
Collected revenue then funds the budget cycle modeled in Public Finance → — a separate domain, not this one.
Nairobi City Twin™ · 1940–2026
Inspect the published definitions and release context.
Every capability below is backed by release evidence or certification. The public page presents the data model rather than the physical design. Taxation represents government revenue collection; budget allocation and departmental spend are presented separately in Public Finance .
The TaxType table contains the levy types represented in the Nairobi release. Its catalog is city-specific rather than assumed to match another jurisdiction.
the TaxAccount record family — one row per taxpayer, individual or corporate, with a strict either/or link to a real Citizen or Business record (never both, never neither).
the TaxAssessment record family — what's owed, for which tax type and year, its due date and its status. A city-specific assessment structure with public semantic differences.
the TaxPayment record family — what's actually been paid, on what channel (M-Pesa, bank, cash, cheque, online, mobile, USSD), and whether it was later reversed.
The share of assessments that ever receive a payment — a real, calibrated figure, never near 0% and never near 100%.
PAYE assessments are derived from a citizen's real Employment Contract, not an unconnected income guess; Nairobi's land-rate assessments carry a real guarded relationship to a Land Parcel.
Synthetic by design: FCTE tax accounts, assessments and payments are analytical representations of a plausible revenue-collection process. They do not represent actual taxpayers or actual government revenue.
Taxation and Public Finance are connected parts of the certified government-finance release, presented as separate public domains because collection and spending answer different policy questions.
| Taxpayer type | Compliance status | Payment date | Tax payment amount | Payment channel | Ward reference | Resident reference | Gender |
|---|---|---|---|---|---|---|---|
| Individual | Active | 2020-04-30 | 19254.00 | Cash | 36 | 14254 | F |
| Individual | Active | 2023-05-22 | 31996.00 | Cheque | 66 | 26996 | F |
| Individual | Active | 2011-04-10 | 48008.00 | MPESA | 10 | 43008 | F |
Showing 3 of 100 sample rows and 8 of 8 fields. “Not recorded” is a display label; downloads retain original values.
The category or type assigned to the taxpayer in the source record.
Original field: TaxpayerType
Example: Individual
The state recorded for the compliance in this extract.
Original field: ComplianceStatus
Example: Active
The date recorded for the payment event.
Original field: PaymentDate
Example: 2020-04-30
The recorded tax payment, in local currency.
Original field: AmountPaid
Example: 19254.00
The channel through which the payment was recorded.
Original field: PaymentChannel
Example: Cash
The reference used to identify the ward associated with this record.
Original field: WardId
Example: 36
The synthetic resident reference used to connect this record to other city data.
Original field: CitizenId
Example: 14254
The gender recorded for the synthetic resident; M and F denote male and female in these samples.
Original field: Gender
Example: Female
CitizenIdResident referenceGenderGenderTaxpayerTypeTaxpayer typeComplianceStatusCompliance statusPaymentDatePayment dateAmountPaidTax payment amountPaymentChannelPayment channelWardIdWard referenceInspect the published definitions and release context.
Excludes reversed payments from the compliance count, matching the definition used by certification check.
Representative row shape — real Nairobi tax codes and the domain's overall 72.88% compliance rate; per-type breakdown varies by live generation run. Explore the release-backed analysis-ready examples in City Twin™ for current data.
Explore Tax Data →
| Public entity family | Represents | Disclosure boundary |
| Tax category | Tax/levy type and jurisdiction context | Physical catalog fields are controlled |
| Taxpayer/account context | Resident, household or business tax relationship | Physical account keys are controlled |
| Assessment context | Liability and assessment history | Exact formulas and rule design are controlled |
| Payment & compliance | Payment, reversal and compliance context through time | Exact transaction logic and fields are controlled |
| TaxCode | TaxName | Assessments | With Payment | Compliance |
| LAND_RATE | Annual Land Rate | 3,412,556 | 2,484,112 | 72.8% |
| PAYE | Pay As You Earn | 5,891,203 | 4,289,477 | 72.8% |
| BIZ_LICENCE | Business Licence Fee | 2,206,110 | 1,606,187 | 72.8% |
| RENTAL_INCOME | Monthly Rental Income Tax | 2,167,465 | 1,578,102 | 72.8% |
Inspect the published definitions and release context.
| Domain or context | Relationship and published scope |
| Citizen / Business | TaxAccount's single-owner relationship, checked: every account belongs to exactly one synthetic owner |
| Land | TaxAssessment, a documented relationship to Parcel for Nairobi's land-rate assessments |
| Employment | Nairobi derives PAYE assessments from a citizen's published contract (and Payroll, where populated) rather than an unconnected income guess |
| Public Finance | collected TaxPayment revenue joins the pool a BudgetAllocation draws against, contextually not via a direct row-level relationship |
Inspect the published definitions and release context.
Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.
| Domain or context | Relationship and published scope |
| Citizen / Business | TaxAccount's single-owner relationship, checked: every account belongs to exactly one synthetic owner |
| Land | TaxAssessment, a documented relationship to Parcel for Nairobi's land-rate assessments |
| Employment | Nairobi derives PAYE assessments from a citizen's published contract (and Payroll, where populated) rather than an unconnected income guess |
| Public Finance | collected TaxPayment revenue joins the pool a BudgetAllocation draws against, contextually not via a direct row-level relationship |
Striped Donkey V5.89 - 7 September 2026
Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.
Only four of eight catalogue levies produce assessments. Counts reflect full-population generation across 1940–2026, rather than a bounded sample. Ward context is modeled metadata, not an enforced relationship to a current ward.
Read the source limits →Inspect the published definitions and release context.
FCTE preserves the real gap between what's owed and what's collected — that gap is compliance, and it's never 0% or 100%.
Representative public release example — exact live identities and run-level values are intentionally not published. Explore the release-backed analysis examples in City Twin™ for current data.
Inspect the published definitions and release context.
Taxation\'s public semantic entity coverage is aligned across Nairobi. What Nairobi actually taxes, and how much of its population and history generation covers, are genuinely different.
Real real-world levies: Annual Land Rate, Business Licence Fee, Pay As You Earn, NSSF, NHIF/SHA, Monthly Rental Income Tax, Building Permit Fee, Property Rate — 8 populated, only Land Rate, Business Licence, PAYE and Rental Income are actually assessed today.
Nairobi's generation instead covers every citizen and business across the full 86-year epoch. Interpret rates and raw row counts within this disclosed Nairobi full-population, full-epoch design.
Only four of eight catalogue levies produce assessments. Counts reflect full-population generation across 1940–2026, rather than a bounded sample. Ward context is modeled metadata, not an enforced relationship to a current ward.
Only four of eight catalogue levies produce assessments. Counts reflect full-population generation across 1940–2026, rather than a bounded sample. Ward context is modeled metadata, not an enforced relationship to a current ward.
Nairobi's TaxType catalog starting configurations 8 real Kenyan levies, but generation currently only produces TaxAssessment rows for 4 of them — Land Rate, Business Licence, PAYE and Rental Income. Property Rate, NSSF, NHIF/SHA and Building Permit Fee exist in the catalog but sit unused today.
Nairobi's generation instead covers every citizen and business across the full 1940–2026 epoch. Absolute row counts should be interpreted in the context of Nairobi's full-population, full-epoch generation design.
certification check location context supports ward-level analysis, but it is not enforced as a relationship to a current ward record. Treat it as modeled location metadata rather than a referential guarantee for every account.
View All Taxation Limitations →
Inspect the published definitions and release context.
Taxation's realism checks target exactly the patterns naive synthetic data production tends to fall into: perfect payment compliance and payments that are never, ever reversed. Both were genuinely found and fixed during graduation and its follow-on live runs.
A fourth check, certification check (Citizen/Business taxpayer ownership mix), also PASSes Nairobi — both categories are present and non-zero in every TaxAccount population.
Open Finance Realism Report →
Taxation shares one deployed certification suite with Public Finance (certification check–C16). The subset below covers accounts, assessments and payments; the remaining 7 checks (budget and government structure) belong to Public Finance .
Both the structural and realism checks replaced two separate legacy certification packs — Nairobi previously each had their own — with a single shared certification suite, matching the pattern used by Employment, Demographics and Transport's own certification.
Explore Every Finance Check →
Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.
Read the terms for public previews and commercial orders before requesting your extract.
Explore the supplied synthetic example and its source references.
A real taxpayer account, linked to the same persistent citizen identity used across the engine.
A real TaxAssessment on this account — currently Overdue.
0 TaxPayment rows exist against this assessment — a real, honest example of the "sometimes" in "payment is sometimes made," not a cherry-picked success case.
What happens next — allocation and spend — is a separate story, told on the Public Finance → page.
Activity → Assess → Collect — the revenue half of a government's books.
Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™