Greece — ftReceiptCase

Understanding ftReceiptCase (Greece)

Country selector

The ftReceiptCase in the main request body identifies the receipt type and how it must be processed for Greek fiscalisation. Its value is an Int64 decimal that represents a hexadecimal pattern with embedded flags. For Greece (country code GR = hex 4752), an unknown receipt case starts as 4752000000000000 (in hex before conversion).

Format

CCCC_vlll_gggg_txcc

• CCCC – Country (ASCII of ISO 3166-1 alpha-2), e.g. GR → hex 4752
• vlll – Tagging version (current: 2000)
• gggg – Flag bits (behavior modifiers)
• txcc – Receipt type

Example for Greece Hex: CCCC_2000_0002_0001

Note: You build the hex pattern and then convert the whole value to decimal for the API field. Flags are combined with bitwise OR (e.g., 0x100 | 0x8 = 0x108, thus gggg = 0108). Example (Greece): 4752_2000_0008_0001 → decimal 5139205309155770369.

Note: ftReceiptCase is a decimal representation of a hexadecimal combination of binary flags, where each section encodes specific aspects of the receipt context. These flags are typically calculated based on powers of 2 (2ⁿ) and can be combined using bitwise OR logic.

Specifically, the gggg part of the ftReceiptCase represents global tagging flags. You can assign one or more flags to it by combining them. For example, the "custom-numbered receipts" flag has a value of 0x8 and the "refund" flag has a value of 0x100. When both apply, they are combined as:

0x100 | 0x8 = 0x108

Therefore, the gggg value for a refund with custom-numbered receipt tagging would be 0108.

The CCCC200000080001 is hex and should be converted to decimal number (5139205309155770369). So, the value that should be passed through in the body request for this hex is 5139205309155770369.

A helpful online tool for your converting tests is this.

Negative amounts in HashPayload (refunds)

Important: The HashPayload is a string with fields joined by a single dash (-) separator:
MerchantVATID-Series-AA-cbReceiptReference-cbReceiptMoment-Amount. When the final Amount is negative (refund/credit), keep the minus sign on that last field. Because the dash is also the field separator, you will see two dashes in a row right before the negative amount (...--2.25). This is expected and correct.

Do not remove, collapse, or encode away the minus sign. Compute the hash on the exact string bytes, then Base64URL-encode the SHA-256 digest (URL-safe, no padding).

Examples

Positive total (2.25 EUR):
099565360-SER-15-REF-2025-11-04T12:40:16Z-2.25

Negative total (-2.25 EUR):
099565360-SER-15-REF-2025-11-04T12:40:16Z--2.25

Formatting rules

• Fields are joined with a single dash (-) separator; for negative amounts, the last field starts with a minus, so you get -- before the number.
• Amount uses a dot decimal (e.g., 12.5, 9.04); no thousands, no spaces, no plus sign.
• cbReceiptMoment must match exactly the ISO-8601 timestamp you send (YYYY-MM-DDTHH:MM:SSZ).
• Compute: SHA-256(HashPayload) → Base64URL (URL-safe, no padding).

Global flags — gggg

t receipt type t

txcc — ReceiptCase values (per Country)

Understanding ftReceiptCaseData for Greece

This field contains jurisdiction-specific fiscalization data that is required to comply with local electronic invoicing or tax regulations.

Examples (per-country)

Each example shows: (a) the human-readable pattern, (b) what it means, and (c) the value you send to the API (decimal Int64).

{
  "ftReceiptCase": 5139205309155770369
}

Conversion reminder

All CCCC_vlll_… show the human-friendly hex. Always send decimal Int64 in the API.