Key Takeaways
4 insights · 10 min readThe message is a catch-all. It appears whenever validation fails and Zoho cannot show a specific field.
In early implementations it is almost always missing data, not a Peppol outage. Our case had 3 data gaps behind it.
Look for VAL codes under the message first. If none show, ask Zoho support for the complete list of failing fields.
A failed e-invoice was never delivered, so you correct the records and push again without a credit note.
“Invoice could not be sent to your customer due to incomplete information or issues with PEPPOL network” is Zoho Books’ generic e-invoice failure. It usually means a required customer or item field is empty, not a network fault. Check for VAL error codes, complete the missing fields, then push the invoice again.
In this guide
What the message meansNetwork fault or data problem?Where the real reasons areMost common hidden causesOur caseWhat to send Zoho supportCheck the customer is on PeppolFix once, not per invoiceDeadlinesIf you have just enabled Zoho Books e-invoicing and pressed Send via PEPPOL, there is a good chance the first thing you saw was a red FAILED badge and this sentence: the invoice could not be sent to your customer due to incomplete information or issues with the PEPPOL network. This is Part 1 of our series on the Zoho Books e-invoice errors we hit on a live UAE implementation. It explains what the message means, what usually sits behind it, and how to get from a vague failure to the exact fields you need to fix. For the full picture of UAE requirements, see our UAE e-invoicing guide.
What does “incomplete information or issues with PEPPOL network” mean?
It means the invoice failed validation and was not delivered. Zoho Books uses this sentence as a catch-all whenever an e-invoice is rejected and it cannot, or does not yet, point to a specific field.
The wording joins two very different problems in one sentence: missing data on your side, and a problem on the network. Because the second half mentions Peppol, many teams assume something is wrong with the network or with Zoho and simply wait. In our experience that is the wrong instinct. On the implementation this series is based on, the network was working perfectly; three separate fields were missing.
The status badge next to the message is the part to trust. FAILED means nothing reached your customer and nothing was reported. That is good news in one respect: there is nothing to undo. You fix the records and push the same invoice again.
Is it a Peppol network problem or a data problem?
In early implementations it is almost always a data problem. A quick test tells you which: if another invoice to a different customer pushes successfully a few minutes later, the network is fine and the issue belongs to this invoice’s customer or items.
| Signal | Points to | What to do |
|---|---|---|
| Other invoices push, this one fails | Data on this customer or item | Check the customer and item records |
| Every invoice to every customer fails | Organisation setup or ASP link | Check EmaraTax shows Zoho as ASP with status Linked |
| Only invoices to one customer fail | That customer’s record or Peppol registration | Check Buyer ID fields and run the Peppol eligibility check |
| Only invoices with one item fail | That item’s classification | Check goods or service type and HSN or SAC code |
| Everything failed during the same hour, then recovered | A genuine service interruption | Wait, then push again |
Organisation-level problems are the easiest to spot, because nothing works at all. The harder cases are the ones where most invoices go through and a few fail, since the fix lives in individual customer and item records.
Where does Zoho Books show the real reason for the failure?
Directly under the FAILED badge on the invoice. Zoho lists one or more reason lines there, and when it can identify the field it shows a validation code such as VAL0001 or VAL1238 with the field name.
On our client’s first attempt, the only reason line was a request to contact Zoho support; no field was named. After the first fix, the same area showed three specific codes. That difference is explained by the way validation works: checks run in layers, and the detailed field checks may only be reached once an earlier blocking problem is cleared.
⚠️ “Sent” is not “delivered”
Zoho Books may still label the invoice Sent if it was emailed. The e-invoice status is separate. Until it reads Pushed with a UUID, the customer has not received a valid e-invoice.
What are the most common causes behind this error?
Across implementations the same handful of gaps account for most failures. Each of the first three has its own guide in this series.
| Hidden cause | Where it lives in Zoho Books | Series guide |
|---|---|---|
| Service item has no SAC code, or goods item has no HSN code | Item record | Part 4: VAL1238 |
| Customer has no legal registration number | Customer › Other Details › Buyer ID Value | Part 2: BillToLegalRegNo |
| Customer’s licensing authority is missing | Customer › Other Details › Buyer ID Authority | Part 3: BillToLegalAgency |
| Wrong or mistyped Peppol ID (0235 plus 10-digit TIN) | Customer › electronic address | Copy from the TRN, never retype |
| Customer not registered on Peppol | Outside Zoho: customer’s own ASP | Run the Peppol eligibility check |
| Free-text unit of measure | Item record | Use UN/CEFACT codes such as H87 |
| Zoho not Linked as ASP in EmaraTax | EmaraTax e-invoicing section | Complete the appointment until it shows Linked |
What caused it in our client’s case?
Three gaps, discovered one layer at a time. The test was a deliberately small invoice of AED 1.05 (AED 1.00 plus AED 0.05 VAT) from a free zone services company to a customer that had agreed to receive it.
- Attempt 1 — FAILED with the generic message and a request to contact support. Zoho support replied that the service line item had no SAC code.
- Attempt 2 — After adding a SAC code, FAILED again with three named errors: BillToLegalRegNo empty, BillToLegalAgency empty, and Invalid ServiceCodeScheme.
- Attempt 3 — After completing the customer’s Buyer ID fields and correcting the item’s code scheme, the status moved to Push Initiated.
The organisation settings, TRN and Peppol address on the supplier side were correct throughout. Every problem sat in the customer record or the item record, which is typical: those are the records most UAE businesses have never had to complete in this much detail.
What should you send Zoho support, and what should you ask?
Send enough for them to open the exact invoice, and ask for every failing field, not just the next one. Our first support reply fixed one field; the second push revealed three more. A better first request saves a round trip.
| Include | Why |
|---|---|
| Organisation ID and invoice link | Lets support open the exact failed document |
| Screenshot of the failure reasons | Shows which layer of validation it reached |
| Customer name and the electronic address used | Rules out routing problems quickly |
| A request for the complete list of missing or invalid fields | Avoids fixing one field per round trip |
| A request for the checklist of mandatory fields at organisation, customer, item and invoice level | Lets you fix every other record before the next failure |
Expert Tip
Keep TRNs, licence numbers and Peppol IDs inside the support ticket, not in public forums or community posts. Support needs them; nobody else does.
How do you check the customer can receive e-invoices?
Run Zoho’s Peppol eligibility check on the customer before pushing. It confirms whether the electronic address you hold is registered on the network.
Every in-scope UAE business, including businesses that only buy, has to appoint its own accredited service provider to receive e-invoices. Until your customer has done so, your invoice has nowhere to go. That is not something you can fix in Zoho Books; it is a conversation with the customer. Ask them which ASP they have appointed and confirm their Peppol ID is 0235: followed by the first 10 digits of their TRN.
Getting the generic FAILED message?
Send us the screenshot on WhatsApp. We’ll tell you which records to check first.
How do you stop this error coming back on the next invoice?
Fix the records, not the invoice. Every field behind this message lives on a customer or an item, so once it is fixed there it stays fixed for every future invoice to that customer or for that item.
✗ Invoice-by-invoice
Push, fail, ask support, fix one field, push again. Each customer and item is only fixed when an invoice for it fails, so failures keep appearing for months.
✓ Master data first
Before go-live, check every active customer and item for the required fields, then push one test invoice per VAT scenario. Later failures become rare and quick to trace.
This is the core of our Zoho Books e-invoicing implementation: a full customer and item check, ASP appointment, scenario tests with recorded UUIDs and a 30-minute training session for the people who raise invoices.
When does this need to be working for your business?
Before your mandatory go-live date. Under Ministerial Decisions 243 and 244 of 2025, businesses with revenue of AED 50 million or more appoint an ASP by 30 October 2026 and go live on 1 January 2027. Businesses below AED 50 million appoint by 31 March 2027 and go live on 1 July 2027. The voluntary pilot has been open since 1 July 2026.
Testing in the pilot window is the cheapest way to find these failures: a rejected invoice now costs time, not a customer waiting on a valid invoice. If you are testing ahead of your phase, keep issuing your normal tax invoices as you do today until your go-live date.