Your whole group on one system. Nobody sees more than their job.
DMS ERP is a cloud ERP for multi-company groups in Egypt and Saudi Arabia. Nineteen modules, full Arabic and English, and permissions tight enough to satisfy an auditor.
Nothing is open by default. A screen or a button only appears once someone grants it — and every grant is recorded. Illustrative extract from the shipped permission set.
Built for how companies here actually run
Several legal entities, two languages, a tax authority to answer to, and a team that learns the system while the business keeps trading.
Every company, one login
Switch between companies from the top bar. Books stay separate, data never crosses, and group reporting still adds up.
Arabic and English, properly
A real right-to-left interface, not a translated skin. Invoices, reports and training material come in both languages.
Duties that stay separated
The system refuses to give one person a conflicting pair of duties — such as raising a purchase order and approving it. Twelve such pairs are blocked out of the box.
Answers for the auditor
Who approved this order, who reversed that entry, who was refused access last week — each is one query, kept for seven years.
Go live without gambling
Run the new permission rules in observe mode first. They log what would have been blocked without stopping anyone. Switch on enforcement once the report is clean.
The builders implement it
DMS Systems writes the product and runs the implementation. Changes you need reach the roadmap directly, and support speaks your working hours.
Nineteen modules on one set of books
Start with finance and buy the rest when you need it. Every module writes to the same ledger, so a delivery note, a payroll run and a cash payment all land in the same trial balance.
Finance
Chart of accounts, cost centers, recurring entries, and approval before anything is posted.
Customer invoices, receipts, credit limits and aging, with statements customers can download themselves.
Vendor invoices matched against the order and the goods receipt before a payment can be scheduled.
Bank accounts, cash boxes, transfers between them, and reconciliation against the statement.
VAT on every document and invoices formatted for the tax authority, including ZATCA/Fatoora submission.
Operations
Quotations to orders to invoices, with discount ceilings per salesperson and approval above them.
Requisitions, quotation requests, purchase orders, and approval limits by value.
Goods receipts, deliveries, transfers, cycle counts and adjustments that need a second signature.
Bills of material, routings, production orders, and scrap recorded against the batch.
Assets, preventive plans, work orders, spare parts and downtime logged by the technician on site.
Budget per project, timesheets, committed cost, and profit measured against the plan.
Shift open and close, cash counts, returns and voids that a supervisor has to approve.
Commercial
Leads, activities and the pipeline, with each representative seeing only their own accounts.
Targets by product, brand or portfolio, uploaded monthly and compared against actual sales.
People
Employee records, contracts, documents and leave, with sensitive fields locked away from the HR desk.
Salary components, monthly runs, and a rule that the person who runs payroll can never approve it.
Platform
Customers, vendors, items and banks, kept once and shared by every company that needs them.
Multi-step approval routes by amount, module and company, with delegation while someone is away.
Financial statements, aging, stock and sales reports, exportable to Excel and filtered by what you're allowed to see.
The part most ERP demos skip
Any system can record a sale. The question your auditor asks is who was able to change it afterwards, and whether you can prove it.
Access is granted, never assumed
A new user starts with nothing. Screens and buttons appear only as their job is defined, so a mistake in setup locks someone out rather than letting them in.
Same screen, different rows
A storekeeper opens the stock list and sees their warehouse. A representative opens orders and sees their customers. Nobody has to be told to look away.
Every posting leaves a trace
Approvals, postings, reversals, deletions, logins and refused attempts are all recorded with the user, the company, the time and the values before and after.
Where a general-purpose cloud ERP leaves you
Global suites are strong products. These are the gaps our customers in Egypt and Saudi Arabia keep running into once they start configuring one.
| Question | Typical global suite | DMS ERP |
|---|---|---|
| Arabic interface | Translated labels over a left-to-right layout; printed documents often need rework. | Right-to-left by design, in the screens, the documents and the user manuals. |
| Several companies | Often a separate subscription or database per entity, then consolidation on the side. | One installation. A user can hold a different job in each company and switch without logging out. |
| Separation of duties | Possible, but you have to design and police the rules yourself. | Conflicting duty pairs are refused at the moment someone tries to assign them. |
| Local tax filing | Usually a paid localization add-on maintained by a third party. | E-invoicing and VAT are part of the product and updated as the rules change. |
| Getting a change made | A partner writes a customization that you then maintain through every upgrade. | You talk to the team that owns the code. Most requests ship as configuration. |
Four phases, each one reversible
Nothing goes into production that hasn't been rehearsed with your own data and your own people.
Agree the shape
Company structure, chart of accounts, cost centers, and a written list of assumptions you sign before anything is built.
Configure and migrate
Modules switched on, opening balances and master data loaded, jobs mapped to roles, approval routes set by amount.
Rehearse in observe mode
Your team works in the system while permissions only watch and log. We fix every wrong block before it can stop real work.
Enforce and hand over
Rules switch from watching to enforcing, your administrators take the controls, and we stay close through the first month-end close.
Questions we get every week
Where does our data live?
Your choice. We host it for you in the cloud, or we install it on your own servers or your own cloud account. The software is the same either way, and the data belongs to you in both cases.
We're on spreadsheets and an old system. Can you move us?
Yes. Master data and opening balances come across on templates we prepare with you, and re-uploading a corrected file updates the existing rows instead of duplicating them. Historic transactions can be brought over as summarized entries or kept in the old system for reference.
How long until the team can actually use it?
Training is by job, not by module, so a cashier learns four screens and a controller learns fifteen. Each role gets a written manual in Arabic and English with screenshots from your own configured system.
Can it talk to our other systems?
Yes. Data goes in and out through Excel files and a documented interface, which covers most bank files, payroll feeds and reporting tools. Tell us what you need to connect and we'll confirm the approach before you commit.
Do we have to buy all nineteen modules?
No. Most groups start with finance, purchasing and inventory, then add manufacturing, payroll or point of sale later. Adding a module is a setting, not a second project.
What does it cost?
Pricing depends on the number of companies, users and modules, plus the implementation effort. Send us your structure and you'll get a written quotation with the assumptions listed, so you can see exactly what the number is based on.
See it running on your own numbers
Send your company structure and one month of real transactions. We'll configure a demo tenant and walk your finance and operations leads through it — about ninety minutes, in Arabic or English.