Global Payroll Documentation

This topic discusses:

  • PeopleSoft Global Payroll application design.

  • PeopleSoft Global Payroll documentation structure.

  • Documentation road map.

Because the structure of the PeopleSoft Global Payroll documentation is similar to the design of the application, the best way to understand the documentation is to review the design of the application itself.

PeopleSoft Global Payroll is composed of two complementary parts:

  • A core payroll application that includes:

    • A payroll rules engine.

    • A payroll processing framework.

    • Processes and setup steps that apply to all countries.

  • Country extensions that include:

    • Statutory and customary objects (payroll rules, payroll processes, reports, additional country-specific pages, and self-service applications).

    • Country-specific rules and elements.

Like the application, the documentation for PeopleSoft Global Payroll consists of two parts: a core book and separate country extension books.

Core Documentation

Like the core portion of the application, which applies to all countries and enables you to develop rules and process a payroll regardless of location, the core book is country neutral. Thus, while it describes the core set of tools that you can use to develop a payroll, it doesn't discuss the local country rules that have been set up for you. For information about how PeopleSoft has extended core capabilities to meet local requirements, refer to the country extension documentation.

Country Extension Documentation

Just as country extensions in the application address local needs, the country extensions in the documentation cover local functionality. This includes:

  • Any core feature with local extensions.

  • Country-specific rule setup.

  • PeopleSoft-delivered rules and tables.

  • Country-specific pages.

  • Country-specific reports.

  • PeopleSoft Human Resources (HR) setup, such as bank definitions, that varies by country.

  • Implementation information that varies by country.

The core and the country extension documentation complement each other, therefore, it is important to read both sets of documentation.

What to Read When

You can approach the documentation in the following way:

  • If a process setup is shared between the core application and the country extension, read the core documentation first and then the country extension documentation.

    For example, banking is a feature that you first define in the core application and then often continue in the country extension, because most country extensions have some type of banking functionality. You would first read the banking documentation in the core documentation, and then the banking documentation in the country extension documentation.

  • If a process is set up only in the core application, read the core documentation.

  • If a process is set up only in the country extension, read the country extension documentation.

Documentation Audiences

We've identified the following audiences for the documentation:

  • Technical

    Technical readers who are interested in the technical design of the product should begin by reading the Understanding the Core Application Architecture topic of this documentation, as well as the batch processing information that is mentioned in many of the other topics.

  • Functional

    Functional readers who are interested in defining rules should begin by reading the country-specific functionality described in the country extension documentation. Functional readers can continue to learn about how to use the tools in the core application by reading the topics on defining payroll elements, such as earnings and deductions, in the core documentation.

  • Managerial

    Managerial readers should begin by reading the introduction topics of both the core documentation and the country extension documentation to get a high-level overview of the Global Payroll product.

Note: To fully understand PeopleSoft Global Payroll, technical or functional persons who are involved in the product implementation should read the core documentation and the applicable country extension documentation in their entirety.