Numeric Reporting: 8 Reports Your Accounting Team Needs

Nigel Sapp
|
Published:
December 9, 2025
|
Updated:
October 15, 2026

Table of contents

See Numeric in action
Schedule a demo

When the CFO asks how much R&D spent on AWS last quarter, the answer lives in a report someone has to build.

The ability of an accounting team to produce timely, relevant reports that execs care to read is what earns it a seat in strategy conversations.

Reporting is one of the most common reasons teams choose Numeric. Josh Goldberg, Accounting Manager at Masterworks states that Numeric’s reporting is his favorite feature in the platform:

“It’s like having a real live dynamic pivot table with analysis that can be refreshed in real-time.” 

Here’s a look at the types of reports teams actually use in Numeric today.

Why Reports Matter More Than Ever

Reports matter more than ever because finance teams no longer simply “close the books”. Today, teams are expected to produce analysis that can inform strategy, quantify tradeoffs, and highlight risk. The presence of good reporting is also a sign of good close maturity.

And to add, building good reports is still often much easier said than done. Between lackluster and rigid ERP-native reporting tools, expensive BI tools that smaller companies may lack resources for, a dizzying array of Excel sheets, and most of all, data that lost its context the moment it became a journal entry, finance teams struggle to get the slices of data that fuel business direction.

Reporting in Numeric

Numeric's reporting is built so the CFO's AWS question gets answered without waiting on a NetSuite admin or exporting to a separate BI tool.

Most of what limits reporting comes from the ERP itself. A traditional ERP was built to store journal entries, not the context behind them, so reporting stays capped by whatever detail the ERP kept: trial-balance-level for tools like Sage or QuickBooks, transaction-level for something like NetSuite. That's why teams end up maintaining the same pivot table in Excel every month, or paying for a separate BI tool just to see a number sliced a new way.

An ERP replacement removes that limit. Numeric's Financial Data Platform (FDP) keeps every business event connected to its full context instead of flattening it into a journal entry, so reports can run at the object level across all of a team's data instead of whatever slice the ERP happened to keep.

That flexibility comes from how the FDP handles dimensions. A traditional general ledger forces a team to decide how a number will be sliced before the data even exists, locked into a fixed chart of accounts. On the FDP, tags for department, vendor, project, region, or anything else a team wants to track can be added to a business event at any time, without touching the accounting itself, and a Virtual Chart of Accounts lets a team define as many reporting views as it needs and apply any of them across all of its historical data. The result is a report that can be cut on any dimension a team cares about, not just the ones the chart of accounts happened to anticipate.

When an agent builds a report on the FDP, it turns the request into a deterministic query, so the report returns the same number every time it runs, and any figure can be traced back to the source record that produced it.

The eight reports below are ones teams build in Numeric today. Where the FDP changes how a report works, we've called it out.

Before Numeric, Michael Hoopes, an accountant at Parafin, would spend “quite literally 8 hours” building reports in NetSuite. Now, with Numeric, he can “jump into Numeric and immediately manipulate the same style of reports.”

With Numeric’s reporting, teams can accomplish the following:

  • Build diverse reports to support management, audit, legal, and financial inquiries and then save them for easy end-of-month retrieval
  • Run agentic flux analysis on any individual account in their GL and any line item in their reports
  • Pivot on any field and drill down into transactions from their GL to produce answers in minutes, instead of working it out in Excel

Excel is still the most flexible tool many teams have, and the report builder keeps that pivot-anything flexibility while staying connected to the GL.

Using Numeric’s AI Report Builder

__wf_reserved_inherit
Here, we prompted the Report Building Agent to create an expense report broken out by department and vendor.

When the CFO sends a quick ask, the Report Building Agent can draft the report for you.

Our Report Building Agent allows you to spin up reports with ease. Simply describe the outcome you want and an agent configures the report for you, adding filters, updating metrics, and restructuring report layout in real-time.

To test it out:

  1. Open the Reporting module
  2. Create a report with "Add Report" or select an existing one
  3. Hit "AI Assistant" in the top-right corner and begin prompting
  4. If you want to see the agent in action, open the Editor in the top-right corner and watch it modify the report as you chat.
  5. After each response, the AI agent will give you the option to Keep or Undo your changes, so you're always in control. 

Curious about what to ask? Try prompts like “How should I group my income statement?” or "What reports should I build for a board meeting?" and let the AI guide you.

How to Build a Report in Numeric

The report builder in Numeric is designed for flexibility, allowing finance teams to create both one-off analyses and recurring Flux reports directly integrated with their NetSuite data.

The initial set-up is fairly simple: 

  1. Teams can add basic details about what timeframes to preview, select the statement type (Income Statement or Balance Sheet), and then state if the report should be for individual subsidiaries or consolidated. 
  2. From there, one can select which prior periods to include for comparison and if they’d like to include variance columns.

Where Numeric’s report builder shines is in its ability to offer granular control over your financial data. With filters, grouping, and metric rows, teams can generate finely tuned reports across their data.

  • Filters: Apply report-wide filters based on ERP attributes like Department, Class, Location, or specific Accounts. For efficiency, you can create "Saved Filters" (e.g., "G&A OPEX") to apply standard logic across multiple reports.
  • Grouping: You can organize accounts into custom groups using Static conditions (manual selection) or Dynamic conditions (rules-based).
  1. Dynamic Grouping: This is highly recommended for scalability. By setting a rule (e.g., "Account Code starts with 4"), new accounts added to NetSuite that match this criteria will automatically appear in the report without manual updates.
  • Metric Rows: Create calculated rows to derive specific KPIs, such as a "Profit" row created by subtracting an Expense group from a Revenue group.

As a final note, any new report is Ad-Hoc. You can set new reports to recur, and once you do, they become part of the Flux Analysis module, allowing you to use AI-generated explanations, add manual notes, and assign review tasks.

Interested in data-centric accounting? Read the whitepaper on the architecture behind Numeric's ERP replacement.

Read the whitepaper

8 Reports Your Team Can Build Today 

Below are eight of the most common reports accounting teams build in Numeric, organized by use case. Each includes the reporting logic needed to build it and the business context for when to use it.

💼 Management & FP&A Reporting

Expense by Department + Vendor

How It Works:

This report groups all expense transactions first by department (e.g., G&A, R&D, S&M), then breaks down spend within each department by vendor. 

How to Build:

  1. Filter to expense accounts only (OPEX + COGS account types)
  2. Pivot by Department first, then add Vendor as a secondary pivot
  3. Configure for your desired comparison period (typically MoM or QoQ)
  4. Optional: Add variance columns to track changes period-over-period

Why It’s Useful:

This report is essential for understanding departmental burn rates and vendor concentration.

Finance teams use it to answer questions like "How much is R&D spending on AWS?" or "Which vendors are we using across multiple departments?" It's particularly valuable during budget reviews, vendor negotiations, and when leadership asks "Where is our money going?"

The team at STASH uses this report to track spend on key vendors like AWS.

Adjusted EBITDA

How It Works:

This report builds a bridge from Net Income to EBITDA to Adjusted EBITDA by creating calculated metric rows that add back non-operating expenses. The report structure shows your standard income statement flowing to Net Income, then systematically adds back interest, taxes, depreciation, and amortization to arrive at EBITDA. From there, you add back one-time or non-recurring expenses (like legal fees, restructuring costs, or stock-based compensation) to calculate Adjusted EBITDA.

How to Build:

  1. Start with your standard I/S structure flowing through to Net Income
  2. Create metric rows to add back D&A, taxes, and interest to calculate EBITDA
  3. Create groups for adjustment categories (Legal Expenses, One-time Costs, Stock Comp, etc.)
  4. Build final metric row for Adjusted EBITDA that sums EBITDA + all adjustments
  5. Configure comparison periods to show the bridge calculation across time

Why It's Useful:

Adjusted EBITDA is the metric investors and boards use to evaluate operating performance by stripping out non-cash expenses and one-time costs. This report is critical for board presentations, investor updates, and debt covenant compliance where lenders often tie requirements to Adjusted EBITDA thresholds.

In Numeric, custom groupings and in-report reconciliation let you show the walk from Net Income through each adjustment layer. Instead of maintaining complex Excel reconciliations that break when your chart of accounts changes, this report automatically recalculates as transactions flow through. 

Income Statement with Functional Expense Disaggregation

How It Works:

This report displays your standard income statement structure (Revenue → COGS → Gross Profit → OPEX → Net Income) but breaks out operating expenses by functional expenses like G&A, R&D, and S&M. Some teams include a "No Department" line item that flags any transactions missing department coding.

Note: If you set up this structure and see “No Department” appear in a report even once, then create a Monitor that flags the relevant data issue. Doing so will ensure you catch data issues before they appear in a report. 

How to Build:

  1. Start with your standard income statement account structure
  2. Add department as a grouping specifically for the OPEX section
  3. Configure your department groupings to match your reporting structure (typically G&A, R&D, S&M)
  4. Add a condition to capture and display transactions where department is empty
  5. Set formatting to show both current period and prior period columns for variance analysis

Why It’s Useful:

Leadership and board members expect to see expenses broken out by functional area to understand the cost structure of the business - how much you're investing in product development versus sales versus keeping the lights on.

The "No Department" check serves as a data quality control, ensuring you catch miscoded transactions before they distort departmental metrics. This report is typically used in monthly board decks, budget vs. actual reviews, and when calculating unit economics like CAC or LTV where you need clean departmental expense allocation.

Income Statement with Natural Expense Disaggregation

How It Works:

This report displays your income statement with operating expenses broken out by natural expense classification - the type of expense (salaries and wages, rent, software, professional fees, insurance, depreciation, etc.) rather than functional areas. Unlike functional expenses which are typically tagged at the transaction level in fields like "Department," natural expenses require grouping entire GL accounts or specific slices of accounts based on what the expense actually represents.

How to Build:

  1. Start with your standard income statement account structure
  2. Create custom groups for each natural expense category (Compensation & Benefits, Occupancy Costs, Professional Services, Software & Technology, etc.)
  3. Use dynamic filters within each group to capture relevant GL accounts - for example, the Compensation group might include accounts 6000-6999, or use "Account Name contains 'Salary'" logic
  4. Apply additional filters if needed to slice accounts by Class, Department, or other dimensions when a single GL contains mixed natural expense types
  5. Reorder groups to present natural expenses in a logical flow for your audience

Why It’s Useful:

Natural expense classification is increasingly required for financial statement disclosures, and is becoming more common in investor reporting where stakeholders want to understand the composition of expenses rather than just departmental allocation.

The challenge with natural expenses is that they don't map cleanly to standard ERP fields - your "Salaries" might span 20 different GL accounts across multiple departments. 

Numeric's grouping capabilities let you define the logic once (using dynamic rules like account code ranges or account name patterns) and the report automatically includes new accounts that match your criteria. This eliminates the monthly Excel gymnastics of manually categorizing accounts and ensures your natural expense disclosures stay accurate as your chart of accounts evolves.

The FDP's Virtual Chart of Accounts goes a step further. Natural classification becomes its own reporting view, defined once and applied across all historical data, while the functional view stays exactly as it is.

For companies that need both functional AND natural expense views, you can build complementary reports - one showing the traditional departmental breakout, another showing natural classification.

OPEX by GL Account + Vendor

How It Works:

This report drills into operating expenses at the most granular level, showing each expense account (e.g., Software - SaaS, Travel, Professional Services) and then breaking down every vendor within that account. It's a detailed spend analysis that answers "who are we paying for what?"

How to Build:

  1. Filter to OPEX account types only (exclude COGS and revenue)
  2. Pivot by Account first to see each expense GL account
  3. Add Vendor as a secondary pivot to show vendor breakdown within each account
  4. Configure date range for the analysis period
  5. Optional: Add variance columns to identify month-over-month or year-over-year spending changes

Why It's Useful:

Controllers use this report for deep vendor spend analysis, particularly during procurement reviews, contract renewals, or when trying to identify cost savings opportunities.

If you're evaluating whether you're overpaying for software, have vendor sprawl, or need to consolidate contracts, this report surfaces those answers. It's also valuable during audits when you need to explain specific vendor relationships or during budget planning when you're forecasting category-level expenses.

See why Built replaced NetSuite with Numeric's Financial Data Platform.

Read the story

📋 Balance Sheet Reporting

Detailed Grouped Balance Sheet

How It Works:

This report takes your chart of accounts and organizes balance sheet line items into custom groupings that go beyond the standard asset/liability/equity structure. You might group multiple prepaid accounts under "Prepaid Expenses," consolidate accrual accounts into "Accrued Liabilities," or create specific groupings for different liability types (current vs. non-current, operating vs. financing leases, etc.).

How to Build:

  1. Start with all balance sheet account types (Assets, Liabilities, Equity)
  2. Create custom groupings that match your financial statement presentation
  3. Organize accounts into meaningful categories (e.g., "Current Assets" → Cash & Cash Equivalents, Accounts Receivable, Prepaid Expenses)
  4. Set up the standard balance sheet equation flow: Assets → Liabilities → Equity
  5. Add prior period columns for balance change analysis

Why It's Useful:

Standard balance sheets in NetSuite often show too much detail (every single GL account) or not enough structure (minimal groupings). This report lets you present the balance sheet exactly how your board, investors, or auditors expect to see it.

It's particularly valuable for companies with complex balance sheets - multiple entities, prepaid/accrual accounts, or detailed fixed asset tracking. You can create the clean, professional balance sheet that goes in your board deck while maintaining the ability to drill into the underlying detail when needed. This is also the foundation for creating balance sheet footnotes and disclosures.

Mapped Disclosures for Footnotes

How It Works:

This report groups specific balance sheet accounts into disclosure categories required for financial statement footnotes. For example, you might map several different accrual accounts (accrued payroll, accrued bonuses, accrued vacation, accrued taxes) into a single "Accrued Liabilities" disclosure line. The report shows both the individual accounts and their rolled-up disclosure presentation.

How to Build:

  1. Identify which accounts need to be disclosed together in your financial statement footnotes
  2. Create groupings that match your footnote disclosure requirements (e.g., "Property & Equipment, net" might include multiple fixed asset accounts and accumulated depreciation)
  3. Filter to the specific balance sheet sections relevant for footnotes
  4. Configure to show both the detail (individual accounts) and summary (disclosure grouping)
  5. Set as period-end report (typically month-end or quarter-end for audit purposes)

Why It's Useful:

Auditors and investors require specific disclosures about balance sheet composition - you can't just show "Accrued Liabilities" as one number, you need to break down what's in there. This report creates the bridge between your detailed GL and your disclosure requirements.

During audit season, this saves hours of manually pulling account details and grouping them into footnote schedules. It's also critical for companies preparing for IPO or raising capital, where financial statement footnotes need to follow GAAP presentation standards. Instead of rolling these disclosures forward in Excel every quarter, you have a repeatable report that automatically pulls the right accounts into the right disclosure categories.

Classified Balance Sheet Views for Investor or Board Reporting

How It Works:

This report presents your balance sheet with strategic reclassifications that differ from your statutory books. You might reclassify certain assets or liabilities to better align with how investors or your board thinks about the business, combine immaterial line items, or restructure the presentation to highlight key metrics like working capital or net debt.

How to Build:

  1. Start with your standard balance sheet structure
  2. Create custom groupings that reflect investor/board preferences (e.g., "Cash & Marketable Securities" combining multiple accounts, "Net Working Capital" showing current assets minus current liabilities)
  3. Apply reclassifications - for example, moving debt issuance costs, reclassifying certain assets from non-current to current, or netting related accounts
  4. Create metric rows for calculated values (Total Debt, Net Cash Position, Current Ratio components)
  5. Format to emphasize key metrics your audience cares about

Why It's Useful:

Your GAAP balance sheet and your investor-friendly balance sheet often aren't the same thing. Investors care about cash position, total debt, and working capital trends - they don't need to see every individual prepaid account.

This report lets you maintain GAAP compliance in your books while presenting a cleaner, more strategic view to external stakeholders. It's particularly valuable for board presentations where you want to focus the conversation on high-level financial health rather than accounting minutiae.

If both views run on the FDP, the GAAP balance sheet and the board version draw from the same dataset, so there's no second set of numbers to tie out before the board meeting.

You can also use this to create "management balance sheets" that align with how your CFO talks about the business, even if the underlying books follow standard accounting categories.

Conclusion

The accounting teams at Masterworks, STASH, and Parafin have built reporting frameworks in Numeric that rival standalone BI tools, complete with custom dimensions, dynamic groupings, and automated variance analysis.

What sets these teams apart is that their reports stay connected to the source data, update in real-time, and live alongside the rest of their close process. No more bouncing between NetSuite, Excel, and three other tools to answer a single question. All of that work now happens in Numeric.

For teams whose reporting has outgrown what their ERP can hold, Numeric's Financial Data Platform (FDP) reports on every dimension a business event carries. Every number traces back to its source record, so the next time the CFO asks what R&D spent on AWS last quarter, the answer can come during the meeting.

That same data is a foundation to build on. Numeric MCP connects it to the AI tools a team already uses, and App Studio lets teams build their own applications on top of it.

Learn how Numeric's Financial Data Platform handles reporting.

Learn more

Related Content

See numeric in action

Schedule a demo