Business Use Case Overview

Treasury's Office of Financial Innovation and Transformation (FIT) is designated as the managing parter for the Federal Financial Management (FFM) Line of Business. With the assistance of a working group consisting of most of the CFO Act agencies and shared service providers, FIT has developed a library of FFM business use cases which reflect the business needs, or requirements that nan agency must follow, in the financial management community.

Select version to view notes:

The FFM Business Use Case Library provides agencies with a resource for:

  • Improving federal financial management workflow and process efficiency
  • Evaluating impacts to federal financial management business processes due to changes in legislation, regulation, guidance, and procedures
  • Evaluating the impact of sequential steps, or events, needed to perform a process where the responsibility for a successful outcome is shared with another Service Area
  • Refining roles and responsibilities among agency finance, program, and other supporting function offices

Service Area, Function, and Activity

Program offices in an agency need various administrative and support systems, procedures, and personnel to deliver on their program missions,  The term "service area" is used to describe the systems, procedures, and personnel that accomplish the necessary end-to-end business processes.

Financial Management (FM) is a service area.  Other service areas include Budget Formulation, Acquisition, Property Management, Human Resource Management, Grants Management, Loans Management, Travel and Relocation Management, and Sales Order and Fulfillment Management.

A service function is a further breakdown of a service area into categories of services provided to service customers.  Examples of FM service functions are Budget Execution, Payable Management, and General Ledger Management.

Within a service function, service activities are the processes that provide identifiable outputs or outcomes to service customers. Example in the area of Payable Management are Payee Set-up and Maintenance, Payment Processing, and Payment Disbursement. 

Service Area Function Activity

A complete listing of FFM Service area functions and activities may be found on the Functions & Activities page. Most of the end-to-end business processes require integration across multiple service areas with their functions and activities to achieve the business outcome.


End-to-End Processes

Eleven end-to-end business processes with an FFM impact have been identified and agreed upon for government-wide use.  An end-to-end business process identifies a start-to-finish outcome for operational transactions and financial reporting. The end-to-end business process provides the context for executing financial management services. Examples of end-to-end processes are Procure-to-Pay and Agree-to-Reimburse.

Business Scenarios

Business scenarios identify differing situation or conditions that occur when executing and end to end business process and reflect the scope and complexity of federal government agency missions. Business scenarios also define various business conditions that would cause the FFM solution functionality to be exercised in a different order or with different business information. For example, the Procure-to-Pay business scenario for a complex software system is different than for a purchase card.

Business Use Cases

Business use cases represent typical processing that occurs in federal business operations. Business use cases are formed by combining business scenarios that could occur together with an end-to-end business process. For example use case 040.FFM.L2.02 Four-Way Match includes scenarios for four-way matching of accounts payable invoices and Prompt Payment Act calculations.

In a business use case, you can expect to see the following:

  • Interactions between FFM and other services areas
  • Business events to be accomplished by both FFM and other service areas
  • Business information expected to be received, processed, and/or provided

You will also see that use cases are agnostic as to whether the events in the business use case are automated, semi-automated, or manually accomplished. This allows an agency using the use cases to make the best decisions about where automation is most beneficial.

This page was last updated on June 10, 2021.