Extract data from tax clearance certificates
Before a company can bid on a public tender, draw down a bank facility, or repatriate profits across a border, the counterparty usually asks for a tax clearance certificate: an official statement from a revenue authority that the taxpayer is in good standing and has no outstanding liabilities. It is not a bill and it is not a return. A tax assessment says money is owed; a tax clearance certificate says the account is settled and the taxpayer is COMPLIANT as of a stated date. HM Revenue and Customs, the Irish Revenue Commissioners, and most national tax administrations issue these with a validity window, because standing on 2026-06-01 says nothing about standing six months later. The document turns on a small set of decisive fields. A certificate for Meridian Infrastructure Ltd, tax ID GB123456789, issued by HM Revenue and Customs for tax year 2025, might carry a compliance_status of COMPLIANT, outstanding_liabilities of false, a total tax amount of 0 GBP, and cover corporation_tax, VAT, and PAYE. Its validity_period_months of 6, running from a document_date of 2026-06-01 to an expiration_date of 2026-12-01, and the purposes_authorized, such as government_bidding and credit_access, determine where the certificate can actually be relied on. The authorized signatory, their title, and whether the certificate carries a digital signature establish that it is genuine, and the issuing_country as an ISO 3166-1 code fixes the jurisdiction whose standing is being certified. Parsed against the clearance schema, the certificate returns the taxpayer identity, the issuing authority and country, the compliance status, the tax types covered, the validity window, and the authorized purposes as fields. In practice, a certificate confirming Meridian Infrastructure Ltd is compliant through 2026-12-01 loads into a vendor-onboarding or KYC file, so a procurement or credit team reads the status, the covered taxes, and the expiry from structured fields rather than re-keying a scanned certificate. Status is reported exactly as certified, without any judgment of the taxpayer’s eligibility.
What gets extracted from tax clearance certificates
How extraction works for tax clearance certificates
Clearance certificates arrive as portal downloads, stamped letters, and scans, and the one field that matters most, the compliance status, is often printed as free text next to a validity window and a list of covered taxes. Sorted by type, the certificate maps to the clearance model in the Field Registry, resolving compliance_status to a canonical enum (COMPLIANT, NON_COMPLIANT, CONDITIONAL, SUSPENDED) rather than leaving it as prose, and typing outstanding_liabilities as a boolean and total_tax_amount as a number in the stated currency. The document_date, expiration_date, and validity_period_months are cross-checked so a certificate dated 2026-06-01 with a six-month validity resolves to a 2026-12-01 expiry, and the tax_types_covered and purposes_authorized are split into lists so a procurement team can confirm the certificate actually covers the tax and the use it is being relied on for. Authenticity stays checkable through the authorized signatory, their title, and the digital_signature flag, and each value carries a confidence score and a source-region pointer under DIN SPEC 91491 so a reviewer can verify the status against the issued certificate.
Sample extraction
A tax clearance certificate issued for a public procurement bid
{
"document_number": "TCC-2026-4471",
"document_date": "2026-06-01",
"expiration_date": "2026-12-01",
"taxpayer.name": "Meridian Infrastructure Ltd",
"taxpayer.tax_id": "GB123456789",
"taxpayer.address": "14 Kingsway, London WC2B 6LH, United Kingdom",
"issuing_authority": "HM Revenue and Customs",
"issuing_country": "GB",
"compliance_status": "COMPLIANT",
"tax_year": "2025",
"outstanding_liabilities": false,
"total_tax_amount": 0,
"currency": "GBP",
"tax_types_covered": "corporation_tax, vat, paye",
"validity_period_months": 6,
"authorized_signatory.name": "Priya Nair",
"authorized_signatory.title": "Tax Compliance Officer",
"signature_date": "2026-06-01",
"digital_signature": true,
"purposes_authorized": "government_bidding, credit_access",
"conditions_or_remarks": "Valid subject to no new liabilities arising before the expiration date",
"document_url": "https://verify.hmrc.gov.uk/clearance/TCC-2026-4471"
}Frequently asked
Is a tax clearance certificate the same as a tax assessment notice?
No. An assessment notice states tax owed and sets a payment deadline. A clearance certificate states that the taxpayer has no outstanding liabilities and is compliant as of a date. Talonic reads each on its own schema and reports clearance as a compliance status, not an amount due.
How does it handle the compliance status?
The status is resolved to a canonical enum, COMPLIANT, NON_COMPLIANT, CONDITIONAL, or SUSPENDED, rather than left as free text, so a CONDITIONAL certificate is not silently read as fully compliant. Any conditions or remarks are captured in their own field.
Does the extractor track the validity window?
Yes. The document_date, validity_period_months, and expiration_date are captured and cross-checked, so a certificate dated 2026-06-01 with a six-month validity resolves to a 2026-12-01 expiry that a vendor file can key an alert on.
What purposes is a certificate valid for?
The purposes_authorized field lists the specific uses the clearance is issued for, such as government_bidding, credit_access, or cross_border_trade, so a procurement or credit team can confirm the certificate covers the transaction in front of them.
Ready to extract from your own tax clearance certificates?
Author note
Reviewed by Talonic engineering, tax schema review · last reviewed 2026-07-09