Guideline on Common Financial Management Business Process 3.2 – Manage Travel
Long description for image: Figure 10. Manage Travel Claims and Advance Requests (Subprocess 3.2.7) – Level 3 Process Flow
This figure is a process flow diagram comprising activities, connectors, inputs/outputs, and decisions.
The diagram depicts the Level 3 process flow for Manage Travel Claims and Advance Requests (Subprocess 3.2.7), which is launched by one of the following:
- Connector from Manage Travel Administration (Subprocess 3.2.6) and the input of a travel claim or travel advance; or
- Connector from Manage Travel Requests (Subprocess 3.2.3) and the input of a travel authorization and advance request.
Both connectors trigger four sequential activities:
- Activity 3.2.7.1 – Confirm That Travel Authorization Terms are Met;
- Activity 3.2.7.2 – Confirm That Payee Is Eligible for Payment;
- Activity 3.2.7.3 – Ensure That Documents are in Agreement; and
- Activity 3.2.7.4 – Ensure Payee Information Is Accurate.
The flow advances to the decision titled “Update/create vendor master file?” where the “Yes” flow goes to the connector for Manage Vendor Master Data File (Business process 7.1) before advancing with the “No” flow to three sequential activities:
- Activity 3.2.7.5 – Ensure That Financial Coding Is Correct;
- Activity 3.2.7.6 – Verify That Relevant Regulations, Policies and Directives Were Followed; and
- Activity 3.2.7.7 – Verify Accuracy of Transaction.
The flow continues to the decision titled “All information is accurate, valid and complete?” The “No” flow for this decision goes first to Activity 3.2.7.8 – Resolve Discrepancies and then revisits Activity 3.2.7.1 – Confirm That Travel Authorization Terms are Met and proceeds through the previously described flow. The “Yes” flow continues to Activity 3.2.7.9 – Exercise or Obtain Certification Authority, which results in an output in the form of certification pursuant to FAA, section 34.
The flow advances to a connector for Manage Commitment (Subprocess 3.2.5) before continuing to the output of a request for payment, and then to a connector for Perform Payment Authority (Subprocess 3.2.8).
Activity 3.2.7.8 – Resolve Discrepancies also has a connector from Perform Payment Authority (Subprocess 3.2.8).