PeopleSoft FSCM Financials → Workday Financials Migration

-- PeopleSoft FSCM → Workday Financials: Chart-of-Accounts Mapping

PeopleSoft FSCM              Workday Financials        Mapping Logic
────────────────────────────────────────────────────────────────────────────────
BUSINESS_UNIT             →   Workday Company ID        | Direct map via VENDOR_SETID lookup
ACCOUNT                   →   Spending Account Ref      | VALUE_MAP.account_type
DEPTID                    →   Spend Category → Cost Center| DEPT_HIERARCHY.parent_wrkctr
FUND_CODE                 →   Worktag: Fund             | CUSTOM_ORG.wrkdtag_fund_id
PROJECT_ID                →   Worktag: Project          | PROJECT.project_wrkdtag_id
PROGRAM_CODE              →   Worktag: Grant            | PS_PROJ_DEFN.grant_cd
ALT_ACCT                  →   Ledger Account            | ACTIVE.gl_nbr = 'Y' → COA_SEG

-- PeopleSoft GL Extraction for Ledger Migration
SELECT JRNL_HDR.JOURNAL_ID,
       JRNL_HDR.JOURNAL_DATE,
       JRNL_HDR.BUSINESS_UNIT,
       JRNL_LINE.ACCOUNT,
       JRNL_LINE.DEPTID,
       JRNL_LINE.AMOUNT,
       JRNL_LINE.MONETARY_AMOUNT
FROM   PS_JRNL_HDR JRNL_HDR
JOIN   PS_JRNL_LN  JRNL_LINE ON JRNL_HDR.JOURNAL_ID = JRNL_LINE.JOURNAL_ID
                             AND JRNL_HDR.JOURNAL_DATE = JRNL_LINE.JOURNAL_DATE
WHERE  JRNL_HDR.FILE_STATUS = 'P'
AND    JRNL_HDR.JOURNAL_DATE BETWEEN :p_start_dt AND :p_end_dt
AND    JRNL_HDR.BUSINESS_UNIT = :p_bu;

-- Workday API: Post Journal Batch (multi-entity consolidation)
POST https://wd2-impl-services1.workday.com/ccx/api/v1/{tenant}/financials/journalEntries

{
  "journalEntrySourceReference": { "ID": "PEOPLE_SOFT_MIGRATION" },
  "companyReference": { "ID": "PSBU-{BUSINESS_UNIT}" },
  "journalEntryLineData": [
    {
      "accountReference": { "ID": "{mapped.account_id}" },
      "amount": { "amount": "{JRNL_LINE.MONETARY_AMOUNT}", "currency": "USD" },
      "memo": "Migrated: {JRNL_HDR.JOURNAL_ID}",
      "customOrganizationReference": { "ID": "{mapped.cost_center}" },
      "spendCategoryReference": { "ID": "{mapped.spend_cat}" }
    }
  ]
}

How we'd take this from discovery to a production-safe cutover — the phases, the canonical mapping, and the edge cases that bite.

This implementation pathway covers the end-to-end migration of PeopleSoft FSCM General Ledger, Accounts Payable, Accounts Receivable, and Fixed Assets modules into Workday Financials, including multi-entity consolidation and chart-of-accounts transformation. The approach assumes a phased extraction from PeopleSoft staging tables, transformation via middleware or ETL, and validation prior to Workday activation.

Implementation Phases

1. Source Extraction & Staging — Extract GL_BALANCE, JOURNAL_LINE, VENDOR, PAYMENT, CUSTOMER, RECEIVABLE, ASSET, and DEPR_DETAIL rows from PeopleSoft into a relational staging schema. Preserve BUSINESS_UNIT, LEDGER_CD, and ACCOUNTING_PERIOD hierarchies. Snapshot AP/AR open items at a defined ledger date; archive closed periods to a separate table to control migration scope.
2. Chart of Accounts Mapping — PeopleSoft uses SETID + ACCOUNT + DEPTID + PRODUCT + PROJECT_ID segments. Map these to Workday's flat account structure with dimension extensions. Build a ACCT_MAP lookup table where PS_ACCOUNT and PS_SETID resolve to WD_ACCOUNT_ID. Validate unmapped accounts before proceeding.
3. GL Migration — Transform GL_BALANCE rows into Workday Ledger transactions. Consolidate multiple PeopleSoft business units into Workday Organizations (company, cost-center, or custom segments). Journal lines must include JOURNAL_ID, JOURNAL_DATE, FISCAL_YEAR, ACCOUNTING_PERIOD, AMOUNT, DEBIT_CREDIT, and mapped ACCOUNT_ID. Balance-validation scripts must confirm debits equal credits per period per ledger.
4. AP/AR Migration — Extract open AP vouchers (VOUCHER, VOUCHER_LINE) and AR items (AR_ITEM, AR_PAYMENT). Map PeopleSoft VENDOR_ID to Workday WORKDAY_SUPPLIER_ID and CUST_ID to WORKDAY_CUSTOMER_ID. Workers and contact persons require mapping to WORKER_ID or CONTACT_ID. Preserve aging buckets and due dates as custom fields or adaptive extensions.
5. Fixed Assets Migration — Extract ASSET, ASSET_ACCTSPV, DEPR_DETAIL, and ASSET_LOCATION. Map ASSET_ID to Workday CAPITAL_ASSET_ID. Carry forward accumulated depreciation, in-service dates, and depreciation rules. Validate that total asset cost minus accumulated depreciation equals net book value per Workday's recalculated balance.
6. Data Validation & Reconciliation — Run pre-validation checks: trial-balance equality, open-item counts, vendor/customer balances, and asset registers. Produce a RECON_REPORT comparing PeopleSoft totals (by FISCAL_YEAR/ACCOUNTING_PERIOD) against staged Workday records. Sign off on each module before enabling Workday.
7. Parallel-Run Audit (UAT) — Run Workday in shadow mode for one full accounting period alongside PeopleSoft. Post identical journal entries in both systems; discrepancies must resolve to zero variance before cutover gate. Test multi-entity consolidation reports and intercompany eliminations.
8. Training & Readiness — Configure Workday roles and security groups mapped from PeopleSoft ROLEUSER/OPRID. Conduct user acceptance testing on Workday-native workflows (expense reports, supplier invoices, customer payments). Validate approval chains and workflow routing.
9. Cutover & Go-Live — Freeze PeopleSoft entries at a defined cutover date and time. Perform final extraction of any incremental transactions. Load into Workday, run final reconciliation, and flip the active ledger. Maintain PeopleSoft in read-only maintenance mode for 30 days post-cutover to support rollback if critical data corruption is discovered.

Field Mapping

Edge Cases

• Segment misalignment — PeopleSoft accounts with fewer segments than Workday's COA will leave dimension fields blank; default values or custom segments must be pre-configured or rows will reject at load.
• Fiscal calendar mismatch — PeopleSoft periods may be 13-period or calendar-month; Workday requires a single fiscal calendar per ledger. Year-end closing entries and adjustments must be reconciled before mapping periods.
• Currency precision — PeopleSoft uses DECIMAL(15,2) or (21,6) depending on setup; Workday uses three-decimal standard. Rounding differences on multi-line journal postings accumulate to cent-level imbalances.
• Open vs. closed items — AP vouchers and AR items with CLOSE_DT prior to the cutover period must be migrated as history, not open items; failing to filter yields inflated open-item counts in Workday.
• Intercompany eliminations — PeopleSoft intercompany journals (INTERUNIT_TEMPLATE) must map to Workday intercompany transaction rules; missing rules produce unbalanced consolidation reports.
• Depreciation convention overrides — Fixed Assets with mid-month or mid-quarter conventions that differ from Workday's default must carry explicit DEPR_START_DATE and CONVENTION values; otherwise Workday recomputes and produces variance.
• Historical journal attachments — PeopleSoft stores document images in PS_ATTACHMENTS; these do not migrate automatically. A document-migration path must be defined or referential links archived separately.

Cutover

Cutover must be fully reversible for at least 30 days. Keep PeopleSoft in read-only maintenance mode with the final incremental extraction stored in the staging schema. Prior to flipping the active ledger, run a LEDGER_BALANCE_COMPARE script that sums all migrated Workday account balances and cross-references the PeopleSoft trial balance report at the cutover date. Any discrepancy exceeding the tolerance threshold (recommended: $0.01 per account) halts cutover and triggers remediation. Once balances reconcile and the consolidation report shows expected entity totals, enable Workday as the system of record. Document the final reconciliation sign-off in the migration audit log with timestamps and responsible-party acknowledgment.