Compliance checks

By Matheel, from ZATCA's specifications and SDK 3.4.8 · Updated

ZATCA compliance checks are sample documents a device files with its compliance CSID before going live: an invoice, credit note and debit note per invoice type.

Compliance checks sit between the compliance CSID and the production CSID. The device proves it can produce valid documents: for each invoice type it issues (standard or simplified) it submits an invoice, a credit note and a debit note. A device issuing both types submits six; a simplified-only device submits three.

Which types are checked follows the functionality map in the CSR (such as 1100 for both). Samples go to /compliance/invoices, signed and authenticated with the compliance CSID; the response carries validationResults, and a pass means no errorMessages.

What goes wrong: the samples must be valid documents. They need an ICV (BR-KSA-33), the notes need a reference to the original invoice (BR-KSA-56) and a reason (BR-KSA-17), and the standard ones need the buyer's VAT number and address. Resubmitting a step that already passed returns 406 with Submitted before.

On Matheel the checks run automatically inside POST /api/v1/onboarding, and Matheel treats Submitted before as a pass so an interrupted onboarding can resume. The response reports the count in compliance_checks.

Example

{"device_token":"mdt1.…","device":{"serial":"1-Matheel|…","certificate_expires_at":"…"},"compliance_checks":3}

FAQ

How many compliance checks are there?

Three per invoice type the device issues: invoice, credit note and debit note. Six for both types.

Onboarding stopped halfway through the checks. Start over?

No. Steps that passed answer Submitted before if resent, so you can continue with the same compliance CSID.

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