An SAP system that fits how you trade in the Kingdom

The first real decision is the product. SAP S/4HANA suits groups with several legal entities, complex manufacturing, intercompany flows or heavy reporting needs. SAP Business One suits a single company or a small group that wants trading, stock and finance in one place without a large programme. Picking the bigger system than you need adds months and licence cost. Picking the smaller one can mean a second migration in three years.

We help you decide with a short comparison against your actual processes, not a feature list. Count your legal entities, your item master size, your approval layers and how many people post transactions daily. Those four answers usually settle it.

Hosting is the second decision. SAP runs on-premises, on a hyperscaler, or as a managed private cloud. Saudi cloud rules from the Communications, Space and Technology Commission and the data classification expectations of the National Cybersecurity Authority affect where production data can sit, so we confirm the hosting model before sizing anything. Indicative effort: one to three weeks of assessment before a fixed scope is written.

Older SAP projects started with a long blueprint document that nobody read twice. We use fit-to-standard instead. In short workshops your process owners see the standard SAP process running on a prepared sandbox, and we record only the places where your business genuinely differs. Each difference is then classified: change the process, configure around it, or build a small extension.

That classification is where cost is controlled. Every extension is a thing you maintain forever and re-test at each SAP upgrade, so the default answer is to adopt the standard flow unless the gap costs real money. We put each approved gap in a register with an owner and an estimate, and the register is part of the scope you sign.

Build and test run in cycles. Configuration is tested by us, then integration is tested with your key users on trial-migrated data, then your team runs user acceptance on realistic scenarios such as a purchase from request to supplier payment. A typical programme for one company runs four to nine months depending on modules and data quality.

Localization is part of the base scope, not an add-on. That covers Saudi VAT codes and returns, bilingual invoices and delivery notes with correct right-to-left layout, Hijri date handling where contracts require it, and Zakat-related reporting inputs. E-invoicing is connected to the ZATCA Fatoora platform under the integration phase requirements, so invoices are generated, signed and submitted as part of posting.

Cutover is where projects are won or lost. We run at least two full trial migrations, reconcile the trial balance and open items against your legacy numbers, and rehearse the weekend of go-live with a written timetable. Customer and supplier masters are cleaned before they are loaded, because duplicates loaded into SAP stay there.

After go-live we stay in hypercare through your first month-end close, then move to a support arrangement with agreed response times. Where an SAP-specific skill is outside what we deliver, we say so up front and plan around it.