Effective accounting services Iraq should control an expense before money leaves the bank, not merely record it afterward. A practical expense-approval workflow checks the business purpose, budget, supporting evidence, approver authority, payment details, accounting treatment, and final reconciliation while keeping routine purchases moving.
Quick answer: Use one written policy, an IQD approval matrix, documented evidence, no self-approval, separate approval from payment, and a monthly exception report. Increase control as value or risk rises.
Disclaimer: This guide is for general information only and is not legal, tax, customs, or accounting advice. Evidence, deductibility, record-retention, payroll, tax, and audit requirements can change. Verify the policy with the relevant Iraqi authority, your auditor, or a qualified advisor before acting.
Hanooot is an Iraqi operating partner founded in Baghdad in 2022. Our accounting services in Iraq connect daily transaction controls with bookkeeping, cash-flow visibility, audit readiness, and a monthly close by Day 5 where the underlying records are complete.
What is an expense approval workflow?
An expense approval workflow is the documented path a purchase or reimbursement follows from request to review, authorization, payment, posting, and reconciliation. It answers who may spend, what they may buy, how much they may approve, what evidence is required, and how exceptions are handled.
A manager may confirm business need; finance still verifies the supplier, duplicates, evidence, budget, classification, and payment destination.
The current U.S. GAO Green Book describes internal control as a process supporting efficient operations, reliable reporting, and compliance. Its principles are useful as a general control reference: authorization, documentation, access control, segregation of duties, and monitoring should work together rather than depend on one signature.
Why do Iraqi businesses lose control of expenses?
The practical issue in Iraq is often fragmented evidence. A request begins in WhatsApp, an invoice arrives on paper, a manager approves verbally, the payment leaves a bank or cash box, and finance receives the documents after month-end. Each handoff creates a gap.
Common failure modes include:
- Self-approval: the requester also approves or releases payment.
- Missing evidence: a receipt exists, but no business purpose, recipient, or delivery confirmation is recorded.
- Split purchases: one requirement is divided into smaller amounts to stay below an approval limit.
- Duplicate payment: the same invoice is submitted through two channels or paid from two accounts.
- Late recording: finance discovers the expense after management reports are prepared.
- Weak cash controls: petty-cash payments are approved retrospectively with no independent count.
A reliable workflow makes these exceptions visible before they become unexplained balances in the monthly close.
What should the approval matrix contain?
The matrix should be based on both amount and risk. A small software subscription may create an auto-renewal commitment; a low-value cash payment may still be risky if repeated many times; a new supplier bank account needs independent verification regardless of invoice value.
| Illustrative spend band | Business approval | Finance check | Extra control |
|---|---|---|---|
| Up to IQD 250,000 | Cost-center supervisor | Evidence and coding | Weekly sample review |
| IQD 250,001-1,500,000 | Department manager | Budget and duplicate check | Approved supplier check |
| IQD 1,500,001-5,000,000 | Director or owner delegate | Full document review | Purchase order or contract |
| Above IQD 5,000,000 | Owner, GM, or committee | Cash-flow and accounting review | Two approvers and payment callback |
| Any bank-detail change | Business owner plus finance | Independent callback | Hold payment until verified |
Figures are indicative and can change by expense type, authority review, exchange rate, company policy, and current regulation. Verify before making a financial decision.
These are workflow examples, not legal thresholds. An Iraqi SME should set limits around its cash flow, branch structure, fraud exposure, and delegation of authority.
Which evidence is required before approval?
Evidence should prove four things: the expense was requested, it served the business, the goods or service were received, and the amount paid matched the approved obligation.
1. Request evidence
Record the requester, department, business purpose, supplier, expected amount, needed date, and budget code before commitment where practical.
2. Commercial evidence
Keep the quotation, purchase order, contract, rate card, or other agreed terms. For recurring services, include the contract owner and renewal date.
3. Receipt evidence
Use an invoice or receipt plus a receiving note, delivery confirmation, timesheet, milestone sign-off, or named service owner. A document alone does not prove receipt.
4. Payment evidence
Retain the approved payment instruction, bank reference or cash voucher, recipient details, and date. Changes to supplier bank details should be verified through a known contact channel, not the change request itself.
5. Accounting evidence
Record the account, cost center, project, branch, currency, exchange-rate source, prepaid or fixed-asset treatment where relevant, and reviewer. This makes the workflow usable for invoice control, not just payment release.
How should duties be separated?
No individual should control every critical stage. The person who requests a purchase should not be the only approver. The approver should not be able to create a supplier, change bank details, release payment, and reconcile the bank account alone.
| Activity | Primary owner | Independent check |
|---|---|---|
| Request and business purpose | Employee or department | Budget owner |
| Supplier setup | Procurement or finance master-data role | Different finance reviewer |
| Receipt confirmation | Operational recipient | Requester manager |
| Expense approval | Authorized manager | Finance policy check |
| Payment release | Treasury or owner delegate | Second authorized approver |
| Ledger posting | Accountant | Close reviewer |
| Bank reconciliation | Finance staff not releasing payment | Finance manager or owner |
The GAO Financial Audit Manual explains the control logic clearly: approvals should be performed by people with authority, key records should be matched, and incompatible duties should be separated to reduce the chance that one person can cause and conceal an error.
For a two- or three-person business, perfect segregation may be impossible. Compensating controls can include owner review of bank alerts, read-only bank access for bookkeeping, a locked supplier list, dual authorization above a low limit, and a monthly report of manual or emergency payments.
What is the step-by-step approval process?
1. Submit one complete request
Use a form or system rather than scattered messages. Give every request a unique number and prevent editing after approval without a visible revision history.
2. Check policy and budget
Finance or the budget owner checks eligibility, available budget, approval level, supplier status, and whether the purchase should follow procurement or contract rules.
3. Confirm receipt
The operational recipient confirms quantity, condition, service period, or milestone. Resolve shortages or disputes before approving the full amount.
4. Match and approve
Compare the request or purchase order, receipt evidence, and invoice. Route exceptions to a named approver with a written reason rather than bypassing the workflow.
5. Release payment securely
Use the approved payment method, verify recipient details, record the bank or cash reference, and prevent the requester from changing the destination after approval.
6. Post and reconcile
Record the expense promptly, clear advances, reconcile the bank or cash account, and investigate duplicates, reversals, and unmatched items before close.
How do you handle urgent and exceptional expenses?
An emergency path is necessary, but it should be narrow. Define who may invoke it, which situations qualify, the maximum amount, what minimum evidence is required before payment, and how quickly retrospective documentation must be completed.
Track exception frequency by requester, branch, supplier, and reason. Repeated exceptions can reveal weak planning, unrealistic limits, or deliberate control avoidance.
Create a monthly exception report showing self-approval attempts, split transactions, missing receipts, weekend releases, new supplier accounts, manual journals, overdue advances, and payments made before receipt confirmation.
What is a worked expense-control example?
Assume a Baghdad business processes 120 expense claims per month. Before introducing one workflow, 15% arrive incomplete and each incomplete claim takes 18 minutes of finance follow-up.
- Incomplete claims: 120 × 15% = 18 claims.
- Follow-up time: 18 × 18 minutes = 324 minutes, or 5.4 hours.
- After mandatory fields and evidence checks, the illustrative incomplete rate falls to 5%: 120 × 5% = 6 claims.
- New follow-up time: 6 × 18 minutes = 108 minutes, or 1.8 hours.
- Illustrative time released: 5.4 - 1.8 = 3.6 hours per month.
If the same control also prevents one duplicate payment of IQD 850,000, the immediate cash protected is IQD 850,000. This is a worked scenario, not a promised result. Actual savings depend on claim volume, data quality, staff behavior, and control design.
Which reports should management review monthly?
Do not measure only total spending. Review approval cycle time, first-pass completeness, expenses submitted after payment, exceptions by reason, transactions just below approval thresholds, duplicate invoice alerts, new or changed supplier bank accounts, overdue employee advances, cash vouchers without evidence, and unbudgeted spending by branch.
Compare actual expense by cost center with budget and the prior period. A variance does not prove a problem, but it gives management a question to investigate. Link the review to accounts-payable controls so approved expenses, supplier balances, due dates, and cash planning agree.
When should the workflow move from spreadsheets to software?
A controlled spreadsheet may be enough when volume is low, approvers are few, and one finance owner maintains the audit trail. Move to a workflow or ERP module when approvals cross branches, evidence is repeatedly lost, policy limits are hard to enforce, remote approval is common, or finance cannot trace a payment back to a complete decision record.
Choose software that records the requester, approver, timestamps, attachments, changes, rejection reasons, coding, payment reference, and ledger export. Automation should enforce policy.
Frequently asked questions
What should an expense approval policy include?
Define eligible expenses, required evidence, approval limits by role, prohibited self-approval, budget checks, exception handling, payment authority, posting rules, retention, and the review reports management receives.
Should the same person approve and pay an expense?
Normally no. Separate requesting, approving, paying, recording, and reconciling where team size allows. A small company that cannot fully separate duties should add owner review, bank alerts, locked access, and a documented monthly exception review.
How quickly should employee expenses be reviewed?
Set a service level that fits the business, such as two working days for complete routine claims, while holding incomplete or unusual claims for evidence. Speed should never remove the independent review step.
Can Hanooot design an expense approval workflow in Iraq?
Yes. Hanooot can map roles, define practical IQD approval bands, standardize evidence, configure digital workflows, reconcile payments, and connect the process to bookkeeping, cash flow, and monthly close.
What is the next practical step?
Export one month of expenses and trace a sample from request through payment and ledger posting. List every missing handoff, then create the approval matrix and required-evidence checklist before buying software.
If your company needs an expense workflow that fits its team, branches, and cash cycle, contact Hanooot for practical accounting and finance operations support in Iraq.