The demo tests the vendor, not the system. This article is the checklist we use before a vendor list exists: the process map, fit levels, e-invoicing and Arabic, integration and migration, total cost, acceptance and exit.
Every ERP demo works. The vendor knows the script, the data is clean, and the difficult step is performed by someone who has done it a thousand times. The selection fails later, in a place the demo never visits: a credit note reversing a delivery that came back in part, a price override granted by a sales manager on a Thursday, a month-end close that needs a report nobody configured, and a new accountant who has to learn the system in a week because the previous one left.
ERP selection is not a product comparison. It is a decision about which processes you standardise, which exceptions you keep, who owns the data, and who is still available in eighteen months when something breaks. This article is the checklist we use before a vendor list exists. It is written to survive the demo, because the demo is the one part of the purchase designed to look finished.
The demo tests the vendor, not the system
A prepared demo walks the happy path: a clean order, a customer with no exception, stock available, and a price with no override. It does not show what happens when the order arrives incomplete, part of a delivery comes back, the customer asks for a corrective invoice, or the unit of measure changes between purchase and sale. These are not rare cases. They are the working day, and they decide whether the system still works in six months.
Ask for the demo to run on your data, or on one case from your operation that carries a real exception. Watch the operator's hands, not the screen: how many clicks, what has to be remembered, and which step needs a note taped to the wall. Then ask whether someone who missed the training could complete the same task in their first week. Staff turnover is normal, and a system that works through one expert is not a system.
Ask who is in the room, and who will be on the implementation. In many deals the person who presents the product is not on the team that delivers it, and the two meet only at the demo. Ask for the name of the implementation lead, and meet that person in a working session rather than a sales one.
Map the processes before the vendor list
Before you open vendor websites, write down the processes that carry money or obligation: quote to order, order to invoice, procure to pay, stock transfers between warehouses, returns and credit notes, month-end close, fixed assets, project costing, approval chains, and the inputs to the tax return. For each one, record the operator, the trigger, the data, the volume, the exception rate, and the current workaround.
The workaround is the real requirement. If the finance team reconciles stock in a spreadsheet every week, the problem is not only the report; it is the data model or the timing of postings. If a sales manager grants price overrides in a chat thread and enters them later, what is needed is an approval policy and a log, not a faster entry screen.
Once the map exists, the vendor list becomes a derived decision: who covers your processes at a reasonable distance from the standard product, has an available implementation partner, can meet the local requirements, and offers a credible way out. A list built before the map is built on reputation, and reputation does not run a month-end close.
Fit, configuration, or customisation
Every requirement in your document sits at one of four levels, and the difference is not linguistic. The level decides who carries it through the next upgrade, and who pays when it changes. When a vendor says “we can do that”, ask at which level, under which contract, and who maintains it in three years.
| Level | What it means | Effect at upgrade | Who maintains it |
|---|---|---|---|
| Standard practice | Works as shipped, with no modification | Survives the upgrade | The software vendor |
| Configuration | Set through supported settings, with no code | Usually survives; needs review when settings change | The implementation partner |
| Licensed add-on | A third-party function under a separate contract | Depends on the third party staying | The third party |
| Custom code | Built for you and absent from the product | May break with a major upgrade | Whoever built it |
| Custom report | Output the standard report does not provide | Needs maintenance as fields change | Whoever built it |
Write the level next to every requirement, and ask each vendor to respond to the level rather than to the possibility. A requirement that is “standard” in the demo and “customisation” in delivery is the most common cause of a budget that breaks, and it is solved by a contract that names the level before signature and states who pays the difference.
E-invoicing and Arabic are scope, not switches
E-invoicing is not a checkbox in the finance module. It touches the tax category on an item, the customer's tax number, credit notes, rounding, the code the invoice carries, the path it travels, and the archive that has to remain extractable. Test an ordinary invoice, a credit note, a partial return, and a rounding case where one field differs by a few halalas. A system that issues a correct invoice in the demo can fail on the credit note, which is the case that appears after the first return.
Arabic is not a language toggle. It is the chart of accounts, the cost centres, the item descriptions, the reports printed and read in the monthly meeting, and the invoices that reach the customer. Test sorting and search in Arabic, mixed numerals, and direction in long tables. If the close report comes out in English because the Arabic layer was never tested, the implementation is not finished.
Run these tests with finance and warehouse staff, not with the IT department alone. They will live in the system, and they will find the first gap in the translation or in the tax logic before a customer does.
Integration and the data model
An ERP is not an island. Payments, shipping, CRM, point of sale, banks, e-invoicing and HR sit around it. Before you ask about interfaces, name the owner of each data domain: item, customer, supplier, price list, tax code, warehouse, chart of accounts, cost centre. A domain with no clear owner will be created in two systems on the same day and reconciled by hand every week.
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
Ask what shape the integration takes: an API, a file, or a direct read from the database. The last is fastest at the start and heaviest when something changes. Ask about duplicates: if the same order arrives twice, is it processed once? Ask about failure: what happens when the other system is down for an hour, who sees the error, when, and how is it replayed?
Add a periodic reconciliation between systems, not only technical monitoring. An integration that runs and is never reconciled produces numbers that agree in shape and differ in meaning. The ERP integration checklist sets out these failure points, and integration services explain how we test each path before launch.
Migration
Migration is not copying data. It is a decision about what deserves to move. Start with master data: items, customers, suppliers, prices, opening balances. Then open transactions: purchase orders not yet received, invoices not yet paid, orders in progress. Long history is usually moved as a summary rather than line by line, because moving all of it doubles the effort and changes no decision.
Rehearse the migration at least twice at real volume, not with ten records. Then plan the close: a freeze window, a parallel run for one close cycle, reconciliation of counts and amounts, and a signature from finance. A system migrated in one night without a parallel run carries the old errors into the new system and adds a month of doubt to them.
Total cost and the implementation partner
Total cost is not the licence price. It is the licence, implementation days, integration, migration, training, care after launch, and the upgrade three years out. The largest line often appears in no proposal at all: your own team's time, from finance, warehouse and procurement, across the months of implementation. That time is real, and it is counted before the decision, not after.
Our published band for enterprise systems is SAR 25,000 to 35,000 over 12 to 20 weeks. That band does not include the ERP licence, which is a separate contract with the software vendor. Ask every proposal for the same five lines: licence, implementation, integration, migration, and care. A proposal that hides a line will show it on an invoice later.
The implementation partner has an incentive: more days mean more revenue. That does not make them an adversary, but it does make a written scope necessary. Ask for the team by name, the implementation lead who will attend the meetings, and references from clients who met an exception similar to yours, not merely a client in your sector. Ask what happens if the lead leaves mid-project, who replaces them, and how context is transferred.
Acceptance and exit
Acceptance is not “the system is installed”. Acceptance is one month closed correctly, an invoice issued and reconciled, a full return processed, and the close report coming out in Arabic. Write a scenario and data set for each process, and name the person from the business who accepts the result, not only from IT. Define what happens to open change requests at go-live: closed, deferred under a condition, or priced.
Exit is written before entry. Ask in which format master data and transactions are exported, whether configuration and customisation documentation is handed over, who owns custom code, whether the licence transfers if ownership changes, and whether the contract includes transition assistance. A system you cannot leave is not a system you chose; it is one that chooses for you.
The selection checklist that survives the demo
This is the minimum we ask for before any demo is booked. If a line is missing, the problem is the sequence of the project, not the system.
A written process map with volumes, exception rates and current workarounds, before any demo.
Every requirement labelled by level: standard practice, configuration, add-on, or custom code.
A demo on your data, or on a real exception from your operation, not a prepared script.
An e-invoicing test: invoice, credit note, partial return, a rounding case, and an extractable archive.
An Arabic report and invoice reviewed by the finance team, not by a translator and not by IT alone.
An integration map naming the data owner in each domain, the system of record, and failure and duplicate behaviour.
A rehearsed migration at real volume, with counts and amounts reconciled and signed before the first close.
An exit clause covering the export format, configuration documentation, ownership of custom code, and transition assistance.
Frequently asked questions
Do we need one system for the whole company? Not necessarily. Start with the processes that carry money or obligation, and leave out what can stay in its current system with a clear integration. One system covering everything is usually a longer project than the need, and its case rests on administrative rather than operational reasons.
How long does selection take? It depends on how ready the process map is, not on the number of vendors. If the processes are written and the data is available, the comparison moves quickly. The first delay is a missing process owner, not a slow vendor.
Is customisation forbidden? No, but it should be a known, priced and documented exception. Large customisations turn the next upgrade into a project of its own, and tie you to whoever built them.
Can we move from an existing system without downtime? It is possible with a freeze window and a parallel run for one close cycle. What we do not recommend is an instant cut-over without reconciliation, because the old errors travel with the data.
Do you work with existing ERP systems? Yes, through enterprise systems and integration services: we help select, integrate, review and migrate. We do not sell software licences; the licence is your contract with the software vendor.
Sources
- Rasad: enterprise systems — how we set scope and build acceptance and delivery.
- ZATCA: the e-invoicing portal — the official requirements that become technical scope.
- Rasad: the ERP integration checklist — the failure points that appear after launch.
- Rasad: integration services — connecting local and external systems and testing each path.
- Rasad's published price bands — the figures this article works from.
Cover image: Asurnipal, CC BY-SA 4.0, via Wikimedia Commons.

