Expense Management: 7 Problems That Silently Leak Profits and Surprise You at Year-End

Expense management covers so much more than just travel costs. Think about software subscriptions, utility bills, professional fees, maintenance contracts, and employee reimbursements – every penny spent that isn’t for direct product creation. In Saudi Arabia, things get even more complex with specific ZATCA requirements for VAT, adherence to SOCPA and IFRS accounting standards, and the need to track costs precisely across different departments and projects. When the systems managing these expenses are scattered, rely on manual steps, or are poorly set up, your company is essentially operating in the dark, making decisions with outdated or incomplete information.

This article goes beyond general advice, offering practical solutions for senior leaders. We’ll dive into seven common problems that weaken financial control in expense management. For each problem, we’ll explain why it happens, how it clearly impacts your financial reports, and provide a clear plan for fixing it using your Enterprise Resource Planning (ERP) system. The goal isn’t just to stop financial leaks but to build a strong, clear, and auditable expense management system. This will improve governance, empower department heads, and ultimately protect your company’s bottom line.

Problem 1: No Clear Expense Approval Rules

The Issue: Approving spending is often a messy, unclear, and inconsistent process. Who can approve what? Where are those rules written down? Too often, they exist only in peoples’ heads or old spreadsheets. This leads to delays, unauthorized spending, and no clear record of who approved what, when, or why. Requests bounce around via email, making it impossible to see where things stand.

Why It Happens: This breakdown usually occurs because no one truly “owns” the approval policy. It often falls between departments like Finance, HR, and individual business units. As a result, ERP systems aren’t set up to enforce company rules because the rules themselves are vague or undocumented. High employee turnover makes things worse, as approval chains based on specific people quickly become outdated, causing requests to get lost or stalled.

How It Hurts You: The financial damage is direct and serious. The most obvious is spending more than planned because there’s no check before money is committed. The risk of fraud jumps significantly when approval controls are weak or easily bypassed. Operationally, it creates huge inefficiencies; delays irritate suppliers and demotivate employees waiting for reimbursements. Ultimately, financial reports become unreliable because the finance team can’t see commitments that have been approved but not yet invoiced.

The Solution: You need to build a smart, rules-based approval system directly into your ERP’s procurement and finance modules. This isn’t just about making your current broken process digital; it’s about a complete overhaul:

• Role-Based Approvals: Set up approval paths based on job titles (like ‘Head of Marketing’ or ‘Division GM’) instead of individual names. When someone changes roles, their permissions update automatically, saving you manual effort.
• Smart Approval Logic: Create a multi-layered approval system in your ERP. Rules should dynamically decide the approval chain based on factors like the type of expense (e.g., major equipment vs. operating cost), the amount, the department requesting it, and the project code. For example, a request for a new server might automatically go to IT, then Finance, then the division head, based on its value.
• Delegation and Escalation: Configure automatic delegation. If an approver is away, the system can automatically send requests to a designated backup if not acted upon after a certain time, preventing hold-ups. Escalation rules can also notify senior management if approvals are consistently delayed.
• Separate Duties: Strictly enforce Segregation of Duties (SoD) by ensuring no one can approve their own requests through the system’s setup.

Problem 2: Confusing Expense vs. Asset vs. Prepaid Costs

The Issue: Expenses are frequently categorized wrongly when first entered into the system. High-value items that should be treated as assets (and depreciated over time) are immediately recorded as expenses, while long-term service contracts are incorrectly booked as a one-time expense in the current month. This creates a distorted picture of both profitability and the company’s actual assets.

Why It Happens: This confusion usually comes from non-finance staff who initiate purchases not fully understanding accounting rules. Your company’s Chart of Accounts (COA) might be poorly designed or too complicated, leading to guesswork. Also, the focus is often on simply “getting the invoice paid fast,” overlooking the need for proper accounting. Crucially, the ERP system might not be configured to guide users to the correct accounting treatment for different items or purchasing categories.

How It Hurts You: The impact on your financial statements is severe and violates core accounting principles under IFRS and SOCPA. Immediately expensing a capital item makes current profit look lower and understates the value of assets (going against IAS 16 for Property, Plant, and Equipment). On the flip side, counting a routine operating expense as an asset inflates profit and overstates assets. Treating a year-long prepaid contract as a single-month expense severely understates profit in the first month and overstates it for the next eleven. These errors can lead to audit flags and a loss of investor confidence.

The Solution: Your ERP must be set up to enforce accounting rules right when a transaction begins. This involves several layers of control:

• Smart Item Categories: Define purchasing categories or item masters within the ERP and link them to default accounting rules. For example, a “Computer Hardware” category can automatically link to an ‘IT Assets Under Construction’ General Ledger (GL) account, while a “Software Subscription” category can default to a ‘Prepaid Expenses’ account.
• Automated Capitalization Limits: Set a clear capitalization threshold in your ERP based on company policy. The system can automatically flag any single purchase line item above this amount, pausing the transaction and sending it to a fixed asset accountant for review before it can be posted as an expense.
• Automatic Amortization: For prepaid expenses, instead of tracking manually in spreadsheets, use the ERP’s “Prepaid Contracts” or “Amortization Schedule” features. When an invoice for a prepaid service is recorded against its contract, the system automatically creates all future monthly journal entries to correctly spread the expense over its useful life. This eliminates human error and ensures you follow the matching principle.
• Restricted GL Access: Prevent data entry clerks and general requesters from directly choosing GL expense accounts. They should only be able to select from a pre-approved list of purchasing categories that have the correct accounting treatment already built in by the finance team.

Problem 3: Missing Out on VAT Recovery

The Issue: Your organization consistently fails to claim the full amount of eligible input VAT on its purchases and operating expenses. This isn’t a temporary delay; it’s a permanent and irreversible loss of cash that directly hits your profits.

Why It Happens: The main reason is a breakdown in discipline when capturing invoices. Employees and even Accounts Payable (AP) staff may not know ZATCA’s strict requirements for what makes an invoice valid for tax purposes. Paper invoices get lost, or data is entered incorrectly into the ERP (e.g., wrong supplier Tax Registration Number (TRN), missing invoice dates). The ERP itself might not be set up to enforce these validation rules, allowing incorrect data to sneak in. There’s also often confusion in applying the correct tax codes for standard-rated, zero-rated, and exempt supplies.

How It Hurts You: This directly reduces your profitability. Every Saudi Riyal of unclaimed input VAT becomes a non-deductible cost, effectively raising the purchase price of goods and services. This directly eats into your margins. Moreover, submitting VAT returns with inaccurate or incomplete data can attract scrutiny and potential fines from ZATCA. Over time, these small, transaction-level losses add up to a significant negative impact on your cash flow.

The Solution: A strong, ERP-centric process is vital to maximize VAT recovery. The focus is on preventing errors and validating data right when it’s entered:

• ZATCA-Compliant Tax Engine: Your ERP’s tax module must be configured with all the specific tax codes, rates, and rules applicable in Saudi Arabia. This ensures consistent and accurate VAT calculation based on the nature of the supply.
• Mandatory Field Enforcement: When entering supplier invoices, the ERP must require fields like the Supplier’s TRN, tax invoice number, and invoice date. The system should also check the TRN format to catch simple data entry mistakes.
• Automated Data Capture and Validation: If possible, use Optical Character Recognition (OCR) solutions that connect with your ERP. These tools can scan PDF invoices, automatically extract VAT data, and validate it against your ERP’s master data, drastically reducing manual errors.
• Prevent Duplicate Invoices: The ERP’s AP module must have strong duplicate-checking logic, typically based on a combination of supplier number, invoice number, and date. This prevents the common error of paying an invoice twice and incorrectly claiming VAT twice.
• Separate VAT Accounting: The system should automatically post the calculated input VAT to a dedicated “Input VAT Receivable” general ledger account. This separates the recoverable tax from the expense amount, providing a clear basis for reconciliation and filing.

Problem 4: Expenses Posted to the Wrong Departments

The Issue: Expenses are constantly misallocated, booked to generic “catch-all” accounts, or charged to the wrong department, project, or business unit. This makes your internal management reports misleading, hiding the true performance and profitability of each department.

Why It Happens: This is a classic data quality problem. Employees making purchases often don’t know the correct cost center code or understand why it’s important. The ERP system might be too flexible, allowing the use of a vague “General Admin” or “Unallocated” cost center as an easy default. For project work, if project codes aren’t consistently created and enforced, expenses meant for a specific initiative get lost in the general operational costs. Finally, shared service costs (like central IT support or office rent) are often not allocated in a consistent or logical way.

How It Hurts You: The consequences are strategic. Managerial profit and loss (P&L) reports become fiction, making it impossible to hold department heads accountable for their budgets or to accurately judge the profitability of a product line or business unit. One division might appear highly profitable simply because its costs were wrongly charged elsewhere. This leads to poor resource allocation, as investments might go to departments that only look good on paper. Over time, managers lose trust in the finance department’s data and might create their own “shadow” accounting systems in spreadsheets, creating organizational chaos.

The Solution: Your ERP must be configured to enforce a disciplined and logical system for allocating costs.

• Logical Cost Object Structure: Design a clear, hierarchical Cost Center structure within your ERP’s controlling module that matches your organizational chart. Add Profit Centers for business lines and Project Codes for specific initiatives.
• Mandatory Field & Validation: Make the ‘Cost Center’ (and ‘Project Code’ where applicable) a required field on all transaction screens, including purchase requests, invoice postings, and expense reports. No transaction should be allowed without this information.
• Contextual Validation Rules: Improve control by creating rules that link certain expense accounts to specific ranges of cost centers. For instance, a ‘Sales Commission’ expense should only be postable to cost centers within the ‘Sales’ department. This prevents illogical entries.
• Automated Cost Allocations: For shared costs, use the ERP’s cost allocation module. Define allocation cycles that run automatically at month-end. These cycles can distribute costs from a holding cost center (e.g., ‘Building Rent’) to operational cost centers based on predefined drivers like headcount, square footage, or revenue share, all managed within the ERP. This ensures consistency and auditability.

Problem 5: Late Accruals and End-of-Period Accounting Errors

The Issue: Expenses are often recorded only when a supplier invoice is received and processed, not when the service or goods are actually used. This violates the matching principle—a core rule of accrual accounting—and causes significant ups and downs in reported monthly profits.

Why It Happens: The main problem is relying too much on the supplier invoice as the signal for an accounting entry. Many organizations lack a clear process for finding and estimating expenses incurred but not yet invoiced. Accruals are often calculated manually in spreadsheets at month-end, a process prone to human error, omissions, and difficult to audit. Procurement and operations teams might not communicate effectively with finance about when work is completed or goods are received.

How It Hurts You: This practice directly distorts your financial performance. A company might use a lot of consulting services in March, but if the invoice arrives in April, March’s expenses are understated, and profits look artificially high. In April, the opposite happens, making performance seem worse than it was. This unevenness gives a false picture of the business’s stability. For auditors, poor cut-off procedures are a significant red flag, potentially leading to major adjustments and questioning the reliability of the entire financial closing process. It directly goes against IFRS and SOCPA principles.

The Solution: A modern ERP offers a systematic, automated solution through the “three-way match” process, shifting the trigger from the invoice date to the date value is received.

• Use Goods Receipt Notes (GRN): For every Purchase Order (PO), the process must require creating a Goods Receipt Note (GRN) or a Service Entry Sheet (SES) in the ERP the moment goods are received or services completed. This creates a time-stamped, system-based record of when the economic obligation began.
• Automated GRNI/Uninvoiced Receipts Report: At each month-end, the ERP can automatically generate a “Goods Received, Not Invoiced” (GRNI) report. This simply lists all GRNs/SESs that have been posted but don’t yet have a matching supplier invoice. The value is based on the PO price.
• System-Generated Accrual Entry: Configure the ERP to use the GRNI report to automatically create a period-end accrual journal entry. This entry debits the correct expense account and cost center (from the original PO) and credits a dedicated “Accrued Liabilities” or “GRNI Clearing” balance sheet account.
• Automated Reversal: The system should then be set to automatically reverse this accrual journal on the first day of the next period. When the actual supplier invoice is processed later, it will be posted as a normal AP transaction. This ensures the expense is recognized in the correct period, and the accrual reversal prevents it from being counted twice when the invoice is paid.

Problem 6: Poor Control Over Regular Payments and Subscriptions

The Issue: Your organization is losing money through ongoing payments for recurring services, especially Software-as-a-Service (SaaS) subscriptions, that are no longer needed, underused, or have auto-renewed without a proper review. There’s no central view or ownership of these commitments.

Why It Happens: This problem thrives in decentralized environments where individual departments or employees can sign up for services using corporate credit cards or simple online forms. There’s no central record of these recurring commitments. Unlike large capital purchases, these smaller, monthly or annual charges often go unnoticed by traditional procurement controls. No single function is tasked with tracking renewal dates and prompting a review of whether the service is still valuable.

How It Hurts You: The impact is a slow, silent drain on profitability. While each individual “zombie” expense might seem small, their combined value across a large organization can be substantial. It’s a direct waste of company funds that could be reinvested in value-adding activities. This uncontrolled spending makes accurate budgeting and cash flow forecasting nearly impossible, as these commitments are effectively hidden liabilities waiting to be paid.

The Solution: Your ERP can become a central hub for managing subscriptions, moving from a reactive payment system to a proactive control framework.

• Create a Subscription Master Record: Use the “Recurring Invoices,” “Standing Orders,” or “Outline Agreements” features within your ERP’s AP or Procurement modules. For every single recurring expense, create a master record. This record must capture key data: supplier, service description, monthly/annual cost, payment frequency, contract start and end dates, the GL account/cost center, and most importantly, a mandatory field for the “Business Owner” of the subscription.
• Proactive Renewal Workflow: Configure the ERP to automatically trigger a workflow well before the contract renewal or next payment date (e.g., 45-60 days prior). This workflow shouldn’t just generate a payment; it should create an approval task—a simple “Approve renewal?” request.
• Owner-Driven Approval: This approval task must be routed directly to the designated “Business Owner” in the master record. The system should prevent the renewal payment from being processed until that owner has explicitly reviewed the request and confirmed that the service is still needed and provides value. If the owner rejects it or doesn’t act, the process flags it for the procurement/finance team to initiate cancellation.

Problem 7: No Budget Tracking or Spending Oversight

The Issue: Expenses are processed in isolation. While they are captured and paid, there’s no pre-set budget or baseline to measure them against. As a result, management has no active control over spending and can only discover significant overruns after the fact, often during year-end closing when it’s too late to fix anything.

Why It Happens: This points to a major gap between strategic planning and daily operations. The annual budget is often seen as a static, one-time exercise done by the finance team in spreadsheets. This budget is never turned into an active control tool by being uploaded into the live ERP system. Consequently, department managers don’t really feel ownership of their budget, seeing it as a “finance number” rather than their own spending plan.

How It Hurts You: The lack of proactive budget control directly leads to uncontrolled spending and severe negative year-end financial surprises. It cripples the organization’s ability to manage costs ahead of time. When departments overspend without limits, funds for critical strategic projects might have to be cut to compensate. This not only puts growth plans at risk but also severely damages the credibility of the finance function, which is seen as unable to enforce financial discipline.

The Solution: Your ERP’s budgeting and controlling modules must be activated to turn the budget from a static document into a live, active control mechanism.

• Upload and Activate the Budget: The final, board-approved annual budget must be uploaded into the ERP. It should be broken down by the same categories used for transactions: by GL account, cost center, and time period (ideally monthly).
• Configure Budgetary Control: This is the most critical step. The ERP’s budget control function can be set up in two main ways:
  • Hard Stop (Preventive Control): The system checks available budget in real-time when a purchase request is submitted. If the commitment exceeds the available funds for that specific cost center/expense account, the system blocks the transaction from proceeding until a formal, approved budget transfer is made.
  • Soft Stop (Detective Control): A less restrictive option where the system allows the transaction to proceed but automatically sends a warning notification to the cost center owner, their manager, and the FP&A team, flagging the impending overspend.
• Enable Self-Service Reporting: The greatest benefit comes when department managers are empowered. The ERP should provide them with real-time, on-demand dashboards and reports. A manager should be able to log in at any time and see their budget, actual spending, and open commitments (from approved POs), giving them full ownership and the ability to manage their costs proactively.

Your 12-Week Plan to Better Expense Control

The 85/15 Rule: Automation vs. Human Oversight

A well-designed ERP system automates most rule-based tasks, freeing up human attention for important exceptions and analysis. This 85/15 split is a practical target for an advanced expense management process.

Key Indicators for Excellent Expense Management

• Expense Processing Time: The average number of days from expense submission to its final payment confirmation. A consistently low number shows an efficient, smooth process. Target: less than 10 business days.
• First-Time-Right (FTR) Rate: The percentage of expense claims and purchase requests approved on their first submission without being rejected or sent back. A high FTR rate indicates clear policies and an easy-to-use system. Target: more than 90%.
• Policy Exception Rate: The percentage of all submitted expense transactions the system flags as being outside policy (e.g., over budget, non-preferred vendor). This directly measures how well policies are followed. Target: less than 5%.
• Input VAT Recovery Rate: The total value of input VAT successfully claimed and confirmed in the ZATCA return, as a percentage of the total potential input VAT recorded on all supplier invoices. This directly measures cash recovery. Target: more than 99.5%.
• Month-End Close Accuracy: The value of manual journal entries needed to fix expense classification, allocation, or accruals after the initial closing, as a percentage of total operating expenses. Target: less than 1%.
• Budget Adherence: The percentage of all cost centers operating within an acceptable range (e.g., +/- 5%) of their year-to-date budget. This is the ultimate measure of proactive financial control. Target: more than 95%.

Common Questions Answered

Ultimately, transforming how you manage expenses by fully using a modern ERP is not just an IT project or a finance-only task; it’s a critical step for building a strong and transparent company. It moves your organization away from reactive, manual processes that create risks and lost profits. It builds a unified system that offers real-time visibility, proactive control, and trustworthy data. This foundation of financial integrity empowers leaders not only to confidently protect the bottom line but also to allocate capital more effectively for future growth.