What should you check when electronic invoices don't arrive by email?
We review the case as a chain. If you jump straight to spam, you may miss a validated invoice, a rejected XML file, or an internal rule that quarantined it.
- Confirm the invoice exists and was validated. In Colombia, buyers must request an invoice for their purchases. If they need to support costs, deductions, or deductible taxes, they must request a previously validated electronic invoice. DIAN says the invoice can be checked with the CUFE data, and the graphic representation includes a QR code to verify it, except in contingency cases: DIAN guide for buyers.
- Verify the registered receiving email. It isn't enough to ask, “What email did they send it to?” You need to check the email registered to receive electronic documents, the buyer’s NIT or ID, and any recent changes to the domain, email provider, or shared inbox. DIAN defines that email as the one provided during the electronic invoicer enablement process to receive invoices, notes, and derived instruments: DIAN tax glossary.
- Ask for the right file package. In Colombia, DIAN Resolution 000165 of 2023 says an electronic invoicing buyer receives the XML and graphic representation inside the electronic container. For buyers who aren't electronic invoicers, it allows several delivery methods, including graphic representation, XML with graphic representation, server-to-server delivery, or printing if no delivery method is provided: DIAN Resolution 000165 of 2023.
- Review email authentication and rejection. If the issuer uses an invoicing provider or a third-party domain, the email can fail authentication. Google requires SPF or DKIM for senders to Gmail, and SPF, DKIM, and DMARC for bulk senders. It also warns that unauthenticated messages can go to spam or be rejected with error 5.7.26: Gmail sender guidelines. Microsoft 365 uses DMARC to decide whether a failed message is rejected, quarantined, or allowed through: DMARC setup in Microsoft 365.
- Look for blocked attachments or quarantine. Many invoices travel in ZIP files or with XML attachments. Gmail blocks certain file types, including compressed files, and password-protected files with archived content: blocked file types in Gmail. In Google Workspace, an admin can create rules by attachment type, name, or size. Those rules can reject or quarantine the message: attachment filters in Google Workspace. Microsoft 365 can also reject or quarantine messages through anti-malware policies, and it recognizes XML and ZIP during analysis: anti-malware protection in Microsoft 365.
Does an electronic invoice without XML work?
The answer changes by country and by invoice use. This isn't legal or tax advice. It's an operational guide to know what to check before closing the case.
| Case | What to request | What to validate |
|---|---|---|
| Colombia, electronic invoicing buyer | XML and graphic representation in the electronic container | CUFE, QR code, and DIAN validation |
| Colombia, buyer who isn't an electronic invoicer | Digital or printed graphic representation, depending on the delivery method provided | CUFE or QR code if you need to verify it |
| Mexico | Invoice XML; printing is optional | Active folio registered with SAT |
| Accounting or tax use | The file required by the applicable rule | That the document supports the cost or tax |
DIAN defines the electronic invoice as a digital XML file and the graphic representation as a way to verify its tax validity: how to identify an electronic invoice. In Mexico, SAT says the issuer must deliver the invoice and XML at the time of the transaction, and the recipient can validate the folio with SAT: SAT invoice verification. SAT also warns that delivering only the printed representation isn't valid when the XML must be made available: SAT criterion on electronic invoice issuance.
What does the diagnosis look like in a realistic case?
This is an illustrative example, not a client. It helps organize a review with accounting, technology, and the invoicing provider.
A company in Colombia receives vendor invoices in an inbox like invoices@company.com. Accounting says transportation invoices are missing, but the vendor shows the graphic representation and says it sent them.
First, we take a sample of expected invoices. For each one, we record the vendor, NIT, number, CUFE, date, email used, and files sent. Then we validate whether the CUFE appears in DIAN and whether the QR code opens the right query.
Next, we review email logs. Some invoices did arrive, but were quarantined because they came in ZIP files. Others were sent to an old email address that was still in the vendor record. A third group arrived correctly, but the receiving system didn't read the XML because it expected a different file name.
The operational result isn't “email failed.” There are three separate actions: update vendor master data, adjust attachment rules, and fix the XML reader. If the process has many invoices, it's better to connect it to the accounts payable flow or to an API integration, instead of depending on manual inbox searches.
For credit transactions or payment-term transactions in Colombia, DIAN has said buyers must send electronic messages for invoice receipt and goods or services receipt through the Electronic Invoicing System. DIAN also says that procedure is needed for those invoices to support costs, deductions, and deductible taxes: DIAN Concept 010573 of 2024.
What signs show you should automate the control?
Not every receiving issue needs new software. But there are clear signs that manual control is no longer enough.
- The team searches for invoices one by one in Gmail, Outlook, or shared inboxes.
- Accounts payable finds missing invoices when it is already closing the period.
- Vendors resend the same XML several times, and no one knows which version was processed.
- The inbox receives PDF, XML, and ZIP files, but the accounting system loads only part of them.
- There are invoices validated by the tax authority, but they don't appear in the internal flow.
- Errors repeat because receiving emails are misspelled or outdated.
- The company needs traceability for receipt, validation, attachments, and vendor response.
Which option makes sense to fix it?
Cost and timeline depend on volume, existing systems, countries involved, and the traceability level you need.
| Option | When it makes sense | Limit |
|---|---|---|
| What your email already includes | A few cases per month and manual review | Depends on searches and people |
| Rules in Google or Microsoft | Quarantine, ZIP, or sender problems | Doesn't validate CUFE or process XML |
| Automation platform | Medium volume and repeated tasks | Can break when formats change |
| Custom development | Several systems, countries, or accounting controls | Requires design and maintenance |
If the problem is repetitive, an AI automation can classify emails, read attachments, and alert on missing invoices. If the issue is in the accounting system, it's usually better to review the full vendor invoice flow before adding more tools.