Choose a country below for its external regimes, responsibilities, exact field mapping, and copyable payload fragments.
These contracts define what the receipt engine can represent and preserve. Cheqi does not determine whether a regime applies or whether the supplied data is legally sufficient for a particular transaction.
Rates, amounts, identifiers, wording, and authority values in the examples demonstrate placement only. Always use the values produced by your current tax, POS, fiscal-device, or authority integration.
| Country | External regimes | What Cheqi can represent |
|---|---|---|
Austria (AT) | AT_RKSV | RKSV register, sequence, signature, certificate/device, and referenced QR evidence |
Belgium (BE) | BE_GKS, BE_GKS_2 | Canonical ordinary retail plus legacy GKS and GKS 2.0 POS/FDM evidence |
Canada (CA) | None | HST, GST-only, GST+PST, and GST+QST variants with optional region attribution |
Switzerland (CH) | None | Canonical UID/VAT and recipient context, plus optional VAT-included presentation |
Germany (DE) | DE_KASSENSICHV | TSE transaction, register, serial, signature, payment split, and referenced QR evidence |
Denmark (DK) | DK_DIGITAL_SALES | Canonical retail plus digital-sales journal/signature evidence |
Estonia (EE) | None | Ordinary, exempt, and exact special-scheme wording variants |
Spain (ES) | ES_SIF, ES_VERIFACTU | SIF and system-selected VERI*FACTU evidence |
Finland (FI) | None | Canonical electronic cash/card receipts and VAT itemization |
France (FR) | FR_CERTIFIED_CASH_SYSTEM | Canonical ordinary retail plus secure cash-system and certificate/attestation evidence |
United Kingdom (GB) | None | Canonical retail VAT and full VAT invoices; UK input normalizes to GB |
Greece (GR) | GR_MYDATA | myDATA classification, MARK/UID, provider, URL, and referenced QR evidence |
Ireland (IE) | None | Canonical invoices plus optional treatment, wording, and second-currency tax data |
Iceland (IS) | None | Canonical consumer/business identity and optional VAT-included presentation |
Italy (IT) | IT_DOCUMENTO_COMMERCIALE | RT, transmission, verification, optional lottery, and referenced QR evidence |
Netherlands (NL) | None | Canonical retail receipts and full or simplified UBL invoices |
Norway (NO) | NO_SALES_RECEIPT | Cash/card sales, returns, corrections, POS, and terminal references |
Poland (PL) | PL_FISCAL_RECEIPT | Fiscal receipt/correction, register evidence, logo, signature/hash, and optional QR |
Portugal (PT) | PT_AT | Receipt, invoice, and credit-note ATCUD/hash/signature/QR variants |
Sweden (SE) | SE_CASH_REGISTER | Sales, returns/corrections, and training-copy variants |
United States (US) | None | State/local extension data for all 50 states and DC |
Only create jurisdictionalData when the selected country page identifies information without a canonical field. When you create it, set countryCode explicitly. The engine still supports supplier-country fallback for compatibility:
- Explicit
jurisdictionalData.countryCodewins. - Otherwise, the supplier address country is used.
- If neither exists, the engine does not invent a country.
The engine does not determine whether an external regime applies. Your integration must keep the explicit country, selected regime, and legal supplier consistent.
- Populate the normal receipt and server-known generation context first.
- Never duplicate a canonical receipt, party, payment, tax, identifier, date, or barcode value in
additionalFields. - Use a direct
ReceiptPayload;jurisdictionalDataandbarcodesare top-level receipt fields. - When a country page requires an external regime, set
regimeand an explicitregimeVersion. - Complete external authority, device, signing, or certified-software work before final receipt generation.
- Use
FISCALIZEDonly after that operation succeeds. - Never submit a final receipt with
PENDINGorFAILED. - Put machine-readable payloads in top-level
barcodes[]; country fields may reference them but do not contain barcode objects. - Preserve identifiers, signatures, hashes, legal text, and QR payloads exactly as produced.
- Add a country field only when the country page confirms that the canonical contract has no field for that value.
See Supplying Jurisdiction Data for the shared schema.