Debit note

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

A ZATCA debit note (code 383) increases the value or VAT of an earlier invoice. It must reference the original invoice and state the reason.

A debit note is issued when the seller needs to increase the value of an original invoice or its VAT amount, for example for an extra service charged after invoicing. It follows the original invoice's type, standard or simplified.

In the XML it is code 383 in cbc:InvoiceTypeCode, with the same requirements as a credit note: the original invoice number in cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID, and the reason in cac:PaymentMeans/cbc:InstructionNote. It takes an ICV and PIH from the device chain.

What goes wrong: the same as credit notes. No reason fails BR-KSA-17, no reference fails BR-KSA-56, and the code must be one of 388, 383, 381 or 386 or BR-KSA-05 fails. During onboarding, the compliance checks require a debit note for each invoice type the device issues, so it has to work even if you rarely use it.

On Matheel you send "document_type": "debit_note" with original_invoice_number and note; Matheel builds the reference and reason, stamps the note and files it on its type's path.

Example

<cbc:InvoiceTypeCode name="0100000">383</cbc:InvoiceTypeCode>
...
<cac:BillingReference>
    <cac:InvoiceDocumentReference>
        <cbc:ID>INV-1001</cbc:ID>
    </cac:InvoiceDocumentReference>
</cac:BillingReference>

FAQ

When do I use a debit note instead of a new invoice?

When you increase the value or VAT of an issued invoice and want the increase tied to that invoice.

Is a debit note cleared or reported?

It follows the invoice type: cleared against a standard invoice, reported against a simplified one.

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