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 11. Level 1 Model of Financial Management

This figure depicts the Level 1 process flow for common financial management business processes, using six chevrons placed in three layers.

The top layer is a chevron labelled “Planning, Budgeting and Forecasting Results and Performance Reports.”

The centre layer is a row of four chevrons, each representing subsequent steps of the high-level financial management business process. The four steps are “Need Identification,” “Obligation,” “Performance,” “Validation and Certification,” and “Payment.” These four steps are further explained in two views—one from a Revenue perspective, the other from an Expenditure perspective.

From the Revenue perspective:

  • “Need Identification” is indicated by the Request;
  • “Obligation” is the Recognition of the Obligation;
  • “Performance, Validation and Certification” is indicated by the Invoice; and
  • “Payment” is indicated by the Deposit.

From the Expenditure perspective:

  • “Need Identification” is indicated by Expenditure Initiation;
  • “Obligation is the Recognition of the Obligation;
  • “Performance, Validation and Certification” is indicated by Section 34 of the FAA; and
  • “Payment” is indicated by Section 33 of the FAA.

The bottom layer is a chevron labelled “Master Data, Integration, Control and Monitoring.”

Note: FAAs. 34 refers to section 34 of the Financial Administration Act, and FAAs. 33 refers to section 33 of that Act.

Return to the Complete Text

Date modified: