How to Stop Employees from Making Purchases Without Approval in the UAE

To stop unauthorized purchases, write a purchasing policy, define who can approve spending and up to what amount, and require a purchase request before any commitment to a supplier. Allow only authorized people to issue purchase orders (LPOs), create a fast-track route for real emergencies, and review every purchase made outside the process.

The goal is control without slowing routine buying. Clear approval rules, visible request status and a reliable record of every decision let procurement, finance and operations work from the same facts.

Key takeaways

• Most unapproved purchases come from an unclear or slow process, not only from bad intent.
• Set approval limits by value, category and budget, and aggregate split orders so they cannot slip under a threshold.
• Require a purchase request (purchase requisition) before ordering, and a PO before any supplier commitment where your policy says so.
• Have a written answer ready for purchases that already happened: hold, review, ratify or reject, record.
• Software enforces your rules; it cannot replace them. Define the policy first.

In this guide: why employees buy without approval, warning signs, a nine-step prevention process, an AED approval matrix, a policy checklist and sample clause, cards and petty cash, what to do after the fact, UAE considerations including e-invoicing, software evaluation, metrics, mistakes and FAQs.

Why do employees make purchases without approval?

An unauthorized purchase (spelled "unauthorised" in British English) happens when someone commits company money without following the required approval process. That might mean ordering directly from a supplier, paying with a personal card, going over an approved budget, or ordering before a purchase order exists.

Not every case is deliberate. Often people are working around a process that is unclear, slow or inconvenient. The common causes:

• Unclear spending authority. Employees do not know what they can buy alone and what needs a manager.
• Direct supplier orders. Someone confirms an order with a supplier and tells procurement afterwards.
• WhatsApp, verbal and email approvals. A manager says yes in a chat, but nothing is recorded in the official process, so the approval often arrives after the purchase.
• Unclear budget ownership. The requester assumes funds exist; finance or the department head has not confirmed them.
• Urgent operational needs. A site needs replacement parts, a warehouse needs stock, or a facility needs emergency maintenance.
• Weak purchase order controls. People can commit the company before procurement has finished its checks.
• Poor visibility. Managers cannot see pending requests, past purchases or existing commitments.
• Inconsistent enforcement. Some people follow the process while others get informal exceptions.

The important distinction is between someone who ignores a known rule and someone who was never given a workable process. A good control system addresses both.

What are the warning signs that your approval process is being by passed?

Finance and procurement teams usually spot the problem in the paperwork first. Watch for:

• Supplier invoices that arrive with no purchase order.
• Purchase requests created after the invoice date.
• Several orders from the same department just below an approval limit.
• Approvals that exist only as WhatsApp screenshots or forwarded emails.
• The same department repeatedly marking purchases "urgent".
• Suppliers contacting staff directly instead of procurement.
• A requester who is also the approver.
• New suppliers that appear in payments without having been onboarded.
• Reimbursement claims for items that should have gone through a request.

One of these is a prompt to ask questions. Several together usually point to a process problem rather than a single employee.

How can a business prevent unauthorized purchases?

The most reliable method is a purchasing process that employees can follow and managers can enforce. Use these nine steps.

1. Write a purchasing policy

The policy should explain how employees request goods and services, who authorizes spending, when procurement must be involved, and what happens when someone buys outside the process. At minimum, document:

• Who may raise purchase requests.
• Who can approve, and up to what amount.
• Which categories need extra approval.
• How unbudgeted purchases are handled.
• When supplier quotations are required.
• Who may issue purchase orders.
• How urgent and emergency purchases are approved.
• How purchases made outside the policy are reported and reviewed.

Publish it where everyone can find it and explain it in plain language. A policy that lives only in a handbook will not stop spending if people cannot apply it in daily work.

2. Separate requesting, approving and ordering

One person should not be able to request a purchase, approve it and place the supplier order without independent checks.

Purchase Approval Roles & Responsibilities

Smaller businesses may combine roles, but higher-risk transactions still need an independent reviewer. If the requester is also the department manager, require a second authorized approver above a set threshold.

3. Set purchase approval limits

Employees need to know exactly when they can proceed and when someone else must approve. Limits can depend on value, department, category, budget availability, supplier risk and whether the purchase is planned or exceptional. Many UAE companies document this as a delegation of authority (DoA) or authority matrix; section "How should you set approval limits?" below gives an example.

4. Require a purchase request before any commitment

A purchase request (also called a purchase requisition, or PR) is the internal request for permission to buy. Employees should submit it before ordering or committing the company to a supplier, unless a documented exception applies. A good request captures:

• Requester and department.
• Item or service description, quantity and estimated cost.
• Business justification.
• Budget, project or cost center.
• Required delivery date and location.
• Suggested supplier, quotation or specification where required.
• Urgency and any exception justification.

A request is not an approval, and an approval is not an order. Keep those three stages separate.

5. Route every request to the correct approver

The route should follow company rules, not depend on someone remembering whom to ask. An office-supply request may go to the department manager; a project purchase to the project manager and budget owner; an unbudgeted expense to finance and senior management. Define what happens when an approver is absent, when a request is returned for more information, and when approval is pending too long. Name delegates and escalation rules so requests do not stall in an inbox.

6. Control who can issue purchase orders

The request records an internal need. The purchase order (called a local purchase order, or LPO, in many UAE companies) is the formal document issued to a supplier. Where policy requires a PO, no one should place the order before approval and PO issuance are complete. Tell suppliers the rule too: an order without a valid PO number is not an order. Procurement should check that the PO matches the approved requirement, including supplier, items, quantities, price and terms. The procure-to-pay process connects these steps to receiving, invoice processing and payment.

7. Record exceptions and emergency purchases

A process that cannot handle a real emergency pushes people to bypass it. Create a documented fast-track route for safety issues, critical equipment failures and operational stoppages. Specify who can authorize it, what qualifies, the minimum information to record, how it is entered in the official system, and when retrospective review is required. Review exceptions regularly: repeated emergencies usually signal poor planning, weak stock management or an approval process that is too slow.

8. Match purchase orders, receipts and invoices

Approval controls should continue after approval. Where applicable, compare the PO, the goods or services received (the goods receipt note, or GRN) and the supplier invoice before paying. This three-way match catches invoices for items never ordered, quantity differences, duplicate invoices, unapproved price changes and orders placed outside the process. Finance should define who may resolve a discrepancy.

9. Review non-compliant purchases and fix the cause

Track purchases made outside policy and ask why: Did the employee know the rule? Was approval too slow? Was it truly urgent? Did the supplier accept an order without a PO? Was the limit unclear? Use the answers to improve training, process design and enforcement. Repeated or deliberate violations may require action under company policy and applicable employment procedures. The aim is to prevent recurrence, not only to discover spending after it is committed.

How should you set approval limits?

The table below is an illustrative example only. These amounts are not UAE legal requirements or universal standards. Set your own thresholds through your company's governance process, based on delegated authority, purchasing volume, financial exposure and risk.

Purchase Approval Matrix - UAE

Do not rely on value alone. A small purchase from an unapproved supplier, an unusual transaction or an unbudgeted expense may need extra review. A routine purchase under an existing contract may follow a simpler route if the policy allows it.

Also decide what the limit applies to: a single purchase, a total commitment, a contract value or recurring spend. Otherwise a large purchase can be split to avoid the control.

Illustrative example of a split purchase. Under the example matrix above, a manager can approve up to AED 2,000 alone. A team needs AED 6,000 of equipment and sends three separate AED 2,000 orders on the same day. Each looks compliant; together they should have needed the budget owner. A rule that aggregates purchases for the same need, supplier or project within a set period closes this gap.

Foreign-currency purchases. State which exchange rate applies when converting a foreign-currency request into AED for the approval limit (for example, the rate on the request date), so the same purchase is not approved at different levels.

How do you create a purchase approval policy?

Use this checklist when writing or reviewing your policy.

Purchase Policy Framework

Sample clause you can adapt (have HR or legal review it before adoption):

No PO, no payment. Invoices for goods or services not covered by an approved purchase order or a documented emergency exception will be held until Finance has reviewed them. The employee who placed the order must submit a written explanation to Procurement and their manager. Finance will decide whether to ratify, reject or return the purchase.

Review the policy whenever your structure, spending authority, purchasing categories or operations change. If you operate across Dubai, Abu Dhabi and other emirates, state whether the same rules apply to every branch and legal entity, or whether local budget owners and approvers differ.

What should a purchase approval workflow look like?

A clear workflow gives employees one route and gives management visibility of every request.

1. The employee submits a purchase request.
2. The request is checked for completeness, budget and policy requirements.
3. The authorized manager approves, rejects or returns it.
4. Procurement obtains quotations or evaluates suppliers where required.
5. An authorized person issues the PO or LPO.
6. The business records receipt of the goods or services.
7. Finance matches the invoice to the PO and receipt.
8. The transaction is closed and included in compliance reporting.

A rejected request should not progress to ordering. A request missing information should go back to the requester. An over-budget request should follow the exception route. You should also be able to see where each request is waiting, who owns the next action and when to escalate.

[Diagram: request-to-PO flow, matching the eight steps above. Alt text: purchase request, budget and policy check, approval, sourcing, PO or LPO, goods receipt, invoice match, close.]

How do you control cards, petty cash and reimbursements?

A PO process does not cover every route money takes. Unapproved spending also happens through company cards, personal cards that are later reimbursed, and petty cash. Close these gaps with the same principle: the approval comes before the spend.

• Say which purchases may use a card and which must go through a request and PO.
• Set per-person and per-category card limits and block categories you do not want.
• Require a receipt and a business reason for every card and petty cash transaction.
• Reimburse personal-card spending only if it followed the request process or an approved exception.
• Set a cap and an approver for petty cash, and reconcile it regularly.
• Review subscriptions, freelancers and agency work, which often start small and recur.

Tools that support virtual cards, petty cash and expense rules, such as ZYNO Expenz, can enforce these rules at the point of spend. Card controls and purchase approvals solve different parts of the problem, so most growing businesses need both.

What should you do when an unauthorized purchase has already happened?

Sooner or later an invoice arrives for something nobody approved. Decide the response in advance so it is consistent and fair.

1. Hold the payment. Pause payment until the purchase has been reviewed.
2. Assess the facts. Was the item delivered? Is it needed? Was the price reasonable? Was the budget available? Was it a genuine emergency?
3. Decide. Ratify (approve after the fact) with a documented reason, return the goods, renegotiate, or reject the invoice according to policy.
4. Record it. Log the exception, who decided and why, so it appears in compliance reporting.
5. Fix the cause. Retrain, clarify the limit, speed up the approval route or warn the supplier.
6. Apply consequences consistently. Define them in policy and have HR or legal review them. Do not let ratification become the normal route, or the rule stops meaning anything.

Tell suppliers in writing that orders without a valid PO number may not be honored. It protects both sides and gives your team a simple reason to say no.

How should UAE businesses handle purchasing approvals?

The right controls depend on the business, but some considerations are specific to companies working across UAE branches, sites and supplier networks.

Construction and contracting

Project teams need materials, equipment and subcontract services at specific sites. Define site-level requesters, project budget owners, urgent maintenance exceptions and who may issue supplier orders.

Trading and distribution

Recurring stock purchases create large commitments. Set controls for replenishment, approved suppliers, existing contracts and purchases above planned quantities or budgets.

Manufacturing and facilities management

Production stoppages and equipment failures may need urgent buying. A documented emergency route lets you respond quickly without losing the record of who authorized the spend.

Multi-branch and multi-entity groups

Define which department, branch, project or legal entity owns each budget. Route requests to the correct authorized approver and record the purchase against the right entity.

E-invoicing, VAT records and supplier documents

The UAE is moving businesses to mandatory e-invoicing, and the approval trail matters more once invoices arrive as structured data. According to the Ministry of Finance's published timeline as reported by advisers, businesses with annual revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 (extended from 31 July 2026) and go live from 1 January 2027. Other businesses follow, with an ASP to be appointed by 31 March 2027 and go-live from 1 July 2027. The mandate applies to businesses operating in the UAE regardless of VAT registration. Dates have already been amended once, so confirm the current position on the Ministry of Finance e-invoicing page and the Federal Tax Authority website before you plan.

Two practical points for procurement and finance:

• Match before you pay. When an invoice arrives electronically, a PO and goods receipt that already exist make matching faster and easier to audit. Check supplier details, including the Tax Registration Number (TRN), invoice values and VAT treatment.
• Keep the records. VAT records generally need to be kept for at least five years and corporate tax records for at least seven. Keep the request, approval, PO, receipt and invoice together so the trail is complete.

Internal approval limits are set by your own governance process. They are not UAE statutory thresholds, and this guide is not tax or legal advice. If your invoicing system is changing, ZYNO Books e-invoicing is one option to review alongside your procurement controls. For a wider look at the category, see our guide to procurement software in the UAE.

Can purchase approval workflow software prevent unauthorized spending?

Purchase approval workflow software helps a company apply its purchasing rules consistently. It cannot guarantee that nobody ever buys outside the process; that also depends on your payment, supplier and card controls.

A good system can:

• Give everyone one place to submit requests.
• Route requests by configured rules for amount, department or category.
• Show pending requests and their status.
• Record approval decisions, comments and supporting documents.
• Show budget information to approvers and apply configured budget checks.
• Connect an approved request to purchase order creation.
• Provide reports on exceptions and bottlenecks.

Process Comparison Table

A small business with few, simple purchases can keep good control with a well-run manual process. A business with many requesters, several approval levels, frequent exceptions or multiple locations is more likely to benefit from a dedicated system.

What should you look for in purchase approval workflow software?

Before choosing, prepare realistic purchasing scenarios and ask each vendor to demonstrate them.

• Can it route approvals by amount, department, category and other rules?
• Can it handle unbudgeted purchases and exception routes?
• Can employees attach quotations and supporting documents?
• Can approvers approve, reject or return a request with comments?
• Can delegates approve when someone is absent, and can overdue approvals escalate?
• Can approvers act from a mobile device, so approvals do not move to WhatsApp?
• Does it record decisions with dates and users?
• Can an approved request move to a PO without re-entering data?
• Does it connect to your ERP or accounting system where needed?
• Can it support your branches, projects and legal entities?
• Can reports show purchases outside policy and recurring bottlenecks?

During a demo, ask to see a routine purchase, an over-budget request, an urgent purchase, a rejected request, and an order that cannot proceed until approval is complete. Also ask how the system helps you detect an employee trying to bypass it, because software that records approvals is useful only if your process also catches off-system buying.

How ZYNO Procurement supports purchase approval controls

Disclosure: ZYNO Procurement is Elite Mindz's product. We have tried to keep this section factual, and we suggest you test any vendor against your own scenarios.

The ZYNO Purchase Request module brings purchase requests and approvals into one workflow. It lets you:

• Collect requests through configured forms, with attachments, on desktop or mobile.
• Route requests by supported conditions such as amount, category and department.
• Show budget information to approvers and apply budget checks you configure.
• Support notifications and escalation options for approvals that need attention.
• Keep approval history so authorized users can see how a request progressed.
• Move an approved requisition toward purchase order creation. The exact handoff depends on how your organization configures it.

If you also need supplier sourcing, see Quotation Management and Vendor Management. For receiving and invoice checks, see GRN and Account Payable. The wider ZYNO Procurement platform connects these stages, and our Middle East procurement page covers regional use.

[Screenshot: ZYNO purchase request with budget check, using AED sample data. Alt text: ZYNO purchase request showing amount in AED, budget status and approval history.]

The important question is whether these capabilities can be configured to match your own policy and delegated authority. In a demo, ask the team to show how:

1. An employee submits a request.
2. The system routes it to the authorized approver.
3. An over-budget or exception request is handled.
4. Approvers review, reject or return it.
5. Approval history is recorded.
6. An approved request moves toward a PO.
7. Procurement or finance sees what is still pending.

Book a ZYNO Procurement demo and see how your approval limits, exception rules and request-to-PO process could work in ZYNO, or start a 14-day free trial.

How do you measure whether purchasing controls are working?

Start with a baseline, then review the same measures regularly.

Do not judge the process only by how fast managers approve. A fast approval that ignores budget, supplier or policy is not an effective control. Tools like ZYNO Spend Analytics can help report on these measures. The aim is fewer unauthorized commitments while legitimate purchases keep moving.

Common mistakes to avoid

• Setting limits without explaining them. Publish the policy and train people on it.
• Requiring approval but allowing direct ordering. Define who can commit the company and how you check.
• Letting informal exceptions become normal. Document emergencies and review repeats.
• Using one route for every purchase. Match controls to value, category, risk and budget.
• Letting people approve their own purchases. Apply separation of duties.
• Ignoring supplier and invoice controls. An approved request does not remove the need to check the order, receipt and invoice.
• Buying software before defining the policy. Configure the system around agreed rules.
• Not monitoring compliance. Without exception reports and periodic reviews, breaches go unnoticed.

Frequently asked questions

How can a company stop employees from buying without approval?

Create a written purchasing policy, define spending authority, require a purchase request before any commitment, route requests to authorized approvers and control who issues POs. Review transactions made outside the process and address why they happened.

What is a purchase approval workflow?

It is the sequence of steps a purchase request follows before the business authorizes the spend. It defines who reviews the request, which checks apply, how exceptions are handled and when procurement can proceed.

How should a company set purchase approval limits?

Set limits according to your budget structure, delegated authority, purchasing risk and financial exposure. Define the approval route for each threshold, and add requirements for unbudgeted, unusual or higher-risk purchases. Aggregate split orders.

Can employees place an order before a purchase order is approved?

They should follow your purchasing policy. Where a PO is mandatory, no one should commit the company before approval and PO issuance, except through a documented, authorized exception.

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

A purchase request (or requisition) is an internal request for permission to buy. A purchase order, often called an LPO in the UAE, is the formal document an authorized person issues to a supplier. Approving the request does not mean the supplier order has been placed.

How should urgent purchases be approved?

Create a defined emergency route with named approvers, clear qualifying circumstances, minimum documentation and a requirement to record and review the purchase afterwards.

How can finance detect purchases made outside company policy?

Compare purchase records, supplier invoices, payment records and POs. Track invoices without a PO, mismatches between invoice and order, repeat exceptions and departments that often bypass the process.

What should we do if an invoice arrives for an unapproved purchase?

Hold payment, review what was bought and why, then ratify with a documented reason, renegotiate, return the goods or reject the invoice under your policy. Record the exception and fix the cause.

Can purchase approval workflow software enforce spending limits?

It can apply configured rules and route, flag or restrict defined exceptions where the product supports that. It cannot guarantee all off-system spending is prevented unless your wider purchasing and payment processes reinforce it.

How can UAE businesses manage approvals across multiple branches?

Define the budget owner and approval authority for each branch, project or legal entity. Use consistent policies where possible, document local exceptions and keep central visibility of purchasing.

What features should businesses look for in purchase approval software?

Configurable routing, budget visibility and checks, request tracking, supporting documents, approval history, mobile approval, exception handling, PO handoff, reporting and relevant ERP or accounting integrations. Test them with your own scenarios.

Conclusion: make every purchase accountable

Stopping unauthorized purchases is not just a matter of telling people to ask permission. You need clear spending authority, a practical request process, sensible approval limits, controlled PO issuance, a plan for purchases that already happened, and a way to see exceptions.

For UAE organizations with several departments, sites or branches, the process should be strict enough to protect company funds and practical enough that nobody has to bypass it to get legitimate work done.

Start by documenting your approval policy and finding where purchases currently escape the process. Then test whether your tools can enforce it.

If manual approvals, scattered records and limited visibility are making purchasing hard to manage, explore ZYNO Purchase Request and book a demo based on your actual approval rules and purchasing workflow.