FMCF 101 Training for Agencies

Financial Management Quality Service Management Office

(FM QSMO)

As of: November 2023
Disclaimer

The purpose of this training is for the U.S. Department of the Treasury’s Financial Management Quality Management Service 

Office (FM QSMO) to provide a general overview of the FM QSMO Marketplace Financial Management Capability Framework 

(FMCF). The training is not intended to supersede or conflict with the FMCF materials published on the FM QSMO website.

The training material may be updated periodically to provide additional clarity or information.
Page 3 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

1. Financial Management Capability Framework (FMCF) Overview

2. Describe each FMCF artifact

a) Define – what is the artifact

b) Use – how to use the artifact

c) Example – visual example of the artifact

d) Connecting each artifact

e) Additional considerations

3. Key Takeaways

4. Appendix

Table of Contents
Page 4 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Learning Objectives

Locate, define and restate the purpose and use of each FMCF artifact. (Learning 

Objective: FMCF Purpose)

By the end of this training, Agencies will have the information needed to:

Recognize how the FMCF was designed and identify continued opportunities to 

provide feedback. (Learning Objective: Design and Development of the FMCF)

Use the FMCF to benchmark and standardize their existing FM capabilities and 

prepare a path toward modernization. (Learning Objective: Standardization and 

Modernization)
FMCF Background
• The Financial Management Capability Framework (FMCF) 

is the set of standards and capabilities that define baseline 

needs for services and solutions in the FM QSMO 

Marketplace, including requirements for cloud-based core

financial systems (Core FS).

• The FMCF consists of nine (9) sections or components, 

described in the visual to the right.

• The FMCF artifacts can be found on the FM QSMO -

FMCF Webpage.

• The FMCF is used as a basis for evaluating and ensuring 

the Marketplace solutions and services meet baseline 

needs.

• Agencies can use the standards and capabilities outlined in 

the FMCF to benchmark their current FM operations and/or 

systems, and use the results to identify, plan for, and

support modernization opportunities.

Learning Objective:

• FMCF Purpose and Definitions

• Standardization and Modernization

Page 6 L E A D ∙ T R A N S F O R M ∙ D E L I V E R

Purpose
Core FS Baseline Solution

The FM QSMO Marketplace will offer Core Financial Systems (Core FS) available in a cloud environment, delivered through a platform 

as a service (PaaS) or software as a service (SaaS) delivery and pricing model. Marketplace Core FS offerings will include a Baseline 

Solution that standardizes what is common and enables agencies the flexibility to further configure to meet agency needs.

The Core FS consists of the:

• Baseline Solution: A combination of configuration, enhancements 

and extensions designated as the starting point for all Federal 

agency implementations of the Core FS. The FMCF defines what 

is included in the Baseline Solution.

• Agency Solution: A combination of configurations, enhancements 

and extensions above and beyond the Baseline Solution, 

controlled by the customer Agency.

The Core FS gives agencies the flexibility to:

• define additional requirements above the Baseline solution, and

• select vendors that offer configurations best suited to their needs.

Key Takeaway: Core FS = Baseline Solution (configuration to meet FMCF) + Additional Agency Configurations

Page 7 L E A D ∙ T R A N S F O R M ∙ D E L I V E R
Evolution of FM Standards in the Federal Government

The FM QSMO developed the FMCF by utilizing policy and standards as a foundation and then engaging with numerous stakeholders to 

understand their needs, requirements, capabilities, and pain points.

• The Federal government established mission-support functional service areas to enable service customers (e.g., program offices) to deliver 

on their mission and accomplish End-to-End Business Processes.

• The Federal Integrated Business Framework (FIBF) strived to create a set of common Business Standards across each Service Area where 

agencies would coordinate and document common business needs based on authoritative policy across agencies, focusing on outcomes, 

capabilities, and data.

• The Financial Management Line of Business (FMLoB) Managing Partner oversaw the development of the FIBF standards and continue to

manage their maintenance, collaborating with agencies from across the federal government.

• When the FM QSMO was established in 2019, the FM QSMO expanded upon the FFM FIBF standards to define the baseline requirements 

for services and solutions in the FM QSMO Marketplace. The result was the FMCF.

Learning Objective: Design 

and Development of FMCF

Page 8 L E A D ∙ T R A N S F O R M ∙ D E L I V E R

Policy & 

Standards RFIs FM Line of Business CX Sessions

Other FIBF 

Functional 

Areas

Agency 

Meetings

Vendor

Meetings

Bureau of the 

Fiscal Service FMSC Other FM Stakeholders

Continuous review, consultation, collaboration and improvement

FM Capability 

Framework (FMCF)
FMCF and the Federal Integrated 

Business Framework (FIBF)
Page 10 L EAD ∙ T R A N S F O R M R A N S F O R M ∙ D E L I V E R E L I V E R

Federal Financial Management Federal Integrated Business Framework

The Federal Financial Management (FFM) Federal Integrated Business Framework (FIBF) artifacts are the 

foundation of the FMCF. 

1

Functions 

and Activities

2

Business 

Use Cases

3

Business 

Capabilities 

4

Business 

Data 

Elements

5

Core FS 

Pre-Built 

Business 

Reports

6

Core FS 

Pre-Built 

Business 

Information 

Exchanges

9

FFM 

Service 

Measures

FM Provider Service Measures

CYB, ERM, 

ITS Service 

Measures

9
FFM Functions and Activities 1

• The FFM Functions & Activities serve as the basis for a common understanding of the FM services agencies 

need and solutions that should be offered.

• The FFM Functions & Activities establish the scope of FM QSMO Marketplace services and solutions, and they

can serve as a tool to evaluate the financial management activities their agency performs.

• Functions: Breakdown of a functional area into categories of FM services provided to customers.

• Activities: Within a function, processes that provide identifiable outputs/outcomes to customers are defined 

as activities.

• Accounting Professionals: Define the scope of financial management activities performed by the agency and 

provide a general awareness of financial management activities to new staff.

• Financial Systems Professionals: Link the financial management activities performed by the agency to the 

system requirements for execution.

• Acquisition Professionals: Define the scope of a vendor’s financial management capabilities and determine 

what’s within the scope of FM QSMO Marketplace acquisitions.

Learning Objective:

FMCF Purpose and

Definitions

What are the FFM Functions & Activities?

Page 11 L E A D ∙ T R A N S F O R M ∙ D E L I V E R

How should I use the FFM Functions & Activities?
Page 12 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Function ID Function Name

FFM.010 Budget Execution

FFM.020 Financial Asset Information Management

FFM.030 Payable Management

FFM.040 Revenue Management

FFM.050 [Retired]

FFM.060 Receivable and Collection Management

FFM.070 Delinquent Debt Management

FFM.080 Cost Management

FFM.090 General Ledger Management

FFM.100 Financial Reconciliation

FFM.110 Financial / Performance Reporting

Function ID Activity ID Activity Name Activity Definition Activity FFMSR 

Reference Authoritative and Other References

FFM.090

FFM.090.010

General Ledger 

Setup and 

Maintenance

Establish and maintain general ledger account classifications, categories, 

and subcategories consistent with the USSGL accounts; Establish and 

maintain proprietary and budgetary account attributes; Establish and 

maintain attributes to support agency financial performance and operations 

reporting

FFMSR 1.1.1

Defining GL Accounts 

and Attributes;

...

•(63) OMB Circular A-11, Preparation, Submission and 

Execution of the Budget, Part 2, Preparation and 

Submission of Budget Estimates, Section 51, Basic 

Justification Materials;

•(111) USSGL, Section I: Chart of Accounts;

...

FFM.090.020 General Ledger 

Posting

Receive general ledger account transaction information provided by 

supporting financial management operations; Prepare manual journal

vouchers and route for approval (as needed); Post general ledger 

proprietary, budgetary, and memorandum account transactions; Includes 

posting adjustments to the general ledger, discrete and aggregated 

transactions from subledgers, and transactions funded, obligated, or 

expended over multiple years to general ledger accounts that do not close

FFMSR 1.1.2

Posting GL Transactions

•(113) USSGL, Section III: Account Transactions;

•(114) USSGL, Section IV: USSGL Account Attributes;

•(117) USSGL, Section VII: GTAS Validations and Edits, 

Closing Edit Details.

FFM Functions and Activities Example 1

The images and call out boxes below describe each part of the FFM Functions and Activities. 

The derived identifier for an 

FFM function

Name of the financial 

management function

The derived identifier 

for an FFM activity

Full definition and 

description of the activity 

along with its applicability

The 

FFMSR(s) 

that 

support 

the activity

Legislation, regulation, 

policies, guidance, and 

standards applicable to 

the activity

Process that provides 

identifiable outputs/outcomes 

to customers 
FFM Business Use Cases

• The FFM Business Use Cases are a set of agency “stories” that document the key activities, inputs, outputs, and other lines of 

business intersections to describe how the Federal government operates. They are organized into eleven end-to-end business 

processes that have a federal financial management impact.

• Each use case explains how federal agencies are to carry out a specific financial management process, starting with a user's goal 

and goes through the steps to take until the goal is fulfilled.

• In a business use case, you can expect to see interactions and events between FFM and other service areas as well as business 

information expected to be received, processed, and/or provided.

• Use Cases are agnostic as to whether the events in the business use case are automated, semi-automated, or manually 

accomplished.

• Accounting Professionals:

• Define, assess, and/or standardize financial management processes.

• Evaluate the steps needed to perform a processes shared with other Functional areas and establish the appropriate roles 

and responsibilities with other Functional areas.

• Financial Systems Professionals: Understand the business scenarios that would cause an FM solution to be exercised or 

transmit business information.

• Acquisition Professionals: Evaluate FM services/solutions capabilities during the acquisition process.

What are the FFM Business Use Cases?

How should I use the FFM Business Cases?

Learning Objective:

FMCF Purpose and

Definitions

Page 13 L E A D ∙ T R A N S F O R M ∙ D E L I V E R

2
Page 14 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

FFM Business Use Case Example 2

The images and call out boxes below describe each part of the FFM Business Use Cases. 

11 End-to-End Business 

Processes 

Typical processing that occurs in within a 

specific business process

Flow of events, of both FFM and other 

Service Areas, as well as Inputs and 

Outputs
Page 15 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Tie it Together: FFM Business Use Cases and FFM 

Functions and Activities 1 2

The FFM Business Use Cases are executed through Service Activities, described in the FFM Functions & Activities artifact.

FFM Functions and Activities

1

Functions 

and 

Activities

Business Use Cases

2

Business 

Use Cases
FFM Business Capabilities

(Federal Financial Management System Requirements)

What are the FFM Business Capabilities (Federal Financial Management System Requirements)?

• The FFM Business Capabilities describe outcome-based business needs mapped to Federal government authoritative 

references, forms, and data standards.

• The FFM Business Capabilities artifact is also referred to as the Federal Financial Management System Requirements 

(FFMSR) which agencies are required to comply with.

• For CFO Act agencies, these requirements determine compliance with the Federal Financial Management Improvement Act 

of 1996 (FFMIA).

• The FFM Business Capabilities (FFMSR) are categorized by Input (I) to capture information, Process (P) to perform the 

action, or Output (O) to provide information, and when used together, they support the execution of a business process.

How should I use the FFM Business Capabilities (FFMSR)?

• Accounting Professionals: Demonstrate compliance with FFMIA.

• Financial Systems Professionals:

• Support the development of technical requirements, system acceptance test plans, scenarios, and scripts.

• Periodically evaluate the system’s ability to meet the requirements, and where gaps in exist, identify further system 

enhancements.

• Acquisition Professionals: Define requirements and evaluation criteria for financial management system acquisitions.

Learning Objective:

FMCF Purpose and

Definitions

Page 16 L E A D ∙ T R A N S F O R M ∙ D E L I V E R

3
Page 17 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

FFM Business Capabilities (FFMSR) Example 3

The images and call out boxes below describe each part of the FFM Business Capabilities (FFMSR). 

Identifies and names an 

activity that groups 

requirements

Classify the requirements as 

a federal government unique 

data input (DI), process (P), 

or data output (DO).

Contain the requirement 

statement. 

Provides the current federal regulatory authoritative 

sources that contain additional clarification of 

business processes and data specifications.

Function 

ID

Federal Financial 

Management 

System Function

Requirement 

ID

DI-Data 

Input

P-Process 

DO-Data 

Output

Federal Financial Management System Requirements Federal Financial Management System Authoritative Reference

1.1.2 Posting GL 

Transactions

1.1.2.1 DI Capture GL account transaction information provided by supporting 

financial management operations (for example, payments, receipts, 

liabilities, assets, and reimbursable/ intragovernmentals) consistent 

with the USSGL account attributes, account transaction codes, 

account transaction categories, and account transaction

subcategories defined in the TFM.

•TFM Volume I, Supplement: United States Standard General 

Ledger (USSGL) Section I: Chart of Accounts; Section II:

Accounts and Definitions; Section III: Account Transactions; 

Section IV: USSGL Account Attributes.

1.1.2.2 P Post GL proprietary, budgetary, and memorandum account 

transactions consistent with USSGL account attributes, account 

transaction codes, account transaction categories, and account 

transaction subcategories as defined in the TFM.

•TFM Volume I, Supplement: United States Standard General 

Ledger (USSGL) Section I: Chart of Accounts; Section II:

Accounts and Definitions; Section III: Account Transactions; 

Section IV: USSGL Account Attributes.

1.1.2.3 P Close non-fiduciary and fiduciary accounts consistent with USSGL 

account closing table rules as

defined in the TFM.

•TFM Volume I, Supplement: United States Standard General 

Ledger (USSGL), Section III: Account Transactions; Section

VII: GTAS Validations and Edits, Closing Edit Details.

1.1.2.4 P Maintain ability to post transactions funded, obligated, or expended 

over multiple years to GL accounts that do not close (for example, 

undelivered orders– obligations, unpaid; delivered orders–

obligations, unpaid; authority outlayed not yet disbursed) consistent 

with the TFM.

•TFM Volume I, Supplement: United States Standard General 

Ledger (USSGL), Section I: Chart of Accounts; Section II:

Accounts and Definitions; Section III: Account Transactions; 

Section VII: GTAS Validations and Edits, Closing Edits Details.
Page 18 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Tie it Together: FFM Functions and Activities and 

FFM Business Capabilities (FFMSR) 3 1

The FFM Business Capabilities (FFMSR) provide the authoritative reference for each FFM Function and Activity. They 

describe the common, baseline business processes and information flows needed to execute a Service Activity. 

Business Capabilities (FFMSR)

3

Business 

Capabilities 

(FFMSR) 

FFM Functions and Activities

1

Functions 

and 

Activities
FFM Business Data Elements

How should I use the FFM Business Data Elements?

• Accounting and Financial Systems Professionals: Define the required data elements in a core financial 

management system solution as they are necessary to execute financial management processes described in 

the Business Use Cases.

• Acquisition Professionals: Reference in solicitation requirements.

Learning Objective:

FMCF Purpose and

Definitions

Page 19 L E A D ∙ T R A N S F O R M ∙ D E L I V E R

4

What are the FFM Business Data Elements? 

• The FFM Business Data Elements artifact identifies the minimum set of business data elements required to 

support the inputs and outputs identified in the business use cases, capabilities, business information exchanges 

and business reports.

• The FFM Business Data Elements enable agencies and providers to have a definitive list of agreed-upon data 

elements to execute federal financial management processes. 

• The FFM Business Data Elements were derived using the Government-wide Spending Data Model (formerly 

known as the DATA Act Information Model Schema), Fiscal Service Data Registry, and other authoritative sources.

• The FM QSMO also designated a subset of FFM Business Data Elements as “Core FS Pre-Loaded Master 

Reference Data”, which indicate the subset of data elements that require pre-loaded domain values in the Core 

FS Baseline Solution.
Page 20 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

FFM Business Data Elements Example 4

The images and call out boxes below describe each part of the FFM Business Data Elements.

Functional 

Area

Functional 

Area 

Steward

Data Element 

Label Definition Service Activity Reference

Business 

Capability 

Reference

Authoritative 

and Other 

Source(s)

Data Group Name Example 

Value

Domain 

Values

Core FS 

PreLoaded 

Master 

Reference 

Data

Related Data 

Element 

Reference(s)

FFM FFM ProgramActivity

Code

Code of a specific 

activity or project 

as listed in the 

program and 

financing 

schedules of the 

annual budget of 

the United States 

Government.

FFM.010.010 

Budget Setup and 

Maintenance;

FFM.010.030 

Budgetary 

Reporting;

FFM.090.010 

General Ledger 

Setup and 

Maintenance;

FFM.090.020 

General Ledger 

Posting;

...

FFMSR 

1.1.1.1;

FFMSR 

1.1.2.2;

FFMSR 

1.3.1.1;

FFMSR 

1.3.1.2;

FFMSR 

1.4.1.1;

FFMSR 

2.1.1.1;

FFMSR 

2.1.1.3; 

FFMSR 

2.1.3.1

(17) OMB Circular 

A-11, Preparation, 

Submission, and 

Execution of the 

Budget;

(33) Governmentwide Spending 

Data 

Model(GSDM);

(48) TFM, Volume 

I, Part 2, Chapter 

6000 Agency 

Reporting 

Requirements for 

USAspending.gov

FFM Transaction 

Information;

FFM Transaction 

Line Information;

FFM Transaction 

Line of Accounting 

(LOA) Information;

Account 

Classification 

Structure (ACS) 

Information;

Program Activity 

Group Information

0002 (131)

USASpending

.gov, Program 

Activity File

https://files.us

aspending.go

v/reference_d

ata/program_

activity.csv

Use unique 

values in 

PROGRAM_

ACTIVITY_C

ODE

Required GSDM: 

ProgramActivity

Code;

USASpending.

gov: 

PROGRAM_AC

TIVITY_CODE

Functional Area 

establishing and 

using the data 

element and 

standard

Unique 

label

Business 

definition

Service 

Activities 

supported

Business 

Capabilities 

dependent 

on the 

element

Policies 

that 

provide a 

source 

need

Name of 

logically related 

business data 

elements

Acceptable 

Entry

Established 

set of valid 

values

Indicates whether preloading the master 

reference data identified 

or referenced in the 

Domain Values column is 

required

Reference to the 

same/similar Data 

Element defined 

in other sources.
Page 21 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Tie it Together: FFM Business Data Elements 1 3 4

The FFM Business Data Elements are the data fields needed to support the FFM Business Capabilities (FFMSR) and FFM 

Functions & Activities that are then executed through the FFM Business Use Cases. 

FFM Functions & Activities FFM Business Capabilities (FFMSR)

Functional 

Area

Functional 

Area 

Steward

Data Element Label Definition Service Activity Reference

Business 

Capability 

Reference

Authoritative and Other 

Source(s)

FFM FFM ProgramActivityCode Code of a specific activity or project 

as listed in the program and 

financing schedules of the annual 

budget of the United States 

Government.

FFM.010.010 Budget Setup and 

Maintenance;

FFM.010.030 Budgetary 

Reporting;

FFM.090.010 General Ledger 

Setup and Maintenance;

FFM.090.020 General Ledger 

Posting;

...

FFMSR 

1.1.1.1;

FFMSR 

1.1.2.2;

FFMSR 

1.3.1.1;

...

(17) OMB Circular A-11, 

Preparation, Submission, 

and Execution of the 

Budget;

(33) Government-wide 

Spending Data 

Model(GSDM);

(48) TFM, Volume I, Part 

2, Chapter 6000 Agency 

Reporting Requirements 

for USAspending.gov
Page 22 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Tie it Together: FFM FIBF Artifacts #1 – 4 

The FFM FIBF Standards 

establish the first step towards 

government-wide agreement on 

outcomes, data, and crossfunctional end-to-end processes 

that will drive economies of 

scale and leverage the 

government’s buying power.

1

2

3

4

1

Functions 

and 

Activities

2

Business 

Use Cases

3

Business 

Capabilities 

4

Business 

Data 

Elements
Which FMCF artifact provides compliance with FFMIA? 

The FFM Business Capabilities (FFMSR)

QUIZ
Core FS Pre-Built Business Reports

What are the Core FS Pre-Built Business Reports?

• The Core FS Pre-Built Business Reports support FFM Functions and Activities and the FFM Business Use Cases. These reports are 

expected to be included in all Core FS solution offerings. 

• The Core FS Pre-Built Business Reports represent the minimum information the Government expects to be provided by a core 

financial management solution in a form users can print or share. Vendors are free to provide any format or technology as 

long as the required data elements are included.

• Note: Specifications for information to be transferred to another system/solution are provided in the Pre-Built FFM Business 

Information Exchanges (BIEs).

• The Core FS Pre-Built Business Reports are intended to provide information for a collection of financial transactions/documents 

based on commonly used data selection parameters.

• The Core FS Baseline Solution should also provide the capability for user-defined reports where the user can select FFM 

Business Data Elements and specify the presentation format and any calculated report data elements.

How should I use the Core FS Pre-Built Business Reports?

• Accounting and Financial Systems Professionals: Evaluate a financial management system’s capability to execute common 

financial reports and provide a baseline for additional reporting requirements, enhancements, or customizations.

• Acquisition Professionals: Reference in solicitation requirements.

Learning Objective:

FMCF Purpose and

Definitions

Page 24 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

5
Page 25 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

1. Report Name

2. Description of the report

3. The list of required and 

optional data selection 

parameters available to 

achieve the needed report 

content.

4. The name of the data 

element on the report.

5. A description of the 

intended content of the 

report data element.

6. The label of one or more 

FFM Business Data 

Elements when the source 

for the Report Data Element 

content is within the FFM 

Functional Area

7. The identifier of another 

FIBF Functional Area. 

8. An indicator of "X" when the 

content of a Report Data 

Element is calculated from 

other Report Data Elements.

Core FS Pre-Built Business Reports Specification Example

The image and corresponding numbered listing describe each part of the Core FS Pre-Built Business Reports specifications. 

1

2

3

4

5

6 7 8

5
Core FS Pre-Built Business Information 

Exchanges (BIEs)

What are the Core FS Pre-Built Business Information Exchanges?

• Core FS solutions need to exchange data with other systems. Business rules provide the common exchanges of business information 

between two Functional Areas or between a Functional Area and a Centralized Service/Solution. 

• The Core FS Pre-Built BIEs are specifications that depict the data and transactional relationships and requirements for a given business

system that exchanges data with the Core FS.

• Each BIE describes the following for exchanges of data between the non-Core FS business system and the Core FS:

• Applicable BIE transaction types, e.g., Entity-Payee/Payer Maintenance and Order-Obligation.

• Data Elements that are mandatory, conditionally required, or optional, using FIBF-based Data Element Labels where a FIBF standard

exists.

• Related BIE logic, i.e., business rules.

• Where a FIBF standard doesn’t exist, the Core FS Pre-Built BIE artifact incorporates or refers to the existing interface, integration, or data

exchange specifications already in use. FM QSMO works in conjunction with other Treasury Centralized Services and Functional Areas to 

maintain the BIE list.

• The Core FS Pre-Built BIE specifications are technology-agnostic, and providers may use them to design the Core FS Baseline offering’s

integrations, interfaces, or Web-service oriented architecture that enables the exchange of data.

How should I use the Core FS Pre-Built BIEs?

• Accounting and Financial Systems Professionals: Define the information to exchange between the Core FS, other functional areas’

solutions and services (i.e., outside of financial management) and government-wide centralized services and inform the selection of non-FM

business systems.

• Acquisition Professionals: Reference in solicitation requirements.

Learning Objective:

FMCF Purpose and

Definitions

Page 26 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

6
Page 27 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

FIBF FFM: Data 

Element Label

FIBF FFM: Data 

Element Definition

FIBF FFM: Data Group 

Name FIBF FFM: Domain Values BIE: Applicable FFM Transaction Type(s)

BIE: Required/

Optional/

Conditional

FIBF ACQ: 

Data Element 

Label

FIBF ACQ-FFM: 

BIE Logic (Business Rules)

FinancialTransa

ctionTypeCode

A code that identifies 

the type of transaction 

generated by a source 

system and processed 

by a financial 

management system. 

FFM Transaction 

Information

Entity-Payee/Payer Maintenance;

Requisition-Commitment;

Order-Obligation;

Receipt and Acceptance-Accrual;

Invoice-Payable;

Billing Invoice-Receivable;

Public Receipt-Collection; 

Journal Voucher-Accrual;

Journal Voucher-Asset; 

Journal Voucher-Payroll

Entity-Payee/Payer 

Maintenance;

Requisition-Commitment;

Order-Obligation;

Receipt and AcceptanceAccrual;

Invoice-Payable;

Billing Invoice-Receivable;

Public Receipt-Collection; 

Journal Voucher

Required N/A Always set to "EntityPayee/Payer Maintenance" for 

this transaction type

Core FS Pre-Built Business Information Exchanges Example

The images and call out boxes below describe each part of the Core FS Pre-Built BIEs. 

Label and definition of 

the FFM Data Element

List of FFM 

Transaction data 

groups to which 

the data element 

belongs

List of the FFM 

Transaction 

Types for which 

the FFM Data 

Element is 

applicable

Provides the 

business 

logic 

(business 

rules) used 

by the other 

Functional 

Area to 

populate the 

element

Provides the 

determination 

whether the FFM 

Data Element is 

always required, 

optional, or required 

under only specific 

business conditions

Established 

set of valid 

values

Provides the label of 

the other Functional 

Area's data 

element(s) to be 

used to populate the 

FFM Data Element. 

"N/A" if a specific 

FFM Data Element 

does not apply to the 

FFM Transaction 

Type or other 

Functional Areas

6
Page 28 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Tie it Together: FFM Business Data Elements, Core FS Pre-Built 

Business Reports, and Core FS Pre-Built BIEs 4 5 6

The FFM Business Data Elements provide the data fields needed to develop the FFM Core FS Pre-Built Business Reports 

and FFM Core FS Pre-Built Business Information Exchanges. 

Core FS Pre-Built BIE

FIBF FFM: 

Data 

Element 

Label

FIBF FFM: Data 

Element 

Definition

FIBF FFM: Data 

Group Name

FIBF FFM: Domain 

Values 

BIE: Applicable 

FFM Transaction 

Type(s)

BIE: 

Required/

Optional/

Conditional

AgencyIdenti

fier

The Treasury 

Account Symbol 

(TAS) component 

that identifies the 

department, 

agency or 

establishment of 

the U.S. 

Government that is 

responsible for the 

TAS. Agency 

Identifier is also 

used apart from 

the TAS to identify 

a major 

department or 

independent 

agency of the 

Federal 

government.

FFM Transaction 

Information;

FFM Transaction 

Line Information;

FFM Transaction 

Line of Accounting 

(LOA) Information;

Account 

Classification 

Structure (ACS) 

Information;

Treasury Account 

Symbol (TAS) 

Information;

Program Activity 

Group Information;

Reimbursable 

Organization 

Information

Use Treasury Bureau of 

Fiscal Service Shared 

Accounting Module (SAM) 

Service: Treasury Account 

Symbol (TAS-BETC)

https://www.fiscal.treasury.g

ov/sam/ 

RequisitionCommitment;

Order-Obligation;

Receipt and 

Acceptance-Accrual;

Invoice-Payable;

Billing InvoiceReceivable;

Public ReceiptCollection; 

Journal Voucher

Conditional: 

Required 

when 

AgencyFundC

ode is not 

provided

Core FS Pre-Built Business Reports

Status of Funding

REPORT DATA SELECTION 

PARAMETERS 

• Accounting Period

• Agency Identifier

• Treasury Account Symbol OR Agency Fund Code (Optional)

...

Report 

Item

Report Data Element 

Label Report Data Element Description FFM Business Data Element Label

1 Accounting Period The fiscal period reported on financial reports. 

Accounting period includes a four digit fiscal year and 

two digit fiscal month. In addition to the standard 

fiscal months of 1-12, the two digit fiscal month may 

include months 13-15 which represent adjustment 

periods. 

AccountingPeriod

2 Agency Identifier The agency code identifying the department or 

agency/bureau that is responsible for the account.

AgencyIdentifier

3 Treasury Account 

Symbol 

The identification code assigned by Treasury, in 

collaboration with OMB and the owner agency, to an 

individual appropriation, receipt, or other fund 

account.

TreasuryAccountSymbol

Data Element Label Definition Service Activity Reference Business Capability 

Reference

Business Information 

Exchange (BIE)

Core FS 

Pre-Loaded Master 

Reference Data

AgencyIdentifier The Treasury Account Symbol (TAS) component that identifies the 

department, agency or establishment of the U.S. Government that is 

responsible for the TAS. Agency Identifier is also used apart from 

the TAS to identify a major department or independent agency of the 

Federal government.

FFM.010.010 Budget Setup and Maintenance;

FFM.010.030 Budgetary Reporting;

FFM.090.010 General Ledger Setup and 

Maintenance;

...

FFMSR 1.1.1.1;

FFMSR 1.1.2.2;

FFMSR 1.3.1.1;

FFMSR 1.3.1.2;

...

ACQ-FFM BIE;

FFM-DATA Act Files 

BIE;

GRM-FFM BIE;

RPM-FFM BIE;

TRT-FFM BIE

Required

FFM Business Data Elements
QUIZ

Which FMCF artifact provides the data fields needed to 

develop the FFM Core FS Pre-Built Business Reports and FFM 

Core FS Pre-Built Business Information Exchanges? 

The FFM Business Data Elements.
FM Provider Service Measures 9

• The FM Provider Service Measures define how the government measures successful delivery of outcomes

based on timeliness, efficiency, and accuracy targets.

• Service Activity Level – a measure that identifies the anticipated work to be accomplished or resources

needed and contains a unit volume (e.g., volume, amount, count).

• Service Performance Level – A measure that identifies an outcome to be achieved by the 

responsible party and contains a unit value (e.g., percent, time, etc.).

• The FM Provider Service Measures:

• Define how the government measures successful delivery of FFM outcomes, as well as the Cyber (CYB), 

Electronic Records Management (ERM), and IT Services (ITS) priorities that support FFM activities. 

• Include both provider measures and service customer measures (e.g., approval timeliness).

• Establish measure targets, reporting frequencies, and measurement methods/sources/formulas applicable

to all Federal agency implementations.

• Defer establishing measure targets, reporting frequencies, and measurement methods/sources/formulas 

where it is more appropriate for each Federal agency to do so (e.g., workload volume) or for the Federal 

agency customer to discuss with its FM solution/service provider during the Federal agency acquisition 

process (e.g., service desk response time).

Learning Objective:

FMCF Purpose and

Definitions

Page 30 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

What are the FM Provider Service Measures?
FM Provider Service Measures

How should I use the FM Provider Service Measures?

• All (Accounting, Financial Systems, and Acquisition Professionals): The FM QSMO will monitor three 

provider service measures (QSMO Monitoring Measure Category) for Marketplace solutions and services. Federal 

agency customers will report measurements to the FM QSMO. QSMO Monitoring Measures include:

• Service Measure Target Success Ratio (FFM)

• Service Customer Satisfaction with Service Provider

• Service Customer Satisfaction by Solution/Service Package (FFM)

• Federal Agency Customers may also select Service Measures from the standard portfolio of FM Service

Measures, as well as agency-specific required Service Measures. These may be part of the agency’s acquisition

requirements.

• Develop Customer Service Agreements that specify the agency’s required service level targets, measures, and 

reporting.

Learning Objective:

FMCF Purpose and

Definitions

Page 31 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

9
Page 32 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

FM Provider Service Measures Example

The images and call out boxes below describe each part of the FM Provider Service Measures. 

1. Functions and 

Activities reference as 

defined in the FIBF

2. Unique ID, name, and 

description for the measure

4. Measure 

Category 

describes 

monitoring 

/ reporting 

of the 

measure

5. Identifies 

Activity / 

Performance 

Measure

3. 

Service 

measure 

threshold 

or goal

6. Identifies whether the service is measuring: Availability, Compliance, 

Efficiency, Quality, Reliability, Security, Timeliness, Usability, Utilization, 

or Volume

7. Organization performing the activity that produces the service measure 

result

8. Organization accountable for monitoring and analyzing service 

measurement results and managing service delivery issues

9. Time period for assessing and reporting the service measurement result

10. Level(s) of detail for reporting the service measurement result

11. Calculation used to determine the service measurement result

6 7 8 9 10 11

9

Function Activity

Service 

Measure 

ID

Service 

Measure Name

Service 

Measure 

Description

Service 

Measure 

Target

Service 

Measure 

Category 

Service Level 

Type 

Service 

Measure 

Type

Performing 

Organization

Accountable 

Organization

Service 

Measurement 

Frequency

Service 

Measurement 

Reporting 

Level

Service 

Measurement 

Formula

FFM.000 All 

Functions

FFM.000.000 

All Activities

FFM.000.

000.0032

Solution/service 

Performance 

Issue Resolution 

Timeliness

Percentage (%) 

of 

solution/service 

performance 

issues resolved 

by due date

98% Provider 

Operations

Performance 

Level

Timeliness Service 

Provider

Service 

Management 

Office

Monthly Marketplace;

Service 

Provider;

Service 

Customer

Count of 

solution/service 

performance 

issues resolved 

by due date / 

Total count of 

solution/service 

performance 

issues resolved
Additions to the FFM FIBF
Page 34 L EAD ∙ T R A N S F O R M R A N S F O R M ∙ D E L I V E R E L I V E R

Adding on to the FFM FIBF Standards

The FM QSMO added requirements from the Cyber (CYB), Electronic Records Management (ERM), and IT FIBF standards, 

and created the FM Solution/Service Evaluation Criteria as an extension to the FFM FIBF standards. The combination of the 

FFM FIBF standards, non-FFM FIBF standards, and the extensions to the FFM FIBF resulted in the FMCF. 

Functions and 

Activities

Business Use 

Cases

Business 

Capabilities 

Business Data 

Elements

Core FS PreBuilt 

Business 

Reports

Core FS PreBuilt 

Business 

Information 

Exchanges

7

CYB, ERM, 

ITS 

Functions, 

Activities, and 

Business 

Capabilities

FM Solution / 

Service 

Evaluation 

Criteria

8

FFM 

Service 

Measures

FM Provider Service Measures

CYB, ERM, 

ITS Service 

Measures
CYB, ERM, ITS Functions, Activities, 

and Business Capabilities

What are the CYB, ERM, ITS Functions, Activities, and Business Capabilities?

• The CYB, ERM, and ITS artifacts establish expectations for FM solutions and services in the 

Marketplace. 

• These include the functions, activities, and capabilities from federal cybersecurity, ITS, and 

ERM which must be incorporated into FM solutions and services. 

How should I use the CYB, ERM, ITS Functions, Activities, and Business Capabilities?

• Financial Systems Professionals: Prescribe the technology standards that FM solutions must 

adhere to.

• Acquisition Professionals: Reference in solicitation requirements.

Learning Objective:

FMCF Purpose and

Definitions

Page 35 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

7
FM Solution/Service Evaluation Criteria 8

What are the FM Solution/Service Evaluation Criteria?

• The FM Solution/Service Evaluation Criteria are used by the FM QSMO when evaluating potential offerings for the FM 

QSMO Marketplace and during Federal Agency Acquisition. This includes business, technology design, and technology

operation criteria for evaluating FM solutions/services and programmatic, economic, and organizational criteria for

evaluating the providers of FM solutions/services. The purpose of each evaluation criteria is as follows:

• Business – evaluates the ability to achieve FM business outputs and outcomes using the FM solution/service; also 

evaluates conformance with FMCF business standards and requirements and usability of an FM solution.

• Technology Design – evaluates the FM solution/service technical architecture and design for servicing customers; 

also evaluates conformance with FMCF technical requirements and capabilities.

• Technology Operation – evaluates the FM solution/service’s ability to respond to user demand and changes 

needed in the FM solution/service; also evaluates conformance with FMCF operational requirements and 

capabilities.

• Programmatic – evaluates a provider’s strategy and management of FM solution/service offerings and delivery.

• Organizational – evaluates a provider’s organizational ability to deliver quality FM solutions/services and ensure 

customer satisfaction.

How should I use the FM Solution/Service Evaluation Criteria?

• All (Accounting, Financial Systems, and Acquisition Professionals): Understand how the FM QSMO evaluates 

vendors for entry into the FM QSMO Marketplace.

Learning Objective:

FMCF Purpose and

Definitions

Page 36 L E AD ∙ T RA NS F O RM ∙ D EL I VER 
Page 37 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

FM Solution/Service Evaluation Criteria Example 8

The images and call out boxes below describe each part of the FM Solution/Service Evaluation Criteria. 

A factor used to 

determine whether an 

FM solution/service or 

provider sufficiently 

meets the 

Government's needs 

and constraints

The name 

of a group of 

evaluation 

indicators

An observable 

indication of 

whether an FM 

solution/service or 

provider meets 

the Government’s 

needs and 

constraints

The level and time 

at which the criteria 

and indicator 

should be 

evaluated

Name or title of the 

documentation that 

provides more 

detailed 

information on the 

Government's 

needs or 

constraints

Contains a description of the type of 

evidence that would enable the 

Government to determine if its needs or 

constraints have been met for FM 

solutions/services and providers with 

offerings under any of the FM QSMO 

Marketplace Categories
Page 38 L EAD ∙ T R A N S F O R M ∙ D E L I V E R

Other relevant FM QSMO resources: 

• Guide to the FM QSMO Marketplace: This 

document explains the scope of the 

Marketplace and how the FMCF will be 

used. 

• FM Solution/Service Definition Template: 

This template is used to document provider 

offerings in the Marketplace, using the FIBF 

FFM Functions and Activities and Federal 

Service Delivery Layers and Resources. 

These are used when evaluating FM 

solutions/service offerings and to populate 

the FM QSMO Marketplace Service 

Catalog.

Additional Considerations

Core FS Baseline Solution 

providers are expected to 

maintain a version of the 

Core FS Pre-Built Business 

Reports as specified in this 

document. Core FS 

Solution Providers may add 

additional fields, but the 

fields listed in this 

document are the minimum 

required for acceptance. 

As updates are made to the 

FMCF (e.g., new 

specifications for Core FS 

Pre-Built Business Reports), 

Core FS providers and 

agencies are expected to 

incorporate the new 

specifications into their Core 

FS Baseline Solution. 

The FM QSMO will continue 

to collaborate with agencies 

and industry partners on 

changes to the FMCF.

Learning Objective: 

Marketplace 

Services/Solutions
Key Takeaways
Page 40 L EAD ∙ T R A N S F O R M R A N S F O R M ∙ D E L I V E R E L I V E R

Key Takeaways

The FMCF is the set of standards and capabilities that define baseline needs for services and 

solutions in the FM QSMO Marketplace, including cloud-based core financial systems (Core 

FS). More information can be found on the Financial Management Capability Framework 

website. (Learning Objective: FMCF Purpose)

The FM QSMO developed the FMCF by utilizing policy and standards as a foundation and then 

incorporating inputs from stakeholders around their needs, requirements, capabilities, and pain 

points. Agencies are encouraged to provide feedback and engage with the FM QSMO on the 

enhancement of the FMCF. (Learning Objective: Design and Development of the FMCF)

Agencies can use the FMCF to help standardize and modernize their financial management 

operations. (Learning Objective: Standardization and Modernization)
Thank You

Email the FM QSMO at FMQSMO@fiscal.treasury.gov

Visit us at www.fiscal.treasury.gov/fmqsmo
Appendix
Page 42 L E AD ∙ T RA NS F O RM ∙ D EL I VER 

Glossary

Readers can find a glossary of terms referenced in the FM QSMO FMCF 101 Training within the Guide to the FM

QSMO Marketplace.