Months after you onboarded a company, someone asks why. It may be an auditor, a regulator, a bank partner or your own risk team. "We checked the register" is not an answer they can accept. What they want is a record: what was checked, what the register said, when, and what you decided because of it. This guide lists what that record should contain, shows a real one, and explains why a technical receipt is useful evidence but not a legal certificate.
What you'll learn
- The eight elements a verifiable company check record should hold
- What a real check record looks like, field by field
- Why the check date, the retrieval date and the source's own date are different
- The difference between a technical receipt and a legal certification
Short answer: a verifiable record identifies the company by its official number, states the check performed and its outcome with reasons, names the source and links to the official record, carries precise timestamps, keeps the data that was served with a hash, records your decision and its reasons separately, and has a stable reference anyone can use to retrieve it later.
The eight elements of a verifiable record
1. The checked entity
The country, the official identifier and its type (a SIREN, a Registro Mercantil sheet, a UK company number), and the company's name as the register showed it at the time. The identifier is what makes the record unambiguous; the name is context.
2. The check performed
What was asked: a lookup, a full verification, an insolvency check. "Verified" means little unless you know what was verified.
3. The outcome, reasons and individual checks
The result from a closed list (for example verified, partial or unverified), the machine-readable reasons, and ideally each check behind it: identifier valid, record found, status active, address present, data fresh.
4. The source
Which register answered, a link to the official record, and the licence the data is reused under. Anyone reviewing the record should be able to go and look for themselves.
5. Timestamps
At least three, kept apart: when the check was run, when the data was retrieved from the source, and when the source itself last published or updated it. They are often different, as the example below shows. Store them with a timezone.
6. Evidence of what was served
The data as it was returned, or a fingerprint of it: a hash that changes if a single character changes. A snapshot identifier ties the answer to the exact copy of the record it came from.
7. Your decision and its reasons
The check result is not the decision. Record separately who or what decided (a rule, a person), when, the policy version applied, and why: "approved: verified, no open procedure" or "sent to review: partial, status unknown". Mixing the two makes it impossible to tell later whether the check or the policy was at fault.
8. A way to retrieve it later
A stable reference, kept for a stated period, that returns the same record when asked. Ideally one you can share with someone outside your company without giving them access to your systems.
A real check record
Here is part of a real verification of TESCO PLC through Fuentio's API, run on 16 October 2026:
{
"verification_id": "ver_IPReWMF3frKzs07d",
"proof_code": "FUE-GB-20261016-5QBDT2",
"checked_at": "2026-10-16T08:41:27.492024+00:00",
"country": "GB",
"identifier": {"scheme": "GB_COMPANY_NUMBER", "value": "00445790"},
"result": {"outcome": "verified", "reasons": ["company_active"]},
"provenance": {"source": "gb_companies_house_api",
"source_url": "https://find-and-update.company-information.service.gov.uk/company/00445790"},
"freshness": {"retrieved_at": "2026-10-16T08:24:46.025149+00:00", "from_cache": true, "stale": false},
"receipt": {"request_id": "req_8SL4ciDFhZlAo1K9",
"data_sha256": "5c7756129f57bfe5e1da995148ee3b66a7422310fbf083b6422407754fc52aa6",
"snapshot_id": "GB-COMPANYNUMBER-00445790@2026-10-16T08:24:46.025149+00:00"}
}
Notice the two times. The record was retrieved from Companies House at 08:24 and the check was served at 08:41, from a stored copy. The answer says so (from_cache: true) and gives the rule it follows: Fuentio's copy is reused for up to 7 days, then fetched again. A record that only said "checked at 08:41" would overstate how fresh the data was.
Every element from the list is there: the entity by identifier, the outcome and reasons, the source and its link, the timestamps, a hash and snapshot of what was served, and two references, a verification ID and a proof code. Element 7, your decision, is the one only you can add.
Receipts and proof codes
Two kinds of reference serve different readers:
- A receipt is the stored copy of one answer, identified by its request ID. With Fuentio,
GET /v1/receipts/{receipt_id}returns it, free of charge. It is for you and your auditors. More in audit receipts: how Fuentio proves what a register said. - A proof code identifies a verification. Anyone you share it with can open it on fuentio.com/proof/ or through
GET /v1/public/proofs/{proof_code}, without an account, and see what was checked and when. Codes are kept 24 months.
How to get one from the API is in how to verify a company and get a proof code.
A technical receipt is not a legal certification
A receipt or proof code proves what a provider served and when, and that it hasn't changed since. It is strong technical evidence. It is not:
- a certified document from the register itself, such as a Kbis extract issued by a French commercial court registry, a certificate or certified copy from Companies House, or a certificate from Spain's Registro Mercantil;
- a legal opinion that the company may lawfully enter into your contract;
- a statement about the company's safety, solvency or ownership.
When a contract, a tender or a court asks for a certified document, get it from the register. For audit trails, internal reviews and showing what you knew on the day, a well-formed technical record is usually what you need, and it is far easier to keep consistently. Where each piece of provenance comes from is explained in provenance on every answer.
Common mistakes
- Screenshots instead of data: they show a page, not its source, time or integrity.
- Storing only "OK": the outcome without reasons, source or dates can't be reviewed.
- Overwriting on re-check: each check is its own record; keep the history.
- No timezone, or a single date standing for all three.
- The decision inside the check result, so a policy change rewrites history.
Limits
A check record shows what an official register stated through a provider at a given time. It isn't a certified extract, a legal opinion or proof that a company is safe to deal with. Fuentio's records cover France, Spain and the United Kingdom (see the coverage page), contain no person's name, and proof codes are kept for 24 months; keep your own copy of anything you must hold for longer.
Frequently asked questions
Is a screenshot of a register page good evidence?
It is weak evidence. It shows a page but not reliably where it came from, when the data was last updated, or that it wasn't altered. Store the data with its source, timestamps and a hash.
What is the difference between the check date and the source date?
The check date is when you asked; the retrieval date is when the provider fetched the record; the source date is when the register last updated it. Keep all three.
Can a proof code replace a Kbis or a Companies House certificate?
No. It proves what was checked and when, which is ideal for audit trails, but a certified document must come from the register itself.
How long should I keep company check records?
As long as your legal and contractual duties require. Fuentio keeps proof codes for 24 months; store your own copy if you need longer.
Sources
- Fuentio outcomes and their meaning: api.fuentio.com/docs/outcomes
- Fuentio API reference, receipts and verifications: api.fuentio.com/llms.txt
- Companies House register: find-and-update.company-information.service.gov.uk
- Infogreffe (Kbis extracts, France): infogreffe.fr
