Retiring Unit4 Agresso means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise attribute definitions, project relationships and voucher history. Compare required reports and documents with source evidence, test permissions and obtain business acceptance before scheduling shutdown.

This guide covers the retirement questions, a mock-data ArchiveHub demonstration and the validation work needed to define a project scope.

What keeping Agresso read-only really costs

Cost categories are a discovery checklist, not a guaranteed savings calculation. Verify support status, deployment, shared infrastructure and contract terms for the actual installation.

  • Licences or subscription. An Agresso installation kept for lookups still carries a maintenance or subscription line in the budget.
  • The database and servers. Agresso runs on SQL Server or Oracle, with its own application and web servers. All of it needs patching and backing up, and eventually an upgrade simply to stay supported.
  • Report and browser knowledge. The browser enquiries and report definitions that answered auditors' questions were built by power users over many years. When those people move on, the answers become hard to reproduce.
  • Security exposure. Resource records, salaries, payroll results and supplier bank details remain on a system that is no longer actively managed.
  • Audit access. Every external review means creating users in a system nobody wants to touch, plus someone to explain the attribute structure.

Scope, versions and evidence

This is an illustrative workflow, not a customer case study. Confirm the source release, deployment, modules, customisations and extraction permissions before using the mappings below. Tables and report labels describe the demonstration catalogue; native-report equivalence has not been independently certified. Use agreed source reports and representative records for acceptance testing.

An archive is not a replacement for every operational feature of the retired ERP. Document required historical tasks, excluded functions and any archive-derived calculations.

Historical data to scope for Unit4 Agresso

ArchiveHub stores Agresso's tables under their native names, with every column keeping its Agresso name and a description. The attribute model stays intact: agltransact keeps its attribute values in dim_1 to dim_4, and agldimension, agldimvalue and aglrelvalue keep the attribute definitions, values and relations, such as project to cost centre or resource to cost centre. A query that filtered on cost centre C1 in Agresso can filter on it in ArchiveHub too.

Representative tables:

  • General ledger: agltransact (every posted voucher line), aglaccounts and aglrules (chart of accounts and account rules), aglbudget, aglvouchtype, acrbatch (posted batches per interface), and acrperiod, where period YYYY00 is the opening balance and YYYY13 the year-end closing. Also acrclient for the clients (companies) in the installation.
  • Customer ledger: acuheader (customer master), acutrans (open items) and acuhistr (matched, closed items with a common match id).
  • Supplier ledger: asuheader, asutrans and asuhistr, plus apayproposal payment runs.
  • Bank: abkaccount, abkstatement and abkstmtline, with statement lines matched to ledger vouchers.
  • Projects and time: atsproject, atsworkorder, atstimesheet and atstrans, with cost, sales value and invoicing status per time line. Project billing is in asoheader and asodetail.
  • Procurement: apoheader and apodetail.
  • Travel and expenses: atrheader and atrtrans.
  • Fixed assets: afxasset and afxtrans.
  • HR and payroll: ahsresources, ahsemployment, apspayrun and apsresult.
  • Tax: atxreport and agltaxcode.

Where a report needs a point-in-time view that Agresso computed on the fly, ArchiveHub stores it as a clearly labelled, archive-derived table rather than pretending it is native. Quarter-end customer and supplier ageing (ah_customer_ageing, ah_supplier_ageing) is rebuilt from the open and matched items. Month-end unbilled WIP (ah_wip_balance) is rebuilt from time transactions and invoice dates.

Explore the demonstration

General Ledger Transactions list in ArchiveHub General Ledger Transactions: agltransact voucher lines by period, account and attribute values. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

General Ledger Transactions detail page in ArchiveHub General Ledger Transactions detail: one voucher line with its account, attributes, amounts and voucher type. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Customer Ageing list in ArchiveHub Customer Ageing: aged debtors per customer at a fiscal quarter end, rebuilt from open and matched items. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Explore the report reference catalogue

These mappings identify intended business workflows, not certified one-for-one equivalents. Confirm availability, source coverage, filters, currencies, dates and calculations for the selected release and implementation.

General Ledger

  • General Ledger Transactions: reference workflow: the Transaction enquiry / browser on General Ledger transactions (agltransact).
  • Trial Balance: reference workflow: the Trial balance / Balance per account and period report (agltransact, aglaccounts), with period YYYY00 as opening and YYYY13 as year-end closing.
  • Chart of Accounts: reference workflow: the Account master file and account rules (aglaccounts, aglrules).
  • Attribute Values: reference workflow: Attributes, attribute values and relations (agldimension, agldimvalue, aglrelvalue).
  • Cost Centre Results: reference workflow: results per cost centre (C1) and period, a browser enquiry on agltransact grouped by attribute.
  • Budget vs Actual: reference workflow: the budget versus actual report per account, cost centre and period (aglbudget, agltransact).
  • Posted Batches: reference workflow: the Batch input / GL07 posting log and voucher journal per interface (acrbatch, agltransact).
  • Subledger to GL Reconciliation: reconciles the customer, supplier, expense, asset and WIP sub-ledgers against their control accounts per period.

Customer Ledger

  • Customers: reference workflow: the Customer master file with addresses and open balance (acuheader, agladdress).
  • Customer Transactions: reference workflow: the Customer enquiry of open and historical (matched) items (acutrans, acuhistr).
  • Customer Ageing: reference workflow: the customer ageing analysis (aged debtors) at fiscal quarter ends, rebuilt from acutrans/acuhistr.

Supplier Ledger

  • Suppliers: reference workflow: the Supplier master file with addresses, bank details (masked) and onboarding documents (asuheader, agladdress).
  • Supplier Invoices: reference workflow: the Supplier enquiry / invoice register with payment status and scanned invoice (asutrans, asuhistr).
  • Supplier Ageing: reference workflow: the supplier ageing analysis (aged creditors) at fiscal quarter ends, rebuilt from asutrans/asuhistr.
  • Payment Runs: reference workflow: the Payment proposal / payment journal history per payment run (apayproposal).

Cash and Bank

  • Bank Transactions: reference workflow: the bank account transactions (cash book) with bank statement value date (agltransact, abkstmtline).
  • Bank Reconciliation: reference workflow: the bank reconciliation per bank statement: statement lines, ledger balance and outstanding items (abkstatement, abkstmtline).

Projects

  • Projects: reference workflow: the Project master file and project enquiry with work orders, billing and team (atsproject, atsworkorder).
  • Timesheets: reference workflow: the Timesheet enquiry and approval status per resource and week (atstimesheet, atstrans).
  • Project Invoices: reference workflow: the project billing invoice enquiry with billed time and expenses (asoheader, asodetail, atstrans).
  • Project Results: reference workflow: the project results / profitability report: hours, cost, billed revenue, WIP and margin per project.
  • Work in Progress: reference workflow: work in progress (unbilled time) per project at month end, tied to the WIP accrual account.
  • Resource Utilisation: reference workflow: the resource utilisation report: chargeable versus available hours per resource and month (atstrans).

Procurement

  • Purchase Orders: reference workflow: the Purchase order enquiry with lines, receipts and matched invoices (apoheader, apodetail).

Travel & Expenses

  • Expense Claims: reference workflow: the travel and expenses claim enquiry with rechargeable lines and payment (atrheader, atrtrans).

Fixed Assets

  • Asset Register: reference workflow: the Fixed assets register / asset enquiry with transactions and capitalisation form (afxasset, afxtrans).
  • Asset Transactions: reference workflow: the fixed asset transaction and depreciation journal per period (afxtrans).

Human Resources and Payroll

  • Resources: reference workflow: the Resource (employee) master file with employment and pay history and HR letters (ahsresources, ahsemployment).
  • Payroll Results: reference workflow: the Payroll results / payslip archive per resource and payroll run (apsresult, apspayrun).
  • Payroll Cost Distribution: reference workflow: the payroll posting to the General Ledger per cost centre and period, payroll results against GL salary accounts.

Tax

  • Tax Returns: reference workflow: the VAT/MVA/BTW return report and tax transactions per tax code with settlement (atxreport, agltransact, agltaxcode).

Source documents stay attached

Document types below illustrate the intended scope. Include source attachments and external repositories explicitly, and test retrieval and record linkage before decommissioning.

ArchiveHub keeps archived documents attached to the Agresso records they belong to: customer invoices, supplier invoices, expense claims with their receipts, purchase orders, bank statements, projects, resources (employees), fixed assets and supplier onboarding documents. An auditor checking an expense claim or a supplier invoice sees the scanned original next to the ledger line.

Beyond the reports

Confirm these capabilities, configuration requirements and limits during the demonstration and scope review; the report catalogue alone does not validate them.

  • Ad-hoc query builder over the configured archived tables, with the Agresso column descriptions and suggested joins, for example agltransact to agldimvalue to resolve attribute values into names.
  • Retention rules and purge with approval, for instance different retention for payroll, projects and the general ledger.
  • Legal hold on a project, client or supplier under dispute.
  • Personal-data governance: agree the lawful retention, access and deletion requirements with the responsible privacy and records teams. Product features alone do not establish regulatory compliance.
  • Access controls: define and test permissions for the required companies, records and sensitive fields. Do not assume that system-level roles reproduce the original ERP permissions, particularly for payroll and HR data.
  • OData feeds to Excel, Power BI and SAP Analytics Cloud.

How the decommissioning project runs

  1. Extract the Agresso tables per client, with their native names, attributes and periods.
  2. Validate. Row counts are checked table by table. Balances must tie out: the archived trial balance has to agree with Agresso's balance per account and period, and the customer, supplier, asset and WIP sub-ledgers must reconcile to their control accounts.
  3. Parallel read access. Finance, project and HR users work in ArchiveHub while Agresso is still available.
  4. Retire after acceptance. Obtain documented sign-off for data reconciliation, document retrieval, user access, retention and legal holds, recovery and remaining integrations. Retire only the approved components; shared infrastructure may still be needed. End or reduce subscriptions, licences and support only where the contract permits. Budget for archive operation and any residual costs.

Keep the attributes, lose the upkeep

Agresso's strength was the attribute model on every transaction. ArchiveHub keeps that model readable for as long as the records must be kept, without the system that produced them.

Questions about Unit4 Agresso retirement

What should an Agresso attribute archive preserve?

Capture the definitions, values and relationships used by the source configuration. Test how users filter historical transactions by project, cost centre and other agreed attributes.

Are attribute mappings identical in every installation?

Do not assume they are. Agree the release, client structure and local attribute configuration, then document how those meanings appear in the historical reports.

What does this ArchiveHub demonstration prove?

The screenshots illustrate how selected records can be presented using mock data. They do not prove production completeness, customer outcomes or parity with every Unit4 Agresso report. Request a demonstration against your own approved scope and acceptance cases.

Related retirement resources

For the broader project approach, see Legacy application retirement planning. To evaluate how users will find transactions, follow relationships and retrieve documents, explore archived data reporting. These resources complement this Unit4 Agresso-specific scope rather than replace source-system validation.

Evidence and further reading

The report catalogue and screenshots originate from an internal mock-data demonstration. They are not vendor certification or customer implementation evidence.

For version-specific mappings, obtain the applicable vendor documentation and compare it with the installed system. No independently verified, release-specific mapping reference is supplied with this draft.

Fixed-price Unit4 Agresso retirement engagement

ArchiveHub offers a fixed-price engagement for Unit4 Agresso retirement and historical data access, based on an agreed scope, deliverables and acceptance criteria. Request a scoped proposal covering your source systems, data, documents, reporting and validation requirements. The proposal should specify included services, exclusions, ongoing platform or hosting charges, and how scope changes will be handled.

Discuss your Unit4 Agresso retirement requirements with ArchiveHub

Unit4 and Agresso are trademarks of their respective owner. ArchiveHub is not affiliated with or endorsed by Unit4.