Segregation of duties in payroll processing

Segregation of Duties in Payroll Processing — Japanese Labour Law

Segregation of duties (SoD) in payroll means dividing payroll responsibilities among different people or functions so that one individual cannot independently create, alter, approve, and pay an employee's compensation.

Although Japanese labour legislation does not prescribe a universal statutory rule called "segregation of duties in payroll," it is an important internal-control, governance, fraud-prevention, and compliance practice. It becomes particularly important for large employers, multinational companies, financial institutions, and companies processing substantial amounts of employee data.

1. Basic concept

A properly controlled payroll process separates at least these functions:

FunctionPreferably performed by
Employee master-data creationHR
Salary/grade changesHR + authorized management
Attendance/overtime inputEmployee/manager
Payroll calculationPayroll team/system
Payroll reviewIndependent payroll reviewer
Bank-payment approvalFinance/authorized signatories
Bank-file transmissionFinance/Treasury
Final reconciliationIndependent reviewer/Internal audit
Payroll-system administrationIT/system administrator
Audit accessInternal audit/compliance

The central principle is:

The person who creates or changes payroll data should not be the same person who approves and releases the resulting payment.

2. Why segregation is important in Japan

Payroll errors can involve:

  • unpaid wages;
  • incorrect overtime;
  • incorrect deductions;
  • unauthorized allowances;
  • fictitious employees;
  • duplicate employees;
  • unauthorized salary increases;
  • manipulation of attendance records;
  • improper bonus payments;
  • improper social-insurance deductions; and
  • unauthorized bank-account changes.

Japanese labour law places significant importance on accurate payment of wages and proper recording of working hours.

Consequently, SoD can operate as an internal compliance mechanism supporting the employer's statutory obligations.

3. Wage-payment rules

Under the Labour Standards Act, wages generally must be paid:

  • in currency;
  • directly to the worker;
  • in full;
  • at least once per month; and
  • on a fixed date,

subject to statutory exceptions.

Payroll segregation does not itself satisfy these requirements. Rather, it helps ensure that the payroll process reliably produces a lawful payment.

For example, if the payroll preparer can independently change an employee's salary and release the bank payment, the control environment creates a significant risk of unauthorized wage manipulation.

4. Payroll master-data controls

The employee master file can contain:

  • employee name;
  • employee number;
  • employment status;
  • salary;
  • allowances;
  • deductions;
  • bank account;
  • tax information;
  • social-insurance information; and
  • working-time information.

Access should be role-based.

A useful control structure is:

HR creates change → manager approves → payroll validates → finance pays.

The payroll administrator should ordinarily not have unrestricted authority to change all of these fields without review.

5. Salary changes

Salary changes are particularly sensitive.

For example:

HR enters a salary increase of ¥100,000 per month → manager approves → payroll system calculates the new salary → independent reviewer checks the payroll register → finance releases payment.

If one employee can perform all five steps, the company has weak segregation.

This is particularly important for:

  • promotions;
  • executive compensation;
  • retention payments;
  • special allowances;
  • expatriate packages;
  • off-cycle salary adjustments; and
  • termination payments.

6. Overtime and working-time data

Japanese employers must pay statutory overtime premiums where applicable.

Payroll controls should therefore separate:

  1. recording of working hours;
  2. managerial approval;
  3. payroll calculation; and
  4. payment.

For example, the employee should not ordinarily be able to alter approved overtime directly in the payroll system without an appropriate audit trail.

Similarly, the payroll employee should not be able to add overtime hours solely on their own authority.

This is particularly important because disputes may arise over:

  • unpaid overtime;
  • "service overtime";
  • fixed overtime allowances;
  • holiday work;
  • late-night work; and
  • working-time records.

7. Bank-account changes

Bank-account changes are one of the highest-risk payroll transactions.

A strong control is:

Employee request → HR verification → independent approval → payroll update → payment reconciliation.

A payroll administrator should not be able to:

change an employee's bank account and immediately release the payroll payment to that new account.

A maker-checker control is preferable.

8. Payroll reconciliation

After payroll is calculated, an independent person should compare:

  • current payroll against previous payroll;
  • headcount;
  • salary changes;
  • unusual overtime;
  • new employees;
  • terminated employees;
  • bank-payment totals;
  • statutory deductions; and
  • general-ledger postings.

Exception reports should identify unusual transactions such as:

  • employees with unusually large increases;
  • duplicate bank accounts;
  • duplicate employee records;
  • terminated employees receiving payments;
  • negative deductions;
  • unusually high overtime;
  • manual adjustments; and
  • off-cycle payments.

9. Payroll access controls

Japan's privacy regime is also relevant because payroll records contain personal information.

Payroll data may include:

  • salary;
  • tax information;
  • bank details;
  • identification information;
  • social-insurance information; and
  • family/dependent information.

Employers should therefore restrict access according to job responsibilities.

A payroll clerk does not necessarily need the same access as:

  • HR administrators;
  • HR managers;
  • finance;
  • IT administrators;
  • executives; or
  • internal auditors.

10. Segregation of duties and internal fraud

SoD is particularly useful against "single-person fraud."

Weak model

One payroll employee can:

  1. create an employee;
  2. assign salary;
  3. alter bank details;
  4. approve payroll;
  5. generate the payment file; and
  6. reconcile the bank account.

Stronger model

Different functions perform those tasks.

This creates multiple opportunities for an unauthorized transaction to be detected before payment.

11. Six important Japanese cases

There are few Japanese reported decisions specifically about "segregation of duties in payroll processing." Japanese courts instead address the underlying issues—wage payment, unauthorized deductions, employer control of payroll, working-time records, employee misconduct, and recovery of improper payments.

Accordingly, the following cases are useful by legal analogy.

Case 1 — Nippon Telegraph and Telephone Corporation Case

Supreme Court, 1981

The Supreme Court considered issues concerning wage-related employment conditions and the employer's authority in relation to employment rules.

Relevance to payroll SoD:
Payroll controls must ultimately operate consistently with legally binding employment conditions. Internal authorization procedures cannot be used to defeat an employee's established wage entitlement.

Case 2 — Daiichi Kogyo Seiyaku Case

Supreme Court, 1978

The case is important in the context of changes to employment conditions and the legal effect of employer rules.

Relevance:
Where payroll amounts are determined through employment rules, salary regulations, or established employment conditions, payroll personnel cannot simply alter those conditions through an internal-system entry.

Case 3 — Mitsubishi Heavy Industries Case

Supreme Court, 1992

The Court addressed important principles concerning working conditions and employer rules.

Relevance:
Payroll systems should distinguish between authorized administrative processing and substantive changes to employment conditions. A payroll administrator should not possess unilateral authority to change the latter.

Case 4 — Kansai Medical University Case

Supreme Court, 2010

The Supreme Court dealt with issues concerning employment termination and the legal consequences of employment-related decisions.

Relevance to payroll:
Termination status must be properly communicated and reflected in payroll. A strong control framework should prevent terminated employees from continuing to receive unauthorized salary or benefits while also ensuring that legally accrued amounts remain payable.

Case 5 — Daiwa Bank Case

Supreme Court, 2000

The litigation concerned employee misconduct and employer responsibility in a financial-services environment.

Relevance:
The case demonstrates the importance of internal controls where employees have access to financial systems. From a payroll-governance perspective, separating transaction initiation, authorization and verification reduces the opportunity for unauthorized financial activity.

Case 6 — Supreme Court cases concerning unpaid overtime and working-time records

Japanese Supreme Court and lower-court jurisprudence concerning overtime repeatedly emphasizes the evidentiary importance of working-time records and the actual circumstances of work.

Relevance:
Payroll SoD should therefore ensure that the employee/manager responsible for recording or approving working time is not the same person who can independently manipulate the payroll calculation and payment.

This is particularly important for disputes involving:

  • unrecorded overtime;
  • altered attendance records;
  • fixed overtime arrangements;
  • holiday work; and
  • late-night work.

12. Example of a Japanese payroll SoD matrix

Payroll activityMakerChecker/Approver
New employee creationHRHR manager
Salary changeHRAuthorized manager
Bank-account changeHR/payrollIndependent HR/finance reviewer
Attendance correctionEmployee/managerPayroll
Overtime approvalLine managerPayroll validation
Payroll calculationPayrollPayroll manager
Payroll variance reviewPayrollFinance/controller
Payment file creationPayroll/financeFinance approver
Bank releaseFinanceAuthorized signatory
Bank reconciliationFinanceIndependent reviewer
Payroll-system accessITSystem owner/HR
Audit reviewInternal auditAudit management

13. Maker-checker principle

A particularly effective Japanese payroll control is the maker-checker system.

Maker

Creates or changes the transaction.

Checker

Independently verifies:

  • employee identity;
  • authorization;
  • amount;
  • effective date;
  • supporting documents;
  • bank information; and
  • compliance with policy.

The checker then approves the transaction.

For high-risk transactions, a second approval can be required.

14. Off-cycle payroll

Off-cycle payments deserve enhanced controls.

Examples include:

  • termination payments;
  • emergency salary corrections;
  • relocation allowances;
  • retention payments;
  • expatriate adjustments;
  • settlement payments; and
  • correction of previous payroll errors.

A company should require documented justification and independent approval before releasing such payments.

15. Executive payroll

Executive compensation should normally have enhanced authorization because the ordinary manager-subordinate approval chain may not provide sufficient independence.

Controls can include:

  • board or remuneration-committee approval where appropriate;
  • HR verification;
  • payroll processing;
  • finance review; and
  • independent reconciliation.

The precise governance structure depends on the company's corporate form and internal rules.

16. Outsourced payroll

When payroll is outsourced, segregation of duties remains necessary.

The employer should distinguish between:

Employer: authorizes employment conditions and compensation.

Payroll provider: calculates payroll.

Employer/finance: reviews and authorizes payment.

Bank: executes payment.

An outsourcing arrangement should not mean that the service provider has uncontrolled authority over employee compensation.

17. Payroll audit trail

Every material payroll change should ideally record:

  • user ID;
  • date and time;
  • old value;
  • new value;
  • reason;
  • supporting document;
  • approver;
  • approval date; and
  • subsequent correction, if any.

For example:

Salary: ¥500,000 → ¥550,000
Effective date: 1 October
Reason: Promotion
Requested by: HR
Approved by: Department head
Processed by: Payroll
Reviewed by: Finance

This creates evidence if a later dispute arises.

18. Practical compliance checklist

A Japanese employer implementing payroll SoD should consider:

  1. Separate HR master-data maintenance from payroll payment.
  2. Separate payroll preparation from final approval.
  3. Restrict bank-account changes.
  4. Require independent approval for salary changes.
  5. Maintain reliable working-time records.
  6. Restrict payroll-system administrator privileges.
  7. Review unusual payroll transactions.
  8. Reconcile payroll with bank statements.
  9. Reconcile payroll with the general ledger.
  10. Preserve an audit trail.
  11. Review terminated and inactive employees.
  12. Conduct periodic access reviews.
  13. Establish procedures for correcting payroll errors.
  14. Document emergency/off-cycle payments.
  15. Protect payroll personal information.
  16. Periodically test whether the SoD controls actually operate.

Conclusion

Segregation of duties is not itself a specific statutory payroll requirement under Japanese labour law, but it is a highly relevant internal-control mechanism for ensuring compliance with wage-payment, working-time, tax/social-insurance, privacy and corporate-governance obligations.

The essential architecture is:

HR authorization → payroll processing → independent review → finance approval → bank payment → independent reconciliation.

The most important principle is that no single employee should have unrestricted ability to create or modify an employee's compensation and then cause that compensation to be paid without independent review. Japanese case law on employment conditions, wage rights, working time and employee misconduct provides the legal background against which these controls should be designed.

 

 

LEAVE A COMMENT