<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
A library of standard reports per module — and customer extensions through metadata.
Hundreds of standard reports across every operational module: AR ageing, AP open-position, GL trial balance, intercompany reconciliation, inventory ageing, work-in-progress, production variance. Customer-specific reports added through metadata definitions — without a release deployment.
Standard library
Every module ships with its operational report library — the reports the function lead asks for on day one.
Customer extensions
Customer-specific reports added through metadata definitions, without a release cycle.
Multi-format output
PDF for the regulator, XLSX for the analyst, XML for the integration, JSON for the API. One report, many surfaces.
Scheduled distribution
Reports distributed on a schedule — daily AR ageing to the credit controller, weekly cash position to the CFO, monthly variance to the controller.
What the report surface covers
Standard library
AR ageing, AP open-position, GL trial balance, intercompany reconciliation, inventory ageing, work-in-progress, production variance, sales pipeline, project P&L. Each module has its library.
Metadata-defined reports
Reports defined as metadata — source ledger, columns, filters, groupings, sub-totals, formatting. Customer-specific reports authored without code deployment.
Output formats
PDF (regulator-grade with legal evidentiary value), XLSX (analyst-grade with formulas preserved), XML / JSON (machine-readable for integration).
Parameterisation
Every report parameterised by date, entity, scope, currency. The same report generates the period view, the prior-period view and the year-to-date view.
Scheduling and distribution
Configurable schedules with role-based recipient lists. Distribution by email, secure portal or integrated channel.
Report audit
Every report execution logged with parameters, user, timestamp and output reference. The compliance team can reproduce any report run.
Why metadata-defined reports outperform code-defined ones
Reports authored in code have a development cycle — request, design, build, test, deploy. The cycle is measured in weeks; the operational reality the report is meant to illuminate moves in days.
Axional's reports are metadata definitions. A new report is composed in metadata, validated against the engine's schema and deployed in the same session. The function lead asks for a report on Monday; on Tuesday they have it. The development cycle that used to be a constraint becomes a non-issue.