What Is Jet Analytics, and Do You Actually Need It?

Jet Analytics is a managed data warehouse and cube layer that sits on top of Business Central, storing a cleaned, structured copy of your data so that Jet Reports, Excel, and Power BI can read from it quickly. If you already run Jet Reports and month-end feels slow, or you need to consolidate several companies and years of history, Jet Analytics is likely worth a look. If your reporting is straightforward and lives in one company, you probably don't need it yet. This article explains what it actually does, how it differs from plain Jet Reports, and how to decide honestly.

What Jet Analytics actually is

Plain Jet Reports queries Business Central live. When you refresh a report, it reaches into the BC database (or the API) and pulls the numbers there and then. That's fine for many reports, but every refresh is real work against your production system.

Jet Analytics changes the model. It builds and maintains a data warehouse — a separate SQL database that holds a copy of your BC data, restructured for reporting. On top of that warehouse it can build OLAP cubes: pre-aggregated, dimensional models designed to answer "revenue by customer by month by region" instantly.

In practice you get three things:

• A staging and warehouse layer that extracts data from Business Central on a schedule (typically overnight).
• A semantic/cube layer with friendly measures and dimensions, so report builders aren't wrestling with raw table and field names.
• A reporting surface that feeds Jet Reports in Excel, and also Power BI, from that warehouse rather than from live BC.

The key idea: your reports read from a purpose-built reporting store, not from the transactional system.

How it differs from plain Jet Reports

This is the distinction that trips people up, so let's be precise.

Jet Reports is the Excel-based report writer. It uses functions like NL() and NF() to pull BC data straight into spreadsheets, live. No warehouse required. You can be up and running quickly, and for a lot of finance teams that's the whole solution.

Jet Analytics is the data infrastructure underneath. It doesn't replace Jet Reports — it feeds it. Your NL() formulas can point at the warehouse instead of live BC, and everything runs faster because the heavy lifting (joining, aggregating, cleaning) happened overnight.

So the honest one-liner: Jet Reports is how you build reports; Jet Analytics is where the data comes from. You can have Jet Reports without Jet Analytics. You don't really have Jet Analytics without something (Jet Reports, Excel, or Power BI) reading from it.

The real benefits

When Jet Analytics earns its keep, it's usually for one or more of these reasons.

• Fast month-end reporting. Complex financial packs that crawl against live BC often refresh in seconds against a cube, because the aggregation is already done. If your month-end reporting has become a "click refresh and go make coffee" ritual, this is the biggest win.
• Historical trending and snapshots. BC is a live system — some data changes or gets archived. A warehouse can retain history and take point-in-time snapshots, so you can genuinely compare this year to three years ago on a consistent basis.
• Multi-company and multi-source consolidation. If you run several BC companies, or you need to blend BC with a CRM, a payroll system, or an old legacy database, the warehouse is the natural place to bring it all together with consistent dimensions.
• Power BI without hammering live BC. Pointing Power BI directly at production BC can be slow and puts load on the system your business runs on. A warehouse gives Power BI a fast, stable source that you can refresh on a schedule.

The honest downsides

Jet Analytics is not free money, and we won't pretend it is.

• Cost. It's a meaningful step up in licensing from Jet Reports alone, plus the infrastructure to host the warehouse (an Azure SQL database or a server).
• Setup and expertise. Someone has to design the warehouse, configure the data sources, build the cubes, and schedule the loads. This is a project, not an afternoon.
• Another moving part. You now have an overnight process that can fail, data that can be stale if a load didn't run, and a layer between your reports and the truth. That demands monitoring and a bit of ongoing care.
• Latency by design. Because it refreshes on a schedule, the warehouse is typically a day behind unless you configure more frequent loads. For live operational numbers, that can be a drawback rather than a feature.

You probably need it if…

• Your month-end or board reporting is slow or timing out against live BC.
• You run multiple companies and consolidation in Excel is painful.
• You need years of consistent history and point-in-time comparisons.
• You want to combine BC with other systems in one reporting model.
• You're rolling out Power BI across the business and don't want everyone querying production BC.

You probably don't if…

• You have one company and fairly standard financial reports.
• Your Jet Reports refresh quickly enough already.
• You only need current, live numbers, not deep history.
• You have no appetite for the extra cost and administration of a warehouse.
• Nobody on the team can own the warehouse day to day — an unmaintained warehouse is worse than none.

There's no shame in the second list. Plenty of well-run finance teams get everything they need from Jet Reports alone.

How it compares to just using Power BI

A fair question: Power BI can connect to Business Central directly, so why add Jet Analytics?

• Direct Power BI on BC works well for smaller models and current data, but it can be slow, it loads your live system, and modelling raw BC tables in Power BI is genuinely hard.
• Jet Analytics as the source for Power BI gives you a clean, pre-modelled warehouse. Power BI reads friendly measures and dimensions instead of raw tables, refreshes fast, and leaves BC alone.

The other angle: Jet Analytics keeps your Excel and Power BI reporting on the same source of truth. Finance can stay in Jet Reports in Excel while the wider business uses Power BI — both reading the same numbers. If your organisation is committed to Power BI and has the skills to model BC data well, you may not need Jet Analytics. If Excel is still central to finance and you want one consistent source feeding both, that's exactly where Jet Analytics fits.

Frequently asked questions

What's the difference between Jet Reports and Jet Analytics?

Jet Reports is the Excel-based report writer that queries Business Central live. Jet Analytics is the data warehouse and cube layer that stores a structured copy of your data for faster, historical, multi-source reporting. Jet Analytics feeds Jet Reports; it doesn't replace it.

Does Jet Analytics work with Power BI?

Yes. One of its main uses is acting as a fast, pre-modelled source for Power BI, so your dashboards refresh quickly without querying live Business Central. You get the same numbers in both Excel and Power BI, drawn from one warehouse.

Do I need Jet Analytics for month-end reporting?

Not necessarily. Many teams do month-end perfectly well with Jet Reports querying BC directly. You benefit most from Jet Analytics when those reports have become slow, when you consolidate multiple companies, or when you need consistent historical comparisons.

Talk it through before you buy

Jet Analytics is a strong tool for the right situation and an expensive over-engineering for the wrong one. The deciding factors are your reporting speed, your history and consolidation needs, and whether you can own the warehouse long term. If you'd like a straight, no-hype assessment of whether it fits your setup, speak to our Jet team and we'll help you make the call.