How to Choose an ERP Software to Enhance your Purchase Management

Where Purchasing Breaks Down Without a System

Here is how a purchase often happens in a mid-sized Saudi company. Someone sends a WhatsApp message to the buyer. The buyer emails three suppliers for quotes, prints them and leaves them on the manager's desk. The manager signs one. The buyer raises a PO in the accounting software. The goods arrive and the storekeeper signs a delivery note. Two weeks later the invoice reaches finance, and an accountant goes looking for the PO and the delivery note to check it.

Every step works, more or less. But nobody sees the whole picture. How much did we spend on this item this quarter? Which requests are stuck waiting for approval? Did we actually receive what we are about to pay for?

An ERP with proper purchase management turns those steps into one connected procure-to-pay cycle. Each document is created from the previous one, every approval is recorded, and every supplier invoice is matched automatically against the order and the receipt. Systems differ a lot here, though. Some treat purchasing as a thin layer over accounting; others cover the cycle in depth. This guide gives you the criteria, a scoring matrix and the demo scenarios that separate the two.

The Cycle Your ERP Must Cover

Agree internally on the target process before comparing vendors. A complete cycle usually looks like this:

1. Purchase requisition: raised by the requesting department, or generated automatically when an item hits its reorder point.
2. Requisition approval: based on value, department, expense type and available budget.
3. Request for quotation: sent to several suppliers, with offers compared on price, lead time and payment terms.
4. Purchase order: a binding document with items, quantities, prices, delivery date and terms.
5. Goods receipt: what actually arrived and in what condition, including partial deliveries.
6. Supplier invoice: recorded and matched against the PO and receipt.
7. Payment: scheduled according to terms and available cash.

A good system creates each step from the one before without re-keying, and lets you trace any document back to its origin. For a deeper look at automating this flow, read our article on procure-to-pay automation.

Problems the System Has to Solve

Start selection from your own problems, not the vendor's feature list. These are the ones we see most often:

• Maverick buying: purchases made without a PO, and an invoice arrives that nobody can explain.
• Slow or missing approvals: a request waits a week for a traveling manager, or large orders go through without approval proportionate to their value.
• Paying for what was not received: invoiced 100, received 90, and nobody notices.
• Duplicate buying: two departments buy the same item from different suppliers at different prices in the same week.
• No price history: nobody knows what was paid last time, so any quoted price gets accepted.
• Lost input VAT: supplier invoices with missing details that cannot support a VAT deduction.
• Budget overruns: discovered at quarter end, when it is too late.

Core Functions to Look For

Configurable multi-level approvals

You should be able to set the rules yourself: under SAR 5,000 the department head approves, SAR 5,000 to 50,000 needs the finance manager, anything above needs the general manager. Approvers should get requests on their phone or email, and delegation should work when someone is away. This is one of the biggest differentiators between systems. Tranquil delivers multi-level approvals as part of its customization services.

Requisitions linked to stock and budget

A requisition for a stock item should show current balance and quantities already on order. A requisition charged to a cost center or project should show remaining budget after open commitments, not just after payments.

Quotation comparison

A side-by-side view of supplier offers per item, covering price, lead time, payment terms and warranty, with the winning offer converted straight into a PO. Our article on RFQ comparison in ERP covers this step in detail.

Three-way match

The supplier invoice is matched against the PO and the goods receipt on quantity and price. If quantity differs or price exceeds a set tolerance, the invoice is held for review instead of paid automatically. This single control prevents an entire class of errors and abuse.

Supplier master and performance

Core supplier data, VAT number, commercial registration and bank details, plus history: past prices, on-time delivery, return rate. That history is the basis of any objective evaluation, which we describe in our guide to supplier performance.

Landed cost

Importers need freight, insurance, customs duty and clearance allocated across imported items, so that inventory cost and sales margins reflect reality.

Tax and local compliance

Correct 15% VAT on purchases, a clear split between recoverable and non-recoverable VAT, and a check that the supplier's VAT number is on the invoice. As e-invoicing integration waves reach smaller businesses (Wave 24 covers taxpayers above SAR 375,000 in revenue, integrating between April and June 2026; Wave 25 covers those above SAR 187,500 from February 2027), a growing share of your supplier invoices will arrive in electronic form, and the system should handle them without friction.

Reporting

Spend by supplier, item, department and project; open requisitions and their age; POs not yet received; price variance against last purchase. For a broader set of measures see our article on procurement KPIs.

Worked Example: What Three-Way Matching Catches

Hypothetical example: a distributor processes 400 supplier invoices a month averaging SAR 12,000, so SAR 4.8 million a month. After switching on three-way matching, 2% of invoices show a quantity or price difference against the PO or receipt, averaging SAR 600 each.

• Invoices with discrepancies: 400 × 2% = 8 a month.
• Value: 8 × 600 = SAR 4,800 a month.
• Annually: SAR 57,600 that would have been paid for nothing.

Some differences are honest mistakes, some are short shipments, a few might be worse. Either way, catching them before payment is much easier than recovering money afterwards. The 2% rate is illustrative; yours will differ.

Worked example: the cost of slow approvals

Hypothetical example: a maintenance company takes five working days on average to approve a request for a part that is not in stock, because the paper request travels between offices. Meanwhile a machine sits idle or a replacement is hired at SAR 800 a day. Ten times a month, that is SAR 40,000. With approvals on the approver's phone and same-day sign-off, the wait drops to one day and the cost to SAR 8,000. It never appears on a purchase invoice, but it is real money.

Selection Criteria Beyond Features

Integration with the rest of the business

Purchasing does not live alone. A PO affects stock, a receipt affects inventory cost, an invoice affects payables and VAT, and a payment affects cash. If purchasing sits in one system and accounting in another, you are back to double entry and manual matching. Purchasing works best as a module inside a single ERP alongside inventory and accounting.

Ease of use for non-specialists

Most requisitions come from site engineers, maintenance supervisors and department heads, not buyers. If raising a request is painful, they will go back to WhatsApp. Test it: ask a non-purchasing employee to create a requisition during the demo.

Flexibility

Can you add fields specific to your business, such as project or equipment number? Adjust print templates? Connect to supplier portals via API? Tranquil offers customization of screens, reports, multi-level approvals and API integrations.

Pricing model and total cost

Per-user pricing gets expensive if you want every department head raising their own requests. Tranquil, for example, offers per-user pricing for small firms or a flat per-module fee with unlimited users for companies above 50 users.

Local support and training

A team that understands Saudi practice and ZATCA requirements and can train your staff in Arabic shortens implementation considerably.

Stock Purchases vs Project and Service Purchases

Evaluating a system only on stock purchases is a common mistake. In contracting, maintenance and service businesses, much of the spend never enters a warehouse: materials delivered straight to site, equipment rental, subcontractor services, facility maintenance. These need different handling:

• Project or cost center on every PO, so cost shows in the project report at commitment, not at payment.
• Service receipts, confirming completion or a percentage of work rather than counting units.
• Direct-to-site delivery, received by the site engineer rather than the central storekeeper.
• Commitment checks against project budget before any new PO is approved.

Deployment Model and Purchasing

For purchasing specifically, cloud usually wins because fast approvals from anywhere are one of the biggest drivers of cycle improvement. Your information security policies and sector requirements still have the final say.

A Weighted Scoring Matrix

Weight each criterion by your priorities, then score each system 1 to 5 after the demo. Hypothetical example for a mid-sized distributor:

System B is easier and cheaper, but weak integration pulls it down because the team weighted integration heavily. Different priorities would produce a different winner. The real value of the matrix is that it forces the selection team to agree on priorities before the slickest demo sways them.

Demo Scenarios to Insist On

1. A SAR 60,000 requisition raised by a department user, routed through three approval levels, rejected at level two and sent back for changes.
2. An RFQ to three suppliers, comparison, and conversion of the best offer to a PO.
3. A partial receipt of 70 out of 100, with the balance received a week later.
4. A supplier invoice priced 3% above the PO: what does the system do?
5. An import shipment with freight and duty allocated across three items by value or weight.
6. Spend by supplier for last quarter, and the open requisitions report.

How the vendor handles these, how long it takes, and what workaround they propose when a function is missing tells you more than any slide deck.

Implementation Steps After Selection

1. Write the purchasing policy: approval limits, number of quotes by value, documented exceptions.
2. Clean supplier data: remove duplicates, verify VAT numbers and bank details.
3. Clean item data: units of measure, categories, approved suppliers per item.
4. Start with one flow, such as stock purchases, then add services and projects.
5. Close the back doors: after a set date, no invoice is accepted without a PO except as a documented exception.
6. Review after two months: average approval time, first-pass match rate, share of spend outside the cycle.

To see what Tranquil offers here, visit the purchase management page.

Frequently Asked Questions

What is the difference between a purchase requisition and a purchase order?

A requisition is an internal document expressing a department's need and requiring approval. A purchase order is an external document sent to the supplier that commits the company to the stated price, quantity and terms.

Does a small company need three-way matching?

Yes, even in a simple form. Matching what was ordered, received and invoiced is the most basic payment control, and it costs little to run in a system compared with the errors it prevents.

How many approval levels are enough?

There is no fixed rule, but two or three value-based levels suit most mid-sized companies. Too many levels slow purchasing and push people to bypass the cycle.

Should purchasing live in the same system as accounting?

Ideally, yes. Separating them brings back double entry, delays commitments appearing in the books, and makes three-way matching and budget checks much harder.

Does Tranquil support multi-level purchase approvals?

Yes. Tranquil's customization services include multi-level approvals, screens, reports and API integrations. Contact the Tranquil team to review your purchasing cycle.