Factory payroll: piece-rate, daily wage and monthly staff in one run

Why spreadsheets fail for mixed factory payroll

A plant that pays some staff by the piece, others by the day and a third group by the month will typically run three separate spreadsheets. Each sheet has its own rules, its own reconciliation against attendance, and its own cut-off date. When the finance team consolidates the three, rounding errors, duplicate advances and missing shift allowances surface. The result is a two-day fire drill every payday, and an audit trail that consists of emailed spreadsheets with conflicting timestamps.

Spreadsheets also lack the ability to enforce approvals. A supervisor can change a piece-rate count after the shift has closed, and there is no log of who made the change or when. When the same system is used to calculate product costing, the error propagates into inventory valuation and gross margin reports.

Map each worker type to a single payroll ledger

Fugen ERP maintains one payroll ledger per employee, regardless of payment method. The ledger has four sections:

• The employee master holds the payment method (piece-rate, daily-wage or monthly), the base rate, and any fixed allowances such as housing or transport.
• The attendance register records clock-in, clock-out, shift code and any unpaid leave.
• The earnings section captures variable components: piece counts, overtime hours, night-shift premiums and advances.
• The deductions section lists statutory contributions, loan repayments and any garnishments.

When the payroll run is triggered, the system applies the correct formula to each section and posts a single journal to the finance module. There is no manual consolidation, and the audit trail is maintained at the transaction level.

Data you must capture on the shop floor

Piece-rate workers: each operator must scan a job card at the start and end of every bundle. The card carries the style code, the operation code, the standard minutes per piece, and the piece rate. The system multiplies the count by the rate and applies any overtime premiums. If the same operator works on multiple styles in the same shift, the system allocates the earnings proportionally.

Daily-wage workers: the shift supervisor records the actual hours worked, including any overtime. The system compares the hours against the attendance register and flags discrepancies above 15 minutes. Night-shift premiums are applied automatically if the shift code is marked as night.

Monthly staff: the system calculates prorated salary for any partial attendance, then adds any variable allowances such as overtime or shift premiums. Leave balances are updated in the same run, so the next payroll reflects any unpaid leave taken.

Worked illustration: piece-rate earnings with overtime and advances

Operator A is paid £0.12 per piece for operation X. The standard time is 1.5 minutes per piece. In a normal 8-hour shift (480 minutes), the expected output is 320 pieces. On Monday, Operator A completes 350 pieces in 8.5 hours (510 minutes). The system calculates:

• Base earnings: 350 pieces × £0.12 = £42.00
• Overtime hours: 0.5 hours × 1.5 (premium) = 0.75 hours
• Overtime rate: £0.12 × 1.5 minutes × 60 = £7.20 per hour
• Overtime earnings: 0.75 hours × £7.20 = £5.40
• Total earnings: £42.00 + £5.40 = £47.40

Operator A had previously drawn an advance of £20. The system deducts the advance and posts the net pay of £27.40 to the payroll register. The same transaction updates the product costing ledger with £47.40 of direct labour for the style produced.

Validate payroll before posting to finance

Before the payroll is finalised, the system generates a pre-posting report that lists:

• Every employee whose earnings exceed 1.5 times their base rate, flagged for supervisor review.
• Every shift where the total hours worked by the team exceed the scheduled hours by more than 10%.
• Every advance that has not been cleared by the end of the pay period.
• Every statutory deduction that falls outside the expected range for the employee’s salary band.

The report is routed through dynamic approvals; the production manager must sign off on the piece-rate counts, and the finance manager must sign off on the deductions. Once approved, the system posts a single journal to the general ledger, debiting the payroll expense accounts and crediting the liability accounts. The finance module then generates the payment file for the bank.

How to handle disputes and corrections

If an operator disputes a piece count, the supervisor can re-open the shift within a 48-hour window. The system logs the change, the reason, and the user who made it. The payroll run is then re-calculated for the affected employee only; the rest of the workforce is unaffected. If the dispute is resolved after the payroll has been posted, the correction is made in the next pay period, and the system generates a supplementary payslip that shows only the adjustment.

For daily-wage workers, the system allows a one-time override of the attendance register if the supervisor provides a signed note. The note is scanned and attached to the payroll transaction, creating an audit trail. Monthly staff corrections are handled through the leave module; any unpaid leave taken is deducted in the next payroll run.

Integrate payroll with the rest of the plant

When payroll is run inside the same system that schedules production, the following links become automatic:

• Piece-rate earnings are allocated to the correct style and operation, updating the product costing ledger in real time.
• Overtime hours are compared against the production schedule, so the planning team can see which orders are driving overtime costs.
• Advances are deducted from the next payroll, and the cashbook is updated immediately, improving working capital visibility.
• Leave balances are visible to the production planner, so shift schedules can be adjusted before a shortage of operators causes a bottleneck.

The table below shows how the same payroll transaction updates multiple ledgers.

What to do next week

Monday: List every payment method used in the plant (piece-rate, daily-wage, monthly, contract). Note which spreadsheets or systems currently hold the data.

Tuesday: Map the data flow from the shop floor to the payroll register. Identify where manual re-keying happens and where approvals are missing.

Wednesday: Run a parallel payroll for one small department using the current method and the new structure described above. Compare the results and reconcile the differences.

Thursday: Set up the employee master in a test system. Enter the base rates, allowances, and payment methods for the same department.

Friday: Train the supervisors on how to record piece counts and shift hours. Use the worked illustration as a training aid. Run the first payroll in the test system and validate the output against the parallel run.