Need SDK ChangeLogs

Dear [Recipient’s Name / ZATCA Support Team],

We are currently encountering the following error during invoice submission:

[BR-KSA-F-08] – The value provided in Other Seller ID (BT-29) or Other Buyer ID (BT-46) for the scheme ID “CRN” appears to be incorrect.

On reviewing the publicly available documentation, we are unable to find any recent updates related to this rule or its handling. We also noticed that details of the latest SDK changes are not reflected in the public release notes.

To help us align with the compliance requirements, we would like to request clarification on the following points:

  1. Have there been any recent updates or modifications in the latest SDK that impact the handling of Other Seller ID (BT-29) or Other Buyer ID (BT-46) with scheme ID CRN?

  2. If yes, could you please provide the updated validation details or change logs?

  3. Is there a formal channel where the latest SDK changes and related validation rules are communicated to taxpayers/integrators?

This information will greatly help us ensure compliance and avoid recurring validation errors.

Looking forward to your guidance.

this is because of the new format validation applied for the other buyer ID (BT-46) other seller ID (BT-29) if B2B Tax invoice

as follows:

enforces format checks for other Seller IDs (BT-29) and other Buyer IDs (BT-46):

  • CRN = exactly 10 digits.

  • 700 = 10 digits, starting with 7.

  • TIN = 10 digits, starting with 3.

  • NAT = 10 digits, starting with 1.

  • IQA = 10 digits, starting with 2.

  • All IDs must be alphanumeric only (no spaces, symbols).

  • Buyer ID is mandatory if VAT number missing.