Almadar A retailer on King Fahd Road issuing invoices with broken right-to-left layout has a legal compliance problem, not a cosmetic one.
ZATCA requires Arabic on tax invoices, and in practice most Riyadh businesses issue bilingual documents so that Arabic satisfies the regulator while English serves international suppliers and customers. Getting the bilingual layout right is a configuration exercise in the ERP, and it interacts directly with Phase 1 field requirements and QR code placement.
The item description problem
The single most common gap is item master data. A system can render every label and heading in Arabic and still produce an invoice where every line item description is in English only, because nobody populated Arabic descriptions in the product master. Fixing this is a data exercise across potentially thousands of items, and it is the reason we assess item master completeness before promising an Arabic invoice go-live date.
Layout and rendering
Right-to-left layout is not simply mirroring. Numbers, currency amounts and Latin-script product codes remain left-to-right within an RTL document, and mixed-direction text needs correct bidirectional handling or it displays in a scrambled order. Font selection matters too: the font must render Arabic correctly in the PDF output and in the printed result, and some default report fonts do not.
Names, addresses and legal identifiers
The seller's legal name in Arabic must match the commercial registration exactly, and the same applies to the buyer's name on B2B invoices. Addresses follow the Saudi national address format with building number, street, district, city and postal code. These are the fields inspectors check first, and mismatches between the invoice and the CR are a common finding.
A common Saudi scenario
An Riyadh industrial supplier configures Arabic invoice templates successfully but discovers during a customer audit that its own legal name appears in a shortened trading form rather than the full registered Arabic name on the commercial registration. Every invoice for two years carries the wrong seller name. Correction is straightforward going forward but the historical exposure has to be assessed and disclosed.
Testing before rollout
We test the configured template against every invoice variant the business issues, long item descriptions that wrap, multi-page invoices, credit notes, foreign currency, zero-rated and exempt lines, and we test the printed output on the actual devices in use. A template that renders correctly in a PDF preview and breaks on a thermal printer is a common and entirely avoidable failure. This connects to broader Arabic reporting configuration across the system.
Populating the item master efficiently
Translating thousands of item descriptions is the part clients dread, and it is manageable with sequencing. We prioritize by transaction volume so the items on ninety percent of invoices are correct first, use consistent terminology across product families rather than translating line by line, and put a validation rule in place preventing new items being created without an Arabic description, so the backlog never rebuilds. The same master data discipline underpins Arabic financial statements.
Businesses trading with government entities and large Saudi corporates face the strictest scrutiny on Arabic legal name and national address accuracy, while retail operations are more often caught out by item master descriptions never having been populated in Arabic.