# Automation data retention: reconcile PDPA, accounting records and execution logs

> Separate business records from automation logs. Reconcile PDPA, GST and employment-record duties with short-lived platform history.

Source: https://www.fyadvisers.com/blog/workflow-automation-data-retention-audit-logs/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

A workflow can place one document in an inbox, an accounting system, a run history and a support ticket. Those copies do not need the same life. Decide which copy is the business evidence, which copy is temporary processing, and who can still retrieve each one after the others are gone.

This page is the retention map. It is not a full PDPA manual, and it is not the [n8n hosting](/blog/n8n-self-hosting-pdpa-singapore/) article. Invoice approval evidence is discussed in the [invoice guide](/blog/invoice-approval-workflow-automation-singapore/). Employment files meet the same problem in [onboarding](/blog/employee-onboarding-workflow-automation-singapore/) and [offboarding](/blog/employee-offboarding-access-revocation-workflow/).

## Inventory the copies

| Class | Typical place | Usual role |
|---|---|---|
| Source file | Restricted library | Evidence, if the business needs the original |
| Extracted fields | A table or a model’s output | A proposal until validated. Often over-retained |
| Transaction | Accounting, payroll, purchasing | Often the system of record |
| Approval event | A row you designed | The decision, the version, the actor, the time |
| Run log | Power Automate, n8n, a script host | Operations. Short life unless you promote it |
| Error payload | The same tools, plus a ticket | Often the most sensitive copy |
| Export and backup | Support zip, snapshot, mailbox | The copy that survives a careless delete |

For each class, write the purpose, the system of record, who can read it and the rule for how long it stays. “The workflow keeps it” is not a purpose.

## Retention limitation is not a number of days

The PDPC’s [Advisory Guidelines on Key Concepts](https://www.pdpc.gov.sg/-/media/Files/PDPC/PDF-Files/Advisory-Guidelines/AG-on-Key-Concepts/Advisory-Guidelines-on-Key-Concepts-in-the-PDPA-17-May-2022.pdf) (17 May 2022) describe the retention limitation obligation. Organisations should cease to retain documents containing personal data, or remove the means of associating the data with particular individuals, when it is reasonable to assume the purpose of collection is no longer served and retention is no longer necessary for legal or business purposes. The guidelines do not prescribe one fixed period for every workflow.

The same guidelines describe a protection obligation: reasonable security arrangements for personal data in the organisation’s possession or control. A log that everyone in an operations channel can download is a protection problem as well as a retention problem. The transfer limitation is a separate question when a log or a backup leaves Singapore. Hosting the app locally does not settle it. FYAdvisers is not a law firm. This article does not decide your schedule.

Business contact information is not a blanket exemption. The guidelines explain that the Data Protection Provisions generally do not apply to business contact information, depending on purpose and context. Payloads with identity numbers, home addresses, signatures or employee salary fields are outside that comfortable assumption.

## GST records and employment records are different rules

IRAS’s [record-keeping page](https://www.iras.gov.sg/taxes/goods-services-tax-(gst)/basics-of-gst/invoicing-price-display-and-record-keeping/keeping-records) says you must keep GST records for at least five years from the end of the accounting period. The page lists tax invoices, receipts, credit notes, bank statements and other source records. If you change software, IRAS expects the old accounting transactions and the associated business documents to remain retrievable. You are not required to migrate them into the new product, but you are required to be able to produce them.

That five-year period does not mean every failed execution payload is a GST record. It also does not mean you should delete a record on day one of year six if another purpose still requires it.

MOM’s [employment records](https://www.mom.gov.sg/employment-practices/employment-records) page applies to employees covered by the Employment Act. Current employees: the latest two years. Former employees: the last two years of records, kept for one year after they leave. It does not authorise deleting every former-employee file on that date. Tax, disputes and contracts may need longer. The automation consequence is narrower: do not build a job that purges an HR system because a log-retention setting said 30 days.

## Platform history is the wrong archive

Microsoft’s [limits page](https://learn.microsoft.com/en-us/power-automate/limits-and-config) lists run retention in storage as 30 days from the run’s start, and a 30-day run duration that includes pending approvals. A decision you must show an auditor next year cannot live only in that history. The [long-running approval](/blog/power-automate-long-running-approval-workflow/) design puts the decision on a record you operate. Exporting that record into a controlled store, with access that is not “everyone who can edit flows”, is the practical control.

n8n’s [execution data](https://docs.n8n.io/hosting/scaling/execution-data/) guidance says to avoid saving data you do not need and to prune what you save. Pruning is described as enabled by default. The page checked for this article showed a default time threshold of 336 hours and a default count of 10,000 finished executions, with annotated executions excluded from pruning. Those are documentation defaults for the version the page described. They are not a legal period and not a reason to keep, or to delete, GST or employment records. Confirm the values on the instance you run. Unfinished and failed executions need an explicit rule because they are where payloads hide.

## Holds, deletion, vendors

A legal hold has to be able to pause the deletion job for the classes it names. Test it. A deletion that does not touch the support export is a failed test: the payload is still there. A restore test that brings a deleted payload back is a success only if you expected the backup to do that, and you know when that backup itself expires.

When a vendor’s contract ends, definitions, business records and credentials need an exit that you have tried. The vendor cannot invent the legal schedule from a template. Finance owns the GST call. HR owns the employment-record call. The person who advises on personal data owns the PDPA call. The workflow owner’s job is to make the systems follow those calls, including the copies in [system integration](/services/system-integration/) queues.

## Tests

1. A payload deleted from the app is still inside a support export. The test fails until the export is covered.
2. An invoice that must be kept is still retrievable after the platform’s run history has expired.
3. A hold stops the deletion job for the affected class and does not stop every unrelated log.

Illustrative scenario, not a client engagement: an invoice workflow stores the supplier’s PDF and the approval row in the finance library, which is the record the business would produce. Extraction text and debug payloads follow a shorter schedule that finance and the privacy lead have agreed, because those copies are not needed once the bill is posted and no dispute is open. The platform’s own history is allowed to expire. Nobody treats that expiry as destruction of the GST record.

To list every copy of one document you already process, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Which system should an auditor use?

The one you name as the record: usually the accounting, HR or purchasing system, plus the approval row you store on purpose. An auditor should not need an admin login to every automation tool to see a decision that the business relies on.

### Do retention rules include backups and failed runs?

They have to, or deletion is theatre. Failed runs and support exports often hold the fullest copy of a payload. Backups restore what you thought you had deleted. Write the backup cycle into the same schedule and test it.

### Is five years the retention period for every workflow?

No. IRAS requires GST records to be kept for at least five years from the end of the accounting period. That is a GST rule. It is not a retention period for employee files, debug logs or unrelated personal data, and it is not an instruction to delete other records on that anniversary.

### Can the automation vendor set the legal retention schedule?

No. A vendor can say what their product deletes by default. Finance, HR and the person responsible for personal data decide what the business must keep. The workflow then has to be able to follow that decision.
