Debit and credit note (invoice type code (BT-3) is equal to 383 or 381) must contain the reason (KSA-10) for this invoice type issuing.
Why ZATCA invoices fail rule BR-KSA-17 (ERROR) and how to fix it: Debit and credit note (invoice type code (BT-3) is equal to 383 or 381) must contain the reason (KSA-10) for this invoice type issuing.
Was diese Regel prüft
Debit and credit note (invoice type code (BT-3) is equal to 383 or 381) must contain the reason (KSA-10) for this invoice type issuing.
Rule family: KSA - business rules (BR-KSA).
Standard: BR-KSA (ZATCA). Severity: ERROR.
Warum Ihre Rechnung abgelehnt wird
ZATCA runs the official EN 16931 + BR-KSA business rules before clearance/reporting. This rule is an error — the invoice is rejected until you fix it.
Wie man es behebt
Correct the invoice element referenced in the rule (the BT-/BG- term above) in your ERP mapping so it satisfies the constraint, then re-validate. The fault is usually in how your software generates the field, not in the rule itself.
Vor dem Senden prüfen
Upload your ZATCA UBL invoice to the validator to confirm this rule — and every other EN 16931 / BR-KSA rule — passes. Validation runs the official ZATCA SDK schematron.
Implementing ZATCA in your software?
Check your generated documents against the maintained official rules across your dev lifecycle — while implementing, before releases, and when the rules change. Tell us what you'd use.
No product yet — we're measuring interest. No spam, unsubscribe anytime.