Unit4 Historical Reporting Without the Live Agresso Bill

Unit4 historical reporting is the ability to query, analyse, and produce regulatory reports against Unit4 Business World (Agresso) or ERPx data from periods that predate your Oracle Fusion go-live. The legacy data lives in Syntra ETL's cloud archive — Parquet files partitioned by fiscal year, period, business unit, and project — and is accessed through a SQL/REST interface that mirrors the original Unit4 schema. Auditors run familiar queries against acrtransact, acrpayroll, project, customer, supplier as if the live Unit4 system were still up. BI tools (Power BI, Tableau, Qlik, Excel) connect via JDBC/ODBC. The result: you decommission Unit4, you keep full historical visibility, and you satisfy UK FOI, HMRC, HESA, NAO, GDPR retention obligations without paying to keep a legacy instance alive.

Retention drives the answer. UK public-sector and higher-education customers commonly retain Unit4 historical reporting access for 7–25 years (FOI minimum 7; institutional FOI policy often longer; HESA-aligned student finance often indefinite). UK private-sector commercial customers: 6 years (HMRC) for VAT, PAYE, Corporation Tax; 7 years recommended for general accounting. Nordic public sector: 10 years statutory accounting minimum, plus national archive transfer requirements. Continental EU: 6–10 years depending on country, with GDPR-bounded retention on personal HCM data. US healthcare under HIPAA: 6 years minimum. Higher ed and research bodies typically need indefinite access to Research Excellence Framework cost data and grant-funded project history. Syntra ETL configures per-domain retention so each data class meets its own rule.

Anything you could run against the live Unit4 database, with the original coding-structure context fully preserved. Standard pre-built reports cover trial balance by ledger and period, AP voucher aging and detail, AR invoice aging and customer history, payroll register and year-end tax extracts (P60/P11D for UK PAYE, year-end tax summaries for Nordic countries), project actuals by WBS and resource, timesheet detail per employee per period, expense claim history, fixed asset register with depreciation history, supplier and customer 360-degree views. UK higher-ed customers get pre-built HESA return extracts and REF cost-capture queries. Public-sector customers get NAO audit-pack templates and FOI-response query templates. Custom reports build in any BI tool that speaks SQL.

Faithfully. The archive preserves Unit4's seven-series coding structure — Account, CostCentre, Department, Project, Activity, Funding source, and any customer-defined series — as the original column structure on every transactional record. The relation tables that defined valid combinations in the live Unit4 system also live in the archive, so any historical analysis can apply the same relation rules. Reports can drill from a GL summary down to a specific acrtransact row with full coding-structure detail. The relation rule history is itself versioned in the archive — so a query against a 2018 trial balance respects the 2018 relation rules, not whatever the rules were at decommission date.

Yes. Higher-education customers in the UK using Unit4 for student-finance and research-cost capture get pre-built HESA return extracts, REF cost-capture queries, and OfS data templates as part of the Unit4 historical reporting service. The pre-built extracts use the same logic Unit4 customers ran in production — Funding source coding-structure values drive the cost-allocation splits, project codes feed the REF unit-of-assessment rollups, student-finance flexi-fields drive HESA finance return amounts. The data shape matches the institutional FOI and HE Funding Council expectations, so retrospective or compliance-driven re-runs of historical periods produce numbers identical to those originally submitted.

Sub-second for typical drill-down queries — a single GL period for a single ledger, a single AP voucher with distribution detail, a project actuals query for one project. Multi-period or multi-year aggregations against billion-row acrtransact history return in 5–30 seconds depending on partitioning. The archive uses Parquet columnar storage partitioned by fiscal year, period, business unit, ledger, and project; the query engine performs column pruning and partition pruning so a year-end audit query doesn't scan 20 years of data. For UK year-end audit, HESA returns, and FOI windows, customers commonly pre-materialize auditor-facing datasets (trial balance, AP aging, project actuals snapshots) for instant access.

AIB (Agresso Information Browser) report definitions and Excelerator template definitions are preserved in the archive as customization-catalog artifacts — auditors can see the exact AIB query a closed-period balance was originally signed off on. For ongoing Unit4 historical reporting, the AIB and Excelerator logic is reimplemented as standard SQL queries against the archive, or as Power BI/Tableau dashboards if business users prefer a modern UI. Critical Excelerator workflows (especially Excel-based timesheet upload, budget upload, project-actuals correction) are reimplemented as Smart View workbooks or Fusion-native Excel integration if the workflow continues post-migration, or retired if the workflow only existed to manage live Unit4 data.

Yes. Access is role-based with mandatory audit logging — every query is logged with user, timestamp, query text, rows returned, and data classification accessed. Archive data is encrypted at rest with KMS-managed keys and in transit with TLS 1.3. Sensitive HCM and payroll fields (NI number, bank account, salary detail) are masked by default and require explicit role permission to unmask. UK public-sector customers get a dedicated FOI-officer role that surfaces full read for legitimate FOI requests while preserving day-to-day masking. Higher-ed customers get registrar-level role partitioning for student-finance data. Every report run leaves a signed, timestamped evidence trail suitable for SOX, NAO, ICO, and internal-audit review.