Flag position 5 of BTAE-02 as a continuous supply and you have made the authority a promise: that this invoice also carries a billing frequency and an invoice period. An invoice that keeps only half that promise validates anyway.
The Eight Transaction Flags post covers what the eight BTAE-02 positions mean. What it deliberately leaves for here is what happens after a flag is set correctly: each position activates a conditional ruleset of its own, and the failure mode this post is about is classifying a transaction correctly and then failing to supply the data that classification promises the authority.
A tax interpretation decision, not a technical one
Before BTAE-02 is read, the receiving system checks two structural identifiers: the Specification Identifier (IBT-024, carried in the UBL CustomizationID element) and the Business Process identifier (IBT-023, ProfileID). Together with BTAE-02 itself, these three fields form the authority's transaction classification layer, and OpenPEPPOL publishes the fixed codelist the Business Process identifier is drawn from. The enterprise does not invent the values. It selects from a fixed list — but that selection is a tax interpretation decision, not a technical one. A system engineer can map a code to a field. Only a tax professional can determine which code is correct for the transaction being invoiced.
Continuous supply: the promise and the gap
Long-term service contracts, leases, outsourcing arrangements and software subscriptions qualify as continuous supplies under UAE VAT, meaning VAT is due periodically over the contract term rather than at a single point of supply. Once the receiving system reads a continuous supply classification through BTAE-02 position 5, two fields become mandatory: BTAE-06, Frequency of Billing, and the Invoice Period group (IBG-14) covering the billing period's start and end dates. Together they let the authority answer a question a discrete-supply ruleset cannot ask: is this invoice being issued at the right point in the billing cycle, for the right period, at the right frequency, for this supplier and this contract?
An enterprise that populates BTAE-02 correctly for its continuous supply invoices but leaves BTAE-06 unconfigured has classified the transaction correctly and then failed to supply the data the authority expects once it has read that classification. The receiving system sees a continuous supply flag with no frequency marker and no billing period — a structural gap the authority's analytics will register, even though the invoice itself validates.
The reverse failure looks cleaner and is worse
The opposite error is easier to miss because it produces no rejection at all. An ERP that maps a long-term service contract as a standard invoice type — no continuous supply classification, no billing period populated — can transmit every invoice on time while the authority receives none of the structured data needed to recognise the arrangement. The authority sees a series of standard invoices from that supplier with no indication they relate to a continuous supply contract, and applies discrete-supply timing analysis to a relationship that was never discrete.
Same lesson, both directions
Both failures share one structure. The classification layer tells the authority's system what kind of transaction it is looking at and activates a specific set of conditional data expectations. Get the classification right and the conditional data wrong, and the compliance picture presented to the authority is wrong even though validation passes. Get the classification wrong entirely, and the authority evaluates the transaction against a ruleset that was never the right one to begin with. The codelist BTAE-02 draws from is fixed; the conditional field logic it triggers is fixed. What the enterprise controls — and what tax has to own at the ERP configuration stage, not the filing stage — is whether the correct transaction type code is selected for each transaction, and whether the conditional fields it activates are fully and accurately populated from the internal data that should govern them.