Skip to content

Country Support

Cheqi can preserve and render country-specific receipt information supplied by your POS, fiscal device, or invoicing system. The current receipt engine accepts these canonical issuance countries:

RegionCountries
European UnionAustria (AT), Belgium (BE), Germany (DE), Denmark (DK), Estonia (EE), Spain (ES), Finland (FI), France (FR), Greece (GR), Ireland (IE), Italy (IT), Netherlands (NL), Poland (PL), Portugal (PT), Sweden (SE)
Other EuropeSwitzerland (CH), United Kingdom (GB), Iceland (IS), Norway (NO)
North AmericaCanada (CA), United States (US)

GB is the canonical United Kingdom country code. UK is accepted as an input alias and is normalized to GB.

Capability is not legal certification

Country support means the engine can create a receipt containing the supplied local fields. It does not mean Cheqi decides which rules apply, certifies the receipt as legally sufficient, or replaces a fiscal device, certified cash register, tax authority, Peppol validator, or local professional review.

Your integration's responsibilities

Supply completed receipt values and any applicable jurisdictionalData to the SDK. Cheqi preserves that information in supported receipt formats.

Your POS, fiscal device, or invoicing system must:

  • determine the applicable jurisdiction, regime, tax treatment, and document type;
  • calculate totals and taxes and supply the required legal wording;
  • complete required signing, fiscalization, and tax-authority reporting;
  • supply authority identifiers, signatures, and exact barcode payloads;
  • check that the data is legally sufficient for the transaction.

Cheqi does not perform those operations or certify legal completeness. Do not submit a final receipt with PENDING or FAILED fiscalization.

Country selection

When jurisdictionalData is needed, new integrations should set its countryCode explicitly. The supplier-country fallback remains available for compatibility:

  1. An explicit jurisdictionalData.countryCode takes precedence.
  2. Otherwise, the engine uses supplier.address.countryIsoCode.
  3. If neither exists, the engine does not invent a country.

Use the issuance jurisdiction selected by your own transaction and compliance logic. Do not use the buyer's country automatically unless that is the correct issuance jurisdiction for the transaction.

The engine does not determine whether an external regime applies. Keep the country, selected regime, and legal supplier consistent in your integration.

Next steps