# United Kingdom
> British documents: the VAT number and company number, rates, e-invoices, dates and GBP, and what a British company’s details need.
>
> Before: [The document](https://ocost.io/docs/en/document.md)

What Ocost reads on a British document and where it writes it in [`ocost.document.v1`](https://ocost.io/docs/en/document.md). An invoice, credit note, delivery note or receipt gets the same `kind` as anywhere.

## Identifiers

| Printed as | Field | Check |
| --- | --- | --- |
| VAT registration number (`GB` and 9 or 12 digits) | `vat_id`, `identifiers` as `EU_VAT` | Check `vat_id`: its format. Ocost doesn't ask HMRC. |
| Company number (Companies House) | `legal_registration_id` | None |
| IBAN | `payment.iban` | Check `iban`: its check digits |

## VAT

Ocost reads the rates a document prints, usually 20 %, 5 % or 0 %. Each rate is one `vat_breakdown` group. The check `vat` holds when a group's VAT is its net times its rate.

`tax_check` is `null`. Ocost checks no British invoice rules yet. It checks the sums, the lines, the dates, the IBAN and the identifiers.

## E-invoices

Ocost reads an e-invoice in UBL or CII without a model. `read_with` is then `e_invoice`, and every value is `checked`.

## Dates and amounts

British documents print `03/11/2026` and `£1,270.92`. Ocost writes `2026-11-03`, `1270.92` and `GBP`. `sources` keeps the quote as printed. [Units and codes](https://ocost.io/docs/en/units.md) lists the codes Ocost writes.

## Your company

Ocost tells incoming from outgoing by your details in [Settings › Company](https://app.ocost.io/settings/company). A British company needs its registered office. A Ltd, PLC or LLP adds its Companies House number. Add the VAT number once you are VAT-registered.

When you add a British company to your group, Ocost looks it up at Companies House by its number or name. A VAT number it looks up at HMRC.

Ocost fills an empty address or VAT number from your documents and the group's, where an exact identifier names you. It never overwrites a value.

Mail to `belege@<name>.ocost.io` reaches Ocost. The name is yours without Ltd or Limited: Example Joinery Ltd gets `example-joinery`.

## Example

An excerpt of an incoming invoice:

```json
{
  "kind": "invoice",
  "kind_detail": "invoice",
  "type_code": "380",
  "number": "INV-2026-0318",
  "currency": "GBP",
  "seller": {
    "name": "Example Joinery Ltd",
    "identifiers": [
      { "scheme": "EU_VAT", "value": "GB123456789", "valid": null }
    ],
    "vat_id": "GB123456789",
    "legal_registration_id": "Company No. 01234567"
  },
  "totals": { "net": 500, "tax": 100, "gross": 600, "payable": null, "prices_include_vat": false },
  "vat_breakdown": [
    { "category": "S", "rate": 20, "taxable_amount": 500, "tax_amount": 100, "exemption_reason": null }
  ],
  "tax_check": null,
  "read_with": "reader"
}
```

## See also

- [The document](https://ocost.io/docs/en/document.md): The ocost.document.v1 schema in EN 16931 terms (maps to UBL and CII): an example, kind and direction, sources, checks, versions, and every field and value.
- [Units and codes](https://ocost.io/docs/en/units.md): The document’s code lists: UNECE units with the words printed for them, ISO currencies and countries, VAT categories, payment means, document types, identifiers, ECLASS.
- [Company groups](https://ocost.io/docs/en/groups.md): Company groups: which companies a key reaches, the Ocost-Business header, routing by the document’s identifiers, needs_company, and files across the group.
- On ocost.io: [Invoice processing](https://ocost.io/en/product/invoice-processing)
