Retiring Infor Lawson S3 means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise accounting-unit context, payroll evidence and grant activity. 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 Lawson read-only 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.

  • The whole Lawson stack. S3 is not a single server: there is the Lawson environment, the application and web tier, the portal and the database underneath it, each on versions that age every year it stays.
  • Database licences and DBA time for a database that only answers lookups.
  • Infor maintenance and support for a product that no longer runs the business.
  • Lawson skills. Knowing which form shows what, how accounting units and activities hang together, or why last year's beginning balances include period 99 is specialist knowledge that walks out of the door with the last Lawson analyst.
  • Security and compliance. Payroll history, employee personal data and bank details sit in a system that must still be patched, monitored and access-reviewed, with auditors and grant reviewers needing accounts of their own.

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 Infor Lawson S3

ArchiveHub archives Lawson S3 by its files, each with its Lawson name and description, so the familiar vocabulary still works.

General Ledger. GLTRANS (General Ledger Transactions), GLAMOUNTS (General Ledger Amounts), GLCONTROL (journal control), GLMASTER and GLNAMES for accounts and accounting units, GLCHARTDTL, GLSRCCODE and GLSYSTEM. Budgets come from FBHEADER and FBDETAIL.

Payables and cash. APINVOICE, APDISTRIB and APPAYMENT, with APVENMAST, APVENADDR and APVENBAL for vendors and APINCCODE for 1099 income codes. CBCHECK, CBTRANS, CBSTATEMNT and CBSTMTDTL cover the Cash Ledger and bank reconciliation.

Receivables. AROIHDR, AROITEMS and ARDISTRIB for open items, ARPYMNTHDR, ARPAYMENT and ARAPPLIED for cash, ARCUSTOMER and CUSTDESC for customers.

Supply chain. ITEMMAST, ITEMLOC, ICTRANS and ICLOCATION for inventory and par locations; REQHEADER, REQLINE and RQLOC for requisitions; PURCHORDER, POLINE, PORECEIVE and PORECLINE for purchasing; MAINVDTL for invoice matching.

HR and payroll. EMPLOYEE and PAEMPLOYEE, PRRATEHIST, PERSACTHST, EMPCODES, PAYMASTR, PRTIME, PAYDEDUCTN, PRDISTRIB, plus QUARTWAGE, QUARTDED and PR941 for quarterly and year-end tax.

Assets, activities and grants. AMASSET, AMASTBOOK, AMTRANS and AMBKHIST; ACACTIVITY, ACTRANS, ACBUDHDR and ACBUDDTL; GMAWARD and GMEFFORT.

Company, accounting unit, account, process level and activity remain the keys they were in Lawson, and every field keeps its description, so ad-hoc queries read like Lawson.

Explore the demonstration

Journal Control list in ArchiveHub Journal Control: archived Lawson GL journal control records, the GL45.1 audit trail, filterable by company and period. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Journal Control detail page in ArchiveHub Journal Control detail: one journal with its control data and posted lines. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Customer Aging in ArchiveHub Customer Aging: open AR items aged at the archive cutoff, as on AR250. 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

  • Transaction Analysis: reference workflow: GL90.1 Transaction Analysis (GLTRANS)
  • Journal Control: reference workflow: the GL45.1 Journal Control audit trail (GLCONTROL)
  • Trial Balance: reference workflow: GL291 Trial Balance from GLAMOUNTS, closed by GL199, with next year's beginning balances including the period 99 close
  • Accounting Units: reference workflow: GL20.1 Accounting Units - Accounts (GLNAMES, GLMASTER)
  • Budget to Actual: reference workflow: FB20.1 Period Budget (FBHEADER, FBDETAIL) against GLAMOUNTS by accounting unit
  • Subledger to GL: reference workflow: the AP, MA, AR, IC, PR, AM, CB and AC closing reconciliations to GLTRANS, by fiscal period

Accounts Payable

  • Invoice Search: reference workflow: AP90.1 Invoice Search by Vendor and Invoice, with AP95.1 Invoice Distributions (APINVOICE, APDISTRIB, APPAYMENT)
  • Cash Payment Register: reference workflow: the AP265 Cash Payment Register and AP91.1 Vendor Activity (CBCHECK, APPAYMENT)
  • Open Payables: reference workflow: the AP230 Open Payables Report, aged by due date at the archive cutoff (APPAYMENT with REC_STATUS below 9)
  • Vendor Master: reference workflow: AP10.1 Vendor (APVENMAST, APVENADDR, APVENBAL)

Accounts Receivable

  • Customer Activity: reference workflow: AR90.1 Customer Activity (AROIHDR, AROITEMS, ARDISTRIB)
  • Cash Batches: reference workflow: AR20.1 Cash Batch and AR30.1 Entry and Application (ARPYMNTHDR, ARPAYMENT, ARAPPLIED)
  • Customer Aging: reference workflow: the AR250 Customer Aging Report at the archive cutoff (AROITEMS, AGINGCODE)
  • Customer Master: reference workflow: AR10.1 Customer (ARCUSTOMER, CUSTDESC), non-patient customers only

Cash Ledger

  • Bank Transactions: reference workflow: CB20.1 Bank Transaction Entry and CB80.1 Bank Transaction Adjustment (CBTRANS)
  • Bank Reconciliation: reference workflow: CB81.1 Reconciliation Statement Maintenance (CBSTATEMNT, CBSTMTDTL) against GL cash

Supply Chain

  • Item Location: reference workflow: IC12.1 Item Location with Inventory Transaction history (ITEMMAST, ITEMLOC, ICTRANS)
  • Par Locations: reference workflow: IC02.1 Location (type P), RQ01.1 Requesting Locations and IC12.2 Replenishment Setup (ICLOCATION, RQLOC, ITEMLOC)
  • Requisitions by Location: reference workflow: RQ40.1 Requisitions by Location and RQ50.1 Issues History (REQHEADER, REQLINE)
  • Purchase Orders: reference workflow: PO20.1 Purchase Order Entry, PO64.1 PO Line Item History and PO30.1 PO Receiving (PURCHORDER, POLINE, PORECEIVE, PORECLINE)

Asset Management

  • Asset Book Analysis: reference workflow: AM90.1 Asset Book Analysis and AM70.1 Asset Analysis (AMASSET, AMASTBOOK, AMTRANS, AMBKHIST)

Grants and Projects

  • Activity Analysis: reference workflow: AC90.1 Activity Analysis, AC10.1 Activity and the Grant Management award (ACACTIVITY, ACTRANS, ACBUDHDR, ACBUDDTL, GMAWARD)
  • Effort Certification: reference workflow: Grant Management effort reporting and certification (GMEFFORT, PRTIME with ACTIVITY)

Human Resources

  • Employee: reference workflow: HR11.1 Employee (EMPLOYEE, PAEMPLOYEE, PRRATEHIST)
  • Personnel Actions: reference workflow: PA52.1 Individual Action history (PERSACTHST, PERSACTYPE)
  • Employee Certifications: reference workflow: certification code type CE (HR04 code setup, EMPCODES, PCODES), status as of the archive cutoff

Payroll

  • Payroll History: reference workflow: PR51.1 Pay Stub Inquiry and PR52.1 Payroll History (PAYMASTR, PRTIME, PAYDEDUCTN, PRDISTRIB)
  • Payroll Hours: reference workflow: PR88.1 Payroll Hours by process level and department per pay period (PRTIME): productive, nonproductive, overtime and paid FTEs

Tax

  • Reportable Income: reference workflow: the AP245 Reportable Income Report, 1099 by payment year (APPAYMENT, APINCCODE), for US companies
  • 941 Information: reference workflow: PR87.1 941 Information by report entity (PR941)
  • W-2 Wage Summary: reference workflow: PR297 W-2 Forms and PR50.1 United States Quarterly Payment Inquiry (QUARTWAGE, QUARTDED), for US companies

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.

Archived documents remain with the records they support. AR invoices, AP invoices and purchase orders carry their PDFs; W-2 and 1099 forms are archived as documents too; employee, vendor, asset and grant records keep their files. A grant auditor sees the award, the activity transactions and the supporting documents together.

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 Lawson file, with Lawson field descriptions and suggested joins (APINVOICE to APVENMAST on vendor, PRTIME to EMPLOYEE on employee).
  • Retention rules and purge with approval, so payroll and HR detail can expire on its own schedule while GL and grant history stays as long as required.
  • Legal hold for litigation, grant audits and payroll disputes.
  • 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 into Excel, Power BI and SAP Analytics Cloud.

How a Lawson decommissioning runs

  1. Extract the Lawson files for each product line in scope, with the data dictionary descriptions.
  2. Validate. Row counts per file, then balances that tie out: AP, AR, IC, PR, AM, CB and AC to GLTRANS by period, GLAMOUNTS to the trial balance, and quarterly wages to the 941 and W-2 totals.
  3. Parallel read access for finance, payroll, supply chain and grants users alongside the old forms.
  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.

Questions about Infor Lawson S3 retirement

Can payroll and grant history use the same access policy?

Do not assume so. Define the groups and sensitive fields each audience can access, then test payroll and grant workflows separately with representative users.

What evidence should Lawson finance sign-off retain?

Keep the agreed source reports, period definitions, row counts and reconciliation outcomes. Record the companies and product lines covered, together with exceptions requiring business approval.

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 Infor Lawson S3 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 Infor Lawson S3-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 Infor documentation 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 Infor Lawson S3 retirement engagement

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

Infor Lawson is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Infor.