Field Orders and Credit Notes: The Two Documents That Decide Whether a UAE E-Invoice Is Right

We covered why the ASP deadline is only half the job: the provider carries the invoice and does not fix it. This follow-up looks at the two places a building-materials distributor is most likely to get an invoice wrong, because neither happens at a finance desk. One is the order taken on site. The other is the credit note raised when something goes back.

The Order Taken on Site Is Now a Tax Document

A large share of a distributor's revenue is written down away from an office: a rep at a construction site, a phone order at 6 a.m. Today that order is a draft. Someone re-keys it, finance issues a PDF, and a wrong detail can be quietly re-issued. Under e-invoicing that slack is gone. A rejected invoice has not been issued, and an accepted one is on record. Xamun's analysis of van sales and field orders makes the point that every re-keying step is a chance for the customer, the price, or the VAT treatment to drift from what was agreed.

Three things have to be right at that moment.

The customer's TRN.

A missing or mistyped Tax Registration Number fails at the provider on every invoice to that customer until someone fixes the record. The field process should show whether a customer already has a validated TRN before the order is confirmed.

The VAT category on each line.

PINT AE carries a category per line, not a rate on the total. One site delivery can mix standard-rated blocks, a delivery charge with its own treatment, and a customer in a designated zone. If the rep's screen shows only a total, someone else decides the VAT later, without having been on site.

What happens without a signal.

Sites and basements lose coverage. If an order can't be captured offline, the rep goes back to the notepad, and re-keying starts again. An offline draft keeps the order as captured and checks stock when the signal returns.

SalesOrderOS is built around these points. Its field-sales app runs from the browser on a rep's own phone with no app store, shows only that rep's customers, saves drafts offline, and re-checks stock on reconnect. Discounts are capped at 5%, and a new prospect is held until the trade licence arrives. Orders can also be said in one sentence in English or Arabic, and the assistant fills the form for a person to confirm. Because the invoice is built from this same order, with VAT frozen on every line, nothing is typed twice.

A UAE e-invoice is only as accurate as the order a rep captures on site, so the TRN, the VAT category on each line, and the delivery depot all have to be right before the sale is confirmed.

The Credit Note Is the Harder Document

Heavy goods break in transit, deliveries come up short, and sites reject loads. Every one ends in a credit note, and credit notes are in scope for e-invoicing in the same way as invoices. Xamun's piece on credit notes under PINT AE explains why this is where many distributors will find their current habits don't survive.

A credit note has to reference the specific invoice it corrects. Many returns processes today produce one month-end credit note per customer covering breakage from one invoice, a short delivery from another, and a price adjustment from a third. That convenience exists only because nothing checks it. Under PINT AE it becomes three credit notes, each tied to one invoice and its lines. The VAT treatment also carries over from the original line, which means the system must know what the category was when the invoice was issued, not what the price list says now.

The reason has to travel with the document too. Agreeing a short list before go-live helps: breakage in transit, short delivery, return, price correction, rejected delivery. Each implies a different control, such as a driver's note, a goods receipt, or an approval, and a system that raises credit notes without asking for that evidence tends to raise too many.

This works cleanly only when the invoice was frozen at issue. In SalesOrderOS an invoice locks once the provider accepts it, and any change is a credit memo raised against it, so the two documents agree.

A Quick Test Before Your Date

Take last quarter's credit notes and ask three questions of each. Can it be tied to exactly one invoice? Do its lines match lines on that invoice, with the same VAT treatment? Is the reason recorded somewhere a system can read? Then take a week of field orders and count how many were typed in a second time. Those two numbers show where January's rejections will come from. Xamun's eight-point checklist covers the rest of last quarter's invoices.

If you want to see what your own field orders and returns look like as PINT AE documents, book a walkthrough of SalesOrderOS with Xamun and BlastAsia, or see the live demo on fictional data.