PA03 — Payroll Control Record
PA03 maintains the payroll control record for a payroll area, not employee Infotype 0003. It controls the current payroll period and payroll-run status, such as release for payroll, release for correction, and exit payroll. The control record also governs whether payroll-relevant master data can be changed while a payroll run is in progress.
This page covers PA03, the transaction used to edit infotype 0003 (Payroll Status) fields that are normally system-maintained and locked against manual change in PA30. It focuses on the diagnostic reasons a consultant ends up here mid-incident: stuck retro accounting, locked personnel numbers, and mismatched payroll dates.
Published 20 Sept 2026· 681 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
PA03 maintains the payroll control record for an entire payroll area. The control record is a payroll-process control object: it identifies the period being processed and moves the payroll area through controlled statuses during the payroll cycle. It is not a personnel-number maintenance transaction and should not be confused with PU03, which is used for employee Payroll Status (Infotype 0003).
When it is used
Payroll administrators use PA03 at the start, correction phase, and completion of a payroll cycle. Typical activities include releasing a payroll area for payroll, releasing it for corrections when permitted, checking which period is active, and setting the payroll area to Exit Payroll after processing is complete. Employee Central Payroll documentation also uses PA03 to check the payroll-area status before off-cycle processing.
How to use it in practice
- Enter the payroll area and display the current control record before changing anything.
- Confirm the payroll period and current payroll status against the payroll calendar/runbook.
- Move the status only to the next state required by the controlled payroll process; do not use status changes to bypass unresolved payroll errors.
- When the area is released for payroll, understand that payroll-relevant master-data changes for the payroll past/present are controlled by that status.
- After the payroll run and required corrections are complete, move to the approved final status and verify downstream posting/payment activities according to the payroll calendar.
Key data objects
The important evidence in PA03 is payroll-area level, not employee-infotype level.
- Payroll area — the population controlled by this payroll control record.
- Current payroll period — the period the payroll area is processing.
- Payroll status — for example Released for Payroll, Released for Correction, or Exit Payroll, depending on the stage.
- Retroactive-accounting boundary/control information — review it in the context of the payroll area and payroll calendar.
- Authorization — access to display/change the payroll control record is governed separately from ordinary HR master-data maintenance.
How to prove it in the data
Use PA03 to capture the payroll area, current payroll period, and status, then compare those values with the payroll driver log and the affected employee's payroll-area assignment. If one employee has a retro or lock problem while the payroll-area control record is correct, move the investigation to employee Payroll Status (Infotype 0003) using PU03/appropriate display tools rather than changing PA03.
ECC vs S/4HANA
PA03 remains the payroll control-record transaction in SAP HCM for SAP S/4HANA and in Employee Central Payroll. SAP's current Employee Central Payroll documentation explicitly identifies PA03 as the transaction that defines the current payroll period/status and controls payroll-relevant master-data changes during the payroll run.
Common pitfalls and how to diagnose them
- Confusing PA03 with Infotype 0003 maintenance — PA03 controls a payroll area; PU03 works with an individual employee's Payroll Status record.
- Changing payroll status to make a payroll error disappear — status transitions should follow the payroll runbook and do not correct schema, master-data, or payroll-result errors.
- Using the wrong payroll area — verify the employee's payroll-area assignment for the relevant date before concluding the control record is wrong.
- Leaving the payroll area in a restrictive status longer than intended — this can block permitted payroll-relevant master-data corrections and replication.
Whose problem this is
PA03 is owned by Payroll Operations/Payroll functional administration. Security owns access to the payroll control record, while Basis or ABAP becomes relevant only when the payroll runtime itself has a technical failure. Production status changes should follow the organization's payroll calendar and segregation-of-duties controls.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/pa03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.