Why Purchase Contracts and Tenders Need Structure
In many companies purchasing starts with a department request, a few calls to suppliers, a quote by email and then a purchase order. That is fine for small, occasional buys. It stops being fine when the company buys the same items every month to the tune of millions of riyals, signs a three-year maintenance contract, or runs a tender for equipment. Without structure, agreed prices are not applied on invoices, contracts roll over without negotiation, departments buy off-contract at higher prices, and award committees have no documented comparison to stand behind.
Managing purchase contracts and tenders in an ERP means the contract becomes a live reference inside the system, not a PDF in a manager's folder. Prices, quantities, terms and payment conditions are recorded; every purchase order raised against the contract is checked against them; alerts fire before the contract expires or its quantity runs out. Tenders follow documented steps from request for proposal to award, so an internal or external auditor can see exactly why a supplier was chosen.
This guide covers the main types of purchase contract, a private-sector tender cycle, a worked weighted-scoring model, how to monitor framework agreements, service level contracts, and the Saudi legal and tax points that matter, from the Civil Transactions Law to VAT, withholding tax and government procurement.
Common Types of Purchase Contract
| Type | When to use it | What it fixes | How it lives in the ERP |
|---|---|---|---|
| Spot purchase order | One-off or irregular buys | Item, quantity, price, delivery | Standalone PO |
| Quantity framework agreement | Recurring need with a roughly known annual volume | Price, total quantity, term | Contract with call-off orders against it |
| Price agreement, no committed volume | Recurring items, uncertain quantities | A price list for a fixed period | Supplier price list linked to items |
| Service contract | Maintenance, cleaning, transport, security | Scope, periodic fee, service levels | Contract with periodic invoices and KPIs |
| Supply and install | Equipment or systems needing installation and commissioning | Milestone payments, warranty | Contract with payment and acceptance stages |
The principle is simple: the contract should be its own record in the system, with a number, start and end dates, consumed and remaining balances, and links to the purchase orders, receipts and invoices raised under it.
A Private-Sector Tender Cycle, Step by Step
Private companies are not bound by government tender procedures, but many adopt a similar internal policy for large purchases. A typical cycle:
- Define the need and budget. The requesting department sets specifications, quantity and required date; finance confirms budget. In the ERP this is an approved purchase requisition tied to a cost centre.
- Select invited suppliers. From the qualified supplier list, after checking commercial registration, VAT registration and valid certificates.
- Issue the RFP. Clear specifications and a terms document stating the evaluation criteria, their weights and the submission deadline. Publishing criteria up front heads off disputes later.
- Receive bids. Ideally separate technical and commercial envelopes, and only open commercial bids for technically compliant offers, so price does not colour the technical review.
- Evaluate. A committee scores bids against the published criteria, with each member's scores recorded.
- Negotiate and award. With the top-scoring bidder, approved according to the authority matrix.
- Sign and register the contract. Convert the winning bid into a contract record with its prices and terms, so purchase orders can flow against it.
For hands-on detail on comparing quotes, see our guide to smart RFQ comparison.
Worked Example: Weighted Scoring of Three Bids
A hypothetical tender for a year's supply of packaging materials. Published criteria and weights: price 50%, technical quality and compliance 25%, delivery lead time 15%, payment terms 10%. Price converts to a score out of 100 by dividing the lowest bid by each bid.
| Criterion (weight) | Supplier A | Supplier B | Supplier C |
|---|---|---|---|
| Total price (SAR) | 1,800,000 | 1,650,000 | 1,720,000 |
| Price score (50%) | 91.7 | 100 | 95.9 |
| Technical quality (25%) | 90 | 70 | 85 |
| Lead time (15%) | 80 | 90 | 85 |
| Payment terms (10%) | 100 (60 days) | 50 (30 days) | 75 (45 days) |
| Weighted score | 90.3 | 86.0 | 89.5 |
For Supplier A: 91.7 x 0.5 + 90 x 0.25 + 80 x 0.15 + 100 x 0.1 = 45.85 + 22.5 + 12 + 10, or about 90.3. Supplier B has the lowest price but the lowest overall score, dragged down by weak technical quality and short payment terms. A and C are less than a point apart, which is where negotiation comes in: if C agrees to 60-day terms, it moves ahead. What matters is that the committee's decision rests on a documented, explainable number rather than an impression.
Quality scores should come from data, not a snap judgement. For existing suppliers, rejection rates and on-time delivery from ERP purchase history are the best input. Our guide to supplier performance explains how to build those measures.
Monitoring a Framework Agreement After Signature
Signing is half the job; the other half is making sure the contract is actually used. A hypothetical framework agreement for 120,000 units at SAR 12 each over 12 months, SAR 1,440,000 before VAT:
| Month | Cumulative call-off | Quantity consumed | Term elapsed | Note |
|---|---|---|---|---|
| 3 | 36,000 | 30% | 25% | Running slightly ahead |
| 6 | 78,000 | 65% | 50% | Quantity will run out before term ends |
| 8 | 98,000 | 81.7% | 66.7% | 80% alert: start negotiating extra volume |
At about 12,250 units a month, the quantity runs out around month ten. The month-eight alert gives the buyer time to agree an addendum for extra volume at the same price, rather than discovering the problem when the supplier rejects a new order or quotes today's market price. The reverse also matters: if consumption is slow and the contract carries a minimum offtake commitment, an early warning allows renegotiation before the company faces a shortfall penalty.
Stopping Off-Contract Buying
Off-contract (maverick) buying happens when a department buys a contracted item from someone else, usually because it is quicker or because the buyer does not know the contract exists. The cost is direct. Hypothetically: an item contracted at SAR 12, of which two branches bought 15,000 units over the year on the open market at an average of SAR 14.50. Extra cost = 15,000 x 2.50 = SAR 37,500, and that volume did not count towards the company's commitment to the contracted supplier.
Practical ERP controls:
- When a PO is raised for an item with an active contract, the system proposes the contracted supplier and price.
- Choosing another supplier requires a documented reason and an extra approval.
- A monthly report of spend under contract by department, with the exceptions and their reasons.
- Three-way matching of PO, receipt and invoice, with invoices above contract price held for review.
Service Contracts and Service Levels
Service contracts have no countable delivery, so the control is a defined, measured service level with a clear deduction mechanism. A hypothetical air-conditioning maintenance contract for an office complex at SAR 40,000 a month requires emergency response within 4 hours, with a 2% fee deduction per late response, capped at 10%. In one month there were 18 emergency calls and 3 breached the response time: deduction = 3 x 2% = 6%, or SAR 2,400, leaving SAR 37,600 payable before VAT. That calculation is only possible if calls are logged with open time and technician arrival time in one system, linked to the contract. Over time the response record becomes the best input to the renewal or re-tender decision.
The Authority Matrix
Every company sets its own limits, but a common hypothetical structure looks like this:
| Value before VAT | Quotes required | Approver |
|---|---|---|
| Up to SAR 10,000 | One acceptable quote | Department manager |
| SAR 10,001 to 100,000 | At least three quotes | Procurement manager |
| SAR 100,001 to 500,000 | Limited tender | CFO |
| Over SAR 500,000 | Tender with evaluation committee | CEO or procurement committee |
The value that counts is the full contract value, not a single order, so a large purchase cannot be split into small POs to slip under a threshold. The ERP can flag several orders to the same supplier for the same item within a short window.
Saudi Legal and Tax Considerations
Civil Transactions Law
The Civil Transactions Law (Royal Decree M/191) took effect on 16 December 2023 and now provides the general framework for contracts between companies. Two provisions bear directly on purchase contracts. First, agreed compensation (liquidated damages) clauses are permitted, but a court may reduce them if they are unreasonably high or the obligation was partly performed, and they are not due if the debtor shows no loss was suffered. Second, hardship: where unforeseeable exceptional circumstances make performance excessively burdensome, the affected party must seek renegotiation without undue delay while continuing to perform, and a court may reduce the onerous obligation to a reasonable level. In practice, delay penalties in supply contracts should be proportionate, and the ERP should record each delay date so it can be evidenced.
VAT on purchases
To recover input VAT, the company needs a valid tax invoice from a VAT-registered supplier containing the required details, including both parties' VAT numbers. If the supplier has not been paid within 12 months of the supply, the deduction must be reversed. Linking contract, PO, invoice and payment in one system lets you flag invoices approaching twelve months unpaid.
Withholding tax on non-resident suppliers
Payments to non-resident service providers are subject to withholding tax at 5%, 15% or 20% depending on the type of service, with 20% common for management fees, and treaty rates available under conditions. The contract record should flag the supplier as non-resident and capture the service type, so tax is calculated on each payment.
Government tenders
If you sell to government entities, you deal with the 2019 Government Tenders and Procurement Law and the Etimad e-procurement platform. That law generally requires a bid bond of 1% to 2% of the bid value, with exemptions including direct purchases and local SMEs. A new Government Tenders and Procurement Law was published on 4 September 2026 and takes effect on 2 January 2027, replacing the 2019 law and strengthening the role of the Local Content and Government Procurement Authority. See our guide to government procurement in Saudi Arabia.
Contract Management KPIs
- Spend under contract: PO value linked to an active contract divided by total spend.
- Price compliance: share of invoices matching contract price with no variance.
- Tender cycle time: days from approved requisition to signed contract.
- Unreviewed expiries: contracts that renewed or lapsed without evaluation or negotiation.
- Documented savings: awarded price against a reference such as the previous price or the average bid.
More on calculating these in our article on procurement KPIs.
Common Mistakes
- Contracts in folders, not in the system. If prices are not in the ERP, nobody checks them at invoicing.
- Criteria set after bids are opened. An open invitation to challenge the award.
- Silent auto-renewal. Service contracts in particular roll over for years at the same or higher price with no market test. Alert at least 90 days before a 60-day notice deadline.
- No conflict-of-interest declarations. Committee members linked to a bidder should disclose and step aside.
- No audit trail. When a contract price changes, the system should keep who changed it, when, and the previous value, backed by an approved addendum.
How Tranquil Fits
Tranquil is a cloud ERP with a purchasing module alongside financial accounting and inventory, so purchase orders, receipts, invoices and payments sit together. Tranquil's customization services include multi-level approval workflows by value and department, custom reports and screens for tracking contracts and spend, and API integrations with other systems. Explore our purchase management solution or contact us to discuss your procurement policy.
Frequently Asked Questions
What is the difference between a framework agreement and a regular PO?
A regular PO covers a specific quantity and delivery, once. A framework agreement fixes price and terms for a period and total volume, with multiple call-off orders raised against it without renegotiating each time.
Do private companies have to run formal tenders?
There is no general requirement for private companies to follow government tender procedures for their own purchasing. A written policy with clear thresholds for quotes and tenders still protects against waste and makes audits easier.
Can a supply contract include a delay penalty?
Yes. The Civil Transactions Law allows agreed compensation, but a court can reduce it if it is excessive or the obligation was partly performed, so keep penalties proportionate to likely loss.
What happens to input VAT if we pay a supplier late?
If the consideration is not paid within 12 months of the supply, the input VAT already deducted must be reversed. It can be reclaimed once payment is made, subject to the rules.
How do we make sure invoices match contract prices?
Use three-way matching in the ERP between the contract-linked PO, the receipt and the invoice, and configure the system to hold any invoice priced above contract until an authorised person approves it.