PeopleSoft Data Archival Built for Compliance

PeopleSoft data archival is the process of moving closed-period transactional data, terminated employee records, and historical payroll detail out of the operational PeopleSoft database into a queryable long-term archive. Organizations archive PeopleSoft data for three reasons: compliance retention (SOX 7 years, IRS 7 years, HIPAA 6+ years, FERPA indefinite for student records), database-size control (PS_LEDGER and PS_JRNL_LN grow at 200M–400M rows per year in mid-size customers), and migration prep (a smaller production footprint is faster, cheaper, and less risky to migrate to Fusion). Syntra ETL's PeopleSoft data archival routes cold data to cloud object storage in Parquet, leaves stubs and access logs in the source system if needed, and exposes a SQL/REST query interface so auditors and tax authorities can still read the data on demand.

Retention requirements vary by data domain and regulation. General Ledger and AP/AR detail: 7 years (SOX, IRS in the US; 6 years HMRC in the UK; up to 10 years in some EU jurisdictions). Payroll: 7 years (IRS), with W-2/T4 data often kept longer for individual employee lifetime claims. HCM employee records: 7 years post-termination at federal US level, longer in many states and EU under labor law. Higher education student records (Campus Solutions): typically indefinite under FERPA-aligned institutional policy. Healthcare HCM under HIPAA: 6 years minimum, often longer. Syntra ETL's archival policies are configurable per domain so each data class meets its own retention rule without paying to keep everything everywhere.

Yes. The PeopleSoft data archival path preserves the source table schema — column names, datatypes, PSRECDEFN-defined record structure — in the archive. Archived data lives as Parquet with embedded schema, plus a JSON Schema sidecar for tooling. The archive query interface lets auditors run familiar SELECT statements against PS_LEDGER, PS_VOUCHER, PS_PAY_CHECK and so on, returning results that match what they would have seen in the live PeopleSoft database — including effective-dated history, ChartField context, and sub-ledger source references. No translation, no schema flattening, no data shape changes.

Code itself isn't archived as data — it's preserved as a customization inventory artifact. Syntra ETL's discovery engine catalogs every PeopleCode script (PSPCMPROG), App Engine program, Component Interface, and Integration Broker service in the source system. The catalog includes source code, version history, last-modified date, and (where derivable) the business purpose. This serves two needs: post-decommission audit evidence ('what did our PeopleSoft system actually do?') and migration support ('what custom logic did we need to re-implement in Fusion?'). The catalog is signed, timestamped, and retained per the same retention rules as the data.

Yes, for organizations that have completed migration to Fusion and no longer need operational PeopleSoft. The Syntra archive holds the complete data, the customization catalog, the security model snapshot, and the reporting library — everything an auditor would otherwise demand a live PeopleSoft instance for. Customers save 70–90% on PeopleSoft licensing, Oracle Database support, infrastructure, and maintenance staff. The archive query interface satisfies SOX, IRS, HMRC, HIPAA, and FERPA access requirements for the full retention window, with sub-second query response and signed, timestamped evidence packs.

Access is role-based with mandatory audit logging. Every query against the archive is logged with user, timestamp, query text, rows returned, and data classification accessed. Archive data is encrypted at rest with KMS-managed keys and in transit with TLS 1.3. Sensitive HCM and payroll data (SSN, bank account, salary detail) is masked by default and requires explicit role permission to unmask. Higher-education customers using the archive for FERPA-covered student records get separate role partitioning so registrar-level access doesn't bleed into general finance access.

Yes. The Syntra archive exposes a standard SQL interface (JDBC/ODBC), so any BI or audit tool that connects to a relational database — Tableau, Power BI, Alteryx, ACL, IDEA — works without modification. There's also a REST API for programmatic access, and the underlying Parquet files can be queried directly from Athena, BigQuery, Snowflake, or Spark if your audit team prefers warehouse-native access. Standard auditor extracts (GL detail by period, AP voucher detail with vendor, payroll register) ship as pre-built saved queries.

Sub-second for typical auditor queries (a single GL period for a single ledger, an AP voucher lookup, a vendor history for a single supplier). Multi-period or multi-year aggregation queries against billion-row PS_LEDGER history typically return in 5–30 seconds depending on partitioning. Archive data is stored in Parquet partitioned by fiscal year, period, business unit, and ledger, and the query engine uses column pruning and partition pruning to minimize scan. For year-end audits, customers commonly pre-materialize an auditor-facing dataset (trial balance, AP aging, asset register snapshots) for instant access.