Saudi VAT Pro turns every paid WooCommerce order into a ZATCA-compliant tax invoice automatically. The customer gets a link to download their invoice PDF, and refunds generate a matching credit note \u2014 no manual invoicing, no exporting orders to a spreadsheet.<\/p>\n\n
The plugin connects to Saudi VAT Pro using a webhook URL and a secret generated from your Saudi VAT Pro account \u2014 there is no API key to manage. Connect your store in two steps, then place a test order:<\/p>\n\n
This plugin covers ZATCA Phase 2 (Integration Phase) e-invoicing. With a ZATCA certificate (CSID) enrolled in your Saudi VAT Pro account, every invoice is generated as signed, hashed, QR-coded UBL XML, then Simplified (B2C) invoices are reported to ZATCA and Standard (B2B) invoices are submitted for clearance. Without a certificate enrolled, invoices are still generated (with a Phase 1 QR code) but are not signed, reported, or cleared until you enroll one. This plugin does not cover Phase 1-only (generation without reporting) setups as its intended operating mode.<\/p>\n\n
The plugin submits paid orders to Saudi VAT Pro for electronic invoicing and stores the returned invoice identifier and PDF link on the WooCommerce order. When a refund is created, the plugin submits the refunded items to create a matching credit note. If the connection to Saudi VAT Pro itself fails before an invoice is created (for example a timeout), the order is retried automatically up to three times, several minutes apart, and can also be retried manually at any time from the order screen using the \"Retry Saudi VAT Pro submission\" order action. Once an invoice has been created for an order, that order won't be resubmitted from WooCommerce; a ZATCA rejection or a missing certificate at that point is resolved from your Saudi VAT Pro dashboard.<\/p>\n\n
The classic shortcode checkout is supported. WooCommerce block checkout does not currently expose this plugin's optional VAT field; collect the VAT number by another compatible checkout extension until native block integration is released.<\/p>\n\n
This release supports WordPress 6.0 or newer, PHP 8.0 or newer, and WooCommerce 7.0 or newer. It supports WooCommerce HPOS. The classic shortcode checkout is supported; the optional VAT field is not currently available in WooCommerce block checkout.<\/p>\n\n
When a paid order or refund is submitted, order identifiers, billing details, purchased items, prices, taxes, and the optional VAT number are sent to Saudi VAT Pro at the merchant-configured webhook URL for invoicing and ZATCA processing. The plugin stores the returned invoice identifier, PDF URL, and submission error on the WooCommerce order. It does not send data to any other endpoint. Merchants are responsible for informing customers and configuring their Saudi VAT Pro account lawfully. See https:\/\/saudivatpro.com\/privacy for Saudi VAT Pro's privacy policy.<\/p>\n\n
For setup help or support, visit https:\/\/saudivatpro.com or contact the Saudi VAT Pro team through your account.<\/p>\n\n\n
It watches your WooCommerce orders. When an order is paid, it sends the order to your Saudi VAT Pro account, which creates the invoice and \u2014 once a ZATCA certificate is enrolled \u2014 signs it and reports or clears it with ZATCA, then returns a PDF link you can share with the customer. When you refund an order, it does the same to create a matching credit note.<\/p><\/dd>\n
By the Saudi VAT Pro service. This plugin only collects order and refund data and sends it, over your configured webhook, to your Saudi VAT Pro account. Invoice generation, XML signing, and ZATCA submission all happen there \u2014 none of that logic runs on your WordPress site.<\/p><\/dd>\n
Yes, both full and partial refunds. When you create a refund in WooCommerce, the plugin sends the refunded line items to Saudi VAT Pro, which issues a ZATCA credit note referencing the original invoice for that exact amount.<\/p><\/dd>\n
ZATCA Phase 2 (Integration Phase). With a ZATCA certificate (CSID) enrolled, every invoice is generated as signed, hashed, QR-coded UBL XML, then Simplified (B2C) invoices are reported to ZATCA and Standard (B2B) invoices are submitted for clearance. Without a certificate enrolled, invoices are still generated with a Phase 1 QR code but are not signed, reported, or cleared. It does not cover Phase 1-only (generation without reporting) setups as its intended operating mode. The PDF link is returned to the order as soon as this processing finishes, whatever the resulting outcome \u2014 a rejected submission or a missing certificate is flagged in your dashboard instead of failing silently.<\/p><\/dd>\n
A Simplified invoice is issued to a consumer buyer and reported to ZATCA. A Standard (B2B) invoice is issued to a business buyer who provides their 15-digit Saudi VAT number at checkout, and it is submitted to ZATCA for clearance instead of reporting. Enable the optional VAT number field in the plugin settings so business buyers can request a Standard invoice; orders without a VAT number get whichever invoice type you've set as the account default in Saudi VAT Pro (usually Simplified, but this is configurable to Standard).<\/p><\/dd>\n
It depends on where the failure happens. If the connection to Saudi VAT Pro itself fails before an invoice is created (for example a timeout), the plugin retries automatically up to three times, several minutes apart, and you can also retry manually using the \"Retry Saudi VAT Pro submission\" action on the order screen \u2014 that action only resends orders that don't have an invoice yet. If Saudi VAT Pro creates the invoice but ZATCA then rejects it, or no certificate is enrolled yet, the order already has its invoice ID and PDF; that failure is flagged in your Saudi VAT Pro dashboard, where you fix and resubmit it.<\/p><\/dd>\n
Not yet for the optional VAT number field \u2014 it currently only appears on the classic shortcode checkout. Orders placed through block checkout are still invoiced automatically using your account's default invoice type; business buyers checking out through blocks should use another compatible field to submit their VAT number until native block support ships.<\/p><\/dd>\n\n<\/dl>\n\n\n