Using Oracle HRMS you can run a payroll, perform post processing on a successful payroll, and also make changes and corrections for a payroll that has not completed successfully.
You can run your payroll as:
A batch process if you want to include all employees or a group of employees in the same run
A QuickPay process if you want to run a payroll for an individual employee
You can perform all the necessary post processing to generate payment for your employees once you are satisfied that your payroll run results are correct:
The PrePayments Process enables you to allocate employee payments between the payment methods that you have defined.
The Payments Processes enable you to make automated payments to a bank account, generate cheques/checks and report on the amounts paid to your employees. You can also verify that cheques/checks have been cashed.
The External/Manual Payments Process enables you to make cash payments or to pay employees from external sources.
You can analyze your payroll run results to get early notification of possible discrepancies:
The Payroll Exception report enables you to identify overpayments or underpayments.
The Void Cheque/Check Payments Process allows you to cancel a cheque/check that was produced in error.
Employee Run Results give you a list of all results created for this payroll run.
You can use these processes for correcting a payroll run:
Correction of Run Results: Retries. Retries enable you to correct a payroll run before post-processing has occurred.
Correction of Run Results: Reversals. Reversals enable you to correct a payroll run when post-processing has already occurred.
Correction of Run Results: Rollbacks. Rollbacks enable you to correct a payroll run without keeping any record of the original run.
You can run these processes to make accurate provision for current payments backdated from a previous pay period, or current payments received in advance for a future pay period:
The RetroPay process enables you to retrospectively distribute current payments to the period in which they were earned.
For non-North American legislations, the Advance Pay process enables you to pay employees in advance for an absence recognized by your legislation.
To enable you to process and analyze payrolls, you need to understand these concepts:
Note: You can use this if it is enabled for your localization.
Running the PrePayments Process, Oracle HRMS Payroll Processing Management Guide
Retries, Oracle HRMS Payroll Processing Management Guide
Reversals, Oracle HRMS Payroll Processing Management Guide
Rollbacks, Oracle HRMS Payroll Processing Management Guide
For non-North American legislations: Advance Pay, Oracle HRMS Payroll Processing Management Guide
See Reports and Processes in Oracle HRMS, Oracle HRMS Window Navigation and Reports Guide
The main purpose of the payroll run is to calculate employee pay correctly at regular intervals. In addition you can perform other payroll processes to ensure accuracy and provide flexibility for your organization. For example, you can roll back a payroll run when you want to carry out a test run without keeping any record of it having taken place. You can also run a RetroPay process when you want to make retrospective adjustments to allow for backdated pay awards.
Yes, Oracle Payroll enables you to run part payrolls. This is useful in each of the following circumstances where you do not want to process a payroll for the entire organization.
If an employee leaves the company before the end of a payroll period, you will need to calculate the individual pay entitlement.
You may also want to calculate individual pay to check the details for an employee before starting a payroll run for all employees.
You may want to specify that only particular types of earnings or particular categories of employee should be included in a payroll run.
On completion of a payroll run you will need to verify that the run completed successfully. You can display run messages and view latest balances and assignment level results. You may also need to have relevant information grouped by topic in report format so that you can review the outcome of processing. Payroll runs can be monitored through the Payroll Progress Monitor, enabling you to view the name of the run and the percentage/time of completion.
Oracle Payroll enables you to make each of the following types of adjustment when a payroll run has completed.
Addition of late entries that were not included in the initial run
Corrections to details that were wrongly entered in the initial run
Retrospective distribution of current payments to the period in which they were earned
When you have made these corrections and modifications you can then run the payroll again. However, you do not need to rerun the entire payroll. You need only to perform a retry, and Oracle Payroll will reprocess only those items that were incorrect in the initial run.
Oracle Payroll enables you to use the results of a payroll run to allocate payments to your employees, and to provide costing information.
When a payroll run has completed you need to pay each employee according to the payment methods that you have specified. You may also need to override the predefined payment methods where employees are receiving special payments such as bonuses, which may not be paid by the usual methods of payment. You also have the ability to pay an employee, who has multiple assignments within your organization, a regular single payment.
On completion of a payroll run you may need to distribute the associated costs across particular cost centers. For information on this, see: Cost Analysis Overview, Oracle HRMS Enterprise and Workforce Management Guide
Yes, the continuous calculation process enables you to process static employee data throughout the payroll period, leaving you extra time for validation and correction at the end of the payroll period.
Where employers have agreed to pay tax on a known fixed net payment, Oracle Payroll can calculate the gross amount that employees must receive in order to meet all deductions and still receive the correct net amount. This is referred to as Net-to-Gross processing, and the calculations that derive the correct gross amounts are referred to as Grossups, provided that the feature is enabled in your country.
Note: The entries made in the "Grossup Processing" tab on the earnings form only specify what deductions are to be included when calculating the gross pay. The system looks at the taxability rules to determine what deductions should be taken from an earning and does not take into consideration what is entered on the grossup processing tab. For example, if the gross up processing tab shows that Federal tax is to be the only tax included in the grossup calculation but the element is subject to CPP, EI and Federal tax as per the taxability rules, all three taxes will be deducted.
Yes, Oracle Payroll enables you to make external and manual payments.
Oracle Payroll enables you to run a payroll and conduct post-processing on a payroll that has completed successfully. You can also enter subsequent changes and corrections for a payroll that has not completed successfully.
Oracle Payroll makes use of the following concepts when implementing payroll procedures:
Occasions when you need to use assignment sets for the payroll run include:
You need to process the night shift earlier than the rest of the payroll as they must receive their pay advices the night before the rest.
You need to process a correction run, as entries were not received in time for the normal run and the overtime must be paid this period.
You want to process an additional run for a long service award, which the enterprise is presenting as a cheque/check to each qualifying employee.
To fulfil these requirements, you can select from a range of assignments:
Include all assignments
Include or exclude individually identified assignments
Use a formula to include or exclude certain groups of assignments
A consolidation set is a grouping of payrolls that simplify post-run processing and reporting. It enables you to produce a single set of reports, costing results, and other results for all payrolls in a consolidation set. When you run a payroll, make sure that you have named the consolidation set to which the payroll belongs.
With a normal payroll run, you would want to include all elements, but for a long service award bonus you would want to include only the bonus element and the statutory elements. You first calculate gross pay for ascertaining the gross amount to transfer into the payroll account. Then you complete the gross to net calculation.
You can select element sets as follows:
Include all elements
Include or exclude individually identified elements
Include or exclude classifications of elements.
Canada only: When creating a Run set, you need to explicitly add the Canadian Tax recurring element to your element set.
US only: When creating a Run set, you need to explicitly add the VERTEX recurring element to your element set.
The predefined elements for Oracle Payroll are processed for every payroll run in which they have been included. The deductions are recalculated using the period totals, the amount already paid in previous runs is deducted, leaving the remainder as the deduction for the new payroll run.
QuickPay enables you to carry out payroll processing for individual employees. You can use QuickPay to pay employees who are leaving and who require payment immediately. If an employee asks what their net pay will be this month, you can run QuickPay to find the answer, then roll it back to remove all results from the database.
Once the QuickPay run has a status of Complete, you have a choice of two options for post-run processing:
Include the QuickPay in the batch prepayments processing for the assignment's payroll.
Choose this option if, for example, you have a new employee who joins after the payroll run for the current period has taken place. Instead of rolling back the whole payroll and resubmitting it with the new employee added, you run QuickPay instead so that you can include the new employee in the consolidation set for batch prepayments.
Start the PrePayments process from the QuickPay window, if necessary overriding the default payment method.
Choose this option if, for example, an employee is leaving and is waiting to be paid by cash or cheque/check.
When you start the QuickPay process, the screen freezes, and you cannot delete or update the QuickPay definition until the process completes.
You may receive one of the following error messages:
The process has not started
This means either that the concurrent manager has not been started, or that there are other requests of a higher priority. Ask your system administrator to start your request or change its priority.
The process has started but has not finished
Ask your system administrator to investigate the reason for this.
Continuous Calculation enables you to distribute your payroll processing throughout a payroll period. You can run processes such as the payroll run, prepayments steps, and costing, which deal with predominantly static employee data, at the start of the payroll period, leaving more time for validation and correction of changed data.
Continuous Calculation works by using triggers. You define triggers and events which inform the system when data has changed. For example, if an employee receives a bonus, the corresponding event is triggered. When you subsequently run the Continuous Calculation process, the system identifies these triggers and marks the corresponding payroll processes (such as the payroll run) to be repeated. The affected processes are repeated in a batch process which can be run as often as required. You define the frequency of the batch process when you run the Continuous Calculation process.
Event Qualification is a system to restrict the type of datetracked-events to be interpreted from the Incident Register. You can qualify the event so only a subset of these event types are actually returned. An event qualifier is a basic definition of events to be monitored for a table to represent additional filtering.
You can form event groups that enable you to construct a grouping of events. A list of events gives you the ability to say “I am interested in this event occurring” and provides a simple solution for most problems. In more complex implementations, you can use Event Qualifiers. If, for example, there are date changes, you can address it to a further level of granularity such as “why the change occurred”. It enables you to specifically control the events creation; for example, “to raise event if the change is from A to B, but do not raise it if it is from A to C. In other words, a specific change qualifies the event.
The Qualifiers button is enabled only when you enter an event with update type “Datetrack Update” using the Event Group window. An event can be qualified if predefined qualifiers exist for that table, and you can enter exact changes that cause the event to be valid or invalid.
If you require qualifiers, you can create a default change with old and new values set to <ANY_VALUE>, such that all changes result in the event being registered. A list of exceptions to this default behavior displays in the Value Change Exception region. You can set some causes of the event and select the Valid check box and if the change occurs, the application fires the event or validates the event. For example, consider 20 possible values for a field but the event is considered important only if value10 is changed to value15. By using the Event Qualifiers, you can add a validation that the application should not process if the fields are changed from and to any other value.
The Event Qualification window enables you to record the name of the qualifier, the table being monitored, the qualifying value and query (the From and To clause for the validation) used to validate comparisons. The table PAY_EVENT_QUALIFIERS holds this information.
Qualifiers are of two types - direct and indirect comparisons. You can use direct comparisons for assignment changes and indirect comparisons for entry value changes. The indirect changes relate to dynamic triggers monitoring one table, but looking for changes in another table. This is particularly relevant to entries, where you can monitor the entries table, then look for changes in the entry value table.
The table PAY_EVENT_VALUE_CHANGES holds information detailing the definitions of the changes that cause the events to be valid or invalid. The table includes the qualifier and name that is to be used, with the values of from and to, the column that triggers the qualification check, with whether it is valid and the type of proration it relates to.
The comparison determines if the event is a valid event and the type of proration that is associated with that event. You can use <ANY_VALUE> and <NULL> to denote the type of change in the comparison.
The Run Proration field is enabled only if the Event Group is Proration and if the legislation has enabled it in PAY_LEGISLATIVE_FIELD_INFO.
For information on how to define event group qualifiers, see: Defining Event Group, Note ID: 971206.1 on MyOracle Support.
You start a payroll run in the Submit Requests window.
To run a payroll
In the Name field, select the name of your payroll run process.
In the Parameters window, which opens automatically, select the payroll.
Select the default consolidation set name for the payroll, then select the current payroll period display.
Select a new consolidation set for the run if required.
Use the consolidation set to control post-run processing of the results.
Select the payroll period for the run.
Select an element set and assignment set if required.
US only: Make sure that you have included the VERTEX seeded recurring element in your element set if you are using an element set.
Select a run type.
If your legislation supports Regular and Supplemental runs, then select R for a Regular run or S for a Supplemental run.
India only: Select "Bonus" run type for paying bonus.
You can optionally enter a message to appear on the statements of earnings for this run if your SOE is designed to support such a message.
Choose Submit.
To set up your system for continuous calculation:
In the Table Event Update window, check that the events are defined for the tables you require for continuous calculation.
If the table has already been defined, but the required event is missing, create either an Update, Delete, or Insert event and enter the table column to which the event refers. Select the change type defined by the event.
If the tables you require for continuous calculation have not been defined in the Table Event Update window, define them now in the Table Event Updates window.
See: Making Table Event Updates, Oracle HRMS Payroll Processing Management Guide
In the Functional Area Maintenance window, choose the Incident Register functional area. Make sure your triggers are included in this functional area. If your triggers are not included, insert them.
You can also activate the triggers according to legislation or business group.
See: Grouping Dynamic Triggers into Legislative Functional Areas, Oracle HRMS Payroll Processing Management Guide
Note: When you save a single trigger, this has the effect of regenerating all triggers contained in the same package.
Run the Continuous Calculation process from the Submit Reports and Processes window.
The Continuous Calculation process enables you to process static employee data throughout a payroll period.
You run the Continuous Calculation process from the Submit Requests window.
To run continuous calculation
Enter Continuous Calculation in the Name field of the Submit Requests window.
Select a payroll.
Schedule your process.
You can choose how often you want to run the continuous calculation process. For example, you can run the process every day, every week, or on specific days.
Choose Submit.
You navigate to the QuickPay window from an employee assignment.
To define a QuickPay run for an employee assignment
Set your effective date to the day you want to make the QuickPay payment.
The Payroll Period displays for the date selected, and the Date Paid and Date Earned for this period also display. Date Paid is the regular payment date for your legislation. You can update the Date Paid field, but only to another period's regular payment date.
Note: If you select an effective date for which there is no valid payroll period, all three fields remain blank. You cannot select an effective date earlier than the start date of the parent record - the employee assignment.
Select a consolidation set.
The default is the consolidation set for the assignment's payroll.
Note: The Number field remains blank and the status field remains set to Unprocessed until the QuickPay run process is completed.
If your legislation makes use of run types, select the run type for this QuickPay.
Enter a pay advice date and message if required. These fields are for information only.
Save your QuickPay definition.
Note: All assignment processes for the assignment's payroll must have a status of Complete for you to save the definition. If not, you see an assignment interlock failure message. Check the status of the assignment processes in the Assignment Processes window, and delete, roll back or rerun any non-Complete processes.
If the QuickPay Run itself displays In Error or Marked for Retry, choose the Retry Run button to run the process again.
To execute a QuickPay run for an employee assignment
Choose the Element Selection button if you want to check or verify element entries for the QuickPay run. All the elements for the assignment that exist as of Date Earned are listed in the Element Selection window. Select or clear the Include in Run check box for elements you want to include or exclude from the run.
You can choose the Entry Values button to view entry values for each element.
Note: You cannot create, update or delete entries or entry values in the Element Selection and Entry Values windows. You can only select or clear the Include check box for entries.
Choose Start Run to run the QuickPay process.
You run QuickPay from the QuickPay window, not from the Submit Requests window. You can view the status of the run in the View Requests window. If necessary, you can then mark it for retry or roll it back either from the QuickPay window or the Payroll Processes window.
When the run is processed, the Status and Number fields in the QuickPay Run block display values for the run as follows:
Number: Numbering is consecutive, starting from 1, for each QuickPay run in a payroll period. There is a separate series for each separate payroll. The numbering restarts from 1 for each successive period.
Status: Values displayed for processed QuickPay runs are Complete, In Error, Mark for Retry. You cannot enter or update values directly in this field. Choose Retry Run to rerun the QuickPay process for runs with the status In Error or Marked for Retry.
For information about running PrePayments, see: Running Post-Run Processes for QuickPay
To archive QuickPay run
You can archive payroll information after running the QuickPay process and QuickPay prepayment process successfully. The Start Archive button on the QuickPay window allows you to start the archive process. The Start Archive button gets enabled only when the QuickPay process and QuickPay prepayment process are completed for an assignment. Use the View Requests window to view the QuickPay archiver process details. The QuickPay archiver process is displayed in the window as the "Retry Payroll Process". Navigate to the Payroll Process Results or Assignment Process Results window to review the Quick Pay Archiver results.
The following rules apply to the Start Archive process:
If an assignment's QuickPay is processed using the Start Archive process, then this QuickPay is not eligible for process using the Payroll Archiver concurrent process.
If an assignment's QuickPay has been processed using the Payroll Archiver concurrent process, then the QuickPay window allows you to retry the archiver process by enabling the Retry Archive button, that is the Start Archive button label gets changed to Retry Archive indicating that the Payroll Archiver or QuickPay Archiver is already processed.
Note: The Start Archive button is not available by default for all legislations.
US Payroll Only: In addition to the general post archive processes, QuickPay archives data for the NACHA, Online Payslip (US), and Deposit Advice processes.
Mexico Payroll Only: In addition to the general post archive processes, QuickPay archives data for the CFDI Payslip process. The Payroll Archiver process or the Quickpay Archiver process archive data used by Cheque Writer (Mexico), Direct Deposit, and CFDI Payslip processes. Format 37 and DIM reports do not use the Payroll Archiver data, they instead use the data archived by the Year End Archiver process. You can roll back the QuickPay archiver results using the Rollback MX Payroll Process concurrent program. See: Correction of Run Results: Rollbacks, Oracle HRMS Payroll Processing Management Guide (Mexico)
Run this process when you want to recalculate run level balance values that may have become invalid, such as through changes to historical data.
You run this process in the Submit Requests window.
To run the Generate Run Balances process
In the Name field, select Generate Run Balances.
Select the Parameters field to open the Parameters window.
In the Parameters window, enter a start date from when you want run balances recalculated.
Select a mode to determine which balances to include. There is no specific time required to run these, such as once a month. All Invalid Balances is likely to be run most often, with Single Balances and All Balances run as required. You can choose from the following:
A Single Balance - If you select Single Balance mode, then the Defined Balance field becomes active.
All Invalid Balances
All Balances
Important: The profile option PAY: Allow All Balances for Assignment Level controls running the process for all balances at the assignment level. The profile option is set to No by default. Set this option to Yes if you want to run the process at the assignment level and for All Balances mode.
If the profile option is set to NULL or No and you select the mode as All Balances, then you can select Group at the balance level. When you select the mode as All Invalid Balances, you can run for both Assignment and Group levels.
Select the option that shows the route for retrieving balance values, even if its status is Invalid.
Select a balance level to determine which balances are to be recalculated, depending if enabled for your localization:
Assignment
Group
Assignment and Group
Click OK and then Submit.
Within Oracle Payroll the PrePayments process enables you to select a payment method to pay your employees. You can distribute employee pay over more than one method using either a percentage or monetary split.
You can override the PrePayments process. For example, suppose you have run the normal payroll run and made payments via one payment method. You then have to run supplementary payments for some employees and pay them by a different payment method. The PrePayments process, having distributed the regular payments over the payment methods entered, allocates the supplementary payments to the override method.
Run the Cheque/Check Writer process to determine the generation of cheques/checks for a specified payroll and consolidation set over a specified time period.
You can generate contiguous serial numbers for cheque/check printing, and you can use this feature to account for cheque/check stationery used during the cheque/check printing process. If you do this, you also need to take into account the cheques/checks you use to carry out the alignment of your printer.
A sample cheque/check report is supplied with the Cheque/Check Writer process. You can customize this report, or add your own cheque/check style to meet your enterprise requirements.
Oracle Payroll provides automatic cheque/check numbering for the Check Writer process. You can keep track of cheque/check numbers when you process multiple cheques/checks per day.
Note: Your System Administrator can enable the HR: Default Check/Cheque Number Method profile which enables you to use the automatic check/cheque numbering process.
See User Profiles, Oracle HRMS Configuring, Reporting, and System Administration Guide
Run the Void Cheque/Check Payments process when you want to void cheques/checks you have issued using Oracle Cheque/Check Writer. You may want to do this if there is a printing error or if the cheques/checks you print are afterwards lost. The process cancels the cheques/checks issued, records details of the cancellation, and enables you to give a reason for cancelling.
When you reissue a check after voiding it using the Void Check Payments process, the Check Writer process prints the check with the original Payment Date by default. Using the Override Check Date feature, you can replace the original check date with a check date of your choice. For reporting purposes, the Payment Register Report captures the replacement date from the reprinted check.
Use the External/Manual Payments window to record cash or cheque/check payments to employees from external sources or petty cash. The window enables you to record details of each payment.
Data locking is a mechanism that enables you to protect your data from unwanted updates. For example: If you are running a monthly report at the end of each month, the data contained in the report has to remain unchanged for as long as the report exists. If you want to change this data, you must first rollback the report.
Some payroll processes automatically lock your data and you do not need to take any additional action to apply a lock. For example, whenever you run the prepayments process, your data is automatically locked against update while the prepayments process completes.
Some payroll processes do not apply a lock automatically, but do provide you with the option of selecting a process to apply a lock. Where this is the case, the lock process can usually be selected from the Submit Requests window for your legislation.
For example, if you are using Oracle Payroll for Ireland you can select the P30 Data Lock process which specifies a date at which you want to lock the P30 monthly report before generating the report output. By applying the data lock you also maintains the lock date as a historical record so that you can be confident that subsequent monthly reports start from the correct point.
You should also be aware that some payroll post-processes can override any data locks that you have established. Oracle Payroll does not provide validation to prevent this, since it is a legitimate action that you may need to perform. For this reason we recommend that you should always refer to the individual topics in Oracle Applications Help before attempting to work with user selectable data locks.
To run PrePayments and other processes from the QuickPay window
Choose the Start PrePayments button. If required, you can override the default payment method for the assignment. You have a choice of Cash or Cheque/Check for prepayments run from the QuickPay window.
The status for the completed process displays in the Status field in the QuickPay PrePayment block.
When a status of Complete displays, do one of the following:
Choose the External Payment button to make payment by cash or cheque/check from the External/Manual Payments window.
Leave the payment to be made by a batch Cash or Cheque/Check Writer process for the consolidation set.
Note: If you have already included the QuickPay run in the default consolidation set for the assignment payroll, it can take part in the batch PrePayment process for the payroll without further action on your part.
To view, retry or roll back payroll processes
Select the name, period dates and action type of the payroll you want to view results for.
If you leave the Period To field blank, the end date in the Period From field becomes the end date for the query. If you run the query directly without entering payroll or period details, the window displays all payroll process results for all payrolls in the Business Group.
Choose Find.
The window displays details of all payroll processes for the payroll and period selected. See below for further display details.
To mark a payroll process for retrial, select the Retry check box for the record. You can then run the Retry process from the Submit Requests window.
To monitor the progress of a payroll run, select the record and choose the Process Info button. This activates the Payroll Progress Monitor, allowing you to view the name of the run currently processing and the percentage/time of completion. You can update these details through the Refresh button or check the Automatic Refresh box to enable changes to display as they occur.
To roll back a payroll process, select the record and choose the Delete Record icon. This deletes the process from the database and returns all values to their former state.
Note: Use the Payroll Processes window to roll back small processes only. It is better to roll back large processes such as payroll runs from the Submit Requests window. This runs the process under concurrent manager control, freeing you to carry out other tasks during processing and handling the process more quickly. You can also run processes for assignment sets in Submit Requests.
To see further information about the assignments making up the payroll process, select the record and choose from the buttons at the bottom of the window. Information then displays for the records you select.
Assignment Process: Lists details of the assignment processes making up the payroll process.
Message: Displays any system messages relating to the payroll process.
Process Info: Summarizes processing status information for the assignment processes.
Conc Manager: Enables you to query details of the run to view log file details.
Breakdown: Summarizes costing process information as follows:
Costings that were correctly costed (Normal Number)
Costings posted to the suspense account
Note: Costings can be posted to the suspense account if costing codes are wrong or, for example, values missing for distributed costing. Such costings still have a status of Complete. For costing processes to be given a status of Error there must be a serious breakdown at system or process level.
Output: This button enables you to view and download magnetic media, audit and other output files from the View Payroll Process Results page after running the Federal/State/Local W-2 magnetic media processes, State Quarter Wage Listings (SQWL's), and TIAA CREF interface. If the Output button is inaccessible (greyed out), this may indicate you are attempting to view output from a process other than the processes listed above, such as the pdf output from the Employee W2 PDF process.
Singapore/Hong Kong users:You can view and download magnetic media, audit, and other output files from the View Payroll Process Results page.
Singapore users: Additionally, you can view the output for these processes: IR8A File, IR8S File, A8A File, A8B File, and CPF Line Report
Reconciliation Details Allows you to see whether a specific payment has been cleared by the system. One of the following statuses will be displayed:
Cleared
Uncleared
In error
You can also see the messages produced by the reconciliation process.
You can generate your payslips to be printed and distributed to your employees using a report that picks up the payroll information you extracted previously through the payslip archive process, and converts it into a formatted file ready for printing. The payslip consists of a header and a body section, with the information you enter in the Parameters window appearing on the header page and the payslip figures in the main body.
You run the payslip report from the Submit Request window.
To run the payslip report
Select your country's payslip report in the Name field.
In the Parameters window, enter the start and end dates for the period of time you want the report to cover. You run the report for the same period as the payslip information extracted by the payslip archiver.
In the Parameters window, select a payroll, consolidation set and assignment set. This selects the employees for whom you want to run the report. Selecting a payroll overrides the consolidation set and processes the report only for the selected payroll. You can opt to select just a consolidation set, but cannot do the same with the assignment set.
The Sort Order fields that appear on the header section of the payslip enable you to divide the payslips into areas of your choice. For example, the current defaults divide the payslips into Person Info 1(Employer), Organization and Full Name areas. You can change the default values that appear by selecting another item from the list of values, selecting information about Additional Employee Details, Address Details, Payroll Information and Employee Details.
Choose the Submit button.
Choose the View Output button to view or print the payslip report file.
Use the Employee Assignments without Payroll report to identify any employee assignments that do not have a payroll.
To run the Employee Assignments without Payroll report
Enter the beginning date. This is the date from which you want to begin identifying assignments without a payroll.
Enter the end date. This is the date at which you want your report to conclude.
If you are running the PDF version of this report, select a template for your PDF template.
Click OK.
Click Submit.
Use the Payroll Actions Not Processed report to identify all payroll actions not yet processed.
You run the Payroll Actions Not Processed report from the Submit Requests window.
To run the Payroll Actions Not Processed Report
Enter a start date for the report to begin from.
Enter an end date to indicate the end of the reporting period.
Enter further identifying information to make your report as specific as possible. For example, you can enter payroll name, consolidation set name, and Government Reporting Entity (GRE).
Select the mode, for example, Costing, Payroll Archive and so on.
If you are running the PDF version of this report, select a template for your PDF template.
Click OK.
Click Submit.
Use the Employee Assignments Not Processed report to produce a list of all unprocessed employee assignments and decide on sort criteria for the list.
You run the Employee Assignments Not Processed report from the Submit Requests window.
To run the Employee Assignments Not Processed report
Enter a beginning date for the start of your reporting period.
Enter an end date to specify the end of your reporting period.
Enter further identifying information to make your report as specific as possible. For example, you can enter payroll name, default consolidation set name, Government Reporting Entity (GRE), and location.
Enter the sort options for your report.
If you are running the PDF version of this report, select a template for your PDF output.
Click OK.
Click Submit.
Use the Element Register report after a payroll or QuickPay run to display a listing of the elements and pay values for each employee. You can specify selection criteria to determine what the report includes. For example, you can select elements by element set, element classification or by individual element name. You can also specify a report output type for browser display, or for export to an editable spreadsheet.
You run the Element Register report from the Submit Requests window.
To run the element register report
Enter the Beginning Date Paid and the Ending Date Paid to specify your reporting period.
Select the criterion for determining which elements appear in your report. You can select one of the following:
Element set - your report includes all elements in an element set
Element classification - your report includes all elements belonging to a classification.
Element Name - your report only includes a single element
When you have selected the criterion, enter a name to identify the particular element set, element classification or element for reporting. For example, if your criterion is element set, you enter the name of the particular element set that you want to report on.
Select the Payroll, or Consolidation Set for your report. If you select a payroll, the consolidation set appears by default. You must select either a payroll, or a consolidation set.
If you want to report on a single GRE, select the GRE name. If you do not make a selection, your report contains information for all valid GREs.
If you want to report on a single organization, select the Organization name. If you do not make a selection, your report contains information for all valid organizations.
If you want to report on a single location, select the Location name. If you do not make a selection, your report contains information for all valid locations.
If you want to report on an individual employee select Employee name. If you do not make a selection, your report contains information for all valid employees.
Select an assignment set if you want to report on all assignments in a particular assignment set. You can only select a static assignment set. Dynamic, or formula-based assignment sets do not appear in the list of values.
Select an Output File Type:
HTML - this file type produces an output file that you can view in your browser.
Comma Delimited - this file type produces a comma delimited file that you can view in a browser. Additionally, you can save the comma delimited file as csv or txt so that you can open it for editing in a spreadsheet.
This report sums all the run results processed for a particular element over a defined period, and displays them by individual assignment. In addition, it lists the run results of each employee's last assignment process for input values you select.
You run the report in the Submit Requests window.
To Run the Element Result Listing
In the Name field, select the report name.
In the Parameters window, select the name of either the consolidation set or payroll for which you want to see information.
Select the element and date range for which you want to see information.
You can further restrict information you see by selecting an organization.
Select up to three input values for which you want to see run results of each employee's last assignment process. These input values appear on the report in the order in which you select them.
Select additional sort parameters for assignment information if you require them. The default is payroll, which is always the first parameter. You can also select from organization, employee name and assignment number.
Choose the Submit button.
Before you can make direct deposit payments to your employees, you must perform the following set-up procedure:
Set up the Direct Deposit payment method for the organization.
Set up the Direct Deposit payment for the payroll.
See: Defining a Payroll, Oracle HRMS Payroll Processing Management Guide
Define and link the recurring payment element.
See: Defining an Element, Oracle HRMS Compensation and Benefits Management Guide and Defining Element Links, Oracle HRMS Compensation and Benefits Management Guide
Set up payroll/element for assignment.
Define a direct deposit payment method for the assignment.
See: Entering Payment Methods for an Employee Assignment, Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide
Run the payroll.
You must run the payroll and prepayments process, then you can run the Direct Deposit process.
See: Running the PrePayments Process, Oracle HRMS Payroll Processing Management Guide
The Direct Deposit (Singapore IBG Format) process enables you to make payments to employees' bank accounts using electronic fund transfer. The process produces a payments file that conforms with the IDEAL Interbank Giro (IBG) file format required by the Development Bank of Singapore.
The process also produces a report for you to verify that the payments file is correct. The report and the payments file use a similar layout for the information included in them.
If the report shows that a pay amount was less than $1, the process rejects the payment, omits it from the payments file, and flags the record in the report. It continues to process all other payments as normal.
You run the Direct Deposit process from the Submit Requests window.
To run the Direct Deposit (Singapore IBG Format) process
Enter Direct Deposit (Singapore IBG Format) in the Name field.
In the Parameters window, select the payroll and consolidation set for which you are creating EFT output.
You must select a consolidation set, but if you want to produce a payments file for all payrolls in the consolidation set, do not select a payroll name.
Enter a start date to restrict the payments to unpaid prepayments from that date. If you do not enter a start date, the payments file includes all unpaid prepayment runs.
Enter the end date of the process. This is used to retrieve only the unpaid prepayments occurring before this date.
Select Direct Deposit as the organization payment method.
Enter the transaction date. This is the magnetic tape submission date.
Click OK and then click Submit.
Run the Direct Deposit (Singapore Enhanced IBG Format) process to make payments to employees' bank accounts using electronic fund transfer. The process produces a payments file that conforms with the SWIFT code.
You run the Direct Deposit (Singapore Enhanced IBG Format) process from the Submit Requests window.
To run the Direct Deposit (Singapore Enhanced IBG Format) process
Enter Direct Deposit (Singapore Enhanced IBG Format) in the Name field.
In the Parameters window, select the payroll and consolidation set for which you are creating EFT output.
To produce a payments file for all payrolls in the consolidation set, do not select a payroll name.
Enter a start date to restrict the payments to unpaid prepayments from that date. If you do not enter a start date, the payments file includes all unpaid prepayment runs.
Enter the end date of the process. This is used to retrieve only the unpaid prepayments that occur before this date.
Select the payment method as Direct Deposit.
Enter the transaction date. This is the magnetic tape submission date.
Select the type whether Payment or Salary. This is mandatory for the magtape file.
Select the purpose code. If you have selected Salary as the payment type, then Salary is displayed as the purpose code. You can choose a different code from the list of values for the payment type, if required. The purpose code is mandatory for the magtape file.
Enter the beneficiary reference. The purpose code with the month and year of the end date appears by default. You can enter a different value if required. This is mandatory for the magtape file.
Click OK and then Submit.
Run this report to generate pay advice for all employees for a specified payroll and payroll run. This is a sample report which you can customize. You run it after completing the Pre-payments process for a payroll. To check printing alignment before generating pay advice run the Pay Advice Alignment report.
You run the Pay Advice report from the Submit Requests window.
To run the Pay Advice report
In the Name field, enter Pay Advice (Singapore)
In the Parameters window, select the payroll for which you want to generate pay advices.
Select the payroll run for which you want to generate pay advices.
Select the organization and if required, the location, that you are reporting against.
Do one of the following:
If you want to generate pay advices for all employee assignments, leave the Assignment Number field blank.
If you want to generate a single pay advice for an employee assignment, enter the employee assignment number.
Specify the sort order for the report.
If you entered an employee number in the previous step, the sort order defaults to assignment number, but you can change this.
Choose the Submit button.
Note: You can also view this report from the Assignment Process Results window, where you select an individual assignment and the process you want to view the report for.
See: Viewing Assignment Process Results for a Payroll Process