Rescinded [2017-10-18] - Guideline On Common Financial Management Business Process 5.1 - Pay Administration

This document, the 'Guideline on Common Financial Management Business Process for Pay Administration' or 'FM-BP/PA', defines the HR/Finance Pay Administration Model (referred hereafter as the Pay Administration Model or PAM), which documents common HR and finance pay-related processes, data, roles and responsibilities, and authoritative sources. The HR/Finance Pay Administration Model is a 'should be' model that reflects best practices and definitions under the current Government of Canada (GC) systems and policy frameworks, specifically identifying how financial policy and the Financial Administration Act (FAA) and other legislation apply to the pay administration process.
Date modified: 2013-03-15


This or these guideline(s) are replaced by:

View all inactive instruments
Print-friendly XML

Long description for image: 17172-13-eng.jpg

The figure is a process flow diagram comprising activities, connectors, inputs/outputs and decisions.

The process begins with inputs from subprocess 5.1.7 - Manage Pay Pre-Payroll, 5.1.9 - Perform payment authority or 5.1.10 – Issue Payment, all of which create the output titled "supporting documentation", which is an input to activity Verify that supporting documentation is complete.  This activity is followed by the decision titled "Complete?".  The No proceeds to activity – Resolve Discrepancies, which returns to the decision titled "Complete?".  The Yes flow continues on to activity – Confirm that requirements are met, followed by activity -  Confirm that payee is entitled to payment, then activity  - Ensure employee information is accurate. The subprocess then flows to activity -  Verify that regulations, policies and directives were followed, which is then followed by activity Verify accuracy of transaction. This sequence of activities then flows to a decision titled "All information is accurate, valid and complete?".  The No flow returns to activity – Resolve discrepancies, which then flows to the "complete?" decision following activity – Verify that supporting documentation is complete.

The Yes flow proceeds to another decision titled "Adjustment to Commitments or Salary Forecast Required?". The Yes flow proceeds to subprocesses 5.1.4  - Manage Commitments or to subprocess 5.1.5 Update Salary Forecast, after which the flow joins the No flow to the output "Request for Pay Transaction". This output flows to the subprocess 5.1.9 Perform Payment Authority.

Return to the Complete Text

Date modified: