PeopleSoft Self Service Payments

By | March 2, 2017

I was recently involved in the design and development of a very useful new piece of functionality for PeopleSoft Global Payroll.  The “Self Service Payment Add-On” (SSP) enables employees to submit payment requests directly into PeopleSoft.  Requests are then routed for a approval before being posted directly to Positive Input or Element Assignment.

SSP is designed as a bolt-on.  There is no customisation of any delivered PeopleSoft objects, with the exception of integration into the portal navigation.

SSP Payment Codes are linked to Global Payroll Earnings or Deductions and are completely configurable, with many useful features such as:

  • Configurable approval workflow (using the PeopleSoft “Approval Workflow Engine”)
  • Calculation rule settings, to control:
    • Component Overrides. Take for example an Earning with a calculation rule of “Unit x Rate”. It is unlikely that you would want a self service user to enter/override the rate value, which is typically derived from the employees’ hourly rate.
    • Label Overrides. For example: the “Units” component of the calculation rule can configured to display “Hours”, making it more meaningful for self service users.
  • Optional or mandatory attachments to support requests (e.g. receipts, certificates etc…)
  • Configurable Payment Code related information.  Ideal for communicating policies and procedures related to a request.
  • Fluid interface, making SSP usable on a variety of devices, including tablets and mobile phones.
  • Privacy settings, to control which Payment Codes may be viewed by managers. There are some payroll transactions that are not
  • Request Lockout, to prevent requests being entered during pay reconciliation and finalisation.
  • “Configuration by Element” support means any Supporting Element Overrides setup in the “Configuration by Element” Component are available to self service users.
  • Eligibility Control. SSP uses the Global Payroll Organisational/Eligibility framework to control which Payment Codes a self service user is able to request.
  • End Date controls, to govern if a recurring payment end date is required, and if it can be changed via self service once entered.

You can see it for yourself in a brief promo YouTube clip that I put together here:

SSP is for sale from Presence of IT.  Let me know if you’re interested and I’ll arrange a demo.