
Does a PDF count as an electronic invoice?
The file extension alone cannot answer that question. Check how the invoice was issued and stored, and which requirements apply to the business and its system. Scanning a paper invoice does not turn it into an electronic invoice. A PDF viewing copy, by itself, neither proves nor disproves compliance.
Separate the viewing copy from the issuing process
ZATCA describes electronic invoices as structured invoices issued and stored through an electronic system. Its definition excludes handwritten and scanned invoices. Start with the process and system that produced the document, rather than its appearance in an email.
Two examples: ask about the process
Hypothetical example one: a team scans a paper invoice and saves it as invoice.pdf. Scanning does not itself meet the electronic-invoice definition. Example two: an invoicing program sends the customer a PDF copy. Do not assess the system from that attachment alone. Ask how issuance and storage work and which records and formats the system produces. Neither example certifies a particular product.
Three questions for your invoicing team
- How is the invoice created and stored? Ask for a clear description of its path through the system and how its record can be retrieved.
- Which invoice type and requirements apply? Do not assume one template fits every transaction.
- Which implementation phase applies to the business? Distinguish issuance and storage from integration requirements and review the business’s official notifications.
A useful message for your software provider
Try this request: “Please document how our invoices are issued and stored, the outputs and records available, and the requirements for our applicable phase. Include the relevant functions and settings, and distinguish your responsibilities from actions our team must take.” Keep customer data and passwords out of general correspondence.
Turn the provider’s answer into reviewable evidence
| If the provider says | Ask | Record |
|---|---|---|
| “We send a PDF” | How was the invoice created and recorded before delivery? | Process explanation and supporting reference |
| “Everything is stored” | How does your team retrieve a particular invoice record? | Retrieval steps and responsible person |
| “The system is ready” | Ready for which scope, and what configuration or business actions remain? | Responsibilities and open questions |
Request a demonstration using test data or information authorised for sharing. Do not put a real customer’s invoice in a public presentation or send passwords. Keep the provider’s explanation with supporting evidence instead of relying on a “compliant” marketing badge.
A focused discussion with your team
- Identify the system, entity and transaction type under discussion.
- Follow a test example through creation, storage and retrieval.
- Record what the demonstration establishes and what it leaves unanswered.
- Assign next actions between the business and provider.
This prepares a review. A demonstration alone does not establish that every technical requirement has been met.
Record the answer and the open question
Use a small internal register: question, provider response, evidence or reference, owner and next action. A marketing description such as “compliant system” does not explain your business’s actual configuration. Ask for something that can be reviewed, and keep unresolved points together rather than scattered across conversations.
Common questions
Is emailing the invoice enough? The delivery channel alone does not explain issuance and storage. Is every PDF unacceptable? Do not draw that conclusion from the extension; distinguish the viewing copy from the process behind it. Does phase two apply identically to everyone? Rollout is phased; consult the business’s notification and applicable requirements. Does this guide test my software? No. It helps structure verification questions and is not a compliance certificate.
After understanding the invoice, review the figures
If your next question concerns differences between reports and a working paper, start with the comparison scope and source records. Mada’s reconciliation guide can help organise that conversation before the appropriate treatment is considered.
Read the VAT reconciliation guide
Sources and scope
The examples and provider message are educational suggestions from Mada. Apply the official requirements to the business’s circumstances; this guide does not provide a technical or tax assessment of a specific system or list all format and integration requirements.
The idea is clear. What about your case?
Explore the support relevant to your question. Every guide is available without providing contact details.
VAT & excise tax