One of the most technically distinctive features of the UAE PINT-AE billing specification is the eight-position binary transaction type flag — the BTAE-03 field. Every electronic invoice and credit note in the UAE system carries this flag, which encodes up to eight simultaneous characteristics of the supply into a single structured value. Configuring this flag correctly for every transaction type the business generates is a mandatory pre-go-live task. Misconfiguring it — sending 00000000 (standard) for a transaction that should carry the Free Trade Zone flag, for example — results in a schematron validation failure or, worse, a structurally valid but legally incorrect invoice that understates the FTA's reporting data.

How the Eight-Position Binary Flag Works

The BTAE-03 field is an eight-character string of zeros and ones, where each position corresponds to one of the eight UAE transaction scenarios defined in the PINT-AE specification. A "1" in a given position means that scenario applies to the transaction. A "0" means it does not. A standard domestic B2B transaction with no special scenario carries the value 00000000. A transaction that involves a Free Trade Zone entity carries 10000000 (position 1 set to 1). A transaction that is both a Free Trade Zone supply and an export carries 10000001 (positions 1 and 8 set to 1). Multiple positions can be set simultaneously where more than one scenario applies.

The Eight Positions and What They Mean

Position 1 — Free Trade Zone

Set to 1 where a transaction involves a Free Trade Zone entity — as supplier, buyer, or beneficiary — or the supply itself takes place within or from a Free Zone. This flag is mandatory for all FTZ-connected supplies, and when set, it activates additional mandatory requirements: the BTAE-01 field (beneficiary identity) becomes mandatory where the beneficiary differs from the buyer. The FTZ flag applies to Commercial Invoices as well as Electronic Tax Invoices.

Position 2 — Deemed Supply

Set to 1 where the supply is a deemed supply under Article 11 of the UAE VAT Decree-Law — including free-of-charge supplies, gifts exceeding the prescribed threshold, and private use of business assets. When position 2 is set to 1, the buyer electronic address must always be the predefined endpoint 0235:9900000097, regardless of who the deemed supply recipient is. In instances where an invoice in respect of deemed supplies is not issued to the recipient, there will be no exchange of Electronic Invoices — only reporting to the FTA by the supplier's ASP.

Position 3 — Profit Margin Scheme

Set to 1 where VAT is calculated only on the supplier's margin under Article 43 of the VAT Decree-Law. This covers qualifying supplies of second-hand goods, antiques, and works of art by dealers operating under the margin scheme. When position 3 is set, the VAT amount displayed on the invoice should be zero — even though PINT-AE mandates the inclusion of a VAT information block — because the actual VAT is calculated on the margin and is not separately disclosed on the invoice under the margin scheme rules.

Position 4 — Summary Invoice

Set to 1 where multiple transactions with the same customer over a defined invoicing period are consolidated onto a single summary invoice under Scenario 4 of the UAE E-Invoicing Guidelines. When position 4 is set, certain document-level fields including the billing period (start and end date) become mandatory. The billing period fields cannot be omitted or left zero when a summary invoice flag is set — their absence triggers a schematron validation failure.

Position 5 — Continuous Supply

Set to 1 for supplies provided on an ongoing or recurring basis, or those involving periodic invoicing under Scenario 5 of the UAE E-Invoicing Guidelines. Monthly advisory retainers, utility supplies, telecom services, and recurring SaaS subscriptions are examples. The continuous supply flag activates the billing frequency code field, which must carry one of the 10 permitted values from the UAE billing frequency code list.

Position 6 — Disclosed Agent Billing

Set to 1 where a person is acting as a disclosed agent on behalf of a principal and issuing invoices in that capacity under Article 8 of MD 243. When position 6 is set, the BTAE-14 field — the principal's identity — becomes mandatory. The agent-billing scenario does not apply to undisclosed agents. The responsibility to issue the Electronic Invoice remains with the supplier (principal) even where the agent issues on its behalf; the flag makes this relationship explicit in the invoice data reported to the FTA.

Position 7 — Supply Through E-Commerce

Set to 1 for electronic commerce supplies through an Electronic Commerce Medium as defined by Ministerial Decision No. 26 of 2023. When position 7 is set, the delivery address fields (BTAE-23) become mandatory — the physical address to which the goods are delivered must be captured and included in the invoice. For B2B e-commerce supplies to UAE business customers, this field requires the buyer's delivery address at the level of completeness specified in the PINT-AE standard.

Position 8 — Exports

Set to 1 for goods or services supplied to customers outside the UAE under Scenario 8 of the UAE E-Invoicing Guidelines. When position 8 is set, and the overseas buyer has no Peppol registration, the predefined endpoint 0235:9900000099 must be used. For physical goods exports, the customs reference number (BTAE-21) and Incoterms code (BTAE-22) become mandatory fields. The tax category for the exported goods is typically Z (zero-rated), and the zero-rating rationale must be documented in the invoice data.

Multi-Flag Combinations

The PINT-AE specification explicitly permits and anticipates multi-flag combinations. A supply from a UAE Free Trade Zone business to an overseas buyer — a common scenario in UAE manufacturing and logistics — carries both position 1 (FTZ) and position 8 (Export): the flag is 10000001. A continuous supply made through an e-commerce platform from a Free Zone facility carries positions 1, 5, and 7: the flag is 10010100. Each set position activates its own additional mandatory field requirements, which must all be satisfied simultaneously.

Practitioner Insight: The transaction type flag configuration is one of the most common sources of schematron validation failures in early testing phases. Businesses configure the flag at the system level — setting a default for all transactions — rather than at the transaction level based on the actual characteristics of each supply. A company that operates both mainland and free zone facilities, exports to some customers and sells domestically to others, and has both continuous and spot transactions cannot use a single flag value for all invoices. The flag must be determined dynamically per transaction, from data that captures the actual scenario attributes of that supply.

Configuring the Flag in Your ERP

For SAP S/4HANA implementations, the BTAE-03 flag value must be determined at the billing document level from the combination of the sold-to party's attributes (FTZ status, country), the delivery data (export indicator, delivery country), and the billing arrangement type (continuous, summary, agent). This typically requires a custom determination function or a condition-based configuration that evaluates these attributes and outputs the correct eight-position binary string into the PINT-AE XML mapping.

For Oracle Fusion implementations, the equivalent determination logic runs through a combination of transaction type configuration, customer attributes from TCA, and DFF values that capture scenario-specific attributes. The flag value is then passed through the e-invoicing output generation process — whether through Oracle's native UAE e-invoicing capability, a BIP template, or a middleware transformation — into the BTAE-03 field of the PINT-AE XML.

For businesses with a diverse transaction portfolio — FTZ operations, export sales, continuous supplies, and agent billing arrangements — the flag configuration exercise is a significant design task that sits at the intersection of business process analysis and ERP configuration. It requires the business to document every transaction type it generates, determine the correct flag combination for each, and validate that the ERP configuration correctly produces that combination. This work should be conducted as part of the transaction universe mapping exercise, not deferred to the integration testing phase.