Retiring Acumatica means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise closed projects, billing relationships and retainage balances. 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 Acumatica "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.

On premises, a legacy system costs you hardware and DBAs. With a SaaS ERP like Acumatica the cost is simpler and harder to ignore:

  • A subscription you pay just to read history. The tenant renews on its own schedule, whether anyone has posted a transaction this year or not.
  • Upgrade cycles you no longer care about. New Acumatica versions still arrive, and customisations, reports and integrations still have to be checked after each one.
  • Partner and admin time. Someone has to keep user access, roles and the occasional custom report working, often through a reseller agreement nobody else remembers.
  • Audit-access workarounds. Owners, sureties, auditors and claims consultants get spreadsheet exports or temporary user licences. Neither gives you a clean, logged trail.
  • Fading know-how. Fewer people each year know which screen holds the retainage release, or how a pro forma relates to an AR invoice.

Moving the history out can support ending or reducing renewals where the contract and remaining workloads permit. How much you save depends on your contract, so we won't put a figure on it.

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 Acumatica

ArchiveHub keeps the Acumatica data model with the native table and screen names, so a project accountant still recognises everything:

  • General Ledger: Batch and GLTran behind Journal Transactions (GL301000), GLHistory by branch, ledger, account, subaccount and period, Account and Sub for the account/subaccount structure, and GLBudgetLine and GLBudgetLineDetail for budgets.
  • Payables and Receivables: the shared document headers APRegister and ARRegister, with APInvoice, APTran, APPayment and APAdjust on one side and ARInvoice, ARTran, ARPayment and ARAdjust on the other. Business accounts sit in BAccount, with Vendor, Customer, Address and Contact.
  • Projects: Contract (projects are the PMProject projection of it), PMTask, PMBudget with cost and revenue lines, PMTran behind Project Transaction Details (PM401000), PMChangeOrder with its budget and commitment lines, PMProforma and PMProformaLine for pay applications, and PMCostCode.
  • Purchasing and subcontracts: POOrder and POLine, with order type RO for purchase orders and RS for subcontracts.
  • Compliance: ComplianceDocument with its attribute types for lien waivers, insurance certificates and licences.
  • Payroll, time and HR: PRPayment, PREarningDetail, PRPaymentTax, PRPaymentDeduct, EPTimeCard, PMTimeActivity, EPEmployee and PREmployee.
  • Cash Management and Fixed Assets: CATran, CARecon, CATransfer and CAAdj, and FixedAsset, FADetails, FABookBalance and FATran. Taxes sit in TaxTran.

In the demonstrated scope, each field keeps its Acumatica name and comes with a description, so an ad-hoc query reads the way an Acumatica consultant would write it. The quarter-end AP and AR aging snapshots are rebuilt from the register and adjustment tables, and they are labelled as archive-derived, not native tables. Retainage is kept out of aging and reported in its own retained-balance reports.

Explore the demonstration

Journal Transactions list in ArchiveHub Journal Transactions: Acumatica GL batches from every module, with module, period and totals. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Journal Transactions detail page in ArchiveHub Journal Transactions detail: one GL batch with its GLTran lines by account and subaccount. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

AP Aging list in ArchiveHub AP Aging: open vendor balances by aging bucket at a fiscal quarter end. 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

  • Journal Transactions: reference workflow: Journal Transactions (GL301000), the GL batches of all modules (Batch, GLTran)
  • Account Details: reference workflow: the Account Details inquiry, GL transactions by account and subaccount (GLTran)
  • Trial Balance: reference workflow: the Trial Balance report and Account Summary from GL history (GLHistory), with income and expense reset each year and net income carried into Retained Earnings
  • Chart of Accounts: reference workflow: the Chart of Accounts (Account, Sub), with balance history by branch
  • Budget vs Actual: reference workflow: Budgets (the budget ledger in GLBudgetLine/GLBudgetLineDetail) compared with actual GL history by period
  • Subledger to GL Reconciliation: reference workflow: AP/AR Balance by GL Account, the cash and fixed asset reconciliations and payroll-to-GL by department: subledger activity against GL control accounts by period

Payables

  • Vendors: reference workflow: Vendors (BAccount, Vendor, Address, Contact), with balances, subcontracts and compliance
  • Bills and Adjustments: reference workflow: Bills and Adjustments (AP301000): AP bills and retainage bills with lines, payments and GL (APRegister, APInvoice, APTran)
  • Checks and Payments: reference workflow: Checks and Payments: AP checks and electronic payments with applications and lien waivers (APRegister, APPayment, APAdjust)
  • AP Aging: reference workflow: the AP Aging report by vendor at fiscal quarter ends (snapshots rebuilt from APRegister/APAdjust)
  • AP Retained Balance: reference workflow: AP Retained Balance (AP635000): retainage withheld on subcontractor bills, released and outstanding

Receivables

  • Customers: reference workflow: Customers (BAccount, Customer, Address, Contact), with projects and balances
  • Invoices and Memos: reference workflow: Invoices and Memos: progress billing and retainage invoices with lines, payments and GL (ARRegister, ARInvoice, ARTran)
  • Payments and Applications: reference workflow: Payments and Applications: customer payments applied to progress and retainage invoices (ARRegister, ARPayment, ARAdjust)
  • AR Aging: reference workflow: the AR Aging report by customer at fiscal quarter ends (snapshots rebuilt from ARRegister/ARAdjust)
  • AR Retained Balance: reference workflow: AR Retained Balance: retainage withheld by owners on progress billings, released and outstanding (ARRegister)

Projects

  • Projects: reference workflow: Projects (PM301000): contract, budget, change orders and subcontracts per project (Contract/PMProject, PMTask, PMBudget)
  • Project Cost Budget: reference workflow: the Cost Budget tab of Projects (PM301000): original, change orders, revised, committed and actual by task and cost code (PMBudget)
  • Project Transaction Details: reference workflow: Project Transaction Details (PM401000): cost and revenue transactions by project, task and cost code (PMTran)
  • Change Orders: reference workflow: Change Orders: revenue, cost budget and subcontract commitment changes (PMChangeOrder, PMChangeOrderBudget, PMChangeOrderLine)
  • Pro Forma Invoices: reference workflow: Pro Forma Invoices and the AIA Report (PM644000): progress billing applications with schedule of values (PMProforma, PMProformaLine)
  • Project WIP: reference workflow: Project WIP (PM651500): percent complete, earned revenue and over/under billing by project and period, with quarter-end figures equal to the WIP adjustment journals
  • Compliance Management: reference workflow: Compliance Management (CL401000): lien waivers, insurance certificates and subcontractor licences (ComplianceDocument)

Purchasing

  • Purchase Orders: reference workflow: Purchase Orders for job materials with bills (POOrder type RO, POLine)
  • Subcontracts: reference workflow: Subcontracts (SC301000): subcontracts with change order lines, pay applications, retainage and lien waivers (POOrder type RS, POLine)

Payroll & HR

  • Employees: reference workflow: Employees and Payroll Employees (EPEmployee, PREmployee, EPEmployeePosition), with pay history
  • Paychecks and Adjustments: reference workflow: Paychecks and Adjustments / the payroll register: earnings by project, taxes, deductions and employer contributions (PRPayment, PREarningDetail, PRPaymentTax, PRPaymentDeduct)
  • Employee Time Cards: reference workflow: Employee Time Cards: weekly time by project, task and cost code (EPTimeCard, PMTimeActivity)

Cash Management

  • Reconciliation Statements: reference workflow: Reconciliation Statements: monthly bank reconciliation of each cash account with cleared transactions (CARecon, CATran)

Fixed Assets

  • Fixed Assets: reference workflow: Fixed Assets: construction equipment, vehicles and office assets with depreciation and disposals (FixedAsset, FADetails, FABookBalance, FATran)

Tax

  • Tax Details: reference workflow: the Tax Details and Tax Summary reports by tax period and document (TaxTran)

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.

In construction, the document often matters more than the number. ArchiveHub keeps the archived files attached to their records: AP bills, subcontracts, change orders, pay applications, lien waivers, insurance certificates and licences, bank statements, projects, employees and fixed assets. When a lien or payment dispute surfaces years after closeout, the signed waiver is attached to the record it belongs to.

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 Acumatica table, with native field descriptions and suggested joins (for example POOrder to PMChangeOrderLine to APTran).
  • Retention rules with approved purge, so project and payroll records are deleted on schedule, and only after sign-off.
  • Legal hold on a project, vendor or customer while a claim is open.
  • 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 for Excel, Power BI and SAP Analytics Cloud.

How the decommissioning project runs

  1. Extract. The tenant's data is pulled out table by table while the subscription is still active, keeping native keys and names.
  2. Validate. Row counts are compared table by table. The trial balance from GLHistory must tie to Acumatica's, and AP, AR, cash, fixed asset and payroll subledgers must tie to their GL control accounts. Project budgets, commitments and retainage balances are checked too.
  3. Parallel read access. Project accountants, payroll and finance use ArchiveHub while the tenant is still live and confirm that the answers match.
  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.

Plan a controlled subscription exit

Your closed projects still have to be answerable. They don't need a live ERP subscription for that. Keep the history, the reports and the paperwork in ArchiveHub, and let the Acumatica tenant go.

Questions about Acumatica retirement

Should retainage be treated as ordinary receivables aging?

Define the required treatment with the finance owner and validate it against source outputs. Keep retained balances distinguishable where required rather than assuming an ordinary aging report covers them.

When can an Acumatica tenant be closed?

After accepted extraction and reporting tests, document retrieval, permission checks and contractual review. Confirm remaining integrations and entities before scheduling the exit.

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 Acumatica 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 Acumatica-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.

Use Acumatica Help to locate the documentation for the installed release. This is a documentation entry point, not verification of every table or report mapping in this article.

Fixed-price Acumatica retirement engagement

ArchiveHub offers a fixed-price engagement for Acumatica 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 Acumatica retirement requirements with ArchiveHub

Acumatica is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Acumatica, Inc.