In the UAE, the Local Purchase Order (LPO) is central to business-to-business trade across contracting, trading, distribution and government supply. In practice, invoices are frequently delayed because the LPO number is missing, quantities or prices do not match, or approval has not been completed.

e-Invoicing makes these weaknesses more costly. Once invoice data is structured and validated, what is captured before the invoice matters more than ever.

An invoice is no longer just a document to return
Where a transaction is cancelled, consideration is reduced, a refund is made or an error needs correcting, an electronic credit note may be required. Late credit notes carry a penalty of AED 100 each, capped at AED 5,000 a month.
Not every disputed invoice attracts a penalty, but the habit of returning an invoice and asking for a replacement no longer fits every case. Finance teams should distinguish three situations: an invoice rejected at technical validation, which is corrected and resubmitted; a commercial dispute, which must be resolved with the customer; and an error in an invoice already issued and reported, which is corrected through a credit note within the applicable time limits.

The LPO number becomes an important data point
In the UAE’s PINT AE specification, the purchase order reference is an optional field. Optional does not mean commercially unimportant. Buyers rely on it to match invoices against approved orders, delivery records and prices. Without it, an invoice can pass technical validation yet still stall in accounts payable.
Suppliers should capture the LPO reference when the sales order is created and carry it automatically into the invoice, rather than relying on manual entry at the end. Where buyers require further references, agree in advance how these will be recorded.

LPO delays do not remove tax obligations
Commercial approvals do not automatically change the VAT tax point or the e-Invoicing deadline. For e-Invoicing purposes, the date of a business transaction is the earlier of the date it occurs or the date payment is received. Businesses should identify where delivery precedes LPO approval, or payment precedes invoicing, and align controls accordingly.

Partial deliveries, advance payments and retentions
Staged deliveries, milestone billing, advance payments and retentions, common in construction and project work, need consistent data across purchase orders, delivery records, invoices and credit notes.

Define how each invoice references the original order and the relevant delivery or milestone. Version 1.1 of the MoF’s Guidelines added an appendix on advance payments and retentions; confirm how it applies to your contracts. A good ERP workflow carries the order reference forward and flags differences before an invoice is transmitted.

What buyers and procurement teams should do
Share your identifiers. Suppliers need your Peppol participant identifier, which is based on your Tax Identification Number, to deliver e-Invoices to you.
Approve LPOs on time, so that orders exist before goods or services are delivered.
Agree how discrepancies will be managed, including price differences, short deliveries and corrections.
Prepare for a phased transition. Businesses below AED 50 million go live from July 2027, so in the first half of 2027 large buyers will receive structured e-Invoices from some suppliers and conventional invoices from others.
What should tax advisers and finance teams review?
LPO-to-invoice mismatches have long caused VAT errors, payment disputes and audit findings. Structured data can strengthen controls, but only if the underlying processes are reliable. Review the full procure-to-pay and order-to-cash journeys, including matching, tax treatment and credit notes, and confirm that the ERP holds references as structured data.
This is not solely an IT task. Procurement, payables, receivables, tax and operations must agree how exceptions will be handled.

What LPO-based businesses should do now
Map the journey from purchase order to payment, then test representative scenarios, including partial deliveries, advances, retentions, disputes and credit notes. Resolve gaps before go-live rather than relying on manual workarounds afterwards.
In an LPO-driven business, e-Invoicing compliance starts not at the invoice, but at the purchase order.

A Nigeria’s private sector is building. Developers are delivering residential estates, office blocks, shopping malls, hotels, factories and warehouses across Lagos, Abuja, Port Harcourt and beyond. Private construction is one of the most visible signs of economic activity, and one of the biggest employers of skilled and unskilled labour.

But behind every finished building sits a long chain of transactions that rarely gets the same attention as the structure itself. Much of the value chain that moves a project from site clearing to handover still runs on cash, handwritten receipts and informal arrangements. Under Nigeria’s e-invoicing mandate, that is no longer just a paperwork problem. It is a direct risk to your VAT input claims, your deductions and your audit position.

Why e-invoicing compliance is non-negotiable

The Nigeria Revenue Service (NRS) e-invoicing mandate, delivered through the Merchant Buyer Solution (MBS), requires businesses to issue invoices that are validated by NRS in real time, each carrying an Invoice Reference Number (IRN).

Large taxpayers (turnover above ₦5 billion) went live in November 2025. Medium taxpayers (₦1 billion to ₦5 billion) went live on 1 July 2026, with compliance enforcement scheduled for January to March 2027. Emerging taxpayers below ₦1 billion follow from July 2027, with enforcement in 2028.

For private developers and contractors, the stakes sit on both sides of the ledger. Every invoice you raise must go through the MBS, and every purchase you want to claim input VAT on, or deduct as a business expense, needs proper documentation behind it. An invoice that never touched the NRS system is an invoice that is harder to defend.

Construction also has a billing pattern most sectors don’t. Projects are paid in stages, Each of those stages becomes an invoice, and each adjustment needs to be handled properly within the system rather than fixed by editing documents after the fact. Your clients are checking too. Large developers and corporate clients will increasingly be expected to have validated invoices especially when working with the government, their input VAT also depends on it.

Two structural challenges unique to construction

A materials supply chain with an inherited gap. Cement and steel may come from large manufacturers with clean invoicing, but sand, granite, laterite, blocks and timber often come from quarries, dredgers, block makers and local dealers who operate informally. When a subcontractor buys these on your behalf, their incomplete records become your exposure. The contractor doesn’t create the gap. They inherit it.

A fragmented equipment and logistics layer. Projects rely on tipper trucks, plant and equipment hire, diesel suppliers, scaffolding, site security and waste removal. Many are small operators who are not issuing e-invoices for their services. Each one is a line in your project costs that may not stand up to scrutiny.

Put together, these two factors mean the documentation gap on a construction site isn’t an edge case. It’s the default state of the transaction.

How construction businesses can close the gap

Make your own invoicing airtight. Every valuation, progress payment and final account should flow through an NRS-validated e-invoice. Connect your ERP, accounting or project costing system to the MBS through an accredited Access Point Provider or System Integrator, so compliance happens as each certificate is issued, not as a scramble at month-end.

Build compliance into procurement. Make a valid TIN, and an IRN-bearing invoice where the supplier is already onboarded, part of subcontractor onboarding and payment approval. If a supplier in scope can’t produce one, that should be flagged before payment, not during an audit.

Know which suppliers are in scope, and which aren’t yet. Map your subcontractors and suppliers by taxpayer category. Large and medium suppliers should already be issuing e-invoices. Emerging suppliers, including most labour subcontractors and local materials dealers, come into scope from July 2027. Until then, keep clean, consistent purchase records for them so the transition is smooth when the mandate reaches them.

Connect invoices to the rest of your paper trail. Projects already generate data: bills of quantities, valuations, interim payment certificates, delivery notes, site diaries, plant logs and withholding tax receipts. Linking e-invoices to these records creates one consistent trail from site to handover, which is exactly what an auditor wants to see.

What sector-wide adoption could look like

No single developer or contractor can formalise thousands of artisans and small suppliers alone. Industry bodies such as the Real Estate Developers Association of Nigeria (REDAN), the Federation of Construction Industry (FOCI), the Nigerian Institute of Building and the Nigerian Institute of Quantity Surveyors are well placed to coordinate e-invoicing readiness across private construction.

A common integration model. Rather than every contractor separately working out how to connect to the MBS, an industry-led framework could agree standard data formats for valuations and progress billing, and a recommended integration approach, cutting duplicated effort and creating consistency across the sector.

TIN registration drives. Registration and supplier verification can run through the places artisans and suppliers already gather: trade associations, materials markets and major sites. That makes formalisation achievable at scale rather than one subcontractor at a time.

A shared supplier registry. Because contractors often use the same subcontractors and materials dealers, a central registry of verified suppliers, holding each supplier’s TIN and taxpayer category with safeguards in line with the Nigeria Data Protection Act, would let members check a supplier’s status before they engage them.

Education on site. Short sessions at sites, materials markets and trade association meetings reach far more artisans than individual contractor efforts ever could. The message should be practical: documented work strengthens a tradesperson’s own tax position and improves their access to finance and bigger contracts.

Technology as the backbone. Once suppliers are verified and in the system, compliant invoicing becomes almost automatic. An accredited integrator like DigiTax can connect each contractor’s ERP, project costing and payment systems to the MBS, so every certificate is validated and every eligible purchase is backed by a compliant invoice.

Construction runs on trust, timelines and cash flow, and a disallowed VAT claim or an audit query hits all three. For private developers, contractors, subcontractors and materials suppliers, the question is no longer whether the documentation gap will be scrutinised, but when. With medium taxpayer enforcement starting in early 2027, the time to close it is now.

Businesses that build e-invoicing into their procurement and billing workflows today will protect their input VAT claims, reduce audit exposure and build a fully documented value chain from site to handover.

If you’re a private developer, contractor, materials supplier or industry body exploring what e-invoicing compliance looks like for your projects, DigiTax can help. Get started at Here.

Many UAE businesses operate through multiple legal entities: a trading company, a property-holding company, a shared-services business or a Free Zone subsidiary, often sharing ownership, management and systems.

A common assumption is that transactions between companies under the same ownership are internal matters, outside e-Invoicing. That assumption can create significant compliance risk. The critical question is not whether two companies belong to the same corporate group, but whether they belong to the same registered VAT group.

Start with one question: are the companies in the same VAT group?

A commercial group and a VAT group are not the same thing. Unless companies are registered together as a VAT group, transactions between them are generally treated as transactions between separate businesses. Management fees, shared-service recharges and intercompany sales may therefore fall within e-Invoicing. Common ownership, consolidated accounts or internal settlement arrangements do not create an exemption.

Companies within the same VAT group

The Ministry of Finance’s Guidelines confirm that transactions between members of the same VAT group remain within scope. However, a temporary 24-month grace period applies from 1 January 2027 to 31 December 2028, during which these transactions need not follow the e-Invoicing process.

This is a deferral, not an exemption, and it covers only transactions between group members. Each member’s dealings with outside customers and suppliers follow the normal timetable. Each member is also onboarded separately using its own Tax Identification Number. The representative member does not cover the whole group, and a centralised finance function does not change that.

Related companies outside a VAT group

Related companies outside a VAT group get no equivalent grace period. Consider a group with a mainland trading company, a Free Zone subsidiary and a shared-services company charging each other for goods, management services or support. Those transactions follow the normal e-Invoicing rules.

Because the timetable depends on each entity’s own revenue, companies in the same group may go live at different times. Where one entity must issue e-Invoices before its sister company has implemented the system, current guidance provides a transitional route: the e-Invoice is sent to a prescribed fallback endpoint and a conventional invoice is provided alongside it. Confirm the process with your Accredited Service Provider.

What about branches and overseas affiliates?

Branches and divisions of one legal entity should be distinguished from separate subsidiaries. Internal allocations within one legal entity do not automatically constitute supplies, but the underlying arrangements must be examined.

Charges to overseas group companies also need care. Not every such charge is automatically an export with identical treatment; the nature of the supply and the recipient’s circumstances matter. Where an overseas recipient has no Peppol identifier, the guidance provides a prescribed endpoint for exports.

Three traps to avoid

1. Treating the grace period as permanent. Use the 24 months to clean up intercompany master data, review recurring charges and align systems.

2. Overlooking year-end adjustments. Reconciliations, management-fee adjustments, cost allocations and transfer pricing true-ups can generate invoices or credit notes. Decide now how they will be processed.

3. Ignoring the Corporate Tax connection. Intercompany charges should be supported by contracts and commercial evidence and aligned with transfer pricing policies. An e-Invoice provides transaction data; it does not, by itself, show that a charge meets the arm’s-length principle.

What should groups do now?

Start with an entity-by-entity map of intercompany transactions: the entities involved, whether they share a VAT group, the nature of the supply, each entity’s implementation date and the systems that create the invoice. Then review recurring charges, master data, contracts and transfer pricing documentation.

For tax advisers, this is an opportunity to address VAT grouping, e-Invoicing readiness, Corporate Tax and transfer pricing in one coordinated exercise.

Common ownership does not mean common invoicing obligations. Understanding the legal and tax relationship between entities is the starting point for getting intra-group e-Invoicing right.

As the 30 October 2026 deadline approaches, several e-Invoicing requirements are being widely misunderstood. Because they determine who must act and when, this mid-week article sets out each one in full.

1. Below the threshold: your legal and commercial deadlines may differ

The legal position. A business with revenue below AED 50 million must appoint an Accredited Service Provider (ASP) by 31 March 2027 and implement e-Invoicing from 1 July 2027. It is not legally required to appoint an ASP by 30 October 2026 or to issue e-Invoices from January 2027, and penalties for late implementation apply only after its own deadlines.

How the gap is bridged. From January 2027, a large supplier selling to a business that has not yet onboarded still issues an e-Invoice, sends it to a prescribed fallback endpoint and provides a conventional invoice alongside it. The smaller business can keep receiving and paying invoices as it does today until its own go-live date.

The commercial position. Large customers go live in January and will want structured invoices they can process automatically. Some may ask suppliers to onboard early, or build e- Invoicing into contracts and tenders. That is a commercial requirement, not a legal one, but itcan be just as decisive. Any business may adopt e-Invoicing voluntarily, so suppliers to major customers should ask about their expectations now.

2. B2C revenue counts towards the threshold

B2C transactions are currently outside the scope of e-Invoicing. The AED 50 million test, however, is not limited to in-scope transactions. Revenue means gross income earned during the most recent accounting period, based on the financial statements or, where there are none, other documentation acceptable to the FTA.

Three consequences follow. A retailer, restaurant or clinic selling mainly to consumers can still fall into the January 2027 phase. The test is gross revenue, not profit, taxable income or VAT-taxable supplies. And a business with revenue of exactly AED 50 million is in the first phase.

The test applies to each legal entity, not to consolidated group revenue. Businesses close to the threshold should confirm their position with their adviser rather than assume.

3. Buying also requires an ASP

E-Invoicing is often described as a seller’s obligation. In the UAE’s 5-Corner Model it is not. Both issuers and recipients must operate through an ASP, and each business uses one ASP for sending and receiving.

A business that sells mainly to consumers but buys from UAE suppliers therefore still needs an ASP to receive e-Invoices from its own go-live date. Recipients also have continuing duties, including notifying their ASP of changes to registered data; late notification carries a penalty of AED 1,000 per day.

4. VAT groups do not share one connection

A VAT group files one VAT return, but e-Invoicing operates at the level of each legal entity. Each member is onboarded separately using its own Tax Identification Number. The representative member’s registration does not cover the others.

The grace period is also narrower than many assume. Transactions between members of the same VAT group are within scope but are relieved for 24 months, from 1 January 2027 to 31 December 2028. Transactions between a member and anyone outside the VAT group, including related companies that are not VAT-grouped, follow the normal timetable from the start.

The common thread

e-Invoicing obligations turn on precise tests: revenue, legal entity and VAT-group status. They do not turn on assumptions about size, ownership or whether a business mainly sells or buys.

Every business should confirm, in writing, its phase, its obligations as a recipient and the position of each entity it controls, with its adviser and its ASP.

Nigeria’s solid minerals sector is formalising fast. Local value addition is now a licensing principle, mining cooperatives are bringing artisanal miners into the formal economy, and processing investment is flowing in.

But much of the chain that moves a mineral from pit to export container still runs on cash, handwritten receipts and informal relationships. Under Nigeria’s e-invoicing mandate, that is a direct risk to your VAT input claims, your deductions and your audit position. Energy companies face the same exposure through long chains of contractors and suppliers, many of whom are not yet issuing e-invoices.

Why e-invoicing compliance is non-negotiable

The Nigeria Revenue Service (NRS) e-invoicing mandate, delivered through the Merchant Buyer Solution (MBS), requires invoices validated by NRS in real time, each carrying an Invoice Reference Number (IRN).

Large taxpayers (turnover above ₦5 billion) went live in November 2025. Medium taxpayers (₦1 billion to ₦5 billion) went live on 1 July 2026, with enforcement scheduled for January to March 2027. Emerging taxpayers below ₦1 billion follow from July 2027, with enforcement in 2028.

Every sale you make must go through an NRS-validated e-invoice, and every purchase you claim input VAT on or deduct needs proper documentation behind it. Exporters should pay particular attention: zero-rated exports often leave them in a credit position, and recovering that input VAT is only as strong as the invoices supporting it.

Where the gaps are

Buying centres and aggregators. Processors and exporters rarely buy straight from the pit. When intermediaries’ records are incomplete, the buyer doesn’t create the gap. They inherit it, along with the compliance exposure.

A fragmented services layer. Haulage, equipment hire, site security, assay labs, warehousing and clearing agents are often small, informal providers who are not issuing e-invoices. Each one is a line in your expense ledger that may not stand up to scrutiny.

Deep contractor chains in energy. Upstream, power and renewables projects run through layers of contractors, subcontractors and community-based service providers, many well below the medium taxpayer threshold.

Special VAT treatment doesn’t mean invoice-free. Exemptions and zero-rating change the VAT on the invoice, not the obligation to issue one.

How to close the gap

Make your own invoicing airtight. Connect your ERP or accounting system to the MBS through an accredited Access Point Provider or System Integrator, so every sale is validated automatically rather than as a manual step at month-end.

Build compliance into procurement. Make a valid TIN, and an IRN-bearing invoice where the supplier is already onboarded, part of supplier onboarding and payment approval.

Know which suppliers are in scope. Large and medium suppliers should already be issuing e-invoices. For emerging suppliers, including most cooperatives and small buying centres, keep clean purchase records until they come into scope in July 2027.

Connect invoices to your paper trail. Link e-invoices to weighbridge tickets, assay certificates, royalty payments, metering data and export documents for one consistent trail from source to sale.

A role for industry bodies

No single company can formalise thousands of small suppliers alone. The Miners Association of Nigeria and mining cooperatives, alongside energy groups such as the Independent Petroleum Producers Group, the Petroleum Technology Association of Nigeria, the Association of Power Generation Companies and the Renewable Energy Association of Nigeria, are well placed to coordinate readiness at sector level.

That could mean agreeing a common MBS integration model, running TIN registration drives through cooperatives and contractor onboarding, keeping a shared registry of verified suppliers in line with the Nigeria Data Protection Act, and educating miners at buying points on how documented sales strengthen their tax position and access to finance.

The bottom line

With medium taxpayer enforcement starting in early 2027, the time to close the documentation gap is now. Businesses that build e-invoicing into procurement and sales today will protect their input VAT claims, reduce audit exposure and build a fully documented value chain from pit to port and wellhead to market.

If you’re a mining company, energy operator, processor, exporter or industry association exploring e-invoicing compliance, DigiTax can help. Get started at digitax.tech/ng

On 4 September 2026, KRA issued a public notice requiring all taxpayers in business to keep accurate and up to date stock records which tally with TIMS or eTIMS figures. This means that companies must account for goods as they move through the business, including stock purchased or received, sold, transferred, returned, adjusted or otherwise disposed of.

For manufacturers, this is a critical requirement for tax compliance and might potentially a tax compliance headache and source for generation of tax audits. Unlike retailers or traders, a manufacturer buys raw materials and packaging, converts them into finished goods for sale. The form of inventory changes form at different manufacturing stages. Therefore, tax compliance with this eTIMS requirement needs planning.

Legal basis

eTIMS was introduced in 2024 and has continued to be an area of focus for the current government. In subsequent legislative amendments, the government has sought to find ways to tighten compliance including reverse invoicing, limitations around expense deductibility and penalty provisions. Under the Finance Act 2026, KRA can also prepare prepopulated returns from eTIMS data, including inventory. Once stock is recorded as purchases on eTIMS, KRA will be able to compare the raw materials a manufacturer bought, the finished goods it sold and the stock it reports as remaining.

For a manufacturer, cost of sales varies depending on the industry and accounting practice and due care needs to be exercised when undertaking operations, particularly, because it forms one of the largest expenses in the income tax return.

Challenges

With the introduction of this requirement we foresee the following challenges.

1. Conversion of inputs - one tonne of raw material does not become one tonne of product due to changes in form in the manufacturing process which might lead to reconciliation differences.

2. Work in progress - at any time, part of the stock is neither raw material nor finished goods. Businesses with long production cycles need to decide how and when work in progress is recorded, so that month end figures make sense.

3. Wastage, scrap and by-products. Some processes also create by-products that are sold separately. These must be recorded as adjustments or as separate stock items. Unexplained losses are likely to be queried by KRA.

4. Transfer of stock across multiple locations for example, manufacturers move goods from the factory to warehouses, depots and distributors. Each transfer needs to be recorded so that stock is not counted twice or lost between sites.

5. Excisable goods. Manufacturers of beverages, cosmetics, plastics and other excisable products already report production and removals for excise purposes. Their eTIMS stock records will need to line up with these excise records.

Proposed actions

Manufacturers need to ensure that the eTIMS stock purchases tally with cost of sales and any variances identified must be explained. For example, if the cost of sales includes indirect costs and service component, this should be clearly articulated and reconciled by the manufacturer in the event of any audit. Therefore, manufaturers should also conduct regular reconciliation exercises to avoid gaps in the event of an audit

Finally, manufacturers should take part in the KRA consultative forums. Issues such as work in progress, by-products and normal process losses that are specific to the manufacturing sector, should be raised and addressed during these forums to ensure ease of implementation once this initiative is rolled out.

For any further clarifications, please do not hesitate to contact Digitax.

Businesses with revenue of AED 50 million or more have until 30 October 2026 to appoint an Accredited Service Provider (ASP). Smaller businesses, with a 31 March 2027 deadline, are only starting to look. For both, this choice will shape how invoices flow for years. It deserves more than a price comparison.

What an ASP does, and what it does not

The ASP is your gateway to the 5-Corner Model. It validates invoices against the UAE PINT AE specification, delivers them to your customer’s ASP, receives invoices from your suppliers and reports the data to the FTA. Each business uses one ASP for both sending and receiving.

What an ASP will not do is fix your data or your ERP. If customer TRNs are wrong, VAT treatments are inconsistent or credit notes sit outside the system, the ASP will simply reject the problem or transmit it faster. Getting clean, complete data out of your ERP remains your responsibility.

Check accreditation properly

The Ministry of Finance publishes two lists: fully accredited ASPs, and pre-approved providers still completing final accreditation. They are not the same. Check the live MoF list rather than a vendor’s brochure, and if a provider is only pre-approved, ask when final accreditation is expected and what happens if it is delayed. DigTax, operated by Namiri Technology Services, is on the MoF’s accredited list.

What to evaluate

ERP integration: proven connectors for your ERP, or a custom build?

Receiving, not just sending: can incoming e-invoices flow automatically into accounts payable?

Security and residency: where is your data hosted, and does archiving meet UAE record-keeping rules?

Uptime and failure support: what service levels apply, and how will the ASP help you notify the FTA when systems fail? Late notification costs AED 1,000 per day.

Exit: how easily can your Peppol registration move if you switch provider?

Red flags in contracts

Be cautious of contracts that lock your ERP integration and data mappings into the ASP’s proprietary tools, leave responsibility for rejected invoices vague, lack clear service levels and exit terms, or price per invoice in ways that escalate as volumes grow.

The safer design separates two layers: an independent ERP extraction and validation layer that prepares compliant data, and an ASP that transmits it. DigiTax has developed tools for extracting data as a separate service from SAP ERP (B1, ByD & S4 landscapes). Your data stays under your control, and your ASP stays replaceable.

Points many businesses miss

1. Below the threshold does not always mean “July”. Legally, smaller businesses go live on 1 July 2027. Commercially, large customers go live in January and may ask suppliers to onboard early. Your legal deadline and your commercial deadline may differ.

2. B2C revenue counts. B2C transactions are out of scope, but the threshold is based on gross revenue for the most recent accounting period, per legal entity.

3. Buying also requires an ASP. Recipients must be connected, not only issuers.

4. VAT groups do not share one connection. Each member onboards separately; only transactions between group members get a 24-month grace period from 1 January 2027.

For advisers: running an ASP evaluation

Advisers can turn ASP selection into a structured exercise: confirm the client’s phase and scope, map invoice scenarios such as credit notes, advances, exports and self-billing, shortlist from the MoF list, score providers against agreed criteria, test with real invoices and review the contract before signature. A documented process also shows the client exercised reasonable care.

An ASP is a long-term partner in your compliance infrastructure. Choose it the way you would choose an ERP, not the way you would buy stationery.

Under KRA’s eTIMS requirements, every business transaction needs an electronic tax invoice. But what happens when your supplier can’t issue one? A smallholder tea farmer, a cooperative of coffee pickers, or a small-scale trader may not be positioned to generate compliant invoices themselves. This is where Reverse Invoicing comes in: it allows the buyer to generate the tax invoice on the seller’s behalf.

The question most finance and procurement teams eventually face isn’t whether to use reverse invoicing: KRA has made that requirement clear for these supplier categories. It’s how: through KRA’s own eCitizen portal, or through an integrated solution like DigiTax. The right answer depends almost entirely on the size and shape of your supplier network.

Two Routes, Two Very Different Workloads

1. eCitizen is KRA’s default access point for this functionality. Buyers can log into their KRA profile, select the relevant module (or dial *222# for the USSD version), enter the supplier’s PIN, and generate the invoice manually one transaction at a time.

2. DigiTax takes a different approach. Rather than manual entry per transaction, it integrates directly with your existing accounting or ERP system through a system-to-system connection, generating reverse invoices automatically from data you’re already recording.

When eCitizen Makes Sense

If your business deals with a small, direct list of suppliers who occasionally need an invoice generated on their behalf, eCitizen’s manual process is a reasonable fit. It’s free, it’s KRA’s own platform, and for low transaction volumes the extra data entry is a minor inconvenience rather than an operational bottleneck.

This tends to describe the buyer-initiated invoicing (BII) use case: a defined, direct relationship with a manageable number of small-turnover suppliers.

Where the Manual Process Breaks Down

The calculation changes for buyers operating in sectors with diffuse, high-count supplier networks — tea, coffee, sugar, dairy, floriculture, and similar sectors where a single buyer may be sourcing from well over a hundred smallholder suppliers in a given month.

At that scale, manual entry through eCitizen means:

• Re-keying every transaction by hand, separate from your accounting records

• A higher likelihood of mismatched PINs, amounts, or missed transactions

• No automatic reconciliation between what’s in your books and what’s been submitted to KRA

• Significant staff time spent on repetitive data capture rather than exception-handling or supplier relationships

This is the operational gap a system-to-system solution like DigiTax is built to close: automating the invoice generation itself, rather than automating around a manual process.

Compliance Considerations That Apply Either Way

A few things worth knowing regardless of which route you choose:

• Reverse invoicing is not enabled by default and is closely regulated by KRA, given its potential for misuse. Going live involves a formal process a commercial and technical review, a meeting with KRA, sandbox testing, and KRA’s user acceptance testing before approval.

• You cannot reverse-invoice a VAT-registered supplier. Before proceeding, confirm the supplier’s tax obligation status if they’re VAT registered, they need to issue their own invoice.

• Supplier consent matters. Whichever platform you use, KRA expects proof of the process you use to obtain consent from suppliers before invoicing on their behalf.

A Simple Way to Decide

Ask yourself two questions:

1. How many suppliers are you reverse-invoicing, and how often? A handful of suppliers a month points toward eCitizen. A hundred-plus scattered across an agricultural supply chain points toward automation.

2. How much staff time is currently going into manual reconciliation? If your team is spending hours matching invoices to your ledger by hand, that’s a sign the manual route is costing you more than the automation would.

There’s no universally “right” platform here: only the right fit for the shape of your supplier base. For low-volume, direct relationships, eCitizen does the job. For high-volume, diffuse networks, an integrated solution changes reverse invoicing from a recurring administrative burden into something your systems handle in the background.

Have questions about whether your business qualifies for reverse invoicing, or what the KRA approval process looks like? Get in touch with the DigiTax team here

The UAE is entering a new phase in its tax transformation journey. After VAT, Corporate Tax and the growth of digital tax services, the next milestone is e-Invoicing.

On 1 July 2026, the Ministry of Finance (MoF) launched the e-Invoicing Pilot Programme with a Taxpayer Working Group, and voluntary adoption opened to all businesses. Mandatory implementation begins on 1 January 2027 for the first category of businesses.

The question for businesses is no longer simply “Are we ready to issue electronic invoices?” but “Are we ready for a tax environment in which transaction data moves digitally and continuously, invoice by invoice?”

More than a digital invoice

UAE e-Invoicing is not simply replacing a paper invoice with a PDF. An e-Invoice is structured data, issued and exchanged electronically between supplier and buyer and reported to the Federal Tax Authority (FTA). UAE Ministry of Finance – e-Invoicing.

Because structured data can be processed automatically, the invoice becomes a source of tax and financial data that supports automated compliance, reconciliation and analysis. This is where e-Invoicing moves beyond an accounting project and becomes part of digital tax administration.

What is in scope?

The framework rests mainly on Ministerial Decisions No. 243 and No. 244 of 2025 (as amended by No. 66 of 2026) and the MoF’s Electronic Invoicing Guidelines, Version 1.1 of June 2026.

It covers the B2B and B2G transactions of persons doing business in the UAE, whether or not they are VAT-registered. B2C transactions are currently excluded, as are certain specific transactions such as some airline passenger services and certain financial services.

The UAE’s 5-Corner Model

The model links the supplier, the supplier’s Accredited Service Provider (ASP), the buyer’s ASP, the buyer and the FTA. Built on the Peppol network and the UAE’s PINT AE specification, it lets businesses connect through ASPs rather than directly to the FTA.

Two points are often missed. First, the obligation is not only on the seller: recipients of e-Invoices must also operate through an ASP. Second, e-Invoicing is not automatically an ERP replacement. Businesses keep invoicing from existing systems but must integrate them with their ASP.

The implementation clock is running.

Businesses with annual revenue of AED 50 million or more must appoint an ASP by 30 October 2026 and go live on 1 January 2027. The ASP deadline was extended from 31 July 2026, but the go-live date was not, and businesses should not expect further flexibility.

Businesses below AED 50 million must appoint an ASP by 31 March 2027 and go live on 1 July 2027. In-scope government entities have the same ASP deadline and go live on 1 October 2027.

Cabinet Decision No. 106 of 2025 backs the timetable with penalties, including AED 5,000 per month of delay in appointing an ASP or implementing the system, AED 100 per late e-Invoice or e-Credit Note (capped at AED 5,000 a month) and AED 1,000 per day for late notification of a system failure.

For large businesses, 30 October is not when preparation begins. It is when the ASP decision must already be made, leaving about nine weeks to integrate and test before go-live.

What does it mean for taxpayers?

Success depends on more than choosing an ASP:

Technology: ERP and accounting systems must generate, receive and process structured invoice data.

Data: customer and supplier details (including TRNs), tax treatments and mandatory fields must be accurate.

Processes: order-to-cash and procure-to-pay cycles, including credit notes, corrections and exceptions, may need redesign.

Governance: finance, tax, IT and operations need clear ownership, including who notifies the FTA when systems fail.

The lesson is simple: better digital tax compliance requires better business data.

Is your revenue above AED 50 million? Then the next three weeks are for choosing and appointing your ASP. Below it? You have until March to appoint one, but getting your systems and data ready is work that starts now.

Every business covered by the NRS e-invoicing mandate must send its invoices through a certified Access Point Provider. That part is settled.

What many finance teams are still asking is how their invoices will get there.

With DigiTax, there are two routes. The Dashboard. And the API.

Both are fully compliant. The difference is how your team works day to day.

Where Every Journey Begins

Whichever route you choose, it starts in the same place. Every business is first set up on the DigiTax Dashboard: your profile, your business details and your onboarding.

From there, you decide how your invoices will be issued.

The Dashboard: Issue Compliant Invoices Directly

The Dashboard lets your team create and send compliant invoices online, with no technical setup.

Everything happens on one business page. Your team creates invoices, issues credit and debit notes when a sale changes, and saves customer and product details so they don’t have to be retyped each time. Records can be downloaded whenever you need them for reconciliation or audit.

The Dashboard is the right fit if you issue a manageable number of invoices, don’t have a technical team, or want to go live quickly.

The API: Compliance Built Into Your Existing System

If your invoices are already generated in an ERP, accounting or billing system, the API connects that system directly to DigiTax.

Your invoices are submitted automatically as part of your normal workflow. Nobody has to re-enter them in a separate platform, which saves time and reduces the risk of errors. Under the NRS framework, inaccurate invoice data is a compliance problem, not an admin one.

To connect, your technical team generates an API key from the Integrations tab on the Dashboard and links it to your software.

The API is the right fit if you issue a high volume of invoices, operate multiple branches or entities, or already run an established invoicing system.

Which Route Is Right for You?

The Dashboard is likely your best route if:

• You issue a manageable number of invoices each month

• You don’t use an ERP or accounting system to generate invoices

• You don’t have in-house technical support

The API is likely your best route if:

• You issue a high volume of invoices

• Your invoices are already generated in an ERP, accounting or billing system

• You have a technical team or partner who can manage the connection

The Dashboard and the API lead to the same outcome: every invoice compliant, every record traceable. The right route depends on your invoice volume, your systems and your team.

If you’re still not sure which fits your business, you don’t have to work it out alone. In a short demo, our team will look at how your business invoices today, recommend the right route and walk you through what going live involves.

Book your demo today. Send an email to firs-si@namiri.tech or call +234 913 652 8711.

Introduction

On 31 August 2026, the Kenya Revenue Authority (KRA) issued a public notice announcing the integration of the Electronic Tax Invoice Management System (eTIMS) with the Integrated Financial Management Information System (IFMIS). This is a significant development for any business that supplies goods or services to government entities.

What is IFMIS?

IFMIS is the financial management system used by the national and county governments to process budgets and payments. When a government entity procures goods or services, the payment to the supplier is ultimately processed through IFMIS.

What the integration means

KRA and the National Treasury have linked eTIMS directly to IFMIS. The effect of this integration is highlighted in the public notice as:

1. government suppliers can only be paid if they have eTIMS compliant invoices;

2. the details of the invoices submitted to government entities must correspond precisely with the invoices generated and recorded in eTIMS.

3. suppliers will be required to regularly verify their tax compliance status and ensure that their tax records and information are accurate and up to date.

4. suppliers are encouraged to regularly verify their tax compliance status and ensure that their tax records and information are accurate and up to date

What is not clear from the public notice is eTIMS compliance by government entities. Various government entities provide services to taxpayers which are tax deductible business expenses (e.g. licenses, government fees, permits) but they do not provide eTIMS compliant invoices. This leads to these expenses not being deductible for tax since they are not eTIMS compliant.

Conclusion

The eTIMS-IFMIS integration is a welcome move and will ensure that suppliers remain eTIMS compliant. Suppliers who are not eTIMS-compliant, or whose invoicing processes produce inconsistencies, will find themselves unable to receive payment. Lastly, we hope to see that the same eTIMS compliance requirements are placed on government entities so that taxpayers dealing with government are not disadvantaged.

For further guidance on eTIMS compliance and integration with IFMIS, please contact Digitax.

For a large enterprise, the value of e-invoicing was never just about staying out of trouble with NRS. It’s about what happens to VAT credit, filing pressure, and audit exposure when thousands of invoices are moving through the business every month, not just a handful.

“We’ll sort it out before filing.”

It’s a familiar posture in large finance teams managing high invoice volume, the belief that compliance can be handled in a final review pass before the return is due. For a business issuing a few dozen invoices a month, that might work. For a large business issuing thousands across branches, subsidiaries, and sales teams, it rarely does. Understanding why is where three specific benefits come into focus, and where real-time e-invoicing changes the outcome.

1. No VAT Credit Risk

Under the Nigeria Tax Act 2025, Input VAT can only offset Output VAT, or carry forward as a credit, if the invoice behind it is genuinely NRS-compliant. At enterprise volume, that condition is harder to guarantee than it sounds, one malformed invoice from one branch, one mismatched tax identifier from one subsidiary, and the credit built on it doesn’t hold up when it’s finally needed.

A simplified version of how that plays out: a business carries a ₦2.4 million VAT credit into a new quarter, built from thousands of invoices across multiple locations. If even a small percentage of those invoices weren’t properly validated at the point of issuance, the business isn’t carrying a ₦2.4 million credit, it’s carrying an unverified number that may not survive scrutiny when it’s used to offset a real liability.

Real-time validation removes the guesswork. Every invoice is checked against NRS requirements the moment it’s created, so the credit on the books is a credit the business can actually use.

2. No End-of-Month Panic

For a large business, “end of month” isn’t one event, its dozens of branches, sales teams, and systems all converging on the same filing deadline. When validation happens manually or in batches, that convergence becomes the moment every uncaught error surfaces at once, with no time left to fix it.

This is the same mechanism at the heart of every e-invoicing mandate, just compounded by scale. A small business reconciling fifty invoices at month-end has room to catch mistakes. A large business reconciling five thousand does not, not without the errors already having been caught earlier, invoice by invoice, as they were issued.

With real-time dashboard or API validation, there’s no batch to reconcile. Invoices are already validated and logged continuously, so month-end becomes a formality, not a scramble.

3. Audit-Ready, Instantly

An audit doesn’t ask a large business to explain one invoice. It asks the business to produce a verifiable trail for every invoice, across every branch and subsidiary, on demand. For a business relying on manual records or disconnected systems, assembling that trail after the fact is its own project, one that can take weeks and still leave gaps.

A business with real-time validation already has that trail. Every invoice, from every part of the business, carries its own verified compliance record from the moment it was issued. There’s nothing to reconstruct, because nothing was ever left unverified in the first place.

Why This Matters More at Scale

Compliance risk doesn’t grow at the same rate as the business, it compounds. More branches, more subsidiaries, more invoicing systems means more places where a single gap can turn into a VAT credit problem, a filing crunch, or an audit exposure, often simultaneously.

• A VAT credit is only as strong as the invoices behind it : at enterprise volume, unvalidated invoices can quietly hollow out a credit worth millions.

• Manual, batch, or end-of-month reconciliation doesn’t scale :it just delays when the errors surface.

• Audit-readiness isn’t something to assemble after the fact : it’s a byproduct of validating every invoice as it’s issued.

DigiTax validates every invoice with NRS in real time, across every branch, subsidiary, and system, so your VAT credit holds up, and you’re audit-ready at any moment, not just at filing time.

Book a Demo Now: https://tally.so/r/mV5LkJ

For more information: firs-si@namiri.tech | +234 913 6528 711

On 4 September 2026, KRA issued a public notice informing taxpayers that a stock management functionality will be rolled out for eTIMS. The notice requires all taxpayers engaged in business to maintain accurate and up-to-date stock records that reconcile with eTIMS. This is a new development being introduced and we detail here below this additional compliance obligation.

Summary of the KRA Public Notice

The notice wishes to inform taxpayers that stock records must accurately account for goods as they move through a business. This includes goods purchased or received, sold, transferred, returned, adjusted or otherwise disposed of in the course of doing business.

KRA also announced that it will hold consultative engagement forums with the business community and other key stakeholders, with the forums expected to commence in September 2026. These forums will allow businesses to understand how the functionality works, seek clarifications, share implementation challenges, and provide recommendations.

What this means in practice

Until now, eTIMS has primarily been concerned with the issuance of invoices and the validation of expenses supporting with eTIMS compliance invoices. According to this new notice, businesses will have an additional obligation to reconcile stock movement with eTIMS.

This will effectively tie stock records to the tax compliance. KRA will be able to see, in real time, what stock a business holds, what has moved, and whether the stock movements align with the invoices and returns on file. Businesses that currently manage stock informally, on spreadsheets or through manual systems that are not connected to eTIMS, will need to reconsider their approach.

Why this matters for audits

Stock discrepancies have in some instances led to tax audits. Unexplained differences between opening stock, purchases, sales and closing stock are among the most common triggers for deeper KRA scrutiny. If eTIMS now tracks stock movements in real time, KRA will have an additional point against which to cross-check returns.

Therefore, the sales and claim cost of goods sold will be required to align to eTIMS and amounts on iTax and any variances explained.

Year-end is when finance teams across Nigeria move from managing tax compliance month to month to defending a full year of it at once. VAT positions get totaled, carried-forward credits get tested, and every invoice issued since January becomes part of one closing number. For most businesses, that shift happens with far less preparation than it deserves.

The problem is not that compliance gaps are common. It’s that they’re invisible for most of the year, and only become visible at the exact moment a business can least afford to discover them.

Why Year-End Compliance Checks Are Non-Negotiable

Every business under Nigeria’s NRS e-invoicing mandate is required to issue validated invoices and hold NRS-compliant documentation to support VAT input credit. This obligation runs continuously through the year, not just at filing deadlines. In principle, that’s a simple requirement to meet. In practice, year-end is where the cracks in it get exposed.

Four Checks That Consistently Surface Problems

1. Real-time validation, not batch uploads - An invoice validated with NRS after the fact isn’t the same as one validated at the point of issue. Batch-uploading invoices at month-end to “catch up” on compliance produces a paper trail that looks compliant but wasn’t, and that gap shows up the moment anyone checks issuance timestamps against validation timestamps.

2. VAT input credit reconciled against validated invoices only - A credit built up over the year is only as strong as the invoices behind it. If any of those invoices weren’t properly validated, the credit isn’t fully substantiated, and that detail tends to surface exactly when the business is counting on the credit to offset a real liability.

3. Non-compliant invoices from earlier in the year - Most businesses have at least a handful, an invoice issued by a supplier who wasn’t actually eligible, one missing required fields, one that never matched cleanly to the underlying transaction. Individually forgettable. Collectively, they’re what an audit finds first.

4. Outstanding credit claims tied to flagged invoices - If any invoice behind a claimed or carried-forward credit has ever been flagged, by an internal check or a supplier dispute, that claim needs resolving before it’s rolled into year-end numbers, not carried forward as an open question.

Why the Gap Widens the Longer It’s Left

None of these four checks are difficult on their own. What makes them expensive is timing. A gap caught in October is a fix. The same gap caught during year-end close is a restatement, a delayed filing, or a credit position that has to be defended after the fact instead of confirmed in advance.

A compliance gap doesn’t show up on a dashboard the way a cash shortfall does. It shows up when someone goes looking, an auditor, a regulator, or the CFO during close. The businesses that get through year-end cleanly aren’t the ones with fewer invoices to check. They’re the ones who checked them before the deadline forced the question.

How Integration Solves It

A business running an integrated e-invoicing and reconciliation system isn’t doing this checklist as a year-end scramble. Every invoice is validated with NRS the moment it’s issued, matched against the ERP automatically, and flagged immediately if something doesn’t reconcile, not discovered in a spreadsheet three weeks before books close.

This is exactly the gap DigiTax closes. As an accredited System Integrator connecting businesses to NRS, DigiTax validates every invoice in real time at the point of issue.

Voluntary, once-a-year compliance checks are no longer a sustainable strategy under an NRS mandate that expects real-time validation. The businesses that treat these four checks as a running practice rather than a year-end scramble are the ones who close their books with numbers they can defend, not numbers they have to explain.

Ready to see where your invoicing stands before books close?

Book a Compliance Readiness Demo https://tally.so/r/mV5LkJ 📞 +2349136528711 ✉ firs-si@namiri.tec

On 31 August 2026, the Kenya Revenue Authority confirmed that the integration between eTIMS and IFMIS is now live. That is a short sentence for a change with a very concrete effect: from now on, the invoice a supplier submits for payment isn’t just checked by a procurement officer or an accountant — it’s checked against KRA’s own record of that invoice, automatically, before Treasury lets the money move. If the two don’t agree, the payment doesn’t move either.

eTIMS and IFMIS: Two systems that now talk to each other

Most businesses that deal with government already know eTIMS — the Electronic Tax Invoice Management System, KRA’s platform for generating tax invoices that carry a verifiable digital signature. It’s how KRA sees a sale the moment it happens, rather than at year-end filing.

IFMIS is the other half of the picture, and it lives entirely on the government’s side. The Integrated Financial Management Information System is what every ministry, county government, and state corporation uses to process its own finances — budgets, expenditure, and critically, supplier payments. Until now, IFMIS took a supplier’s invoice largely at face value; whether it actually matched what KRA had on file was someone else’s problem, discovered later, if at all.

The integration closes that gap. IFMIS can now query eTIMS directly and validate an invoice before payment is authorised. KRA frames this as part of the government’s Digital Transformation Agenda — more transparency in public spending, tighter compliance, less manual reconciliation. For a supplier, the framing matters less than the mechanism: your invoice is now cross-checked at the point of payment, not the point of filing.

Step 1: Supplier generates an invoice in eTIMS for the supply

Step 2: That invoice is recorded on KRA’s own eTIMS ledger

Step 3: Same invoice details submitted to the government entity for payment via IFMIS

Step 4: IFMIS validates the match against eTIMS — payment releases only if they agree

What the notice actually says

KRA’s public notice sets out four requirements for any business supplying a government entity. Worth reading in the original before unpacking what each one means day to day.

KRA Public Notice — Implementation of the eTIMS – IFMIS Integration

Generate the eTIMS invoice first, not after

The invoice submitted for government payment has to already exist in eTIMS before it goes anywhere near IFMIS. There’s no sequence where you invoice the client on your own letterhead, get a purchase order moving, and generate the eTIMS copy afterward to tidy up the books.

In practice: Whatever issues your invoices — a billing clerk, an accounting package, a spreadsheet — eTIMS generation has to be the first step in the sequence, not the last.

Invoice consistency is now machine-checked

“Correspond precisely” means exactly that — the amount, the KRA PIN, the item descriptions, the date, the invoice number. A figure rounded differently on the payment voucher than on the eTIMS invoice, or a line item re-typed by hand into a different format, is now a discrepancy a system flags, not a nuance a clerk waves through.

In practice: Any manual re-typing of an eTIMS invoice into a separate payment claim, LPO, or voucher is now a point of failure. The two documents need to be the same record, not two versions of it.

Compliance status can hold up an otherwise valid invoice

A correctly generated, correctly matched invoice doesn’t fully insulate a supplier if their broader tax standing has lapsed — outstanding returns, arrears, an expired compliance certificate. KRA is explicit that suppliers should keep verifying their status, not just their invoices.

In practice: Treat your Tax Compliance Certificate the way you treat your business licence: something to renew ahead of time, not something to discover has lapsed when a payment stalls.

Support exists — but only if you use it before, not after

KRA points suppliers who need help onboarding to eTIMS or generating invoices toward its support channels. That’s a genuine offer, and also a signal: KRA expects unfamiliarity with the system to be resolved proactively, not discovered at the payment desk.

In practice: Budget time to train whoever issues your government invoices on eTIMS specifically — a delay caused by not knowing the system reads the same as a delay caused by noncompliance.

The real risk is cash flow, not paperwork

Why this matters more than it sounds

Government contracts already run on long payment cycles — 30, 60, sometimes 90-plus days is normal even when everything is in order. Under the old process, a mismatch between what a supplier billed and what KRA had on record was something an accountant might catch and quietly fix weeks later. Under the integrated process, IFMIS can hold the payment at the gate the moment it doesn’t reconcile — before it enters the approval queue at all.

For a business that leans on government work for a meaningful share of its revenue, that isn’t a compliance footnote. It’s a working-capital problem: payroll, supplier terms, and rent don’t wait for a resubmitted invoice to clear a second validation cycle. The businesses most exposed are exactly the ones the notice is addressed to — the micro and small suppliers for whom one delayed government payment can ripple through the rest of the business.

Where DigiTax Fits

The mismatch this notice warns against almost always starts the same way: an invoice gets generated once for eTIMS, and generated again — by hand — for whatever the government entity’s payment process asks for. Two versions of the same sale, produced separately, are two chances to disagree.

DigiTax removes the second version. It generates your eTIMS invoices directly from your actual sales data and keeps them synced with KRA in real time, so there is exactly one invoice record — the one KRA already has. Whatever you submit through IFMIS is, by construction, identical to what’s already sitting in eTIMS, because it’s the same invoice, not a re-entered copy of it.

That’s the whole fix: no gap for a rounding error, a re-typed PIN, or a stale invoice number to slip into, and no manual step between generating the invoice and submitting it for payment.

Talk to us to get started on +254 112 685368 or +254 795 279403/ Email us at support@namiri.tech or Request a Demo

Kenya’s avocado sector has become one of the country’s most visible horticultural success stories. Export volumes have climbed steadily over the past decade, farmers across Murang’a, Kiambu, Nakuru, Kandara and beyond have shifted from subsistence to commercial cultivation, and international buyers increasingly treat Kenyan avocado as a reliable, quality-certified supply source. But behind that growth story sits a tax compliance problem that gets far less attention than it should: most of the value chain that moves an avocado from farm gate to export container is invisible to eTIMS.

That invisibility is not a minor administrative footnote. It is a structural feature of how the sector sources fruit, and it exposes exporters, aggregators and cooperatives to real audit and deduction risk. Understanding why the gap exists and how reverse invoicing closes it matters for anyone operating in or advising this value chain.

Why eTIMS Compliance Is Non-Negotiable Here:

Every business in the avocado value chain is required to issue eTIMS-compliant invoices for taxable supplies and to hold eTIMS-compliant documentation to support tax-deductible expenses. This obligation doesn’t pause at any single point in the chain it applies from the first farm-gate purchase through to the point of export. In principle, that’s a straightforward requirement. In practice, the avocado value chain has a structure that makes it unusually difficult to meet.

Three Structural Challenges Unique to This Sector

• Smallholder sourcing at scale - Most exporters and traders don’t buy from a handful of large commercial farms they buy from thousands of individual smallholders, often through local buying agents. Each delivery is its own transaction requiring its own compliant documentation. The reality on the ground is that a large share of these farmers have no KRA PIN, no access to an invoicing system, and little to no awareness that eTIMS obligations even apply to them.

• Buying agents and brokers as an inherited gap - Exporters commonly rely on agents who aggregate fruit from multiple farmers across a growing area. These agents’ own purchase records are frequently not eTIMS-compliant, and the individual farmer transactions underneath them are often undocumented entirely. The exporter doesn’t create this gap but they inherit it, along with the compliance exposure that comes with it.

• A fragmented logistics layer - Avocados are perishable and depend on unbroken cold chain handling from farm to port. That means exporters are working with refrigerated transporters, casual loaders, fumigation providers and clearing agents a layer of small and informal service providers, many of whom are not issuing eTIMS-compliant invoices for their services.

Put together, these three factors mean the documentation gap in avocado sourcing isn’t an edge case. It’s the default state of the transaction.

How Reverse Invoicing Solves It

Reverse invoicing flips the usual invoicing relationship: instead of waiting for an undocumented supplier to issue a compliant invoice they may never be able to produce, the buyer generates the eTIMS-compliant invoice on the supplier’s behalf, with the supplier’s consent.

For an avocado exporter, this means a compliant invoice can be generated at the moment fruit is delivered, or when payment is processed, without requiring every farmer in the network to operate their own invoicing system.

The mechanism works best when it isn’t a standalone add-on but is built directly into procurement and payment workflows. A third-party integrator such as DigiTax can generate these invoices automatically, drawing on farmer records, buying data and payment information already flowing through the exporter’s systems.

What Sector-Wide Adoption Could Look Like: The AEA Kenya Model

The Avocado Exporters Association of Kenya (AEAK) brings together the country’s licensed avocado exporters — and is well positioned to coordinate reverse invoicing adoption at a sector level rather than leaving each exporter to solve the problem alone.

Coordinated member onboarding - Rather than every exporter separately negotiating integration approaches with KRA and technology providers, an association-led framework could establish a standard integration model, agreed data formats and a template consent process that all members adopt cutting duplicated effort and creating sector-wide consistency.

Farmer consent and registration at scale - Supplier consent is a prerequisite for reverse invoicing, and for an exporter sourcing from 5,000 farmers, collecting that consent individually is a serious administrative undertaking. An association-coordinated approach field teams running registration drives in key growing regions, collecting consent and verifying farmer details makes this tractable.

A shared farmer database - Because exporters frequently source from overlapping farmer populations, a centralised, association-managed database holding each farmer’s name, ID number and PIN, with appropriate data protection safeguards would let members check whether a farmer is already registered and consented, reducing duplication and speeding up procurement across the board.

Reverse invoice generation at the buying point - Once farmer data is centralised, generating the invoice itself becomes almost automatic. When a buying agent logs a delivery from a registered farmer, the system generates a reverse invoice, transmits it to KRA via eTIMS, and links it to the eventual payment. DigiTax, as a third-party integrator, can provide this technology layer configured to work with each member’s own payment and procurement systems while drawing on the shared farmer registry.

Farmer education as a force multiplier - An association-led education programme reaches far more farmers per shilling spent than individual exporter efforts ever could. Training materials explaining eTIMS and reverse invoicing and the very real upside for farmers, including that documented sales strengthen their own tax position and improve access to credit delivered through workshops at collection centres during buying season, reach farmers exactly when compliance is most relevant to them.

The Bottom Line

Voluntary compliance is no longer a sustainable strategy for the avocado sector. The combination of high-volume smallholder sourcing and heavy reliance on informal service providers means the documentation gap will keep widening unless it’s addressed structurally. Reverse invoicing offers exporters, aggregators and cooperatives a practical path to protect their deductions, reduce audit exposure, and build a fully documented value chain without asking thousands of smallholder farmers to become invoicing-system operators overnight.

For exporters and industry associations exploring what eTIMS implementation and reverse invoicing could look like for the avocado sector, DigiTax can help.

Dubai, United Arab Emirates – 2 September, 2026: DigiTax, a leading global e-invoicing technology company, has launched in the United Arab Emirates following its pre-approval by the UAE Ministry of Finance as an e-invoicing Service Provider.

The global company has opened a new office in Dubai to support its growth and has launched a recruitment drive, anticipating strong demand in line with the UAE government’s e-invoicing regulations. It is actively hiring local talent for key sales, account management, customer service and technical support roles, as well as dedicated tax and compliance experts.

Demand for e-invoicing is surging thanks to the UAE’s progressive national strategies and emirate-level reforms. This includes We the UAE 2031’s Forward Economy pillar that outlines the roadmap for digital transformation of the government and private sector, complemented by the UAE Digital Economy Strategy 2031, which targets an increase in GDP contribution from the digital economy from 9.7% to 19.4%.

The pre-approval, granted under the UAE Ministry of Finance and in line with the Federal Tax Authority framework, comes as businesses move to comply with new requirements that will standardise digital invoicing and reporting.

Since 2022, DigiTax has helped companies navigate the complexities of e-invoicing and currently serves thousands of customers on a daily basis across the world. From enterprise giants to independent sole-traders, DigiTax has grown rapidly by simplifying e-invoicing and tax compliance for a range of businesses, processing more than US$20B in invoices to date.

With presence across the Middle East and Africa, DigiTax anticipates expansion to 10 more international markets in 2026. In the UAE, it aims to help businesses transition to FTA-compliant e-invoicing without having to rebuild their existing finance systems, supported by a dedicated on-ground team with native Arabic and English speakers.

Speaking about DigiTax’s expansion to the UAE, Caine Wanjau, CEO and co-founder said:

“It’s a privilege to launch in the UAE, a country that is deeply admired around the world for its forward- thinking. It is a country that inspires us, especially as it pursues digital transformation. We are looking forward to supporting the many exciting enterprises and passionate entrepreneurs that fuel the UAE’s continued growth.”

Ahmed Farouk, DigiTax’s UAE Director, added:

“We are already hiring here in the UAE and will need more top talent over the coming months to support our growth. We have a real advantage for businesses in the UAE because we already have a proven recipe for e-invoicing success built in international markets. It stems from three main factors: safety and security that underpins everything we do; a relentless focus on making systems as simple and easy-to-use as possible; and, hiring talented people who are obsessed with customer happiness and are honest and transparent. This is a winning formula, for us and for our partners.”

The UAE’s e-invoicing framework is quickly advancing digital transformation. Enterprise-scale businesses (AED 50 million and above) are already mandated to comply with digital invoicing and reporting requirements, which go live on January 1, 2027, with all other B2B businesses following by July 1, 2027. The UAE’s Electronic Invoicing System (EIS) uses PINT AE (a Peppol International Billing standard, with 5-Corner Continuous Transaction Controls). In simple terms, UAE businesses will have to exchange and validate digital invoices through an FTA-approved Accredited Service Provider (ASP), rather than basic PDFs or paper invoices. In line with these standards, DigiTax is also a Peppol-licensed business.

The e-invoicing provider acts as the compliance layer between a company and the FTA e-invoicing ecosystem, accurately recording, transmitting and automating invoices. DigiTax’s proprietary technology integrates with existing accounting and ERP systems (with more than 50 API-ready integrations), with the goal in the UAE to help businesses turn FTA compliance into a strategic and operational advantage rather than an administrative burden. It also greatly benefits finance teams by reducing manual workloads.

For companies without sophisticated systems, DigiTax also provides a web-browser-based dashboard to improve visibility and automated reporting. Structured invoice data can also enable companies to turn a perceived compliance challenge into a competitive advantage, where better insights inform operations, cash flow and management of suppliers and customers.

DigiTax currently serves government partners, family offices, multinational companies, ERP and POS vendors, auditors, accountants, consultancies and organisations spanning verticals as diverse as construction, ecommerce, finance, FMCG, logistics, manufacturing, technology and transport, among many others.

To find out more about e-invoicing in the UAE, visit https://digitax.tech/ae

For a retailer with multiple branches, growth should feel like a win. More stores, more customers, more revenue. But for retailers and business, expanding across locations comes with a quieter, less celebrated cost: staying eTIMS compliant gets harder with every new branch that opens.

Here is Carpet City’s story on how the simplified Multi-Branch eTIMS compliance:

About Carpet City

Carpet City is one of Kenya’s leading carpet and flooring retailers, offering luxurious, contemporary carpets and rugs sourced from Egypt and Turkey.

With showrooms across Nairobi and beyond — including Kilimani, Ridgeways, Westlands, Buru Buru, Kitengela, Nakuru, and Kisumu — Carpet City has built a reputation for quality craftsmanship and countrywide delivery, bringing premium flooring to homes and businesses across Kenya.

The Before: eTIMS Compliance, Disconnected From the Business

Carpet City already ran its operations on Uzapoint, an ERP platform managing sales, stock, and branch performance across its showrooms. But eTIMS compliance sat outside that picture. Invoicing for KRA purposes was handled separately from Uzapoint, which meant every branch was effectively managing its own compliance step, disconnected from the system that already had the transaction data in it.

That disconnect showed up in small but constant ways: numbers that had to be pulled from Uzapoint and re-entered on iTax portal for eTIMS submission, branch-level inconsistencies in how invoices were logged, and a finance team that had to manually bridge two systems instead of working from one source of truth. At month-end, reconciling what Uzapoint showed against what had actually been submitted to KRA took real time — and real risk, since any gap between the two only became visible after the fact.

For a business built on consistency across every showroom, running compliance as a parallel, manual process to its ERP was a problem worth solving.

The Turning Point

Carpet City didn’t want another standalone tool to manage. They wanted eTIMS compliance to work through the system they already relied on, Uzapoint, not alongside it. That’s where eTIMS by DigiTax came in.

The After: eTIMS Compliance Built Into the ERP

DigiTax integrates directly with Uzapoint — one of DigiTax’s ERP partners — turning eTIMS compliance from a separate task into a built-in function of the system Carpet City already runs on.

• Compliance from the source of truth. Since eTIMS by DigiTax works on top of Uzapoint itself, invoices generated across every branch are captured for eTIMS compliance automatically: no re-entry, no separate submission step.

• One system, every branch. Because the integration lives at the Uzapoint ERP level, every branch is compliant by default, without needing its own standalone process or device.

• No gap between operations and compliance. What Uzapoint records is what gets submitted to KRA — closing the reconciliation gap that used to only surface at month-end.

• Compliance that scales with the business. As Carpet City opens new branches, each one plugs into the same Uzapoint + DigiTax integration, so compliance scales without adding manual work.

In Their Own Words

“It has improved efficiency significantly since our sales team can now process sales easily, and I’m able to pull tax reports from all 14 of our branches easily and at my convenience.”

~ Gladys Wairimu, Head of Operations, Carpet City

Visit Carpet City to see their showrooms you could shop at and get your eTIMS compliant receipt with every purchase.

Why This Matters

Carpet City’s story reflects a broader truth for multi-branch retailers: compliance shouldn’t live in a separate system from the one that already runs the business. The businesses that scale smoothly are the ones where eTIMS compliance is built into their existing ERP, not bolted on as an extra step at every branch.

That’s the model DigiTax was built on partnering with POS and ERP providers like Uzapoint to meet businesses inside the systems they already use, and making eTIMS compliance a natural extension of that, rather than a parallel process to manage.

#BeforeandAfterDigiTax #DigiTax

DigiTax by Namiri Technology Limited — Pan-African TaxTech for eTIMS compliance, e-invoicing, and tax automation across Kenya, Zambia, Nigeria, and the UAE. eTIMS by DigiTax integrates directly with ERP partners like Uzapoint to bring compliance into the systems businesses already run on.

“The Nigeria Revenue Service owes me money.”

It’s a common assumption the moment a business owner sees Input VAT outrun Output VAT on their books. Spend heavily on inventory, equipment, or services in a slow sales month, and the math can flip, VAT paid out exceeds VAT charged on sales, and the natural next thought is that NRS should send a refund.

It doesn’t work that way, and understanding why is exactly where non-compliant invoicing turns an accounting credit into money genuinely lost.

The Credit, Not Cash, Mechanism

Under the Nigeria Tax Act 2025, when qualifying Input VAT exceeds Output VAT in a given period, that excess isn’t paid out as cash. It’s carried forward as a VAT credit on the business’s tax account, available to offset Output VAT in future periods as the business makes more taxable sales.

A simplified version of how that plays out: a business closes one month with Output VAT of ₦180,000 against Input VAT of ₦310,000, a credit position of ₦130,000. The following month, sales pick up: Output VAT comes to ₦620,000, Input VAT to ₦150,000. Before the carried-forward credit, that’s ₦470,000 payable. Apply the ₦130,000 credit from the prior month, and the actual VAT payable drops to ₦340,000.

That’s the credit doing exactly what it’s meant to do, reducing a real tax liability in a later period. But there’s a condition attached to every naira of it: the credit is only as good as the invoices that created it.

Where Non-Compliance Turns the Credit Hollow

A VAT credit isn’t an abstract number sitting in a ledger, it has to be traceable back to specific, valid, compliant invoices for specific qualifying purchases. If the Input VAT behind that ₦130,000 wasn’t properly identified, wasn’t supported by valid tax invoices, or wasn’t carried forward correctly, the business doesn’t just risk a filing headache. It risks losing a legitimate credit it’s already entitled to, and ending up paying more VAT in that second month than it should have.

This is the same mechanism at the heart of every e-invoicing mandate on the continent, just viewed from the credit side rather than the immediate-claim side. Nigeria’s NRS framework ; the principle holds: Input VAT, whether claimed this period or carried forward to a future one, depends entirely on the invoice behind it being valid. An invoice that isn’t structured correctly, wasn’t issued by a compliant supplier, or can’t be matched back to the transaction doesn’t just fail today’s claim. It fails the credit sitting on the books for however long it’s carried forward, and it’s often invisible until the exact period the business is counting on that credit to reduce a real liability.

Why This Catches Businesses Off Guard

The credit is silent until it’s needed. A business can carry a VAT credit for months without any issue surfacing, until the period it actually tries to use that credit to offset a liability, and the underlying invoice doesn’t hold up.

Filing obligations don’t pause for a credit position. Even when Input VAT exceeds Output VAT and no VAT is currently payable, the return still has to be filed. A credit position removes the payment, not the obligation, and an unfiled or incorrectly filed return is its own compliance exposure, independent of whether the credit itself is valid.

It compounds the longer it’s carried. A credit built on shaky invoicing doesn’t get safer with time. Each period it’s carried forward without correction is another period where the business is relying on documentation that may not survive a closer look.

Protecting the Credit, Not Just the Claim

The fix isn’t reconstructing invoices months later, once a return is being prepared or an audit has started, by then, the transaction is long closed and there’s little room to correct it. It’s validating Input VAT at the point it’s recorded:

Confirming every qualifying invoice is genuinely compliant, correctly structured, correctly matched to the purchase, and issued by a supplier who was actually eligible to issue it, before it’s counted toward the credit at all.

Tracking the credit itself as carefully as the liability. A carried-forward VAT credit deserves the same scrutiny as VAT payable, since it’s the same claim, just deferred to a later period.

Filing on schedule regardless of position. A credit period is not a reason to treat the return as optional.

What This Looks Like With Integration

A business with an integrated e-invoicing and reconciliation system doesn’t discover a problem with its carried-forward credit the month it needs to use it. Every invoice contributing to that credit is validated as it’s recorded, matched against the ERP, and kept in a state that can be substantiated whenever the credit is drawn down, not reconstructed under pressure once the business is relying on it to reduce a real bill.

Key Takeaways

• Excess Input VAT isn’t refunded as cash under the Nigeria Tax Act 2025 — it’s carried forward as a credit to offset future Output VAT.

• That credit is only as strong as the invoices behind it; non-compliant invoicing can hollow it out long before the business tries to use it.

• A VAT credit position doesn’t remove the obligation to file — that requirement stands regardless of what’s owed.

• The safest approach validates Input VAT at the point of purchase, not at the point the credit is finally needed.

  Check Where Your Exposure Is

  DigiTax validates invoices with NRS at the point of purchase and keeps your Input VAT position, current and carried forward — audit-ready, so the credit on your books is one you can actually use. Book a Demo Now : https://tally.so/r/mV5LkJ For more information: firs-si@namiri.tech | +234 913 6528 711

Somewhere between a Lagos manufacturing plant and a kiosk in Kano, a truck is being loaded before dawn. On it: cartons of the same handful of fast-moving goods, soap, seasoning, soft drinks, biscuits, cement and others,bound for a network of distributors, sub-distributors, and retail outlets that stretches across states most head offices never see directly. This is how FMCG actually moves in Nigeria: not from manufacturer to shelf, but through two or three layers of distribution in between.

It’s also exactly the layer where Nigeria’s NRS e-invoicing mandate creates the most operational friction, because distributors sit at the intersection of two very different compliance realities: manufacturers who are large, systems-capable, and already integrated with NRS, and downstream retailers who are frequently small, informal, and unaware the mandate applies to them at all.

The NRS Mandate, in Brief

Nigeria’s NRS Merchant Buyer Solution requires businesses to issue e-invoices that are validated and reported to NRS in real time, structured in a standard format, for both VAT and income tax purposes. The rollout began with large taxpayers running ERP systems capable of API integration, with the obligation extending progressively down the business scale. For a distributor, that means the compliance clock is already running on the buying side, invoices received from manufacturers, even in markets where the selling side, invoicing retail customers, is still catching up.

Where Distributors Carry the Exposure

Upstream: invoices from manufacturers. Most FMCG manufacturers supplying Nigerian distributors are large enough to already be NRS-compliant, so a distributor’s exposure here is mostly about receiving and correctly matching those invoices, not generating them. The risk is more mundane than dramatic: mismatched line items, incorrect buyer details, or invoices that don’t reconcile cleanly against purchase orders, all of which can hold up a distributor’s own input VAT claim on that purchase.

Downstream: invoices to retail customers. This is where it gets structurally harder. A distributor selling to hundreds or thousands of retail outlets, supermarkets, provision stores, open-market traders, is issuing the invoice itself, and the mandate requires that invoice to be NRS-compliant regardless of how small or informal the buyer is. High transaction volume across a fragmented retail base makes manual compliance checking impractical without a system doing the validation automatically.

In between: the sub-distributor layer. Many FMCG supply chains run through sub-distributors who are themselves informal or under-resourced. A distributor selling through this layer inherits the same documentation risk that flows through any fragmented supply chain, the invoice a sub-distributor issues onward may or may not meet the standard, and that gap can surface in the distributor’s own reconciliation long after the sale happened.

Three Structural Challenges Specific to FMCG Distribution

Volume, not value, drives the risk. FMCG distribution runs on thin margins and high transaction counts, dozens or hundreds of invoices a day per outlet network. The compliance burden scales with transaction volume far more than with contract value, which is the opposite of how most finance teams are used to prioritising risk.

Multi-tier supply chains blur accountability. With manufacturer, distributor, and sub-distributor all touching the same goods before they reach a retail shelf, it’s easy for compliance gaps to open at a tier nobody is actively monitoring.

Retail-facing invoicing has to work at the point of sale. Distributors selling directly into retail outlets need invoicing that happens where the transaction happens, often via a mobile POS device in the field, not back at a head office days later.

Getting Ahead of It

The practical fix isn’t a manual invoicing process bolted onto existing sales workflows, it’s integration at the point where the transaction is already being recorded. For distributors running ERP or sales-force-automation tools, connecting that system directly to a NRS-accredited integrator means every sale, upstream or downstream, generates a compliant invoice as part of the transaction itself, rather than as a separate step someone has to remember to do later.

For the manufacturer-facing side, that same integration reconciles incoming invoices against purchase orders automatically, flagging mismatches before they become a blocked input VAT claim rather than after.

• Nigerian FMCG distributors sit between NRS-compliant manufacturers upstream and a fragmented, often informal retail base downstream, with real compliance exposure on both sides.

• The upstream risk is mostly reconciliation accuracy; the downstream risk is generating compliant invoices at high volume across many small buyers.

• Sub-distributor layers can create compliance gaps that surface later, in the distributor’s own books, long after the transaction closed.

• Point-of-sale integration — not manual, after-the-fact invoicing, is what makes compliance viable at FMCG transaction volumes.

Ready to Simplify NRS Compliance Across Your Distribution Network?

DigiTax is an accredited NRS e-invoicing integrator, connecting directly with the ERP and POS systems distributors already use, so every transaction, upstream or downstream, is compliant as it happens.

Book a Demo Now https://tally.so/r/mV5LkJ or firs-si@namiri.tech | +2349136528711