Insights

Operating Expense Reporting: Budget, Run Rate, and BigQuery Model

Operating expense reporting guide for budget vs actuals, run rate, department spend, vendor detail, FP&A forecasting, and BigQuery models finance can trust.

Operating expense reporting shows whether the business is spending in line with its plan, current forecast, and operating priorities.

That sounds like basic finance work until the company starts growing.

More departments appear. Headcount changes quickly. Software vendors multiply. Contractors move in and out of the cost base. Payroll, prepaid expenses, credit card spend, accruals, and reclasses all affect the monthly view. Leaders ask for budget versus actuals, run rate, vendor detail, department accountability, and forecast impact, often before finance has finished reconciling the close.

The result is familiar: finance can produce a profit and loss statement, but leadership still does not have a clean answer to a practical question.

Are operating expenses under control, or are we only finding out after the fact?

Good operating expense reporting helps CFOs, founders, COOs, department leaders, and board members see the cost structure of the business clearly enough to make decisions. It separates accounting categories from management views, distinguishes recurring spend from one-time items, shows which owners drive each cost, and ties variance explanations back to source data.

It is not just a dashboard problem. It is a reporting model problem.

What operating expense reporting should do

Operating expense reporting should explain the cost of running the business.

For a growing company, that usually means answering questions like:

• Are we spending above or below budget?
• Which departments are driving the variance?
• Is the variance caused by timing, hiring, vendors, usage, reclasses, or a real change in the operating model?
• Which expenses are recurring versus one-time?
• Which vendors are growing fastest?
• Is payroll cost aligned with the headcount plan?
• Which costs should affect forecast, cash planning, or board reporting?
• Which numbers are accounting-approved versus directional?

Those questions are different from simply listing expense accounts.

A chart of accounts is necessary, but it is rarely enough for leadership reporting. Leaders usually think in terms of teams, owners, initiatives, vendor commitments, hiring plans, and business tradeoffs. Operating expense reporting needs to connect the accounting view to that management view without losing reconciliation discipline.

If operating expense appears on the finance leadership dashboard, its definitions should align with the broader CFO dashboard requirements. Otherwise, finance may end up with one version of expense reporting in the dashboard, another in the board deck, and another in the monthly close package.

Why operating expense reporting gets harder

Operating expense reporting usually becomes difficult when the company moves beyond a simple owner-managed cost base.

Early on, the founder, bookkeeper, or finance lead may know most expenses by memory. A quick accounting report and a few notes may be enough.

That changes when the business adds:

• multiple departments
• managers with budget ownership
• more software and subscription vendors
• outside contractors and agencies
• payroll complexity
• prepaid expenses and amortization
• accruals and reclasses
• corporate cards and expense reimbursements
• new locations, entities, or cost centers
• board or lender reporting requirements

The accounting system still records expenses, but leadership needs more context than the accounting system usually provides by default.

When card and reimbursement activity is material, the Ramp to BigQuery reporting guide covers how that spend can be modeled with employees, merchants, normalized vendors, departments, approvals, cash timing, and accounting sync status before it feeds operating expense reporting.

When payroll cost is material, the Gusto to BigQuery reporting guide covers how payroll runs, employees, departments, labor cost, pay dates, benefits, taxes, and accounting mappings can be modeled before they feed operating expense reporting.

For example, software expense may be spread across several account names, paid by card, booked through AP, and owned by different departments. Payroll may be posted by account, but leadership wants to understand headcount cost by team, role, hiring cohort, or planned start date. Consulting spend may include one-time implementation work, temporary backfill, or recurring outsourced capacity.

If those distinctions are handled manually each month, the operating expense report will stay fragile.

Budget versus actual is the starting point

The first operating expense view most companies need is budget versus actual.

At minimum, the report should show:

• reporting period
• account or management category
• department or cost center
• owner
• budget
• actual expense
• variance amount
• variance percentage
• favorable or unfavorable flag
• explanation for material variances
• forecast impact
• reconciliation status

That structure lets finance move beyond "we are over budget" and explain what actually happened.

An expense variance can have many causes:

• a vendor invoice arrived earlier than expected
• a new hire started later than planned
• a prepaid expense was booked differently than budgeted
• a department used more software seats
• a contractor project expanded
• an accrual was missed in a prior period
• the budget used the wrong department mapping
• spend was approved but not reflected in the latest forecast

Those explanations need to be categorized. Otherwise, leadership sees a variance but cannot tell whether the business is overspending, timing shifted, or the reporting model needs cleanup.

The same discipline applies in forecast variance reporting. Budget variance and forecast variance are related, but they should not be blended casually.

Run rate needs careful definition

Run rate is one of the most useful and most abused operating expense metrics.

In practical terms, operating expense run rate estimates the current recurring cost base. It helps leadership understand what the business is spending now and what that implies if the cost structure continues.

But run rate becomes misleading when one-time, seasonal, delayed, prepaid, or accrual-related expenses are mixed into the calculation without labels.

Before reporting run rate, define:

• which expense categories are included
• whether payroll is based on actual payroll, active headcount, or planned headcount
• whether one-time projects are excluded
• whether annual prepaid expenses are normalized monthly
• whether accruals are included
• whether vendor commitments are included before invoice receipt
• whether the view is accounting-based, management-adjusted, or forecast-based

A clean operating expense report should usually separate actual expense, normalized run rate, and forecast expense.

Those views can sit side by side, but they answer different questions. Actual expense explains what was booked. Normalized run rate explains the current cost base. Forecast expense explains expected future spend.

When those views are blended into one number, the report loses trust quickly.

Department ownership matters

Operating expense reporting should make cost ownership visible.

That does not mean every expense needs to become a blame exercise. It means leadership should know which team can explain the spend and which owner can act on it.

Useful owner views may include:

• executive owner
• department
• cost center
• budget owner
• hiring manager
• vendor owner
• project or initiative owner
• approving manager

The owner structure should match how the company actually manages spending.

For some companies, department-level reporting is enough. Others need function, location, product line, customer segment, or project views. The key is to avoid a report where expenses are technically categorized but no one owns the explanation.

This is especially important when operating expense reporting feeds board materials. A board pack should not show expense variance that management cannot explain by owner, driver, and action. The broader board reporting pattern is covered in Board Reporting for Growing Companies.

Vendor detail explains the cost base

Expense categories show what type of spend occurred.

Vendor detail often explains why it occurred.

For many SMB and mid-market companies, vendor-level reporting is one of the fastest ways to make operating expense reporting more useful. It helps finance and leadership see:

• top vendors by monthly or annual spend
• new vendors added this period
• vendors with growing spend
• duplicate or overlapping tools
• annual renewals coming due
• software seat growth
• contractor and professional services concentration
• spend split across multiple departments
• vendors coded inconsistently in accounting

Vendor reporting also exposes data quality issues. The same vendor may appear under several names. A parent company may bill for several products. A credit card descriptor may not match the approved vendor name. A software renewal may be coded to a different account than the monthly subscription.

Those problems look small until leadership asks for a clear view of software spend, contractor spend, or vendor concentration.

The report should preserve both the accounting vendor and the normalized vendor where needed. Finance should be able to reconcile to the source system while leadership sees a cleaner management view.

Payroll and headcount need their own logic

Payroll is often the largest operating expense category.

It also has timing and ownership details that do not behave like vendor invoices.

A useful operating expense report may need to connect:

• payroll actuals
• active headcount
• planned hires
• start dates and termination dates
• departments and managers
• compensation type
• bonuses or commissions
• benefits and payroll taxes
• contractors and consultants
• capitalization or allocation rules where relevant

The important point is that payroll expense should not be treated as just another general ledger line if leadership needs to understand hiring capacity, department budget, or forecast risk.

For example, a department may appear under budget because hiring slipped. That is different from real cost savings. A company may appear over budget because commissions were earned earlier than expected. That is different from uncontrolled spending.

Operating expense reporting should make those distinctions visible.

Timing and accounting treatment can distort the story

Operating expense reports often lose trust because timing effects are not separated from real spending changes.

Common timing and accounting issues include:

• prepaid expenses booked upfront but budgeted monthly
• annual software renewals that distort one month
• late vendor bills
• accruals booked after department reports were prepared
• reclasses between cost centers or accounts
• expenses paid by card but not yet coded
• invoices approved in one period and posted in another
• payroll periods that do not align cleanly with calendar months
• contractor work performed before invoice receipt

None of these issues are unusual.

The reporting problem starts when they are invisible. Leadership may think spend is increasing, decreasing, or under control when the movement is mostly a timing artifact.

A strong report should identify whether a variance is caused by timing, true run-rate change, coding change, one-time spend, or forecast assumption.

That also reduces month-end reporting errors. If finance is repeatedly fixing the same timing and coding issues in spreadsheets, the process should be strengthened using the practices in How to Reduce Month-End Reporting Errors.

Operating expense and cash flow are connected but different

Operating expense reporting and cash flow reporting should be connected, but they should not be treated as the same report.

Operating expense reporting usually explains the cost structure of the business. Depending on the company, it may use accrual accounting, management groupings, normalized run rate, and forecast views.

Cash flow reporting explains when money actually leaves the business.

The difference matters.

A software subscription may be paid annually, expensed monthly, and forecast as a renewal commitment. A contractor may perform work in May, invoice in June, and get paid in July. Payroll may be earned in one period and paid in another. A prepaid expense may affect cash immediately but operating expense over time.

Leadership needs both views.

If the cash side is also difficult to explain, use the cash flow reporting guide as the companion model. The operating expense report should explain cost behavior. The cash report should explain payment timing and liquidity impact.

What the BigQuery model should include

BigQuery can support operating expense reporting when finance needs to connect accounting, payroll, AP, expenses, procurement, and forecast data in one reusable reporting layer.

The goal is not to copy the accounting system into another place and call it a warehouse.

The goal is to model expense reporting once so budget owners, finance, leadership, and board reporting can use consistent definitions.

For FP&A teams, operating expense is often one of the first models that belongs in a single source of truth for reporting. It connects general ledger actuals, budget owners, forecast versions, vendor mappings, and the monthly management reporting process before those numbers reach a dashboard or board pack.

A practical BigQuery model may include:

• general ledger transactions
• chart of accounts and management account mappings
• department, cost center, owner, and location dimensions
• vendor normalization tables
• AP bills and payment status
• corporate card and expense reimbursement data
• payroll actuals and headcount data
• budget and forecast versions
• prepaid expense and accrual schedules
• purchase orders or procurement approvals where relevant
• allocation rules with effective dates
• exception tables for missing owners, unmapped vendors, miscoded accounts, duplicate transactions, and late data
• reporting tables for department spend, budget variance, run rate, vendor detail, and board views

The model should preserve source-system traceability. Finance should be able to click from a management category back to the source transaction, vendor, department mapping, and adjustment rule.

For many teams, the service fit is BigQuery reporting automation, with BigQuery implementation when the source data, mappings, and reporting tables need to be built.

Reconciliation should be built in

Operating expense reporting needs reconciliation before leaders use it.

Useful checks include:

• modeled expense totals compared with the general ledger
• department totals compared with finance-approved reports
• vendor totals compared with AP or card data
• payroll totals compared with payroll system reports
• budget and forecast versions matched to the correct period
• transactions with missing department, owner, vendor, or account mappings
• expenses booked to suspense, uncategorized, or miscellaneous accounts
• prior-period changes after the report was published
• manual adjustments without owner or reason

These checks should be visible to finance.

The report does not need to pretend every source is perfect. It needs to show which exceptions remain before the numbers are used in leadership reporting.

This is the same reason a single source of truth for reporting should include definitions, ownership, and exception handling instead of only centralizing raw data.

Common mistakes to avoid

Mistake 1: treating the chart of accounts as the management report

The chart of accounts is essential, but it rarely matches how leadership manages the business.

Build management categories and department views deliberately, then reconcile them back to accounting.

Mistake 2: mixing actuals, run rate, and forecast

Actual expense, normalized run rate, and forecast expense answer different questions.

Show them separately. If one feeds another, make the rule explicit.

Mistake 3: hiding one-time and timing items

One-time projects, annual renewals, late invoices, accruals, reclasses, and prepaid expenses can distort the trend.

Label them so leaders do not mistake timing noise for structural cost change.

Mistake 4: leaving vendor cleanup until the board pack

Vendor detail is hard to fix at the last minute.

Normalize vendors, owners, and categories in the reporting model so finance is not manually rebuilding spend views before every leadership meeting.

Mistake 5: ignoring owner accountability

An expense report without owners is hard to act on.

Department and vendor ownership should be part of the model, not added manually in commentary after the report is complete.

A practical first phase

The first phase should focus on the expense questions leadership already asks repeatedly.

For many growing companies, a strong first version looks like this:

1. choose the operating expense categories leadership cares about
2. map those categories to accounting accounts
3. define department, cost center, and owner logic
4. load budget and forecast versions with clear period ownership
5. centralize GL, AP, payroll, expense, and vendor data where needed
6. separate actual expense, run rate, and forecast views
7. add variance categories and owner commentary
8. create exception checks for missing mappings and late data
9. publish concise finance, department, and leadership views

That scope is usually enough to make operating expense reporting more dependable without turning the work into a full finance systems redesign.

If the company already has monthly management reporting pressure, this model should support the workflow in How to Automate Monthly Management Reporting for Finance Teams. Finance should not have to rebuild operating expense logic separately for the close package, dashboard, forecast review, and board deck.

FAQ

What should operating expense reporting include?

Operating expense reporting should include budget versus actuals, run rate, forecast variance, department and owner views, vendor detail, recurring and one-time spend, headcount-related cost, timing adjustments, and reconciliation status.

Why does operating expense reporting become unreliable?

Operating expense reporting becomes unreliable when accounting categories, department ownership, vendor names, payroll timing, accruals, prepaid expenses, and spreadsheet adjustments are not modeled with consistent rules. The problem is usually the reporting foundation, not the chart.

How is operating expense reporting different from cash flow reporting?

Operating expense reporting explains the cost structure of running the business, usually on an accrual or management-reporting basis. Cash flow reporting explains when money actually leaves the business. Growing companies need both views connected but clearly separated.

Can BigQuery support operating expense reporting?

BigQuery can support operating expense reporting by centralizing accounting, payroll, AP, expense, procurement, and forecast data, then modeling department spend, budget variance, run rate, vendor detail, and reconciliation checks in reusable reporting tables.

How should FP&A teams model operating expense data?

FP&A teams should model operating expense data by separating actuals, budget, forecast, run rate, department ownership, vendor detail, one-time spend, and reconciliation checks. That lets leadership compare spend without rebuilding spreadsheet logic for each monthly review.

Final thought

Operating expense reporting should help leadership understand whether the company is spending deliberately.

That requires more than an accounting export and a dashboard. It requires stable categories, clear owners, visible timing adjustments, vendor detail, budget and forecast context, and reconciliation checks finance can defend.

When operating expense logic is modeled once and reused across finance, department, leadership, and board reporting, the monthly conversation gets sharper. The team spends less time debating where the numbers came from and more time deciding which spending choices actually support the business.