My Oracle Support Banner

WS: 07: Executive Order 13673: Fair Pay and Safe Workplaces – Paycheck Transparency (Doc ID 2248518.1)

Last updated on MAY 27, 2021

Applies to:

JD Edwards World U.S. Payroll Processing - Version A9.3 cume 1 and later
Information in this document applies to any platform.


On July 31, 2014, President Obama signed the Fair Pay and Safe Workplaces Executive Order to require prospective federal contractors to disclose labor law violations and give agencies guidance on how to consider labor violations when awarding federal contracts. The purpose of E.O. 13673 is to improve contractor compliance with labor laws in order to increase economy and efficiency in Federal contracting.
On August 25th, 2016, the Secretary of Labor issued the  Final Ruling and Guidance for Executive Order (E.O.) 13673. The final rules and guidance of the Fair Pay and Safe Workplaces Executive Order 13673 are organized into three separate rulings:

(1) Disclosure Requirements and Responsibility Determinations;
(2) Paycheck Transparency; and
(3) Arbitration of Title VII Claims and Tort Claims related to Sexual Assault or Harassment.

On January 1st, 2017, the Paycheck Transparency clause took effect. Contractors and subcontractors who perform on covered government contracts are subject to the EO’s Paycheck Transparency clause and should review the Final Ruling and Guidance for more information.

You can find more information at:

Federal Register

Guidance for Executive Order 13673

DOL’s Fair Pay and Safe Workplaces

DOL’s Fair Pay and Safe Workplaces – Paycheck Transparency


Note: This document should not be considered legal advice. Customers should review the law and consult with legal counsel to determine application of and compliance with the Law. Oracle cannot be held responsible or liable for non-compliance based on information included in this document.

Paycheck Transparency

Under Paycheck Transparency provisions, covered contractors and subcontracts must provide each worker with a detailed written wage statement or pay stub along with each paycheck. The written statement must contain

In addition, if the workers are paid bi-weekly or semi-monthly (instead of weekly), then the hours worked and the overtime hours worked must be broken down into amounts by work week in the written wage statement. FAR 52.222-60 (b)(2).

Oracle JD Edwards Position - Paycheck Transparency and Wage Statements

Oracle JD Edwards is planning to deliver an update for JD Edwards World in March, 2017, to support Paycheck Transparency provisions of Executive Order 13673. The update will include enhancements to support the ability to include pay information by workweek on the paystub.

Customers can monitor the progress of these updates with the following bugs:

Release Bug Software
A9.3.1  <BUG 25119973> Single byte: <JDEWORLD A935709433>

Double byte: <JDEWORLD D935709433>

A9.4  <BUG 25119980> Single byte: <JDEWORLD A945709437>

Double byte: <JDEWORLD D945709437>

Documentation   Payroll Guide I: A9.3.1

Payroll Guide I: A9.4



Note: JD Edwards Paycheck Transparency Wage Statements does not support the provision for the translation of wage statements to alternate languages.

Paycheck Transparency Wage Statements - Feature Summary

The JD Edwards World Paycheck Transparency Wage Statements enhancement focuses on the ability to include pay information reported by workweek on the pay stub. Refer to published documentation when available for detailed information about setup and processing.

Paycheck Transparency Wage Statements – Flexibility

Paycheck transparency options provide additional flexibility for reporting pay information by workweek. With these options, you can control certain aspects of the functionality, including:

Application Enhancements

Paycheck Transparency includes the following enhancements:




Sample Screen Prints


 Following are sample screen prints illustrating Paycheck Transparency enhancements.


Pay Stub (S06231) – The following example illustrates a pay stub reporting weekly detail pay stub lines. The employee worked a total of 80 hours in a biweekly pay period. Based on the timecards and their work dates, the system reported 40 hours in week one and 40 hours in week two.


Payroll General Constants (G0741).  New menu options 9 and 10.

Pay Period Workweeks (P069064) - Use Pay Cycle Workweeks to establish the weekly periods for each pay Cycle Code and pay period.  Use the copy feature to automatically create these dates for weekly and biweekly pay cycles.  (Note:  You may choose not to report weekly detail for a weekly payroll since the standard stub lines already represent a week).

Workweek Detail Pay Types (P059065) - Create a record for each applicable Pay Cycle Code that includes the ranges of pay types for which to report weekly detail.


Pay Cycle Processing (P06210) - Paycheck Transparency (P062103).  In this example, on the Paycheck Transparency form, processing for reporting pay information by workweek is turned on for employees who are FLSA non-exempt.  In addition, workweek detail reporting is set for certified jobs only.  The system will reference the timecard's chargeout business unit.  In addition to referencing the business unit master Certified Job flag, the system will also reference the business unit Category code RP11 and value 'ER' to determine if the job is certified.  Reporting full stub line detail (hours, rate, and gross) is selected.  The option to allocate auto pay timecards to workweeks is selected.

 Interim Check Entry (P060531) - For interim checks, use Option 8 to access Paycheck Transparency options.





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.