Reporting
Reporting is ZATCA's model for simplified (B2C) invoices: the buyer gets the invoice at once, stamped by your device, and it is reported within 24 hours.
Reporting is the model for simplified (B2C) invoices and their notes. The seller issues the invoice, stamps it with its own device certificate and hands it to the buyer straight away, then submits it to ZATCA within 24 hours of issue. ZATCA validates and answers, but does not stamp it or return a new copy.
The call: POST /invoices/reporting/single with the header clearance-status: 0 and the same body of invoiceHash, uuid and the base64 invoice. The response carries reportingStatus, REPORTED or NOT_REPORTED.
What goes wrong: BR-KSA-98 warns when more than 24 hours separate IssueDate plus IssueTime from the time of the check, which also fires on old test fixtures. A simplified invoice needs a QR code (BR-KSA-27) and a cryptographic stamp (BR-KSA-60). Because ZATCA does not stamp it, your device's signed XML is the legal document: keep it.
On Matheel, "type": "simplified" is reported; the response says status: reported and invoice_xml is the signed XML that was sent. Store it with the order and print the qr.
Example
POST /invoices/reporting/single
accept-version: V2
clearance-status: 0
{"invoiceHash": "…", "uuid": "…", "invoice": "<base64 signed XML>"}
FAQ
How long do I have to report a simplified invoice?
24 hours from issue. After that, BR-KSA-98 raises a warning.
Do I wait for ZATCA before giving the customer the invoice?
No. A simplified invoice is given to the buyer immediately once stamped and QR'd; reporting follows.
What if I submit the same invoice twice?
ZATCA's guidelines say the same document must not be submitted twice, even though it is not rejected at submission. Matheel bills a repeated uuid once.
Related ZATCA rules
Related terms
Let Matheel handle this for you
Matheel signs the invoice, files it with ZATCA and keeps the counter and hash in one request, and returns the PDF with the QR.
Try Matheel, no signup Matheel API docs