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 8. Manage Payables (Subprocess 3.3.5) – Level 3 Process Flow

The figure is a process flow diagram consisting of activities, connectors, inputs, outputs, gateways and decisions.

This diagram depicts the Level 3 process flow for Subprocess 3.3.5 – Manage Payables, which is launched by a connector from Subprocess 3.3.4 – Manage Commitments. Subprocess 3.3.4 – Manage Commitments provides an input labelled “Supporting documents, launching the process flow for payments not impacting appropriations.” The flow advances to Activity 3.3.5.1 – Verify That Documentation Is Complete.

The flow advances to a decision labelled “Complete?” The NO flow for the decision “Complete?” leads to Activity 3.3.5.11 – Resolve Discrepancies and then returns to the decision Complete? before continuing to the decision labelled “ Legal opinion required?” The YES flow for the decision “Complete?” continues to the Activity 3.3.5.2 – Obtain Legal Opinion and then advances with the NO flow to four sequential activities:

  • Activity 3.3.5.3 – Confirm That Requirements Are Met;
  • Activity 3.3.5.4 – Confirm That Payee is Eligible for Payment;
  • Activity 3.3.5.5 – Validate That Amount or Price is Reasonable; and
  • Activity 3.3.5.6 – Ensure That Payee Information is Accurate.

The flow advances to a decision titled “Update payee information?,” The YES flow for this decision leads to a connector for Business process 7.1 – Manage Vendor Master Data File before advancing with the NO flow to three sequential activities:

  • Activity 3.3.5.7 – Verify That Financial Coding is Correct;
  • Activity 3.3.5.8 – Verify That Relevant Regulations Were Followed, including policies, legal obligations and directives; and
  • Activity 3.3.5.9 – Verify That Balance is Sufficient.

The flow advances to a decision titled “Update commitment. The YES flow for this decision leads to a connector for Subprocess 3.3.3 – Verify Unencumbered Balance before advancing with the NO flow to Activity 3.3.5.10 – Verify the Accuracy of Transaction.

The flow continues to a decision titled “All information is accurate, valid and complete?” The NO flow for this decision leads to Activity 3.3.5.11 – Resolve Discrepancies and then revisits the decision titled “Complete?” The YES flow for the decision “All information is accurate, valid and complete?” continues to Activity 3.3.5.12 – Exercise Authority or Obtain Approval, which results in an output labelled “Certification pursuant to FAA, section 34.” The flow continues to the output labelled “Request for payment” and then to a connector for Subprocess 3.3.6 – Perform Payment Authority.

Activity 3.3.5.11– Resolve Discrepancies can also be launched by a connector from Subprocess 3.3.6 – Perform Payment Authority.

Return to the Complete Text

Date modified: