Business Case Example — Receipt with Issuer Branch
Case Sample — Retail Receipt (11.1) Issued by a Branch
Important Notice: This page provides a sample scenario intended to illustrate a typical business case. However, this example is not exhaustive and may not fully reflect your specific operational or legal obligations under the Greek fiscalisation framework (myDATA/AADE). It is essential that your complete fiscalisation scenario is thoroughly prepared and validated by your team, in collaboration with a qualified tax consultant or accountant familiar with Greek tax law and AADE requirements.
Important: All timestamps must be provided in UTC (ISO 8601 with Z). Using local time or mismatched timestamps may lead to validation or hash mismatch errors.
Applies to online (card-not-present) fiscalisation only: the branch override shown here is used with the Fiscalization API (POST /fiscalization/v1/receipts:sign). For card terminals the branch is not sent in the request. Each terminal is linked to its branch during onboarding, and the branch is applied automatically to every receipt that terminal issues.
SignRequestReceipt_RetailReceipt_IssuerBranch_1
summary: example of a retail receipt (11.1) issued by a specific branch of the merchant, sent through the online Fiscalization API
description: a merchant with several stores sends the branch number of the store that issues the receipt, so that myDATA records the sale under that branch
ftReceiptCase: POS receipt (11.1) with own Series/AA. One goods item at 24 % VAT, paid in cash
branch: set in ftReceiptCaseData.GR.mydataoverride.invoice.issuer.branch
{
"ftReceiptCase": 5139205309155770369,
"ftReceiptCaseData":
{
"GR":
{
"MerchantVATID": "123456789",
"Series": "AB",
"AA": 1,
"HashAlg": "sha256",
"HashPayload": "123456789-AB-1-branchreceipt00001-2025-07-23T00:01:06Z-1.24",
"mydataoverride":
{
"invoice":
{
"issuer":
{
"branch": 1
}
}
}
}
},
"cbReceiptReference": "branchreceipt00001",
"cbReceiptMoment": "2025-07-23T00:01:06Z",
"currencyCode": "978",
"cbChargeItems":
[
{
"quantity": 100,
"description": "product x",
"amount": 124,
"vatRate": 2400,
"ftChargeItemCase": 5139205309155246099,
"vatAmount": 24,
"currencyCode": "978",
"moment": "2025-07-23T00:01:06Z",
"position": 1
}
],
"cbPayItems":
[
{
"description": "Cash",
"amount": 124,
"ftPayItemCase": 5139205309155246081,
"currencyCode": "978",
"moment": "2025-07-23T00:01:06Z",
"position": 1
}
]
}How the branch works
branchis an integer: the branch number (αριθμός εγκατάστασης) of the issuing store, exactly as registered in TaxisNet for the merchant’s VAT number.- It goes under
ftReceiptCaseData.GR.mydataoverride.invoice.issuer, at receipt level. It does not go underftChargeItemCaseDatalike the line-level overrides. - The same block is used for every document type: retail receipts (11.x), credit notes (11.4), invoices (1.x, 2.x) and credit invoices (5.x). Only the document body changes, the branch block stays the same.
- In the myDATA XML it becomes
<issuer><branch>1</branch></issuer>. - A merchant with a single location sends nothing. myDATA then records
branch 0, which is the headquarters. - Card terminals: do not add this block to terminal requests. The branch comes from the terminal-to-branch link created during onboarding.