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 14. Manage Payments for Employee Relocation – Level 2 Process Flow

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

This diagram depicts the Level 2 process flow for Manage Payments for Employee Relocation. The process flow starts with a connector from the Common Human Resources Business Process – 3.0 Staffing and Employee Integration, and an input labelled “Approved letter of offer or equivalent,” which includes FAA, section 32 and expenditure initiation authority. The process for producing the input “Approved letter of offer” is outside of the scope of this process flow and is therefore not described. The flow continues to Subprocess 3.3.10 – Open Relocation File with Contracted Relocation Service Provider (or CRSP), which includes transaction authority.

The flow advances to four inputs:

  • An invoice from Central Removal Services, which leads to a connector for Business Process 2.2 – Manage Interdepartmental Settlements;
  • A departmental travel expense account invoice, which leads to a connector for Business Process 3.2 – Manage Travel;
  • An invoice from the CRSP, which continues the process flow for Manage Payments for Employee Relocation; and
  • An invoice from the moving company, which also continues the process flow for Manage Payments for Employee Relocation.

The flow advances to Subprocess 3.3.5 – Manage Payables and the output labelled “Certification pursuant to FAA, section 34.”

The flow continues to a decision titled “Overpayment?” The YES flow for this decision leads to a connector for Business Process 2.1 – Manage Revenue, Receivables and Receipts. The NO flow continues with an input labelled “Request for payment” to Subprocess 3.3.6 – Perform Payment Authority (FAA, section 33), followed by Subprocess 3.3.7 – Issue Payment, which is performed by the Receiver General.

The flow advances 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 before continuing with the YES flow to Business Process 8.2 – Manage Financial Close, where the process flow for Manage Payments for Employee Relocation ends.

Return to the Complete Text

Date modified: