Most people starting with e-invoicing begin at the wrong question: "which software should I buy?". The right question comes first: which implementation phase applies to me now, and what must be ready before my first invoice?
This guide walks through seven practical steps, from registration to issuing your first correct electronic invoice.
1. Confirm Your Tax Position First
Before any software: is your business tax-registered? What is your TRN? And which implementation phase applies to your turnover in your country?
That information comes from your tax authority, not from a software vendor, because phases are updated periodically and vary by business size. Buying a system before knowing your phase means you may buy more or less than you need.
2. Organise Your Master Data
An e-invoice is built from stored data, not from typing. Prepare:
- Your entity details: full legal name, address, TRN, commercial registration.
- Your customer file: legal names, addresses, and TRNs for business customers.
- Your item and service list with clear descriptions, units, and prices.
- VAT rates applied per item, including exempt and zero-rated.
What stalls implementations most is the second item: a customer file with no TRNs means every B2B invoice halts at issue. Collect them before you start, not during.
3. Choose the System on Its Output, Not Its Interface
Before that, make sure you know what makes a tax invoice compliant — it is the yardstick for judging any invoicing system.
Don't judge software by its screens. Ask for three things:
- A sample e-invoice actually issued from the system in your country's format
- A credit note linked to an original invoice
- A tax report ready for filing
A vendor who cannot produce all three today is selling you a roadmap, not a system.
4. Set Up Numbering Before the First Invoice
Sequential numbering is a decision made once and hard to change later. Define:
- One series, or a series per branch or document type
- The starting point, especially if migrating from a previous system
- No manual editing of the number — this must be locked in the system, not merely a policy
The most common error here is starting from an arbitrary number or repeating a previous series, breaking the sequence from day one.
5. Issue a Test Invoice and Check It Field by Field
Before going live, issue a test invoice to a real customer from your own data, print it, and check:
| Check | What you're looking for |
|---|---|
| Title | "Tax Invoice" written explicitly |
| Tax numbers | Yours and the customer's, present and correct |
| Sequence and date | A unique number and correct date |
| Line items | Detailed descriptions, not a generic word |
| VAT | Net, rate, amount, and gross shown separately |
| QR code | Present and actually scannable by phone |
| Arabic text | Rendered correctly, not broken, in the printed copy |
The last item is widely overlooked: many systems display Arabic correctly on screen and break it on print or export.
6. Train Your Team on Two Situations Specifically
General system training matters less than mastering two recurring cases:
- What do we do when there's an error? Answer: a credit note linked to the invoice — never an edit, never a delete.
- What do we do on a return or cancellation? Same principle: a linked document, not a change to the original.
Most invoicing violations don't come from bad intent — they come from a member of staff trying to "fix" an invoice in good faith.
7. Monitor the First Month, Then Review
After the first month live, review three numbers: is the sequence unbroken? Does every B2B invoice carry a customer TRN? Does the tax report reconcile with your books?
Any discrepancy caught in the first month is corrected easily. The same discrepancy after a year becomes a review of hundreds of invoices.
Frequently Asked Questions
Where do I start with e-invoicing?
Start by confirming which implementation phase applies to you on your tax authority's site, then organise your master data (entity, customers with TRNs, items and VAT rates), then choose a system based on an invoice actually issued from it rather than on its interface.
What do I need before issuing my first e-invoice?
An active TRN, complete entity details, a customer file with TRNs, an item list with descriptions and VAT rates, and a system that outputs the format required in your country. The most common gap is missing customer TRNs.
Is a QR code mandatory on invoices?
It depends on your country and the phase in force. Where it is required, make sure it isn't merely printed but actually scannable — test it with your phone on a printed invoice before going live.
How do I migrate from an old system without breaking the sequence?
Set the starting number in the new system so it continues the previous series, or begins a new series documented with the migration date. What matters is that the transition is recorded and justified, not that numbering starts arbitrarily.
Can I issue e-invoices from Excel?
Generally not in the legal sense. Excel doesn't prevent editing an issued invoice, doesn't guarantee an unbreakable sequence, and doesn't produce the structured format or digital stamp that e-invoicing frameworks require.
What if my customer is an individual with no TRN?
Invoices to individuals carry different and lighter requirements than B2B invoices in most frameworks. What matters is that your system distinguishes the two automatically rather than blocking issue over a number that isn't required.
Conclusion
E-invoicing isn't a technology project — it is a data-organisation project. Businesses that stumbled during implementation mostly stumbled at step two, on an unorganised customer and item file, not on choosing software.
Start collecting your customers' tax registration numbers this week. That alone covers half the distance before you open any system.
Read next: Invoicing Software — The Complete Selection Guide.