Update on ZATCA ERPGulf Based on New Regulation Updates

Here’s what we implemented in ZATCA ERPGulf for Sales Invoices and POS Invoices to ensure ZATCA compliance and proper handling of tax and customer data:Buyer ID Validation ZATCA requires that the Buyer ID field is only filled if the Buyer ID Type is specified.

1. For B2C customers, Buyer ID is not mandatory. If the Buyer ID Type is blank, the Buyer ID field must also be blank.
2. For B2B customers, Buyer ID and Buyer ID Type are mandatory. The system enforces that both fields must be filled.
3. This validation ensures invoices do not contain incomplete or inconsistent customer identification information.

Intra-Company Transfer Handling These invoices are not submitted to ZATCA; they remain in ERPNext as normal submissions without generating XML or QR codes.

1. We implemented logic that automatically detects when a company sells to itself (i.e., the Company Tax ID and Customer Tax ID are the same) and marks the invoice as an intra-company transfer.
2. When the company and customer tax IDs match, the invoice’s ZATCA status and full response are updated accordingly:
3. ZATCA Status: Intra-company transfer
4. ZATCA Full Response: Intra-company transfer

This approach ensures that:

1. B2C invoices can be submitted without requiring Buyer ID.
2. B2B invoices comply with ZATCA rules and enforce proper customer identification.
3. Intra-company transactions are correctly flagged internally while remaining aligned with ZATCA reporting requirements.