How We Made a Saudi Contractor ZATCA-Compliant - Without Replacing Their Software

When Saudi Arabia's ZATCA e-invoicing mandate started rolling out in waves, it created a clear divide in the market. Companies running modern cloud software adapted quickly - their providers pushed updates, and compliance was handled. Companies on large ERPs like SAP or Oracle paid their vendors for a new module and moved on.

But there was a third group. Companies running specialized, industry-specific software that no vendor was going to update. Software that was built - sometimes over years - to handle workflows that generic tools simply don't understand.

One of those companies came to us.

The Client

A mid-sized Saudi construction and contracting firm. For confidentiality, I won't name them - but their situation is one I've seen repeated across niche industries.

Construction invoicing is not like retail invoicing. It's not "product × quantity = total." It involves progress billing tied to project milestones, retention amounts held across months or years, partial invoices against contracts that span multiple phases, change orders that modify previously issued documents, and back-charges between subcontractors. This company had spent years customizing their invoicing system to handle all of this. Their workflows were deeply embedded. Their finance team knew the system inside out. The data was structured around how construction projects actually work.

No off-the-shelf invoicing tool could replicate what they had.

The Problem

ZATCA's Phase 2 - the Integration Phase - requires businesses to connect their invoicing systems directly to ZATCA's Fatoora platform via API. Invoices must be generated in structured XML format, digitally signed, stamped with a cryptographic hash, and submitted for real-time clearance before they're considered fiscally valid.

Their existing system didn't support any of this. No API connectivity to ZATCA. No XML generation. No digital signing. No cryptographic stamping. And their software vendor? A small outfit that had built the system years ago and had no plans - or capacity - to implement ZATCA integration.

The obvious advice was: switch to a ZATCA-compliant invoicing solution. But that advice ignores reality. Migrating would mean abandoning years of customization, retraining an entire finance team, rebuilding reporting workflows, and risking data loss during migration - all under the pressure of a compliance deadline.

They didn't need a new system. They needed their current system to become compliant.

Our Approach: Wrap, Don't Replace

Instead of asking the client to change how they work, we built a compliance layer around their existing workflow using Nemra, our data aggregation and regulatory compliance platform.

The integration was designed to be as low-friction as possible on the client's side. No API development. No changes to their software. No new training for their team.

Here's how it works:

Step 1 - Export. Once a week, the client's finance team does what they were already doing: they export their invoices as PDF files from their system. A bulk export - nothing new in their workflow.

Step 2 - Upload. They upload the batch of PDFs to Nemra's dashboard. Drag and drop, bulk upload. Takes a few minutes.

Step 3 - Extract and validate. This is where Nemra does the heavy lifting. Our hybrid OCR + LLM pipeline processes each PDF, extracting invoice data - supplier details, amounts, tax calculations, line items, dates, invoice numbers. The system classifies the document, validates the extracted data against ZATCA's business rules, and flags anything that needs attention. (I wrote a separate technical deep-dive on how this pipeline works if you're interested in the architecture.)

Step 4 - Register with ZATCA. Once validated, Nemra generates the required structured XML, applies the digital signature and cryptographic stamp, and submits each invoice to ZATCA's Fatoora portal via API. The client gets confirmation that their invoices are registered and compliant.

The entire flow - from PDF export to ZATCA registration - requires no developer on the client's side. No system integration. No middleware. No IT project.

The Result

The client became ZATCA Phase 2 compliant without changing a single thing in their daily invoicing workflow. Their finance team still uses the same system they've used for years. They still generate invoices the same way. The only addition is a weekly upload step that takes minutes.

No migration. No disruption. No retraining. No risk.

Why This Matters Beyond Saudi Arabia

The ZATCA story isn't unique to Saudi Arabia. It's a pattern that's playing out - or about to play out - across the region and beyond.

Algeria is building a centralized e-invoicing framework (CTC model) that will require businesses to transmit invoices to the tax authority in near real-time via API. The original 2026 target has slipped, but the direction is clear and the infrastructure is being built. When it lands, every business in Algeria will face the same question this Saudi contractor faced: does my current system support this?

Morocco and Tunisia are on similar trajectories. France is rolling out mandatory B2B e-invoicing starting September 2026 for large and medium companies, with smaller businesses following in 2027.

The pattern is always the same. A government announces a digital invoicing mandate. Companies on modern cloud platforms adapt quickly. Companies on large ERPs pay for an upgrade. And companies on specialized, legacy, or niche software - the ones whose workflows are too unique for generic tools - get stuck.

That third group is who we build for.

The Compliance Layer Philosophy

I believe the answer to regulatory change shouldn't be "throw away what works." When a company has spent years building a system that fits their operations, the right approach is to add compliance around the edges - not force a migration that disrupts the core.

Nemra is built on this principle. The same ideas that handles ZATCA registration in Saudi Arabia powers Comptalegal.dz for Algerian fiscal compliance. Different regulations, different markets, same philosophy: meet companies where they are, not where a software vendor wishes they were.

If your business runs on specialized software and you're watching e-invoicing mandates approach - whether in Saudi Arabia, Algeria, or anywhere in the francophone ecosystem - the question isn't whether you need to be compliant. It's whether you need to rebuild everything to get there.

You probably don't.