PINT-AE is a closed field set. The Guidelines state that Persons and Government Entities will not be allowed to add additional optional fields of their own, and that industry-specific field requirements should be discussed with the appointed ASP to determine how they can be accommodated. Every piece of information an enterprise currently prints on an invoice has to find an existing PINT-AE field or leave the document. Section 12.2 names the fields that receive the commercial and operational data most often assumed to need a custom extension.
Contract Value, and the Obligation to Keep It Current
The Contract Value field carries the value of the underlying project or agreement. The Guidelines attach a maintenance obligation to it: if the project value changes, the Contract Value must be updated in the invoice issued after the change.
That obligation runs against how most project billing works. Contract value is typically captured once at project setup and left alone, with variations tracked in a change register that sits apart from the billing master. Under this requirement, the variation order becomes a trigger for a master data update, and an invoice issued after an approved variation carrying the original contract value states a figure the contract has already moved past. For contracting and engineering businesses, the practical control is a hard link between variation approval and project master maintenance.
Payment Instructions and Invoice Terms
Two distinct payment situations have two distinct fields. Where multiple payment methods apply to a single invoice, they can be included using the Payment Instructions field. Where buyer and supplier have agreed multiple payment dates for a single invoice, that arrangement can be included using the Invoice Terms field.
The separation matters because staged payment terms are frequently modelled in ERP as multiple due dates on a single document, and the instinct is to look for a repeating due-date structure. The Guidelines route that arrangement to Invoice Terms instead, which means the schedule is expressed as terms rather than as structured dates. Enterprises that rely on the invoice to drive customer-side payment scheduling should confirm with their ASP how the receiving system will render it.
Batch Number and Authority Name
The Batch Number field exists for manufacturing and trading businesses that categorise goods by batch for inventory management and traceability. Because it is a designated field, batch data has a home outside the item description, where free-text batch references degrade line-item matching on the buyer's side.
The Authority Name field carries the name of the trade licence issuing authority, and the Guidelines confirm that it must be manually populated by the issuer, with no code list provided. Free text with no controlled vocabulary, across an economy where each emirate operates its own licensing authorities, will produce many spellings of the same body. For a group issuing from several emirates, the useful step is to fix the exact string for each licensing authority in the entity master before go-live, so that the value is consistent across every entity and every invoice rather than being typed differently by each billing team.
What to Do With a Requirement That Has No Field
Where a genuine industry requirement finds no home, the Guidelines direct the Person to discuss it with the appointed ASP. That is the sanctioned route, and it has a timing consequence: any accommodation is a conversation with a provider rather than a configuration change inside the enterprise, so it belongs in the ASP selection and onboarding period rather than in the weeks before go-live.
The mapping exercise this implies is small and worth doing early. Take the current invoice layout, list every element on it, and mark each against a PINT-AE field. What remains unmapped is the agenda for the ASP conversation, and the length of that list is a reasonable proxy for how much billing redesign the mandate will actually require.