Five Reports Your CFO Wants That You Cannot Build Inside Business Central

Your CFO asks for reports that sound reasonable: margin by customer over the last three years, forecast versus actual, and the customer cost-to-serve ratio including freight.

The data exists somewhere.

That does not mean the report belongs inside Business Central.

Business Central has substantial reporting functionality. It includes more than 300 built-in reports, financial reporting, analysis mode, Excel integration, Power BI apps and ad-hoc analysis. But there is a line between reporting on transactions stored in Business Central and building an analytical model from multiple systems, companies and periods.

Three different reasons a report will not exist

Before deciding Business Central cannot produce a report, establish why.

1. The data is not in Business Central. This is different from Business Central being unable to produce the report. If your freight costs live with a carrier, your sales pipeline lives in CRM and your forecast lives in another planning system, Business Central cannot natively report across all of it. The information first needs to be brought together somewhere.
2. The data exists, but not in the structure the analysis requires. Business Central’s Financial Reporting feature works primarily with general ledger data, budgets and dimensions. It can produce custom financial statements, comparative views, period analysis and budget-versus-actual reporting. That is different from building a semantic model where customers, items, cohorts, freight, inventory and CRM activity need to interact over several years.
3. Business Central technically has the data, but it is the wrong place to perform the analysis.

That third distinction matters most.

Do not commission a custom AL report simply because the data originates in Business Central. Sometimes the better answer is Power BI or Microsoft Fabric.

These are five Business Central reporting limitations that usually tell us the reporting architecture needs to extend beyond the ERP.

1. Rolling 36-month margin by customer cohort

Your CFO wants to see customers grouped by when they were acquired, then compare revenue and margin performance over the following 36 months.

Business Central has much of the raw transactional information needed to start this analysis. You have customers, sales transactions, items, costs, posting dates and dimensions.

The difficulty is the cohort model. You first need a reliable definition of when a customer entered the cohort. First invoice? First order? Account creation? First meaningful purchase?

Then every transaction needs to be evaluated relative to that date. A customer acquired in January 2024 is at month 12 in January 2025. A customer acquired in June 2024 is only at month seven.

That is not a conventional financial statement. You can build custom code to calculate it, but this is the type of historical analytical model Power BI is much better suited to handle. Keep the transactions in Business Central. Build the cohort logic in the analytical layer.

2. Forecast versus actual where the forecast lives outside BC

This one is straightforward. Business Central can absolutely report budget versus actual when the budget exists in Business Central. Its Financial Reporting functionality can compare general ledger entries against G/L budget entries for a specified period and can apply dimension filters.

But your CFO may not be asking for budget versus actual. They may be asking for forecast versus actual, where the forecast is maintained in Excel, a planning platform, CRM or another financial planning application.

Now you have two sources. You can import data into Business Central or create custom integration around it. But first ask why. If the forecast is intentionally maintained in another application, moving it into Business Central solely so Business Central can report against it creates another data-management process.

The cleaner architecture is often to take actuals from Business Central and forecast data from its source, then compare the two in Power BI or another analytical layer. One model. Two governed sources.

3. Blended cost-to-serve across ERP, freight and CRM

This is where the limitation becomes obvious. Your CFO does not just want gross margin. They want to know what it actually costs to serve a customer.

Business Central can tell you about sales, cost of goods, invoices, credits and other financial transactions recorded in the ERP. But suppose freight invoices arrive separately. CRM contains sales activity. Service information lives somewhere else. E-commerce transactions contain another set of customer behaviours.

Now the calculation might look more like this:

• Revenue
• minus product cost
• minus freight
• minus returns
• minus service cost
• minus other allocated customer costs

The exact formula should be defined by your finance team. The important point is that Business Central cannot natively calculate costs it does not contain.

This is precisely what an analytical data model is supposed to solve: combine transactional information from different sources, establish common customer and product definitions, and calculate metrics across them.

The difficult part will not be the dashboard. It will be agreeing on what “cost-to-serve” actually means and matching the same customer correctly across every source. Do that work before choosing the reporting technology.

4. Inventory aging across multiple entities in one view

Business Central has substantial inventory reporting. The multi-entity requirement is where things get more interesting.

Business Central supports financial consolidation across companies. But that does not mean every operational inventory transaction from every company becomes one native consolidated inventory model.

Microsoft documents a different approach for cross-company reporting, using Microsoft Fabric, with OneLake as the shared data layer.

If the CFO wants one inventory-aging view across several companies, with consistent item definitions, currencies, locations and aging buckets, build the consolidated analytical model in Fabric.

5. Cash conversion with bank, AR and AP in one model

This is the one most likely to cause an argument, because Business Central already has cash-flow functionality, and it is useful. Business Central’s cash-flow forecast can include receivables, open sales orders, service orders, payables, purchase orders, fixed-asset activity, budgets, manual revenues and expenses, and liquid funds.

If your CFO needs a short-term operational cash forecast based primarily on Business Central information, start there.

But a broader cash-conversion model can be different. Your CFO may want actual bank balances from external banks, AR aging, AP timing, inventory investment, historical working-capital trends and possibly forecast assumptions in one analytical model.

Now you are no longer asking for Business Central’s cash-flow forecast. You are asking for a management model that combines several measures and potentially several sources. Build it accordingly. Do not replace a useful native Business Central cash-flow function. Use it for the problem it was designed to solve.

The honest test for whether you need more than Business Central

Ignore how impressive the requested dashboard looks.

Ask where the data comes from. If almost everything comes from one Business Central company and the calculations are based on existing G/L entries, budgets, dimensions or operational transactions, exhaust the native options first.

If you repeatedly need data from multiple Business Central companies, start evaluating a cross-company Power BI model or a centralized data platform such as Microsoft Fabric.

Do not jump from “BC can’t produce this report” directly to “we need Fabric.” There is a lot of architecture between those two statements.

How to apply this

1. Take the five reports your CFO asks for most often.
2. For every field and calculation, identify its source.
3. Mark it as Business Central, another system, manually maintained or calculated.
4. Then look at the pattern.

If the data is already in Business Central, fix the Business Central reporting. If you are repeatedly joining companies and systems manually in Excel, stop building individual reports and fix the reporting architecture.

Qixas Group works across Business Central, Power BI and Microsoft Fabric. We also tune and recover Business Central environments where years of custom reporting have made the ERP more complicated than it needed to be.