Analytics Catalog/Workday/Payroll/Off cycle payments
Workday · Payroll · Object

Payments outside the normal run

The regular run is the easy part. Corrections are where the person gets paid right and the books go wrong. Three kinds, what each does to the accounting, and the check that pairs them.

RuleCarry the run type on every fact row, so corrections are countable, auditable, and separable from regular pay.
Nevernet corrections into regular pay in the model. A reversal that vanishes into a total cannot explain the books it changed.
A correction pays the person made right Three kinds each with its entries The pairing check reversals matched or flagged
The person gets paid right and the books go wrong; the three kinds and the pairing check keep both right.
◆ What goes wrongthe plain version.

Most pay moves in the regular run. The rest moves in corrections: someone was paid wrong, paid late, paid twice, or paid outside the system and the record has to catch up. Workday documents three kinds, manual, on demand, and reversal, and picking the wrong one is a classic way to duplicate or drop cost. The mistake is quiet: the person ends up paid correctly while the accounting behind the payment is wrong.

◆ The three kindswhat each is for, and what it does to the books.
KindWhen it is usedWhat it does to the books
Manual paymentThe person was already paid outside the system, a handwritten check in a crisis, say. The record has to catch up.Creates the accounting entries without moving money. The danger is using it when money did not already move, which records cost for a payment nobody made.
On demandAn urgent real payment that cannot wait for the next run: a missed new hire, a final paycheck due by law.Moves money and creates entries, a calculation for one person, flagged Replacement or Additional. Easy to double: an Additional payment for pay the next regular run also carries pays the person twice.
ReversalA payment that should not have happened.Backs out the original entries in full. The cost disappears from the books, correctly. A reversal with no replacement payment leaves the person unpaid; the books are right and the person is not.

Workday lists no reissue kind (status October 2026). A payment that replaces a reversed one runs as an on-demand or manual payment flagged Replacement, and the pairing check below treats it as the reversal's partner.

Every failure in this table is a pairing failure: a payment and its correction that should reference each other and do not. The source system knows each event. What it does not readily show is the pair.

◆ What we buildcorrections as first-class rows, and the orphan check.

Every fact row carries its run type, and correction rows carry a reference to the payment they correct. That one column turns the pairing failures above into a query.

-- corrections with no partner: reversals and replacements pointing at nothing
SELECT f.run_type,
       f.worker_key,
       f.amount,
       f.corrects_payment_id
FROM fct_payroll_result_line f
JOIN dim_date d ON f.accounting_date_key = d.date_key
LEFT JOIN fct_payroll_result_line p
       ON f.corrects_payment_id = p.payment_id
WHERE d.fiscal_period = '2026-05'
  AND f.run_type IN ('reversal','on_demand_replacement','manual_replacement')
  AND p.payment_id IS NULL
ORDER BY f.amount DESC

The paired and orphaned lines are all rows of the payroll cost star.

Empty result, every correction has its partner. Any rows, and each is a person, an amount, and a correction pointing at a payment that is not there: the exact list to resolve before close, instead of a difference to hunt for after it.

Use case
Problem
Corrections fix the person and quietly break the books: doubled pay, vanished cost, reversals with no replacement. The source records each event but not the pair, so the damage surfaces weeks later as a difference nobody can explain.
What we build
Run type on every fact row and a correction reference linking each fix to the payment it fixes, with an orphan check that runs before close.
What you get
Corrections you can count, pairs you can prove, and a named list of unresolved fixes each period instead of a mystery difference after it.
Want corrections that explain themselves?
We model the run types, wire the pairing, and the orphan list lands before close, not after.
Talk to us
Terms on this page
off cycle
A payment made outside the regular payroll run.
manual payment
Recording a payment already made outside the system. Entries without money movement.
on demand
An urgent real payment run for one person. Money and entries both.
reversal
Backing out a payment that should not have happened.
replacement
An on-demand or manual payment that takes the place of the regular payment for a period.
additional
An on-demand or manual payment made on top of the regular payment.
run type
The column on every fact row saying which kind of run produced it.
orphan
A correction whose referenced payment cannot be found.
close
The monthly process of finalising the books.