Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Lagos · Government & public services

Taxation.
Inspect assessments and recorded payments.

Read taxpayer context, compliance and payment records while keeping assessments and completed payments distinct.

Public sample available

Published domain facts

Tax Accounts, Lagos
1,532,748
Tax Assessments, Lagos
38.76M
Tax Payments, Lagos
24.84M
populated Levy Types (8 + 8 Nigeria)
16

Overview

Domain scope

Read taxpayer context, compliance and payment records while keeping assessments and completed payments distinct.

Read the published guide →

Known limits

Counts reflect a bounded analytical sample and limited fiscal-history window. Ward context is modeled location metadata, not an enforced relationship to a current ward. Interpret scale within the documented sampling boundary.

Review the source limits →
Full scope reference 3 documented sections
Published domain scope.

Published domain scope.

Trace taxpayer accounts, assessments and recorded payments. Amounts assessed, collected and reversed remain distinct; budget spending belongs to Public Finance.

  • Compare taxpayer and compliance categories
  • Inspect payment dates and channels
  • Review collected amounts and geography
Tax Accounts, Lagos
1,532,748
Tax Assessments, Lagos
38.76M
Tax Payments, Lagos
24.84M
populated Levy Types (8 + 8 Nigeria)
16
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

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.

Lagos City Twin™ · 1940–2026

From a taxpayer's obligation to a settled — or reversed — payment.

From a taxpayer's obligation to a settled — or reversed — payment.

Inspect the published definitions and release context.

Read the published detail

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 Lagos 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 draw on the citizen's Employment Contract, while business tax assessments can use the taxpayer's own business context rather than an unconnected income guess. Exact assessment formulas remain controlled.

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.

  • TaxType
  • TaxAccount
  • TaxAssessment
  • TaxPayment
  • BudgetHead
  • BudgetAllocation
  • BudgetExpenditure
  • Department / Directorate
  • Income
  • Expenditure
  • Credit
  • Not built — deliberate

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Taxpayer typeCompliance statusPayment dateTax payment amountPayment channelWard referenceResident referenceGender
IndividualActive2022-04-29520834.95BankNot recorded4725360M
IndividualSuspended2024-05-231090651.54MobileNot recorded4809360F
IndividualActive2025-06-25206681.67MobileNot recorded4832120F

Showing 3 of 100 sample rows and 8 of 8 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Taxpayer type

The category or type assigned to the taxpayer in the source record.

Original field: TaxpayerType
Example: Individual

Compliance status

The state recorded for the compliance in this extract.

Original field: ComplianceStatus
Example: Active

Payment date

The date recorded for the payment event.

Original field: PaymentDate
Example: 2022-04-29

Tax payment amount

The recorded tax payment, in local currency.

Original field: AmountPaid
Example: 520834.95

Payment channel

The channel through which the payment was recorded.

Original field: PaymentChannel
Example: Bank

Ward reference

The reference used to identify the ward associated with this record.

Original field: WardId
Example: Not provided

Resident reference

The synthetic resident reference used to connect this record to other city data.

Original field: CitizenId
Example: 4725360

Gender

The gender recorded for the synthetic resident; M and F denote male and female in these samples.

Original field: Gender
Example: Male

Complete published field dictionary · 8 fields
CitizenIdResident reference
The synthetic resident reference used to connect this record to other city data.Example: 4725360
GenderGender
The gender recorded for the synthetic resident; M and F denote male and female in these samples.Example: Male
TaxpayerTypeTaxpayer type
The category or type assigned to the taxpayer in the source record.Example: Individual
ComplianceStatusCompliance status
The state recorded for the compliance in this extract.Example: Active
PaymentDatePayment date
The date recorded for the payment event.Example: 2022-04-29
AmountPaidTax payment amount
The recorded tax payment, in local currency.Example: 520834.95
PaymentChannelPayment channel
The channel through which the payment was recorded.Example: Bank
WardIdWard reference
The reference used to identify the ward associated with this record.Example: Not provided
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
From a tax catalog to a settled — or unsettled — payment.

From a tax catalog to a settled — or unsettled — payment.

Inspect the published definitions and release context.

Read the published detail

Excludes reversed payments from the compliance count, matching the definition used by certification check.

Explore the release-backed analysis-ready examples in City Twin™ for current data.

Explore Tax Data →

Public entity familyRepresentsDisclosure boundary
Tax categoryTax/levy type and jurisdiction contextPhysical catalog fields are controlled
Taxpayer/account contextResident, household or business tax relationshipPhysical account keys are controlled
Assessment contextLiability and assessment historyExact formulas and rule design are controlled
Payment & compliancePayment, reversal and compliance context through timeExact transaction logic and fields are controlled
TaxCodeTaxNameAssessmentsWith PaymentCompliance
LAND_RATEAnnual Land Rate3,412,5562,484,11272.8%
PAYEPay As You Earn5,891,2034,289,47772.8%
BIZ_LICENCEBusiness Licence Fee2,206,1101,606,18772.8%
RENTAL_INCOMEMonthly Rental Income Tax2,167,4651,578,10272.8%

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
Citizen / BusinessTaxAccount's single-owner relationship, checked: every account belongs to exactly one synthetic owner
EmploymentLagos derives PAYE assessments from a citizen's published contract (and Payroll, where populated) rather than an unconnected income guess
Public Financecollected TaxPayment revenue joins the pool a BudgetAllocation draws against, contextually not via a direct row-level relationship
Full relationship reference 1 documented sections
Known and possible relationships.

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
Citizen / BusinessTaxAccount's single-owner relationship, checked: every account belongs to exactly one synthetic owner
EmploymentLagos derives PAYE assessments from a citizen's published contract (and Payroll, where populated) rather than an unconnected income guess
Public Financecollected TaxPayment revenue joins the pool a BudgetAllocation draws against, contextually not via a direct row-level relationship

Domain guide

Taxation · archived guide edition

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.

Published scope and limits

Counts reflect a bounded analytical sample and limited fiscal-history window. Ward context is modeled location metadata, not an enforced relationship to a current ward. Interpret scale within the documented sampling boundary.

Read the source limits →
Accessible HTML reference 2 documented sections
An assessment is not automatically a payment.

An assessment is not automatically a payment.

Inspect the published definitions and release context.

Read the published detail

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.

The architecture is shared. The tax code and the scale are not.

The architecture is shared. The tax code and the scale are not.

Inspect the published definitions and release context.

Read the published detail

Taxation\'s public semantic entity coverage is aligned across Lagos. What Lagos actually taxes, and how much of its population and history generation covers, are genuinely different.

Real FIRS/LIRS levies: PAYE, Companies Income Tax, VAT, Capital Gains Tax, Land Use Charge, Development Levy, Withholding Tax, Stamp Duty — all 8 populated types are actually assessed.

This BRONZE-tier taxation release uses a bounded analytical sample and a limited fiscal-history window as an explicit scale-control boundary. Interpret rates and absolute record counts within that disclosed scope; exact sampling coefficients remain controlled.

Evidence & limits

Scope and known limits

Counts reflect a bounded analytical sample and limited fiscal-history window. Ward context is modeled location metadata, not an enforced relationship to a current ward. Interpret scale within the documented sampling boundary.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

Counts reflect a bounded analytical sample and limited fiscal-history window. Ward context is modeled location metadata, not an enforced relationship to a current ward. Interpret scale within the documented sampling boundary.

Read the published detail

The taxation release intentionally uses a bounded analytical sample and a limited fiscal-history window. Absolute record counts should be interpreted within that sampling boundary; exact scale-control parameters remain in controlled technical documentation.

certification check location context is used as an analytical location attribute, but the Lagos release does not enforce it as a relationship to a current ward record. Ward-level tax analysis should therefore treat this field as modeled location metadata rather than a referential guarantee.

View All Taxation Limitations →

A tax system with 100% compliance, or 0% reversals, isn't real.

A tax system with 100% compliance, or 0% reversals, isn't real.

Inspect the published definitions and release context.

Read the published detail

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 Lagos — 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 — Lagos 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 →

  • C01 — TaxType catalog is populated and active
  • C03/C04 — TaxAccount Citizen/Business reference integrity and strict either/or ownership
  • C05/C06 — TaxAssessment reference integrity, non-negative amounts, DueDate ≥ AssessmentDate
  • C08 — TaxPayment reference integrity, AmountPaid > 0
  • C15/C16 — assessment status vocabulary; payment date not before its own AssessmentDate

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Explore the supplied synthetic example and its source references.

Read the published detail

A real taxpayer account, linked to the same persistent citizen identity used across the engine.

A real TaxAssessment on this account — currently Revised.

A real TaxPayment on 2022-03-24 via Bank — about 17% of the assessed amount, an honest partial-payment example, not a cherry-picked full settlement.

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™