How CFOs Can Improve Visibility Into Company Spending
CFO spend visibility depends on coverage, context, trust, and action. A dashboard shows recorded transactions, but finance needs reliable records and clear decision rights to change spending outcomes.
This guide sets out seven steps CFOs can take to improve visibility into company spending. It also shows you how to identify workflow gaps and evaluate solutions based on your finance team’s operational needs.
What company spending includes
Company spending reaches finance through several channels, and each system records a different part of the process. Accounts payable (AP), procurement, payroll, and card platforms each capture part of the picture, but posted actuals live in the general ledger of the enterprise resource planning (ERP) system. Every other source has to reconcile to that ledger before finance can rely on it for reporting.
Mapping how the different spending sources fit together helps finance see what is included, what may be missing or delayed, or who owns each record:
- Employee spending: Expense reports, corporate cards, and travel bookings capture purchases employees make on the organization's behalf
- Vendor invoices: AP records supplier invoices and routes them through the organization's approval process
- Purchasing commitments: Procurement records orders and agreements before an invoice arrives
- Payroll: Payroll systems hold employee compensation and related payments
Together, these records show spending that a card feed alone cannot cover. Employee purchases need particular attention because the receipt and business purpose may arrive after the transaction, leaving the record incomplete until the expense is submitted.
Four things a CFO needs from any spend view
An effective spend view should provide four capabilities: coverage, context, trust and action. In practice, that means showing what spending is included, explaining what each amount means, presenting records finance can trust, and making clear who has authority to act.
Assess each spending view against these four capabilities:
| Capability | Information that finance needs | Consequence of a gap |
|---|---|---|
| Coverage | Sources, entities, and systems included in the view | Finance cannot assess spending that never enters the records |
| Context | Business purpose, policy result, budget owner, entity, and account | Reviewers cannot judge a transaction without its business context |
| Trust | Complete records, reconciliation status, source timestamps, and consistent coding | Conflicting records undermine budget and accounting decisions |
| Action | Authority to investigate, enforce policy, correct records, and assign responsibility | An identified exception remains unresolved without an accountable owner |
A useful view connects each amount to its meaning, status, and next decision. That clarity becomes harder to achieve when spending records, and the people responsible for acting on them, are spread across different systems or departments.
Among CFOs of North American companies with at least $1 billion in revenue, 46% cited siloed departments or autonomous business units as their top internal cost-management challenge in early 2026, reinforcing the need for spend visibility to cross entity and departmental lines rather than stop at one team's system.
- A separate survey of 1,434 CFOs and senior finance leaders across 26 countries found that 48% prioritized real-time financial data and insights for the business. Faster access supports a spending decision only when the records carry the context and controls that decision requires.
Why a fuller dashboard still leaves CFOs guessing
Consider a $2,300 hotel stay in Frankfurt. The corporate card feed shows the amount, but the information finance needs develops over several stages:
- Documentation: The receipt arrives a week later without a business purpose
- Approval: A manager approves the expense from a phone
- Accounting: The expense posts under the US entity, while the traveler works for the German subsidiary
The amount remains visible on the dashboard throughout the process , yet finance still needs to establish whether the cost was appropriate, correctly allocated, fully reconciled, or awaiting action.
Why a visible transaction may still require work:
| Area | What a dashboard can display | What finance still needs |
|---|---|---|
| Visibility and control | Spending after a purchase | A policy rule or approval opportunity before or during the purchase |
| Transaction visibility and financial accuracy | A card charge | The correct account, entity, period, and currency |
| Totals and actionable information | Spending by category | A reason, owner, and next step for each exception |
| Real-time feeds and validated records | An authorization amount | A receipt, business purpose, and completed policy review |
| Approval and accounting completion | An approved expense | Separate posting, payment, and reconciliation statuses |
| Consolidated reporting and entity correctness | A group total | Correct entity amounts, since allocation errors can offset |
| Historical reporting and intervention | A month-end report | Information early enough to change a decision |
The same principle applies to tax substantiation: an approved expense can still fail a tax, accounting, payment, or control test.
Under IRS guidance for the 2025 tax year, travelers using the standard meal allowance must keep records proving the time, place, and business purpose of their travel. If a receipt is without a recorded business purpose, finance should resolve that gap before treating the expense as complete.
Where visibility breaks and how to repair it
When visibility breaks down, the right fix depends on what went wrong. Missing transactions require a different response from incorrect coding or failed accounting transfers; adding more data to a r dashboard will not resolve those underlying problems.
The table below links each gap to its consequence, the action needed to fix it, and the owner responsible for tracking whether the fix worked:
| Gap and cause | Business consequence | Repair | Owner and measure |
|---|---|---|---|
| Card spending appears late because feeds or receipts arrive after purchase | Budget owners see overruns only after the spending decision | Capture card authorizations and request supporting details promptly | Controller: median time from purchase to finance visibility |
| Expenses lack a business purpose because employees add context later | Reviewers lack the information needed to assess the expense | Require decision-relevant fields at submission | Controller: percentage of expenses complete at submission |
| Categories differ because entities use inconsistent mappings | Finance must reclassify spending before comparing totals | Maintain shared categories and document local mappings | Controller and financial planning and analysis (FP&A): postings requiring manual correction |
| Approved items remain unposted because a transfer fail | Ledger balances omit approved activity | Queue failed postings and investigate each mismatch. | Finance systems lead: number , value, and age of approved but unposted items |
| Entity or currency details are missing or incorrect because of manual entry or stale organizational data | Entity expenses, tax treatment, and related reporting can be misstated | Use current HR and ERP data, apply the allocation policy at review, and source exchange rates from a defined system | Corporate controller and tax owner: entity pr currency reclassifications per close |
| Possible duplicates and policy breaches surface only after payment | Finance must recover payments, and the same leakage may recur | Flag possible duplicates and policy breaches before payment , then prioritize review by risk and amount | Finance operations and internal audit: median age of open exceptions |
| Systems show conflicting amounts or statuses because no system owns each financial state | Finance cannot determine which record should guide a decision | Define the governing system and reconciliation process for each financial state | CFO and finance systems lead: unresolved differences and their age |
Each owner should record the current level of the problem, then check it again after the repair to see whether the fix worked.
For example, a provisional card amount can change when the charge posts. Reconciling each card charge against its receipt and accounting record during the period helps finance catch changes before close. Matching related records can also reveal a purchase represented by both a card charge and a reimbursement claim.
Finance operations should distinguish three exception types:
- Missing information: Return the expense to the employee for the receipt or business purpose needed for review
- Possible duplication: Compare the merchant, date, amount, and supporting documents before approving reimbursement
- Failed posting: Have the finance systems owner establish whether the ledger received the record before retrying the transfer
Together, these responses help finance resolve incomplete, duplicated or misposted spending while the details are still available.
Earlier review also matters when an exception may point to irregular spending. Among 1,921 occupational fraud cases investigated in 138 countries and territories between January 2022 and September 2023, expense reimbursement schemes made up 13%. Those schemes had a $50,000 median loss and typically ran 18 months before detection. Across all fraud types, schemes uncovered through active detection had shorter durations and lower median losses than those detected passively. B
A seven-step sequence for CFOs
You can improve visibility without replacing every spending system. The sequence begins with the sources that matter to the organization's decisions. Shared definitions and clear ownership then support capture, exception handling, and reconciliation.
These seven steps turn those requirements into a repeatable process:
- Map material spending sources: List each channel by annual spending and record owner, then identify which sources reach a report that finance can reconcile
- Set shared categories, owners, and fields: Define the categories, budget owners, and fields used across systems, including entity, currency, and project
- Capture context at submission: Require employees to provide the receipt and business purpose before submitting an expense for review
- Define ownership of each financial state: Document who is responsible for authorization, expense approval, ledger posting, and settlement, as well as how conflicting records are resolved
- Surface exceptions early: Route missing information, potential duplicates, policy exceptions, and failed postings to named reviewers before approval or payment, prioritizing each queue by risk and amount
- Reconcile during the period: Match approved items with posted entries on an agreed schedule and queue each mismatch with an owner and track how long it remains unresolved
- Measure whether visibility is improving: Track submission completeness, visibility delay, exception resolution time, and approved but unposted items using consistent definitions and reporting periods
What finance needs to resolve for visibility to work
Even a well-designed spend process can break if the data and handoffs around it are not maintained. A stale manager record or retired cost center can therefore undermine a newly configured workflow. Resolve these dependencies before activating the affected routes or mappings.
Finance needs to make four practical decisions as it configures the process:
- Employee effort: Ensure reviewers get the context they need without asking employees to re-enter information already available in connected systems
- Review capacity: Rank exceptions by risk and amount, and assign capacity before introducing additional checks
- Provisional amounts: Treat card authorizations as estimates until the final charge posts
- Control ownership: Keep posted accounting entries in the ERP while AP, procurement, payroll, card and payment systems manage their respective tasks.
Together, these choices let the systems work together while keeping each system’s responsibilities clear.
How automation, AI, and people share the work
Automation and AI can both reduce manual work but they perform different jobs within an expense workflow. Automation follows rules finance has defined, such as routing an expense above a set amount for approval. AI uses available data to extract, match, classify or flag information, such as identifying a merchant on a receipt or spotting an unusual transaction.
Finance must define in its policy and workflow which tasks can proceed automatically and which require human judgment.
Separate the functions before assigning decision rights:
- Policy rules: Apply configured requirements, such as a spending limit or required receipt, and route exceptions through the authorized approval process
- Receipt extraction: Extract merchant, date, and amount from the receipt, and send unreadable or uncertain results to a reviewer
- Transaction matching: Compare receipt details with the related card transaction before it affects reimbursement or reconciliation
- Anomaly detection: Rank unusual records for investigation without treating an unusual expense as proof of misconduct
- Human judgment: Keep policy exceptions and fraud referrals with the people authorized to make those decisions
The boundary between an AI recommendation and decision-making authority matters: an AI output is a recommendation or flag, not permission to approve, pay or post.
A useful flag should tell the reviewer why it was raised, such as a hotel rate exceeding the applicable city limit. While the National Institute of Standards and Technology identifies explainability and accountability as characteristics of trustworthy AI, a clear explanation does not guarantee a correct result. Finance needs to assess three things separately: whether the result is correct, whether the reason is understandable, and whether the decision can be audited.
Finance operations should retain the evidence needed to reconstruct decisions that affect reimbursement, payment or posting:
- Inputs and outputs: Record the relevant source information, model result, and applicable policy
- Actions and overrides: Identify who approved, returned, or changed the decision, with the reason and timestamp
- Review outcomes: Track overturned flags and unresolved exceptions before changing detection or routing rules
Deloitte’s survey points to a practical boundary: 77% of finance leaders were comfortable with agentic solutions making some autonomous decisions, only 14% felt the same about more critical decisions. For expense workflows, that means letting automation handle defined, lower-risk tasks while maintaining strong human oversight for higher-risk activities such as regulatory reporting and tax.
How the requirements change with scale
The workflow requirements will not look the same for every organisation. Transaction volume changes review capacity, while organizational variation increase the number of mappings, owners and reconciliations finance must manage. . These differences make complexity a better guide than headcount when deciding which controls an expense operation needs.
Assess the complexity of the expense operation across four dimensions:
- Volume: Match automation and reviewer capacity according to transaction and exception workloads
- Organizational variation: Define common policy rules and identify the entity or business-unit exceptions that require separate ownership
- International operations: Retain original currency amounts and apply the relevant accounting and tax treatment to each jurisdiction
- Connected systems: Document field mappings and reconcile transfers when a new system joins the workflow
How to evaluate any spend visibility solution
With the operating model defined, turn it into a vendor test. Evaluate the operating problem before comparing product features. Ask each provider to demonstrate both a successful transaction and an exception using your organisation’s requirements.
Ask each provider to demonstrate these capabilities using these requirements:
- Source coverage: Show which spending channels and entities connect directly, and identify any connector or manual-upload dependency
- Transaction context: Show when the employee supplies a receipt and business purpose, and what happens when either is missing
- Record status: Distinguish provisional amounts, approved expenses, and ledger entries in the same workflow
- Failed transfers: Demonstrate how finance detects an unsuccessful ERP posting and who can correct or retry it
- Policy variation: Show who maintains rules that differ by entity, role, or region.
- AI review: Explain what triggers a flag, whether a confidence level is shown, and which actions require human approval
- Audit evidence: Export a sample decision history in the format that the organization's auditors need
These demonstrations show whether the solution can resolve the visibility problem you identified, rather than display more transactions.
Next steps
Request a demo to see how Embure can help you make faster, better-informed decisions about spend, using the processes and systems your team already relies on.
Frequently asked questions
Spend visibility shows finance what was spent, by whom, and where. Spend control applies a rule before or during the spend.
Visibility without control reports problems after the money has moved. Control without visibility leaves finance unable to tell whether the rules are working. You need both to know whether spending follows policy and where action is required.
No, a connected spending view can retain the ERP as the ledger.
Finance must define which system owns each record and reconcile the information that flows between them.
They may represent different stages of the same purchase. An authorisation, posted card charge, approved expense, and ledger entry can be created or updated at different times.
Check whether the difference relates to:
- Documentation: A receipt or business purpose is still missing
- Approval: The expense is still awaiting a decision
- Coding: Accounting fields are incomplete or incorrect
- Transfer: An accounting integration failed
- Amount: The posted charge differs from original authorization
Reconcile these records during the period and assign each unresolved difference a named owner and an age.
Measure whether finance receives usable records earlier and whether unresolved exceptions are declining under consistent definitions.
Useful measures include:
- Completeness: The share of submissions with the required supporting information
- Visibility delay: The time from purchase to the first usable finance record
- Exception resolution: The number and age of unresolved items, and the time taken to close them
- Posting status: The count and age of approved expenses that have not reached the ledger
Keep recovered amounts and entity reclassification effort separate from these operating measures.
Yes, AI can extract information, suggest clarifications, and flag potential problems for review without making the final decision.
Assign each AI function a defined review step:
- Receipt extraction: Areviewer checks extracted details against the receipt
- Classification: Low-confidence suggestions go to a person
- Risk ranking: Each flag states its reason, helping reviewers prioritize higher risk items
The audit trail should record what the system evaluated, what it recommended, and what the authorized reviewer decided.
No, our expense products focus on employee spending rather than all company spending.
AP automation for supplier invoices is a separate Emburse offering, and none of these products replace procurement, payroll, or the ERP.