Skip to content

Country Capabilities

Choose a country below for its external regimes, responsibilities, exact field mapping, and copyable payload fragments.

Capability is not legal certification

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.

Example values are illustrative

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 index

CountryExternal regimesWhat Cheqi can represent
Austria (AT)AT_RKSVRKSV register, sequence, signature, certificate/device, and referenced QR evidence
Belgium (BE)BE_GKS, BE_GKS_2Canonical ordinary retail plus legacy GKS and GKS 2.0 POS/FDM evidence
Canada (CA)NoneHST, GST-only, GST+PST, and GST+QST variants with optional region attribution
Switzerland (CH)NoneCanonical UID/VAT and recipient context, plus optional VAT-included presentation
Germany (DE)DE_KASSENSICHVTSE transaction, register, serial, signature, payment split, and referenced QR evidence
Denmark (DK)DK_DIGITAL_SALESCanonical retail plus digital-sales journal/signature evidence
Estonia (EE)NoneOrdinary, exempt, and exact special-scheme wording variants
Spain (ES)ES_SIF, ES_VERIFACTUSIF and system-selected VERI*FACTU evidence
Finland (FI)NoneCanonical electronic cash/card receipts and VAT itemization
France (FR)FR_CERTIFIED_CASH_SYSTEMCanonical ordinary retail plus secure cash-system and certificate/attestation evidence
United Kingdom (GB)NoneCanonical retail VAT and full VAT invoices; UK input normalizes to GB
Greece (GR)GR_MYDATAmyDATA classification, MARK/UID, provider, URL, and referenced QR evidence
Ireland (IE)NoneCanonical invoices plus optional treatment, wording, and second-currency tax data
Iceland (IS)NoneCanonical consumer/business identity and optional VAT-included presentation
Italy (IT)IT_DOCUMENTO_COMMERCIALERT, transmission, verification, optional lottery, and referenced QR evidence
Netherlands (NL)NoneCanonical retail receipts and full or simplified UBL invoices
Norway (NO)NO_SALES_RECEIPTCash/card sales, returns, corrections, POS, and terminal references
Poland (PL)PL_FISCAL_RECEIPTFiscal receipt/correction, register evidence, logo, signature/hash, and optional QR
Portugal (PT)PT_ATReceipt, invoice, and credit-note ATCUD/hash/signature/QR variants
Sweden (SE)SE_CASH_REGISTERSales, returns/corrections, and training-copy variants
United States (US)NoneState/local extension data for all 50 states and DC

Country selection

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:

  1. Explicit jurisdictionalData.countryCode wins.
  2. Otherwise, the supplier address country is used.
  3. 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.

Shared request rules

  • 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; jurisdictionalData and barcodes are top-level receipt fields.
  • When a country page requires an external regime, set regime and an explicit regimeVersion.
  • Complete external authority, device, signing, or certified-software work before final receipt generation.
  • Use FISCALIZED only after that operation succeeds.
  • Never submit a final receipt with PENDING or FAILED.
  • 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.