Payroll data explained: the records behind every pay run

Payroll feels like it’s about money, but underneath it’s about data — two layers of it, mirroring the master-list-and-transaction split that runs through all accounting. Knowing those layers is what makes payroll setup, migrations and audits tractable instead of terrifying.

Layer one: the employee master record

The stable data that defines a person for payroll, set up once and referenced every run:

• Identity — name, address, Social Security number.
• Employment — hire date, status, work location (which drives state tax).
• Compensation — pay rate, frequency, currency.
• Tax setup — the Federal W-4 elections and state/local details.
• Deductions and benefits — the recurring pre- and post-tax items.

Get this record wrong and every pay run for that employee inherits the error — which is why accurate setup is the foundation of correct payroll.

Layer two: the pay-run transaction

Each payroll references the master record and produces a detailed result per employee: earnings (hours, overtime, bonuses), taxes calculated for the run, deductions actually taken, and net pay.

Why the two-layer view helps

It tells you where to look. A recurring error across every check points at the master record; a one-off error points at the transaction. It also explains migrations: moving payroll means carrying the employee master data and, if needed, historical run data — and getting FICA limits right requires bringing prior wages across so year-to-date figures stay accurate.