Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $499.00 USD
- dynamics_365_business_central versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
ایک بار کی خریداری
Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi)
A custom-built Business Central (AL) extension that ties card/Mada payment capture to invoice posting and auto-generates ZATCA Phase-2 compliant UBL 2.1 e-invoices — cryptographically stamped, QR-signed, cleared/reported to ZATCA, and rendered in Arabic/RTL. Built, deployed per-tenant, and supported by ECOSIRE.
$499.00USD
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
اہم خصوصیات
AL event subscriber on the sales-invoice posting routine that links payment capture to ZATCA e-invoice generation in one flow
Card and Mada payment capture (authorize/settle/refund) tied to invoice posting via a configurable payment-provider codeunit
ZATCA Phase-2 UBL 2.1 XML generation with the required invoice, line, and tax-category structures
Cryptographic stamp (digital signature) and TLV-encoded signed QR (Base64) embedded on every compliant invoice
Clearance submission for standard (B2B) invoices and Reporting submission for simplified (B2C) invoices against the ZATCA API
PIH (Previous Invoice Hash) chaining and ICV counter management with ZATCA acknowledgement/clearance-status persistence
Payment status (captured, partially paid, refunded, failed) reflected on the cleared invoice and posted to BC customer/G-L ledgers
Arabic/RTL invoice rendering on a custom report layout, bilingual with English
Dedicated table extensions storing ZATCA UUID, hash, QR, clearance status and provider transaction references on the posted invoice
Job queue entry for asynchronous retry of failed clearance/reporting submissions with backoff and audit logging
Per-tenant configuration page for ZATCA CSID/PIH, EGS unit/branch registration, VAT number and provider credentials (secrets via Isolated Storage)
Dedicated permission sets so finance and compliance roles see clearance status and resubmission actions without broad system access
BC REST/OData endpoints to expose clearance status and QR for downstream reconciliation or Power Platform reporting
Idempotent posting guard so a re-posted or retried invoice never double-charges or double-clears
اس مصنوع کے بارے میں
One paid flow for Saudi compliance and collections
Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi) کیوں منتخب کریں
AL event subscriber on the sales-invoice posting routine that links payment capture to ZATCA e-invoice generation in one flow
Card and Mada payment capture (authorize/settle/refund) tied to invoice posting via a configurable payment-provider codeunit
ZATCA Phase-2 UBL 2.1 XML generation with the required invoice, line, and tax-category structures
Cryptographic stamp (digital signature) and TLV-encoded signed QR (Base64) embedded on every compliant invoice
Clearance submission for standard (B2B) invoices and Reporting submission for simplified (B2C) invoices against the ZATCA API
PIH (Previous Invoice Hash) chaining and ICV counter management with ZATCA acknowledgement/clearance-status persistence
Saudi merchants on Business Central usually run two disconnected processes: take the card or Mada payment in one system, then scramble to produce a ZATCA Phase-2 compliant e-invoice in another. This extension closes that gap inside BC. When a sales invoice is posted, an AL event subscriber on the posting routine captures the payment authorization/settlement and triggers ZATCA e-invoice generation in the same transaction, so the document the customer pays is the document that gets reported and stamped.
The extension is delivered as AL source — table extensions, page extensions, codeunits and a job queue entry — installed as a per-tenant extension on your Business Central environment (cloud SaaS or on-prem). It is not an instant AppSource download. ECOSIRE scopes your ZATCA onboarding (CSID/PIH, EGS unit registration), card-payment provider, and chart-of-accounts mapping, builds against your tenant, deploys, and supports it.
On the compliance side it produces UBL 2.1 XML, applies the cryptographic stamp, embeds the TLV signed QR (Base64), and submits to the relevant ZATCA API — Clearance for standard (B2B) invoices and Reporting for simplified (B2C) invoices — handling the PIH chain, ICV counter, and ZATCA acknowledgements. Payment status (captured, partially paid, refunded) is reflected on the cleared invoice and posted to BC ledgers. Invoices render in Arabic/RTL alongside English.
Because it is built for your tenant, your VAT registration, branch EGS units, sequence rules, and approval flow are wired in correctly the first time — not forced into a generic template. ECOSIRE owns the AL extension and keeps it current as ZATCA specifications evolve.
What you get
- Per-tenant Business Central extension (.app) built in AL and deployed to your sandbox then production environment
- Full AL source code: table/page extensions, posting event subscribers, ZATCA signing codeunit, payment-provider codeunit, and job queue entry
- ZATCA onboarding wiring: CSID/PIH provisioning support, EGS unit/branch registration, and Clearance/Reporting endpoint configuration
- Arabic/RTL bilingual invoice report layout (Word/RDLC) with embedded signed QR
- Custom permission sets and a configuration setup page for ZATCA, VAT and payment-provider credentials
- Sandbox UAT cycle covering standard (B2B Clearance) and simplified (B2C Reporting) invoices, payment capture, refund, and retry scenarios
- Deployment runbook, admin documentation, and a post-go-live support and update window agreed in your engagement
Who this is for
Saudi BC Finance Manager
Runs accounting on Business Central and is accountable for ZATCA Phase-2 compliance. Needs paid invoices cleared/reported and stamped automatically, with clearance status visible inside BC rather than in a separate portal.
Merchant / E-commerce Owner (KSA)
Sells online and in-store, collecting Mada and card payments. Wants the payment the customer makes to immediately produce a compliant, QR-stamped invoice with no manual re-keying between the gateway and BC.
BC Implementation Partner / IT Lead
Owns the tenant and integrations. Prefers a clean per-tenant AL extension with proper permission sets, Isolated Storage secrets, and OData endpoints over fragile manual customizations or a black-box AppSource app that can't be tailored to the client's branches and EGS units.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi) module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi), and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| ZATCA Phase-2 UBL 2.1 + cryptographic stamp + signed QR generated inside BC | Included | Partial support | Included | |
| Card/Mada payment capture tied to the same invoice-posting flow | Included | Partial support | Partial support | |
| Built and tailored to your branches, EGS units and chart of accounts | Included | Included | Not included | |
| Delivered as a maintained per-tenant AL extension with source | Included | Partial support | Not included | |
| Installed and supported on your tenant by the vendor | Included | Not included | Partial support | |
| Arabic/RTL bilingual invoice rendering | Included | Partial support | Partial support | |
| Ongoing alignment with evolving ZATCA specifications | Included | Not included | Partial support | |
| Clearance status and QR exposed via REST/OData for downstream systems | Included | Partial support | Partial support |
Frequently Asked Questions about Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi)
How long does delivery take and how is it installed?
This is a build-to-order extension, not an instant AppSource download. After a short scoping call we confirm your ZATCA onboarding state (CSID/PIH, EGS units), payment provider, and invoice rules. Typical delivery is around 3 to 5 weeks depending on the number of branches/EGS units and provider complexity. We build the AL extension, deploy it to your Business Central sandbox for a UAT cycle, then publish it as a per-tenant extension to production and assist with go-live.
Do I get ongoing support and updates as ZATCA changes?
Yes. ECOSIRE owns and maintains the AL extension. Your engagement includes a post-go-live support window for fixes and clarifications, and we keep the extension aligned with evolving ZATCA Phase-2 specifications and BC platform updates. Continued maintenance beyond the initial window is available as an agreed support arrangement — we don't abandon the extension after handover.
Does it handle both standard (B2B) and simplified (B2C) invoices?
Yes. Standard tax invoices follow the Clearance flow (submitted to ZATCA and returned cleared with the cryptographic stamp before issuance), while simplified invoices follow the Reporting flow (stamped and QR-signed locally, reported to ZATCA within the required window). The extension manages the PIH chain, ICV counter, and clearance/reporting status for both on the posted invoice.
Where are my ZATCA and payment credentials stored?
Sensitive values — CSID, private signing material references, and payment-provider API keys — are stored using Business Central Isolated Storage, scoped to the extension, never in plain fields on pages. Access to resubmission and clearance actions is gated by dedicated permission sets so only authorized finance/compliance roles can use them.
Can the cleared invoice and QR feed our other systems?
Yes. Clearance status, the ZATCA UUID/hash, the signed QR, and payment status are stored on table extensions of the posted invoice and exposed through the Business Central REST/OData API. That lets you reconcile in Power BI, surface data in a Power Platform app, or feed an external storefront without scraping the BC UI.
Related Modules
قیمت کا تخمینہ طلب کریں
Stripe ZATCA-Linked Pay & e-Invoice Bridge (Saudi)
A custom-built Business Central (AL) extension that ties card/Mada payment capture to invoice posting and auto-generates ZATCA Phase-2 compliant UBL 2.1 e-invoices — cryptographically stamped, QR-signed, cleared/reported to ZATCA, and rendered in Arabic/RTL. Built, deployed per-tenant, and supported by ECOSIRE.
- AL event subscriber on the sales-invoice posting routine that links payment capture to ZATCA e-invoice generation in one flow
- Card and Mada payment capture (authorize/settle/refund) tied to invoice posting via a configurable payment-provider codeunit
- ZATCA Phase-2 UBL 2.1 XML generation with the required invoice, line, and tax-category structures
- Cryptographic stamp (digital signature) and TLV-encoded signed QR (Base64) embedded on every compliant invoice