DAXIA Reporting · the business surface

Where every number is defensible.

Used after data integration, for as long as the business runs, by finance and business users. It reads Gold and nothing else. It also holds a full ERP — a general ledger, sub-ledgers, close engines, statements and group consolidation — where the density is tables of money rather than trees of objects.

Reporting pod

Answer a question on Gold.

Explorer — the SQL workbench, Gold-scoped, with Ask DAXIA and Explain
Builder — pivots and Insight visuals, with wells you fill
Insights — dashboards you can ask DAXIA to build, from a question in plain words

ERP pod

Keep the books, and prove them.

Enterprise — the book of record: 27 screens in five groups, the way a month is worked
Financials — a connected ledger, a chart of accounts, scenarios, statements
Group Reporting — structure, packages, rates, eliminations, the worksheet

Reporting · Explorer

The workbench, scoped to Gold.

The same SQL workbench as DAXIA Data, reading Gold only. Ask DAXIA in plain words and follow up in the same conversation: each answer states its confidence and caveats, keeps its SQL one click away, and runs. Expand a table to see it whole.

The assistant cannot suggest a question about a table you may not read.

The Gold schema Ask DAXIA sees, and the starter questions it offers, are narrowed to the caller’s allow-list. It enumerates the user-facing views, never the history tables behind them.

Every read goes through the same door.

Explorer, Builder and Insights all issue SQL against Gold through one executor with one allow-list check, so a table hidden in one is hidden in all of them.

Object tree
Ask DAXIA
Follow-ups
Show SQL
Explain
Expand
CSV export

Reporting · Builder

Pick a visual, fill the wells it names, and it draws.

A new visual starts blank and tells you what it needs — Axis, Legend, Values — rather than guessing silently. Saved reports export to CSV and XLSX, and can be scheduled.

Each visual queries at its own grain.

A dashboard of six visuals is six queries, each grouped the way that visual needs, which is how a canvas escapes the server’s 10,000-row pivot cap without truncating anything silently.

A scheduled export runs with the authority of the person who scheduled it.

A headless run used to execute with no principal, so a user restricted to three Gold tables could schedule a report over a hidden one. The run now carries run_as, and the allow-list is enforced — failing closed.

report_runner.enforce_run_authority

An export is preflighted before it is written.

The preflight names the sources and applies the same allow-list as the preview, so the file you download is the report you saw.

Wells
Custom columns
Top and bottom N
Number formats
Saved reports
Export
Schedule

Reporting · Insights

Ask for a dashboard in plain words. Read the plan before it is built.

Ask DAXIA a question in Explorer, save the answer as a report, and say what the dashboard should show. DAXIA proposes every visual with its fields and its reason; you untick what you do not want, name it, and it is built in Insights — pinned to Home if you choose. The canvas is yours to change afterwards: KPI, matrix, table, bar, line, pie, stacked and 100% bars, combo and variance KPIs, progress.

A dashboard is planned before it is built.

The proposal lists every visual, the fields it uses and why it was suggested. Nothing is written until a person has read it and pressed Create — and each visual is checked again on the server against the live report.

The model sees the shape of the report, never its rows.

What travels is the report’s column names and types, the question and SQL behind it, and your brief — never a row, never the result of running it. Every field the model names is checked against the report; an unknown one drops that visual, and the dialog says so.

Variance ink comes from a favourability verdict on the server.

Whether “less” is good depends on the section — spend below budget is favourable, revenue below budget is not. That judgement lives in one place and every visual reads it.

Ask DAXIA
Save as report
Build dashboard
KPI
Bar
Line
Table
Variance KPI
Pin to Home

ERP · Enterprise

The book of record, grouped the way a month is worked.

ERP · Enterprise · Sales orders

This is where invoicing actually begins.

Raise sales orders directly in DAXIA. Use external sources as feed stream. Review, adjust, invoice. Each sales order is tied to an invoice. Sales orders can be consolidated. Define sales orders to invoice schedules, to automate invoice creation, including invoice sending.

ERP · Enterprise · Invoices

This is where the sales orders land.

Each invoice holds what was passed from the sales ordering process. Manually send invoices to customers if needed. Void if the invoice needs reversal — this automatically adjusts the journal and balances the control account.

ERP · Enterprise · Journals

The journal is the only way money moves, and a posted one is immutable.

Nothing writes a balance: balances are maintained only inside the posting transaction, and a verification pass proves they still equal the lines beneath them. The database refuses an update to a posted line with a schema-bound predicate. Publish materialises a DAXIA-kept entity’s posted ledger as one Gold table per entity, one row per journal line. A published entity’s statement runs the identical code path as an externally connected one.

ERP · Enterprise · Trial balance

Live trial balance.

Verify whenever you want, on the spot. Every mismatch is clearly surfaced and explained.

ERP · Enterprise · Audit

If your business is audited by an external financial auditor, then DAXIA is exactly what you need to run your business.

Enterprise Audit reflects the whole audit pack that is needed by an external auditor, in 98% of the cases. One click = full pack. Or go for generating each individual caption. Your choice. Custom audit reporting is supported.

ERP · Enterprise · Financials

Bind your ledger, bind your chart of accounts, define your Balance Sheet, P&L, Cash Flow and Changes in Equity.

Everything is live. Access, run and see your numbers on the spot. Drill-down on each item, both at line level and account level.

ERP · Enterprise · Group Reporting

Consolidation that is valid to an accountant and to an auditor.

Structure, chart and mapping, exchange rates, entity packages, intercompany, investments, consolidate. An admin sets the structure and locks a run; a Reporter submits packages and reads the worksheet.

Effective ownership multiplies along a chain and adds across paths.

80% of 70% is 56%, and the minority in that company is 44% — not the 30% the org chart shows. A cross-holding is a simultaneous equation and is refused, with every loop listed.

Full consolidation brings in one hundred per cent and shows the minority separately.

Share and consolidation factor are two fields, and the screen shows both, because this is the commonest misunderstanding of consolidation and it changes every line of the balance sheet.

Control is a judgement, and the method is declared.

A 45% holding with a shareholders’ agreement is control; a 55% holding with a blocking minority may not be. The engine never infers the method from a percentage — it reports when the two look inconsistent, as a finding for a person.

A run is frozen with the hash of its inputs.

Re-running a period with the same inputs and version yields identical results; a restatement is a new run linked to the prior one. A disposal is a date, not a deletion, so no past period loses its consolidation.

Structure
Chart & mapping
Exchange rates
Entity packages
Intercompany
Investments
Consolidate

The one hard guarantee

Reports read Gold and nothing else.

Explorer, Builder, Insights, Financials and the published ledger all read the Gold layer through one executor. From this application there is no path to Bronze or Silver.

The allow-list applies when nobody is watching.

A scheduled export carries the authority of the person who scheduled it and fails closed. Who fired it and whose rules applied are recorded as two different facts.

How data security is enforced

Every request carries a role, and the server checks it.

People sign in with Entra ID and the API validates the token on every call. A directory member with no DAXIA role is refused, a deactivated user is refused, and roles are resolved on the server for every endpoint — never in the page.

One allow-list, on every read path.

Prod Config names the Gold tables each role and each person may read. The same check runs on the object tree, ad-hoc queries, Builder previews and exports, Insights, and the schema Ask DAXIA is shown and the questions it suggests. A refused read names the tables it was refused.

Row security lives in the database.

A row rule becomes a SQL Server security policy on Gold storage, fed the reader’s identity on every connection. DAXIA’s own queries carry the same predicate, and a free-typed query over a restricted table is refused rather than quietly filtered.

How Gold is restored

Any Gold table, back to any moment.

In Restore Production an admin picks a table and a date and time — or a change on the table’s timeline, and restores to just before it. The preview shows how many rows the table held at that moment before anything is written. How far back you can go is how far the table’s ledger history goes.

A restore never deletes.

In one transaction the current rows are retired to history and the snapshot becomes the active generation. If any step fails, the table is left exactly as it was. A restore can itself be undone, by restoring to the moment before it.

Every restore is on the record.

Who ran it, the moment it went back to, and the rows retired and reinstated are stored in the restore history, the audit log and the table’s own timeline. Being a ledger write, the restore is itself tamper-evident.

Before the reports

DAXIA Data

The workbench that reconciles itself.

Connect, replicate, model and transform — every run streamed and recorded, every table counted.

Connections
Data quality
Deploy
Explore data
Model
Transform
Orchestrate
Semantic pack

See DAXIA Data

The Platform

Built to be audited.

The architecture, the security model and what a deployment into your subscription looks like.

Medallion
Security
Deployment

See the platform

Bring a question. We will answer it on Gold.

Name a figure you need to defend — a statement line, a consolidation, an aged-debt number. The walkthrough builds it in front of you, with the person who built the product.

Request a walkthrough See how the data gets there