Pick Payroll Effective Change Interface (PECI) when your third-party payroll vendor must replay every effective-dated worker change in order. Pick Payroll Interface Common Output File (PICOF) (also called Payroll Interface / PI) when the vendor only accepts a net top-of-stack payee extract. The connectors share payroll framework concepts (pay groups, period schedules, run categories) but they do not export the same change story.
Workday’s Global Payroll Connect materials state the decision plainly: PECI uses effective stack processing and reports all changes in sequence; PI/PICOF uses top of stack processing via Get Payees and reports net changes only. Workday recommends PECI for detail, and continues essential maintenance on PI without enhancing that template. Some vendors still require PICOF because their intake cannot consume an effective stack.
How Do PECI and PICOF Differ on Stack and Retro Behavior?
| Topic | PECI (Payroll Effective Change Interface) | PICOF / PI (Payroll Interface Common Output File) |
|---|---|---|
| TopicStack model | PECI (Payroll Effective Change Interface)Effective stack: every change in sequence | PICOF / PI (Payroll Interface Common Output File)Top of stack: net result only |
| TopicPrimary engine | PECI (Payroll Effective Change Interface)Data Initialization Service (DIS) | PICOF / PI (Payroll Interface Common Output File)Get Payees web service |
| TopicMid-period events | PECI (Payroll Effective Change Interface)Multiple staffing and data changes per worker | PICOF / PI (Payroll Interface Common Output File)One staffing event view per worker (net) |
| TopicOutput annotations | PECI (Payroll Effective Change Interface)Section/field flags such as isAdded, isUpdated, isDeleted, priorValue | PICOF / PI (Payroll Interface Common Output File)Net payee payload without PECI’s effective-change sequence |
| TopicVendor fit | PECI (Payroll Effective Change Interface)Engines that apply chronologies and retros carefully | PICOF / PI (Payroll Interface Common Output File)Engines that overwrite current state from a snapshot |
| TopicWorkday roadmap note | PECI (Payroll Effective Change Interface)Preferred for detailed payroll feeds | PICOF / PI (Payroll Interface Common Output File)Essential maintenance only; not the enhancement path |
PECI structures each worker with a worker summary plus one or more effective-change sequences. Education materials describe each effective change with a derived event code, effective moment, entry moment, and only the impacted data sections (unless you enable the include-sections service). Sequence ordering follows how changes became effective in Workday.
PICOF remains the right label when you are configuring Payroll Interface outputs, field overrides for configurable personal information fields, or Studio samples that tag output documents for payroll interface processing. Do not invent vendor-specific column names; configure inclusion through the connector’s field attributes and field overrides.
How Does PECI Change Detection Decide What Exports?
PECI change detection (and the shared method language used for PI) hinges on entry dates, effective dates, last successful run date (LSRD), and pay period bounds:
- Include all changes effective in the pay period — first launch in a period. Exports changes effective in the current period regardless of when they were entered. Future-period effective dates wait for that later period.
- Include only changes entered since the last successful run — incremental launches. Exports changes entered after LSRD that are effective in the current or a prior period.
Important edge behavior documented for PECI:
- An all-effective run does not pick up entry-dated object changes made before LSRD even if they become effective in the current period.
- Entry-dated changes generally must ride LSRD windows; you can enable the attribute that sets effective moment to entry date for non-effective-dated transactions without changing which data returns.
- Full Snapshot seeds the vendor with workers active in the pay group window and does not perform change detection. With Transaction Log enabled, Full Snapshot can produce empty output. Full Snapshot also does not report one-time payments; those appear on standard change detection runs inside the entry and effective ranges.
- Future terminations appear when the effective range includes the day after termination; attributes such as reporting termination on the last day of the pay period change that boundary.
# Wrong first-cycle cutover
1. Enable Transaction Log + Full Snapshot together
2. Expect a full employee seed file with change flags
3. Vendor receives empty or unusable output# Documented cutover pattern
1. Full Snapshot without Transaction Log to seed the vendor
2. Primary runs with All Effective for the first pay period launch
3. Later launches with changes since last successful run
4. Optional Effective Stack Sync sweeper when running frequently with Transaction LogWhich PECI Services Change What the Vendor Sees?
Configure only the services you can explain to payroll operations:
- Transaction Log Service — improves performance by limiting comparison; indirect changes (for example manager reassignment without a subscribed transaction) may not surface unless a qualifying subscribed transaction also occurs.
- Effective Stack - Expanded Effective Changes — expands same-date collapses and can trace rescinds/corrections; enable Transaction Log data section fields or the run errors. Does not support entry data roll-up configurations.
- Include Sections Configuration Service — outputs data sections even when unchanged.
- Effective Stack Sync Service — for frequent primary runs (education materials describe up to every six hours) paired with Transaction Log, plus a daily sync-style run to catch indirect changes without duplicates.
- Event Driven Integration for Third Party Payroll — one primary integration per pay group for near-real-time hire/termination style sends through a business process step (PECI otherwise supports only one business process attachment and does not support Orchestrate).
Documented PECI limits worth citing to sponsors: contingent workers are excluded (use Worker Effective Change Interface for contingents), soft ceiling around very large active populations, one-time payments beyond two years not reported, benefit elections with deduction begin before hire not reported, and no support for dynamic calculated compensation plans (prefer event-driven calculated plans).
How Should Studio and Field Overrides Fit?
Use field overrides (not ad-hoc invented schema) to map Workday values to vendor codes on both PECI and PICOF, including configurable personal information fields. When you need transformation beyond the connector, follow the delivered pattern in Steps: Run the Payroll Interface Sample: a PayData-style extract tagged for payroll interface processing, then a Studio assembly that streams and transforms event documents. Keep connector vs. Studio boundaries clear with Studio vs EIB vs Cloud Connect and debug failed runs with Debug Workday Studio integrations.
What Proves the Connector Choice and Run Mode Are Correct?
- Confirm the vendor contract: effective stack vs. net top-of-stack.
- Launch a controlled sandbox worker through Hire → mid-period compensation change → correction, and compare PECI multi-sequence output against PICOF net output for the same pay period.
- Verify LSRD and change detection method on the launch/schedule parameters for primary vs. incremental runs.
- For PECI, open the integration event and confirm derived event codes and change flags on impacted sections only (unless include-sections is on).
- Reconcile missed retros to entry vs. effective dating before rebuilding field overrides.
Kiweely Vine can help consultants inspect the live integration system configuration, field overrides, and Studio assemblies against the connected tenant with consent, then keep each client’s payroll connector notes isolated while you compare PECI and PICOF behavior on real events.
Frequently asked questions
Is PICOF the same thing as Payroll Interface?
In Workday documentation, Payroll Interface Common Output File (PICOF) is the Payroll Interface connector family that vendors often call PI or PICOF. It uses top-of-stack processing based on Get Payees and reports net changes, not the full effective-dated sequence PECI produces.
When should a vendor insist on PECI instead of PICOF?
Choose PECI when the payroll engine must apply every effective-dated change in order, including mid-period stacks, derived event codes, and field-level change flags. Choose PICOF when the vendor only consumes a net payee snapshot and cannot process an effective stack.
Why did a Full Snapshot PECI run return no changes when Transaction Log was enabled?
Full Snapshot does not provide change detection. When Transaction Log is enabled, that combination can yield an empty output. Use Full Snapshot to seed the vendor without Transaction Log, then switch to normal change detection runs.
Do PECI and PICOF use the same change detection launch methods?
Change detection methods are described the same way for both families: include all changes effective in the pay period for the first run, then include only changes entered since the last successful run for incremental runs. What differs is the output shape: PECI emits the effective stack; PICOF emits net top-of-stack results.