Guideline on Common Financial Management Business Process 3.3 - Manage Other Payments

Constitutes the model for Manage Other Payments, which involved common payment transactions not covered by Manage Interdepartmental Settlements (Business Process 2.2), Manage Procure to Payment (Business Process 3.3), Manage Travel (Business Process 3.2), Pay Administration (Business Process 5.1), and Manage Grants and Contributions (Business Process 6.1).
Date modified: 2010-05-30
Print-friendly XML

Long description for image: Figure 1. Manage Other Payments – Level 2 Process Flow

The figure is a process flow diagram consisting of subprocesses, connectors, inputs, outputs, gateways and decisions. The subprocesses are grouped into subprocess groups.

This diagram depicts the Level 2 process flow for Business Process 3.3 – Manage Other Payments. This business process consists of four subprocess groups and seven subprocesses.

The four subprocess groups are:

  • Manage Requirements;
  • Control Commitments;
  • Manage Payables; and
  • Manage Payments

The Manage Other Payments business process begins with a connector from Business Process 1.1 – Manage Planning and Budgeting, which provides an input labelled “Approved plan and budget.” Alternatively, Manage Other Payments begins with an input labelled “Ad hoc requirement.” The inputs start the process flow for other operational payments and periodic payments.

The flow advances to the decision titled “Periodic payment?” The NO flow for the decision “Periodic payment?” leads to the Manage Requirements Subprocess Group, which consists of Subprocess 3.3.1 – Determine Requirements and Subprocess 3.3.2 – Determine and Exercise Expenditure Initiation Authority. An input labelled “Copy of the court or tribunal decision” connects to Subprocess 3.3.2 – Determine and Exercise Expenditure Initiation Authority and is the starting point for legal payments.

The flow from Subprocess 3.3.2 – Determine and Exercise Expenditure Initiation Authority and the Yes flow for the decision titled “Periodic payment?” advance to the Control Commitments Subprocess Group, consisting of  Subprocess 3.3.3 – Verify Unencumbered Balance (section 32 of the FAA) and Subprocess 3.3.4 – Manage Commitments (section 32 of the FAA), which are performed concurrently. Completion of the two subprocesses results in an output labelled “Supporting documents.”

The flow advances to the Manage Payables Subprocess Group, consisting of Subprocess 3.3.5 –Manage Payables, which results in the output labelled Certification pursuant to section 34 of the FAA. Another input labelled “Supporting documents” also connects to Subprocess 3.3.5 –Manage Payables, beginning the process flow for payments not impacting appropriations.

The flow continues to the Manage Payments Subprocess Group, where an input labelled “Payment requisition” is used in Subprocess 3.3.6 – Perform Payment Authority (section 33 of the FAA). The flow proceeds to Subprocess 3.3.7 – Issue Payment, which is performed by the Receiver General and concludes the Manage Payments subprocess group.

The flow continues to the decision titled “Quality assurance performed?” The NO flow for this decision leads to a connector for Business Process 8.1 – Manage Post-Payment Verification and then advances with the YES flow to Business Process 8.2 – Manage Financial Close, signalling the end of Business Process 3.3 – Manage Other Payments.

Return to the Complete Text

Date modified: