Use caseApplication retirement
An unsupported AP server stays on, license and all, for eight years of invoices auditors may ask for. Two people still know how to search it.
Each database row becomes a record with its fileRetention and legal holds are set on arrivalCompliance tests the records before anything is switched off
5.7 million business rows linked to their files. 16,789 invoice rows have no file, and 3,402 files have no row.
source · discovery scan, database and file storeSome items need a person · each one is named, with its reason
In an application like this one, an invoice scan means nothing without its database row: the supplier, the amount, the fiscal year that make it findable. Export the files alone and the auditors get millions of scans with no way in. Keep the application, and you pay for a server to hold an archive.
Row and file travel together and become one record of the repository, with its properties, its retention rule and any legal hold. Compliance tests the records, signs, and only then is the application switched off.
Nothing is switched off until the last link holds: map the rows and the files, design the records and their retention, move and reconcile year by year, then let compliance sign the shutdown. Henrik and Omar map, Claire tests, and Sofia answers the IRS long after the servers are gone.
A document here makes sense only with its database row, so the team maps both before deciding anything else.
Henrik Vos owns the old application. He connects the operations engine to its SQL database and to the store where it kept its scanned files, through a connector set up for this application. The scan links each file to its row and reports the orphans on both sides.
Omar Bashir, the records manager, defines one record class per business object: supplier invoice, purchase order, payment proof, dispute file. Each record takes its properties from the database row, so an invoice is found by supplier, number, fiscal year and amount.
An EDI invoice that never had a file still becomes a record, with its data and no document. The link between an invoice and its purchase order is kept as a link between records.
Claire Russell, the compliance officer, sets the retention of each class with its trigger: invoices and payment proofs ten years after the end of their fiscal year, purchase orders five, dispute files ten after closure.
Two suppliers are under legal hold for an ongoing dispute. Their records get the hold on arrival. While it stands, the planned deletion is suspended, whatever the retention date says.
The application is still running, read-only for finance, while the team moves everything, checks it, and hands compliance the result.
Henrik runs one batch per fiscal year. For each record the operations engine reads the row, fetches its file, applies the class, the retention and the holds, loads the record and checks what arrived.
The reconciliation report compares each fiscal year with the database it came from: rows read, records loaded, files fetched, properties written. Every record has its own line, with the row key next to the new record identifier.
The 3,402 files that no row points to are listed apart, with their original path. Omar decides to keep them as unclassified records.
Claire picks twenty records across classes and years. For each one she checks the class, the retention end date and the hold where it should be. She opens an invoice of Brennan Packaging and sees LH-2024-03 on it.
The records are in place and tested. The application can go, and the people who need the records find them in the repository.
Henrik prepares the shutdown file in the repository: the reconciliation report, the compliance sign-off, the decision on the orphan files and the date the servers go off. Claire signs it. The license is not renewed.
Sofia Marin, in finance audit, gets a request: every invoice from Kerrow Logistics for fiscal 2018. She asks the assistant in plain language. It returns a table of 214 records, names the record class it searched, and offers an Excel export.
She opens the disputed one in the viewer, in the browser, without downloading it.
In January 2027, the invoices of fiscal 2016 reach the end of their ten years. The retention rule starts a review workflow. Omar gets the list, sees that the held records are excluded, and approves the deletion.
The deletion is logged like every other action, so the trail shows what was destroyed, when and on whose decision.
Every fiscal year closes in one of three states. Only the first lets compliance test it and brings the shutdown date closer.
Counts agree with the database, retention and holds are on every record.
What follows: compliance tests a sample and signs the year.A file with no row, a row with a value the rule rejects. Each one is listed with its reason.
What follows: the records manager decides, and only those items run again.Rows read and records loaded do not match for a table or a year.
What follows: the shutdown date waits until the cause is found and a person decides.It switches off no server. It sets no retention period and lifts no legal hold. It deletes nothing on its own. Across the nine steps on this page, the shutdown and every deletion are signed by a named person.
The operations engine moves and reconciles, the repository applies the rules it was given. The periods and the holds belong to compliance, written once and applied to every record.
These counts come from one AP application and its eight fiscal years. Yours will follow your own application and your retention schedule.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
Switching off an application that holds records takes a yes from IT, from compliance and from the people who search the archive. Each yes rests on something different:
You pay every year for a server nobody uses, except to look up old invoices.
You are asked to approve a shutdown without seeing where the records went.
Two people know how to search the old system, and one of them is leaving.
With one fiscal year. Map the tables and files of the application, design the record classes, and move one year as a pilot. One year is enough for compliance to judge the method.
The application keeps running read-only until compliance signs, so finance never loses access to its archive.
Ready to try
Tell us which system stays on only because of what it stores. We will map its tables and files with your team and draft the record classes and the retention schedule.