The whole cycle, requisition to payment, built for the region's realities — a different regime in every jurisdiction, decennial liability on construction, Arabic-prevailing contracts — hosted in Canada today, with a dedicated in-region instance stood up when you sign.
A GCC instance stood up when you signKSA · UAE · Qatar · Oman + jurisdiction switchPublic & private sectorArabic & decennial-liability aware
.../rules
Data residency — the question that decides it
Your procurement data can stay in the country.
Saudi Arabia's Personal Data Protection Law allows personal data to leave the Kingdom only with safeguards, and classified government data must be hosted in-country. Most platforms host in one place and cannot answer that. Atlas runs in Canada today, and a dedicated instance in your region is stood up for you when you sign.
In-region, when you sign
A dedicated instance of the entire system is stood up in a data centre in your region when you sign. Its servers sit in that region, and we name every provider involved, including the network edge in front of it.
Named region, in writing
The region your instance runs in is set out in the agreement, not left to a vendor's convenience. A residency review has a one-line answer: it never left the jurisdiction.
Your identity, your sign-on
Connects to your own Microsoft Entra or identity provider — staff use the accounts they already have, governed by your policies.
When the law says data stays in-country, in-region hosting is the answer. No separate infrastructure project, no hand-off to an ops team, no parallel system — the same product, stood up in your region when you sign.
Not a claim — the live setting
The GCC edition is honest about the Gulf, not generic about it.
The actual settings screen, not marketing copy. There is no pan-GCC regime: Saudi Arabia, the UAE (federal, Dubai, Abu Dhabi), Qatar, Kuwait, Oman and Bahrain each have their own law, currency and VAT rate. So the threshold matrix starts honestly empty, for your own jurisdiction's figures.
No invented pan-GCC thresholds — the matrix starts blank, for your own jurisdiction's figures
Currency defaults to USD, VAT to 5% (UAE, Bahrain, Oman) — Saudi Arabia's 15% is one field away
Switch jurisdiction, or regions entirely, from this same screen
.../settings
Region ProfileUSD default · VAT 5% · thresholds intentionally blank.
Public sector Ministries · Government entities · State-owned
Tenders that respect the jurisdiction.
For government entities, ministries and state-owned enterprises across the Gulf — where the
rules, the language and the guarantees change from one country to the next.
Jurisdiction switch — KSA, UAE federal, Dubai, Abu Dhabi, Qatar, Kuwait, Oman and Bahrain — set before a tender issues
ITT, RFP and construction-tender routes, with the region's master documents and response forms
Decennial liability, on-demand bank guarantees and Arabic-prevailing terms reflected in the templates
Sealed bids opened by a named person, committee evaluation and a complete audit trail
An ICV clause in the Gulf templates and local-content evaluation criteria; a full ICV report is built on request
Where procurement data must stay in-country, a dedicated in-region instance is stood up when you sign
.../sourcing
Sourcing & TenderITT to award, jurisdiction-aware.
Private sector Construction · Energy · Conglomerates · Free zones
Spend visibility for a region building fast.
For the contractors, energy firms and diversified groups delivering Vision 2030 and the
UAE's growth agenda — procurement control at the pace the Gulf actually moves.
See and cut off-process spend — drive it under contract, in AED, USD or any currency you transact in
Supplier qualification with ESG and Scope-3 tracking — ahead of Net Zero 2050 reporting
Contract lifecycle with milestones, retention and renewal alerts
Connects to eleven accounting systems, including SAP S/4HANA and Oracle Fusion, the systems most of the Gulf runs on. QuickBooks Online, Xero, Business Central and Sage Accounting are proven against live ledgers; the other seven are built and each is proven on your own ledger at onboarding; older SAP ECC pulls a feed
Live in days to weeks, not the year a global suite takes to stand up
.../spend
Spend AnalysisUnder-contract, off-process and cycle times — in AED.
.../suppliers
Supplier MasterQualification, risk and local content in one view.
Qualify before you commit
Suppliers qualified, not just registered.
A full supplier record with qualification, risk and performance — and the local-content
and ESG signals the region increasingly reports on.
Lifecycle gates block awards to suspended, on-hold or debarred suppliers
Certifications and documents chased automatically before they lapse
Controlled bank-detail changes — the most abused field in procurement, locked down
A supplier portal where they register, quote, receive POs, submit invoices and get paid — and keep their own documents and bank details current
Local-content and diverse-supplier spend tracked for the reports that matter
The gap it fills
Most tools handed to Gulf teams weren't built for the Gulf.
Imported cloud platforms and generic workflow tools miss the things that actually decide a Gulf
procurement — where the data lives, which jurisdiction applies, and how a tender has to be run.
Single-region platforms host wherever they host — so a PDPL review that asks where the data physically sits stops them cold.
In-country, when you sign. A dedicated instance is stood up in your jurisdiction, with its servers there and every provider named in your order.
Global enterprise suites cost a fortune — and still need in-country hosting stood up separately, at more cost and delay.
A fraction of the price, in-region once you sign. We stand up your in-region instance — no separate hosting project for you to fund or staff.
There is no single GCC regime — but generic tools treat the region as one, ignoring the country-by-country patchwork.
A jurisdiction switch for KSA, UAE, Dubai, Abu Dhabi, Qatar, Kuwait, Oman and Bahrain — each with its own forms and rules.
Government tender portals post the RFP — then leave evaluation, contracts, POs and payment to spreadsheets.
Runs the whole cycle — tender, evaluation, award, contract, PO, invoice and payment, in one auditable flow.
Decennial liability, on-demand guarantees and Arabic-prevailing terms are unknown to imported workflow tools.
Built into the Gulf templates, so the legal realities are in the paperwork from the start.
Sustainability and local-content reporting get bolted on late, as a separate exercise.
ESG, Scope-3 and local-content tracking are built in, with an ICV clause in the Gulf templates; a full ICV report is built on request.
Connects to your stack
Sits alongside the systems you already run.
SAP and Oracle dominate Gulf finance. Atlas stays the procurement record and posts straight to your connected
ledger; an older ERP pulls a read-only feed on its own schedule — so contracts and their milestones reach AP without a manual handover.
Coded bills post to all eleven connected ledgers; purchase orders to eight, journals to six
Older ledgers pull read-only purchase order, invoice, supplier, contract and journal feeds, as JSON or CSV
A feed is pulled on your ERP's own schedule — no middleware, no integration project
One API key, secured; integration is off until you switch it on
Your ERP reaches it over your own approved network path
.../integrations
Integration HubPosts to eleven ledgers; older ERPs pull a feed.
See it on your own procurement
Gulf procurement, in one system.
A short demo on your jurisdiction, your categories and your sector — with the whole cycle,
end to end, with an instance in the region you nominate stood up when you sign.
