Status summary of debit notes

Issue datetime

Issue datetime

Search the documents by an exact value: the whole search must equal the document number, customer name, customer tax number, reference or any metadata value, ignoring case (INV-123 finds inv-123, never INV-1234). To match one field only, write document.id:<value>, document.customer.name:<value>, document.customer.tax_registration_number:<value>, reference:<value> or metadata.<key>:<value> (quote a metadata key that contains a colon: metadata."<key>":<value>).

Status

• ERROR - Error
• FAILED - Failed
• PENDING - Pending
• PROCESSING - Processing
• QUEUED - Queued
• REPORTED - Reported

Supply date

Supply date

If the account is under a Group VAT, then it is required to be the TIN of the instance under the Group VAT. Otherwise it is optional and can be used as a branch name

The unique identifier of the connected account you're operating on behalf of.

Connected accounts should be used only for Platforms and White Label integrations that onboard customers and report documents on their behalf. Omit the X-ZATCA-Connected-Account-Id header when registering devices or reporting documents for your own organization. See the Platforms and White Label guide.

The ZATCA environment to use, one of ['production', 'simulation']. A ZATCA API key (starting with zatca_live_ or zatca_sim_) already names its environment, so the header is optional with it and must match it when sent. Other API keys and OAuth tokens need it.