ERP & e-invoicing integration
Connect the ERP or accounting system you already run to e-invoicing. Built to work with ZATCA e-invoicing requirements; the scope for your company is confirmed in your proposal.
Who it is for
Companies that issue invoices from an ERP or accounting system and need them to meet e-invoicing requirements without changing the system itself.
What is in scope
Assess
- Which requirements apply to your company, and from when
- How your invoices are produced today
- What your system can and cannot provide
Map
- Invoice and customer fields from your system to what e-invoicing needs
- Tax categories and VAT handling
Connect
- The connection from your system, built or configured
- A process for invoices that fail validation: who sees them and how they are corrected and resent
Test and go live
- Testing on sample invoices before go-live
- A documented flow
- Support terms after go-live
What you receive
- A written scope stating which requirements apply and how invoices reach the authority
- A field-mapping document
- A working connection, tested on sample invoices before go-live
- A short runbook: what your team does when an invoice fails
What we need from you
- The name and version of your system, and administrator access to a test environment
- Sample invoices of each type you issue
- Your tax registration details, and the contact who holds the registration with the authority
- The timeline the authority has given you
How it is quoted
Custom and itemised by the system and the invoices involved.
What shapes the quote
- Which system and version
- Invoice types and volumes
- Number of entities or branches
- How much of your process has to change
Questions about e-invoicing integration
Which ERP systems do you work with?
Tell us the system and its version. Compatibility is confirmed at scoping, and we do not publish a list.
Do you hold an approval from ZATCA?
We make no claim of approval for any system. We build the connection to work with ZATCA e-invoicing requirements, and the proposal states exactly what is in scope.
Do we need to change our ERP?
Not necessarily. The assessment says what your system can provide, and what would have to change if anything does.
What happens when an invoice is rejected?
The design includes a process for invoices that fail validation: who sees them, how they are corrected and how they are resent. It is documented for your team.
Can the MUZN Unified Platform do this instead?
Yes. Invoicing is part of its Finance module, built to work with ZATCA e-invoicing requirements, with the scope confirmed in your proposal.
Start from the system you already run.
Tell us the system, its version and the kinds of invoices you issue. We reply with next steps and what the assessment would cover.