Financials is where most Fusion implementations begin, because every other module posts to it. A well-designed ledger lets procurement, projects and HCM fit in cleanly afterward, while a poorly designed one passes its compromises to every later module.

That makes the design phase the most consequential part of the program, and it is where the chart of accounts, tax configuration and bank integration are settled.

Chart of accounts and ledger design

A Saudi chart of accounts has to serve three purposes at once: management reporting by business line and region, statutory reporting under SOCPA-adopted IFRS, and Zakat computation, which needs specific visibility of Zakat-base items. We design segment structures so all three come from the same ledger without side spreadsheets, and so future entities can be added without redesign.

Tax and e-invoicing

VAT configuration covers standard, zero-rated, exempt and out-of-scope treatments, with the reporting to support VAT return filing directly from the system. Receivables invoicing is configured for Arabic and English output with the QR code and structured data that ZATCA Phase 2 requires. The integration to ZATCA's platform is built, tested and onboarded as part of the implementation instead of deferred.

Bank integration and cash management

Saudi banks each have their own payment file and statement formats. We configure Cash Management for automated bank statement import and reconciliation, and Payables for payment file generation in the formats your banks accept, so that supplier payment runs and reconciliations stop being manual. Where a treasury function exists, this connects directly to it.

A hypothetical example

Consider a distribution group in Riyadh that implements Financials across several entities. Its chart of accounts is built on a legal entity segment, a business line segment and a cost center segment, and Zakat-relevant balances are tagged at the natural account level. At year end, the group's Zakat advisor could extract the Zakat base from a standard report instead of rebuilding it from trial balances.

Fixed assets and period close

Fixed Assets is configured for the depreciation methods and useful lives your policy specifies, with separate books where Zakat treatment differs from accounting treatment. Period close is structured as a documented checklist with a subledger close sequence, so month-end becomes a repeatable process instead of one experienced person's routine.

Intercompany and multi-entity design

For groups, intercompany is where Financials design earns its keep. Trading between entities is configured to generate matching receivable and payable entries automatically, with the balancing segments that make elimination on consolidation a system function instead of a spreadsheet. This is also where consolidation readiness is decided, long before any consolidation tool is switched on.

Reporting for different audiences

The people who read your financials do not all want the same thing. The external auditor wants IFRS statements, ZATCA wants the Zakat base, the bank wants specific financial ratios, and the board wants a summary in Arabic. We design the reporting layer so each of these comes from the same ledger instead of being prepared separately.