Getting payroll results out

The biggest routine extract in the system, and three ways it fails: too big, too slow, or quietly early. The shape that avoids all three, and why each choice is made.

RuleExtract completed runs by pay period, land them unchanged, and build on top. Rerun any period, get the same answer.

Neverpull payroll during the close window or while a run is processing. The extract competes with the people doing payroll.

◆ What goes wrongthe plain version.

Payroll is the largest routine extract in the system: every person times every kind of pay times every period. Pull it naively and one of three things happens. The report exceeds the size a single response can carry and fails. It exceeds the time a report is allowed to run and fails. Or it succeeds and quietly includes a run still being processed, so the numbers change when you pull again. Two failures are loud. The third is a wrong answer.

◆ The shape that workscompleted runs, one period at a time, landed unchanged.

Period by period, finalised only, kept as received. Any period can be pulled again and match.

Choice	Why
Completed runs only	A run still processing is a moving target. Extracting finalised results means the same pull gives the same answer tomorrow, which is what makes the ledger tie repeatable.
One period per pull	The size and time limits are per report. A period at a time stays far inside both, and a failed pull loses one period, not the history.
Landed unchanged	The raw layer holds exactly what the source sent, dated. When a number is questioned, the answer starts from evidence, not from a transformation someone has to unwind.
Off the close calendar	Extraction competes with payroll processing for the same system. The schedule runs after runs complete and never during the close window. Practitioner guidance, to be confirmed in the customer system.

Corrections from the off cycle page are the one wrinkle: a correction can land in a period already extracted. The period of the correction is pulled again, which is cheap precisely because pulls are one period at a time.

Use case

Problem

Payroll extracts fail three ways: too large for one response, too long for the time limit, or pulled mid-run so the numbers move afterward. Two are loud, the third is a wrong answer.

What we build

Completed runs only, one period per pull, landed unchanged in a raw layer, scheduled clear of processing and close. Corrections trigger a fresh pull of their period.

What you get

An extract that reruns to the same answer, fails small when it fails, and never hands the model a number that is still moving.

Want the extract that survives contact with month end?

We wire the period pulls, the raw landing, and the schedule that stays out of the way.

Talk to us

Terms on this page

extract: Pulling data out of the source system on a schedule.
completed run: A payroll run that is finalised. Anything earlier gives numbers that still move.
pay period: The span one payroll run covers.
raw layer: Where extracted data lands exactly as received, dated, before anything is built.
close window: The days each month when the books are being finalised.
pull: One scheduled extraction of one pay period.
correction: An off cycle payment changing a period after it was extracted.