Services · Mobile app development · Payroll software

Payroll software for Riyadh head offices that close the month without spreadsheets.

Codeeo offers payroll software development Riyadh finance teams can run from calculation to bank file in one place. We build payroll systems for group head offices, regional headquarters, government contractors and professional firms in the capital, covering gross to net calculation, GOSI contributions, end of service provisions, Mudad wage protection files, bilingual payslips and journals for your ERP. Payroll stops living in a workbook that only one accountant understands.

Riyadh payrolls tend to be complicated at the top rather than the bottom: several legal entities, executive packages with schooling and ticket allowances, and finance controllers who want every variance explained before they approve the run. That is where custom software earns its place.

Built for
Group finance and payroll teams in Riyadh running several entities, cost centres or government linked contracts.
Typical timeline
Agreed with your finance controller after discovery, and planned around your payroll calendar so go live never lands in the middle of a run.
What you own
The source code, the database, the calculation rules and every payroll record, held in accounts your company controls.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the system handles

Payroll features built for Riyadh group finance.

A head office payroll in Riyadh rarely fails on the arithmetic. It fails on the edges: an employee transferred between two entities halfway through the month, an allowance that counts for GOSI in one company and not in another, a bank that rejects a file because one IBAN is a digit short. The features below are the ones that remove those edges. We order them by how much manual checking they replace, and we build the first release around the controls your auditors already ask about, so the new system is easier to defend than the spreadsheet it replaces. Everything runs in Arabic and English, and every figure on a payslip can be traced back to the rule that produced it.

Explain your project
  • Multi entity payroll under one login

    Each commercial registration keeps its own establishment number, Mudad file and bank account, while group finance sees every entity in one console. Transfers between companies in the group are dated, so the employee is paid correctly by both entities for the days each one owes.

    Group payroll runs once, with each entity still filing on its own.

  • Pre approval variance report

    Before anyone approves the run, the system compares this month with last month per employee and flags new joiners, leavers, changed allowances and unusual overtime. Controllers in Riyadh head offices tend to sign faster when each change already has a reason beside it. Controllers can comment on a flagged line and send it back to the preparer without reopening the whole run.

    Approval becomes a review of exceptions, not of every line.

  • Executive and expatriate packages

    Housing, transport, schooling support, annual air tickets and family allowances are set up as separate components, each with its own rules for GOSI, end of service and proration. Senior hires on regional headquarters packages stop needing a manual adjustment every month. Package changes at promotion take effect from the date HR records, with arrears calculated automatically.

    Complex packages calculate the same way every time.

  • Cost centre and project allocation

    Salaries split across departments, projects or government contracts by percentage or by timesheet, so contractors billing ministries in Riyadh can show exactly which staff cost sits on which contract. The allocation flows into the payroll journal without rekeying.

    Contract costing that matches what payroll actually paid.

  • ERP journal posting

    Approved payroll posts a summarised journal to Dynamics 365, Business Central, Odoo or SAP through their APIs, mapped to your chart of accounts and cost centres. Accruals for end of service and leave are posted the same way, every month.

    The general ledger agrees with payroll without a reconciliation day.

  • Mudad and bank file generation

    The system produces the wage protection file in the layout Mudad expects and a payment file for each bank you use, then checks IBANs, contract wages and missing employees before upload rather than after a rejection.

    Fewer rejected uploads and fewer late salaries.

  • End of service provisions

    Monthly provisions follow the Labour Law tiers, half a month's wage for each of the first five years and a full month after that, with the resignation reductions applied when a resignation is recorded. Finance sees the liability per entity at any month end.

    The balance sheet liability is current, not estimated once a year.

  • Final settlement statements

    When someone leaves, the system assembles the last salary, unused leave, the end of service award with any resignation reduction, outstanding advances and ticket entitlements into one statement in Arabic and English. HR reviews it, the employee signs it, and the payment joins the next bank file or goes out as an off cycle run.

    Exit settlements agreed in days instead of argued over for weeks.

  • Approval chain with audit trail

    Preparer, reviewer and approver roles are separated, every change to a salary or rule is logged with who made it and when, and a closed month cannot be edited without a recorded reopening. External auditors get read only access to the evidence.

    Audit requests answered from the system, not from email threads.

  • Bilingual payslips and self service

    Employees open Arabic or English payslips on their phones, download salary certificates for banks and embassies, and raise a payroll query that lands with the right payroll officer instead of the general HR inbox.

    Payroll queries arrive in writing, with the payslip attached.

Who this is for

Four Riyadh payroll situations we are asked to fix.

Most Riyadh payroll projects begin with one painful month: a run that took a week, a Mudad rejection that delayed salaries, or an audit question nobody could answer quickly. The four situations below cover most of what we hear from finance teams in Olaya, King Abdullah Financial District and the business parks along the northern ring road. Each one points to a different first release, which is why we ask about the pain before we talk about features. None of them needs a giant system on day one; each needs the right first piece done properly.

01

A group with several companies and one payroll team

Holding groups often run trading, contracting and services companies from one Riyadh head office, each with its own registration and bank. The payroll team ends up maintaining parallel spreadsheets and copying formulas between them. We build one rule set with entity level differences switched on where they apply, so a change to the housing allowance policy is made once and reaches every company it should.

Shared rules, separate filings.

02

A regional headquarters with mixed packages

Companies that moved their regional headquarters to Riyadh hire senior staff on packages that mix Saudi and international conventions: schooling support, home leave tickets, relocation repayments and bonuses spread across quarters. Generic payroll tools force these into one allowance line. We model each component properly, including whether it counts towards GOSI and the end of service base. Bonus deferrals and clawbacks follow the dates in each executive's agreement.

Package rules your HR director can read.

03

A contractor costing staff to government projects

Firms delivering contracts for ministries and authorities in Riyadh must show which employees were charged to which project, often with Saudisation commitments attached. We link payroll to project codes and timesheets so cost reports and invoices draw on the same numbers your payroll paid, and contract managers stop asking finance for a separate breakdown.

One source for payroll and contract cost.

04

A finance team preparing for an external audit

When auditors ask how a salary was calculated three months ago, a spreadsheet answer is slow and fragile. We replace manual workbooks with a system where each run is locked, each rule change is versioned and each payslip can be rebuilt from the rules that applied at the time. Controllers can answer the question in minutes.

Evidence on demand.

How a Riyadh payroll build runs, step by step.

  1. 01Payroll walkthrough at your officeOur Riyadh team sits with your payroll officers through a live month end, records every manual step and collects the workbooks, policies and bank formats that drive the current run.
  2. 02Rule book in plain languageEvery allowance, deduction, proration and contribution rule is written in Arabic and English and signed off by finance before a line of code is written, so disputes are settled on paper first.
  3. 03Calculation engine and controlsWe build the gross to net engine, the approval chain and the audit log together, because controls added after the calculations rarely cover every path a change can take.
  4. 04Integrations with banks and ERPBank payment files, the Mudad wage protection file and ERP journals are built against real samples from your banks and ledger, then tested with your treasury and accounts teams.
  5. 05Parallel runsThe new system runs beside your existing payroll for at least one full cycle, and every difference is explained, fixed or accepted in writing before the old process is retired.
  6. 06Live support through year endWe stay close through the first annual events: increments, bonus months, Ramadan hours and the year end provision review, adjusting rules as finance requests.

Technology

What we build this with.

A web console for payroll and finance, a mobile app for employee payslips, and a calculation service your team can test independently. Hosting sits in a Saudi cloud region where your data policy requires it, with encryption at rest and role based access.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

03Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions Riyadh finance teams ask about payroll software.

It depends mostly on how many entities and integrations go into the first release.

A single entity payroll with Mudad and bank files moves faster than a group rollout with ERP posting and project costing. We agree the schedule with your finance controller after the walkthrough, and we always plan the parallel run around your payroll calendar. Go live is set for the start of a cycle, never midway through a month that is already being processed, so your staff are paid on time throughout the switch. Groups with several entities often phase the rollout, moving one company at a time so the payroll team learns the system on the simplest payroll first.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews