Payroll Processing is where ERP discipline either begins or breaks.
Run Regular Payroll (Gross-to-Net Calculation) looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: All employees receive correct net pay on scheduled pay date; payroll journal balances; no manual bank adjustments required.
The control flow a finance team actually needs.
Step 1
Gross-To-Net Engine Apply Withholdings...
Step 2
Payroll Register Reconcile Total Gross...
Step 3
ACH File Conform To NACHA Format
Step 4
GL Posting Use Configurable Account...
Step 5
Pay Run Lock Input Records To Prevent...
The ERP surface involved.
Module
Payroll Processing
Actors
Payroll Administrator, Payroll Engine, GL System
Tier
Tier 1
Finance area
Human Resources, Payroll & Workforce Management
Region lens
US and UK finance teams
Publication date
May 27, 2026
Gross-to-net engine must apply withholdings in IRS-mandated priority sequence; payroll register must reconcile total gross to total net + deductions with zero variance; ACH file must conform to NACHA format; GL posting must use configurable account mapping per pay component and cost center; pay run must lock input records to prevent mid-run edits; processing of 10,000 employees must complete within 15 minutes.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Gross-to-net engine must apply withholdings in IRS-mandated priority sequence | Given a pay group with 10,000 employees having valid salary, time records, and W-4 elections |
| Control 2 | payroll register must reconcile total gross to total net + deductions with zero variance | when a pay run is initiated |
| Control 3 | ACH file must conform to NACHA format | then gross-to-net engine applies withholdings in IRS-mandated priority sequence, payroll register total gross equals total net + all deductions with zero variance, and ACH NACHA file is generated within 15 minutes |
| Control 4 | GL posting must use configurable account mapping per pay component and cost center | negative) when a mid-run edit is attempted on a locked input record then 409 CONFLICT with error code PAY_RUN_PERIOD_LOCKED is returned. |
| Control 5 | pay run must lock input records to prevent mid-run edits | All employees receive correct net pay on scheduled pay date; payroll journal balances; no manual bank adjustments required. |
| Control 6 | processing of 10,000 employees must complete within 15 minutes. | All employees receive correct net pay on scheduled pay date; payroll journal balances; no manual bank adjustments required. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Payroll Administrator initiates the pay run for a defined pay group and period; the payroll engine locks the period and aggregates gross earnings from time records, salary tables, and variable pay inputs; gross-to-net calculations apply federal, state, and local tax withholdings, pre-tax deductions (401k, health), post-tax deductions, and garnishments in statutory sequence; the engine generates a payroll register and net pay file; Administrator reviews exceptions, approves, and the system posts payroll journals to GL and transmits ACH/EFT files to the bank. |
| Control rules | Gross-to-net engine must apply withholdings in IRS-mandated priority sequence; payroll register must reconcile total gross to total net + deductions with zero variance; ACH file must conform to NACHA format; GL posting must use configurable account mapping per pay component and cost center; pay run must lock input records to prevent mid-run edits; processing of 10,000 employees must complete within 15 minutes. |
| Acceptance proof | Given a pay group with 10,000 employees having valid salary, time records, and W-4 elections; when a pay run is initiated; then gross-to-net engine applies withholdings in IRS-mandated priority sequence, payroll register total gross equals total net + all deductions with zero variance, and ACH NACHA file is generated within 15 minutes; (negative) when a mid-run edit is attempted on a locked input record then 409 CONFLICT with error code PAY_RUN_PERIOD_LOCKED is returned. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`pay_run` { id: string, external_id: string, pay_group_id: string, period_start: date, period_end: date, pay_date: date, status: enum(DRAFT,PROCESSING,PENDING_APPROVAL,APPROVED,PAID,VOID), employee_count: int, gross_total_minor: int64, currency_code: char(3) }; `payroll_line` { id: string, pay_run_id: string, employee_id: string, gross_minor: int64, net_minor: int64, currency_code: char(3), external_id: string }; (reference, product may differ).API and events
`POST /v1/pay-runs` { pay_group_id, period_start, period_end, pay_date } -> 201 { id, status: "DRAFT" }; `POST /v1/pay-runs/{id}/process` -> 202 async; `GET /v1/pay-runs/{id}/register` -> 200 { lines[], gross_total_minor, net_total_minor, currency_code }; `GET /v1/pay-runs/{id}/ach-file` -> 200 NACHA binary; emits `payroll.pay_run_approved`, `payroll.ach_generated`; idempotent via `external_id`.State transitions
`DRAFT -> PROCESSING -> PENDING_APPROVAL -> APPROVED -> PAID`; terminal `VOID`; guard: transition from PROCESSING blocked if any employee input record is edited; transition to APPROVED blocked if register gross ≠ net + deductions; transition to PAID requires ACH file generated.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.