Attachment J-4.3_ FMCF-6 Core FS Pre-Built Business Information Exchanges Release FY2024.xlsx
XLSX spreadsheet 553 KB Posted
- Attached to
- E-Gov Travel Service, Next Generation (ETSNext) Travel and Expense (T&E) Technology Managed Service
- Solicitation number
- 47QMCB23R0011
- Issued by
-
GSA Federal Acquisition Service
About this file
This file describes a forthcoming solicitation for the E-Gov Travel Service, Next Generation (ETSNext) Travel and Expense (T&E) Technology Managed Service. The General Services Administration Federal Acquisition Service will issue the solicitation to acquire a managed service provider to operate ETSNext, which will replace the current E-Gov Travel system. ETSNext will provide a next-generation travel booking and expense management solution for federal employees. The solicitation number is 47QMCB23R0011 and responses are due based on the pre-solicitation posting date. The awarded contract will support federal agencies in migrating to the new ETSNext system for travel booking, reimbursement processing, and travel spend management.
View the file
Other files
Show 40 more
Latest 50 of 61 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Cover
Core FS Pre-Built Business Information Exchanges (BIEs)
Release FY2024
This document contains proposed updates to the currently published Financial Management Capability Framework (FMCF) and corresponding Federal Financial Management (FFM) components of the Federal Integrated Business Framework (FIBF) that support capabilities defined for solutions and services in the FM QSMO Marketplace. Once finalized, documents will be published accordingly.
https://fiscal.treasury.gov/fmqsmo/financial-management-capability-framework.html Overview
| Overview |
| Release FY2024 |
| Core FS Pre-Built Business Information Exchanges (BIEs) | |
| FMCF Context | The Financial Management Capability Framework (FMCF) provides a common set of FM standards and capabilities that are the foundation for all offerings in the FM QSMO Marketplace. The Core FS Pre-Built Business Information Exchanges (BIEs) are component 6 of the FMCF. Refer to the FM QSMO Marketplace Overview for a description of each FMCF component and how the components relate to each other. |
| Change Log | |
| Objective | Describes the change(s) that have occurred with the Pre-Built Business Information Exchanges and the rationale for the change. |
| BIE Principles and Assumptions | |
| Objective | This tab provides business rules that govern the generation of FFM Transactions from both the FFM and other Functional Areas' perspectives. The assumptions provided for other Functional Areas include information on when and why specific FFM Transaction Types are generated or not generated, and align with the other Functional Area's FIBF Business Use Case events and Business Capabilities. A visualization of FIBF FFM Data Groups is also provided to assist with understanding the FFM Transaction Data Elements List. |
| FFM BIE Principles and Assumptions | This section of the tab provides an identifier and description of the FFM principles and assumptions that govern the scope and content of BIEs and generation of FFM Transactions by all other Functional Areas. |
| ACQ-Specific BIE Assumptions | This section of the tab provides an identifier and description of the ACQ-specific BIE assumptions that apply to the generation of FFM Transactions by the ACQ Functional Area. |
| GRM-Specific BIE Assumptions | This section of the tab provides an identifier and description of the GRM-specific BIE assumptions that apply to the generation of FFM Transactions by the GRM Functional Area. |
| TRT-Specific BIE Assumptions | This section of the tab provides an identifier and description of the TRT-specific BIE assumptions that apply to the generation of FFM Transactions by the TRT Functional Area. |
| HCM Payroll-Specific BIE Assumptions | This section of the tab provides an identifier and description of the HCM Payroll-specific BIE assumptions that apply to the generation of FFM Transactions by the HCM Functional Area. |
| GSA SAM-Specific BIE Assumptions | This section of the tab provides an identifier and description of the GSA SAM-specific BIE assumptions that apply to the exchange of information between the GSA SAM system and Core FS Baseline Solution. |
| G-Invoicing-Specific BIE Assumptions | This section of the tab provides an identifier and description of the G-Invoicing-specific BIE assumptions that apply to the exchange of information between the G-Invoicing system and Core FS Baseline Solution. |
| Core FS Pre-Built BIE List | |
| Objective | This tab provides an inventory of Federal government centralized services' systems and other Functional Areas' solutions with which the Core FS Baseline Solution is expected to exchange information. |
| Centralized Service / Functional Area |
| This column indicates whether the system/solution expected to exchange information with the Core FS Baseline Solution is a Federal government centralized service's system or a solution from another Functional Area. |
| System Exchanging Information with | ||
| Core FS Baseline Solution | This column contains the name of the centralized service's system or other Functional Area's solution that exchanges information with the Core FS Baseline Solution. | |
| System Description | This column provides a description of the system/solution and its functionality. | |
| System Information URL | This column provides the website location to obtain additional information about the system/solution. |
| System Manager | This column provides the name of the Federal agency managing the system/solution or indicates whether Federal agencies manage system implementation themselves and/or on behalf of other Federal agencies. |
| BIE Required / Conditionally Required / Future Requirement | This column indicates whether the BIE is required, conditionally required (and under what scenario), or a future requirement for the Core FS Baseline Solution. |
| Core FS Incoming/Outgoing Information | This column indicates whether the BIE is an incoming or outbound information flow with the Core FS Baseline Solution. |
| BIE Specification | This column provides the location of the BIE specification. |
| FFM Txn Data Element List | |
| Objective | This tab provides the subset of FIBF FFM Standard Data Elements selected for inclusion in each type of FFM Transaction between FFM and other Functional Areas. |
| FIBF FFM: Data Element Label | This column provides the label of the FFM Data Element. |
| FIBF FFM: Data Element Definition | This column provides the business definition of the FFM Data Element. |
| FIBF FFM: Data Group Name | This column provides the list of FFM Transaction data groups to which the FFM Data Element belongs. |
| FIBF FFM: Domain Values | This column provides the list of valid values when needed for a specific FFM Data Element. |
| BIE: Required/Optional/Conditional | When an FFM Data Element is applicable to an FFM Transaction Type, this column provides the information needed to determine whether the FFM Data Element is always required, optional, or required under only specific business conditions. |
| Entity-Payee/Payer Maintenance | This column indicates whether the FFM Data Element is applicable to the Entity-Payee/Payer Maintenance type of FFM Transaction. |
| Requisition-Commitment | This column indicates whether the FFM Data Element is applicable to the Requisition-Commitment type of FFM Transaction. |
| Order-Obligation | This column indicates whether the FFM Data Element is applicable to the Order-Obligation type of FFM Transaction. |
| Receipt and Acceptance-Accrual | This column indicates whether the FFM Data Element is applicable to the Receipt and Acceptance-Accrual type of FFM Transaction. |
| Invoice-Payable | This column indicates whether the FFM Data Element is applicable to the Invoice-Payable type of FFM Transaction. |
| Billing Invoice-Receivable | This column indicates whether the FFM Data Element is applicable to the Billing Invoice-Receivable type of FFM Transaction. |
| Public Receipt-Collection | This column indicates whether the FFM Data Element is applicable to the Public Receipt-Collection type of FFM Transaction. |
| Journal Voucher | This column indicates whether the FFM Data Element is applicable to the Journal Voucher type of FFM Transaction. |
| ACQ-FFM BIE |
GRM-FFM BIE
TRT-FFM BIE
| Objective | Each tab provides BIE data element labels and business logic for Federal Financial Management (FFM) Transactions generated by another Functional Area. | |
| FIBF FFM: Data Element Label | This column provides the label of the FFM Data Element. | |
| FIBF FFM: Data Element Definition | This column provides the business definition of the FFM Data Element. | |
| FIBF FFM: Data Group Name | This column provides the list of FFM Transaction data groups to which the FFM Data Element belongs. | |
| FIBF FFM: Domain Values | This column provides the list of valid values when needed for a specific FFM Data Element. | |
| BIE: Applicable FFM Transaction Type(s) | This column provides a list of the FFM Transaction Types for which the FFM Data Element is applicable. | |
| BIE: Required/Optional/Conditional | When an FFM Data Element is applicable to an FFM Transaction Type, this column provides the information needed to determine whether the FFM Data Element is always required, optional, or required under only specific business conditions. | |
| FIBF [Functional Area Acronym]: | ||
| Data Element Label | For the FFM Transaction Type specified, this column provides the label of the other Functional Area's data element(s) to be used to populate the FFM Data Element. "N/A" will appear in this column if a specific FFM Data Element does not apply to the FFM Transaction Type specified or the type of FFM Transaction is not applicable to the Functional Area. | |
| FIBF [Functional Area Acronym]-FFM: | ||
| BIE Logic (Business Rules) | For the FFM Transaction Type specified, this column provides the business logic (business rules) used by the other Functional Area to populate the FFM Data Element. "N/A" will appear in this column if a specific FFM Data Element does not apply to the FFM Transaction Type specified or the type of FFM Transaction is not applicable to the Functional Area. | |
| GSA SAM-FFM BIE | ||
| Objective | This tab provides BIE data element labels and business logic for Federal Financial Management (FFM) data elements generated by GSA SAM. | |
| FIBF FFM: Data Element Label | This column provides the label of the FFM Data Element. | |
| FIBF FFM: Data Element Definition | This column provides the business definition of the FFM Data Element. | |
| FIBF FFM: Domain Values | This column provides the list of valid values when needed for a specific FFM Data Element. | |
| GSA SAM: | ||
| Data Element Label | For the FFM Transaction Type specified, this column provides the label of the other Functional Area's data element(s) to be used to populate the FFM Data Element. "N/A" will appear in this column if a specific FFM Data Element does not apply to the FFM Transaction Type specified or the type of FFM Transaction is not applicable to the Functional Area. | |
| GSA SAM-FFM: | ||
| BIE Logic (Business Rules) | For the FFM Transaction Type specified, this column provides the business logic (business rules) used by the other Functional Area to populate the FFM Data Element. "N/A" will appear in this column if a specific FFM Data Element does not apply to the FFM Transaction Type specified or the type of FFM Transaction is not applicable to the Functional Area. | |
| FFM-DATA Act Files BIE | ||
| Objective |
| This tab provides BIE data element labels and business logic for Data Act data elements generated by Federal Financial Management (FFM). |
| Structured Sort Order |
Element Number Data Element Label Definition Example Value Required/ Optional Valid Data Type Max Field Length Instructions
| Terse 30 Label | These columns provide the information for the Data Act submission files. They are defined in the "RSS Overview" tab in the DAIMS rss-v2 workbook found at https://fiscal.treasury.gov/files/data-transparency/rss-v2.1.xlsx. | |
| FFM Data Element Label | For the Data Act File data element specified, this column provides the label of the FFM data element(s) to be used to populate the Data Act data element. | |
| FFM Data Element BIE Logic (Business Rules) | For the Data Act File data element specified, this column provides business logic (business rules) used by FFM to populate the Data Act data element. | |
| FFM-GTAS BIE | ||
| Objective | This tab provides BIE data element labels and business logic for GTAS data elements generated by Federal Financial Management (FFM). | |
| Field Name | This column provides the name of the GTAS data element. | |
| Length | This column provides the length of the GTAS field. | |
| Starting Position | For a file using a fixed field length format, this column indicates the starting position of the field. | |
| Ending Position | For a file using a fixed field length format, this column indicates the ending position of the field. | |
| Description | This column provides the definition of the GTAS data element. | |
| Domain Values | This column provides the list of valid values when needed for a specific GTAS data element. | |
| FFM Data Element Label | For the GTAS data element specified, this column provides the label of the FFM data element(s) to be used to populate the GTAS data element. | |
| FFM Data Element BIE Logic (Business Rules) | For the GTAS data element specified, this column provides business logic (business rules) used by FFM to populate the GTAS data element. |
DRAFT/PRE-DECISIONAL
Change Log
| Core FS Pre-Built BIE Change Log |
| Release FY2024 |
| General Changes |
| Changed all references to "FFM-Data Act File A, B, C BIE" to "FFM-Data Act Files BIE" |
| Workbook Tab | Item Changed (revised item name) | Summary of Change | Rationale |
| FFM Txn Data Element List; |
ACQ-FFM BIE;
TRT-FFM BIE;
| GRM-FFM BIE | ProgramActivityCode | Modified FIBF FFM: Data Element Definition | Align to change in FFM Business Data Elements |
| FFM Txn Data Element List; |
ACQ-FFM BIE;
TRT-FFM BIE;
GRM-FFM BIE;
| GSA SAM-FFM BIE | EmailAddressTypeCode | Added Data Element | Align to change in FFM Business Data Elements | |
| BIE Principles and Assumptions | G-Invoicing-Specific BIE Assumptions | Added Assumptions | Align to G-Invoicing guidance | |
| ACQ-FFM BIE; |
TRT-FFM BIE;
GRM-FFM BIE AgencyIdentifier;
AgencyTransactionIdentifier;
AllocationTransferAgencyIdentifier;
DocumentReferenceNumber;
LegalEntityAddressLine1;
LegalEntityAddressLine2;
LegalEntityAddressLine3;
LegalEntityCityCode;
LegalEntityCityName;
LegalEntityCountryCode;
LegalEntityForeignCityCode;
LegalEntityForeignCityName;
LegalEntityForeignPostalCode;
LegalEntityStateOrTerritoryCode;
LegalEntityStateOrTerritoryName;
LegalEntityZIP5Number;
LegalEntityZIPLast4Number;
LegalEntityCountyCode;
LegalEntityCountyName;
LegalEntityCountryName;
MainAccountCode;
SubAccountCode;
| AddressTypeCode | Modified FIBF FFM: Data Group Name | Align to change in FFM Business Data Elements |
| ACQ-FFM BIE; |
TRT-FFM BIE;
GRM-FFM BIE AgencyIdentifier;
AllocationTransferAgencyIdentifier;
CreditCohortYear;
DisasterEmergencyFundCode;
InternalOrganizationCode;
LegalEntityCityCode;
LegalEntityCityName;
LegalEntityCountryCode;
LegalEntityCountryName;
LegalEntityCountyCode;
LegalEntityCountyName;
LegalEntityForeignCityCode;
LegalEntityForeignCityName;
LegalEntityForeignSubdivisionCode;
LegalEntityForeignSubdivisionName;
LegalEntityStateOrTerritoryCode;
LegalEntityStateOrTerritoryName;
MainAccountCode;
MajorObjectClass;
MinorObjectClass;
ProgramActivityCode;
SubAccountCode;
SubObjectClass;
TradingPartnerAgencyIdentifier;
TradingPartnerBusinessEventTypeCode;
TradingPartnerMainAccountCode;
USSGL_AccountNumber Modified FIBF FFM: Domain Values Align to change in FFM Business Data Elements
BIE Principles and Assumptions
| BIE Principles and Assumptions |
| Release FY2024 |
| FFM BIE Principles and Assumptions | |
| FFM-1 | Core FS Pre-Built Business Information Exchanges (BIEs) define the incoming and outgoing business information flows needed to execute core financial management processes (e.g., budget execution, accounts receivable and payable management, general ledger postings). They: |
• Are derived from, traceable to, and use terminology consistent with FFM Service Activities, FFMSR Inputs (I) and Outputs (O), and FFM Business Use Cases.
• Represent the minimum information the Government expects to receive into or provide from a core financial management solution
• Use Data Element Labels and Definitions consistent with FFM Business Data Elements
• May include Business Data Elements originating in another Functional Area's business processes when the information is critical for effective and efficient execution of FFM business processes (e.g., calculation of interest due or optimal payment date)
• Do not include Business Data Elements originating in another Functional Area's business processes when the information is used only for reporting and not for transactional processing; this information is expected to be obtained through the use of reporting tools with access to shared business information repositories (e.g., a business intelligence tool accessing an agency data warehouse). For example, additional acquisition or grants management data elements would be accessed in the shared business information repository using the Procurement Instrument Identification Number or Federal Award Identification Number which would have been included in the FFM Transaction as the Document Reference Number).
FFM-2 Core FS Baseline Solution providers are expected to include in their offering at least one BIE with each of these other Functional Areas: acquisition (ACQ), grants (GRM), human capital management (HCM) payroll, and travel and transportation (TRT) expense management.
• If the other Functional Area has defined FIBF Business Data Elements for their future state solutions (e.g., NewPay, ETSNext), BIEs with their future state solutions are expected to be implemented using both the other Functional Area’s and FFM’s FIBF Business Data Elements.
• BIEs between another Functional Area’s existing solution (e.g., NFC Payroll System, ConcurGov (SAP Concur), E2 Solutions (CWTSatoTravel)) and a Core FS Baseline Solution may be implemented using existing data elements on the other Functional Area’s side of the BIE and are expected to be implemented using FIBF FFM Business Data Elements on the FFM side of the BIE.
• If a provider offering is a cross-Functional Area integrated solution (e.g., ERP solution), the provider is expected to ensure all of the specified FFM Transaction data elements can be exchanged with the core financial management component of the integrated solution. For example, even though an ERP solution includes a procurement module, at a minimum, the data elements specified in the ACQ-FFM BIE as being exchanged (i.e., those not marked as N/A) must be able to be received and stored by the core financial management module to support Federal agencies that do not use the ERP solution’s procurement module.
| FFM-3 | If a BIE specification has been provided in this document, the expectation is the BIE data elements and business logic will be implemented as specified unless a waiver is granted by the FM QSMO. If a BIE specification reference in this document is denoted as TBD (to be developed), providers may initially define their own BIE specification. If at a later time a BIE specification is provided by FM QSMO, providers will be expected to modify their initial BIE specification to conform to the BIE specification provided by the FM QSMO. |
| FFM-4 | Core FS Baseline Solution providers are expected to maintain a version of the Core FS Pre-Built BIEs as specified in this document; if modifications are needed to meet agency-specific needs (e.g., add or remove FFM Business Data Elements), a separate agency-specific version must be created and managed. |
| FFM-5 | The FFM Transaction data elements list includes only those data elements that can reasonably be expected to be provided by another Functional Area through an automated business information exchange (BIE) without human intervention. |
| FFM-6 | Functional Areas (source solutions/services) will generate an entity (payee or payor) FFM Transaction prior to generating the initial financial FFM Transaction (e.g., commitment, obligation, payable, receivable) to ensure the FM solution/service either has or establishes the entity before processing the financial transaction. The FM solution/service may also separately validate and/or update entity information based on information received from other sources (e.g., GSA SAM). If differences are found between entity information provided by another Functional Area source solution/service and entity information in the FM solution/service, it will be flagged for investigation. The FM solution/service will resolve duplicate entity records provided to the FFM Functional Area by other Functional Areas (i.e., perform payee/payer entity resolution). |
| FFM-7 | The Functional Area (source solution/service) that generates the FFM transaction determines the appropriate identifier for the entity (payee or payer) when included in the FFM Transaction. |
| FFM-8 | The Functional Area (source solution/service) that generates the FFM transaction ensures the completeness and validity of address information for the entity (payee or payer), including ZIP last 4 and county for addresses located in a US state or territory. |
| FFM-9 | The Functional Area (source solution/service) that generates the FFM transaction determines the appropriate date for the FFM transaction effective date (e.g., document creation date, receipt date, approval date). |
| FFM-10 | The Functional Area (source solution/service) that generates the FFM transaction determines the appropriate identifier for the source reference document for both original and any modification/amendment transactions. |
| FFM-11 | The Functional Area (source solution/service) that generates the FFM transaction determines the appropriate FFM transaction amount for both original and any modification/amendment/cancellation transactions. The amount for modifications/amendments/cancellation transactions will reflect the net change (positive or negative). |
| FFM-12 | The Functional Area (source solution/service) that generates the FFM transaction will not provide prior FFM transaction identifier, but will provide the identifier of the preceding source document in the Functional Area's lifecycle (e.g., award source document identifier when generating an invoice-payable FFM Transaction). |
| FFM-13 | The Functional Area (source solution/service) that generates the FFM transaction will retain a copy of the generated FFM Transaction for audit and recovery purposes. |
| FFM-14 | The FM solution/service will use the FFM transaction information to determine general ledger (journal) entries including appropriate debits, credits, and accounting period. |
| ACQ-Specific BIE Assumptions | |
| ACQ-1 | The ACQ Functional Area will ensure its entity information is consistent with GSA SAM entity information before generating entity FFM Transactions. |
| ACQ-2 | In the ACQ Functional Area, at the time of contract award (or if vendor is known at time of procurement request processing), an entity (payee) FFM Transaction will be generated before generating an obligation (or commitment) FFM Transaction. The entity FFM Transaction will include sufficient information for the FM solution/service to retrieve from GSA SAM any required entity information not provided by the ACQ solution/service. |
| ACQ-3 | In the ACQ Functional Area, procurement requests may generate a commitment FFM Transaction if the Federal agency elects to reserve funds before contract award. |
| ACQ-4 | In the ACQ Functional Area, an accrual FFM Transaction may be generated if the Federal agency documents the acceptance of the goods or services. |
| ACQ-5 | In the ACQ Functional Area, at the time of vendor invoice approval, a payable FFM Transaction may be generated using either the IPP or ACQ solution/service. |
| ACQ-6 | Intra-governmental procurement actions may be executed using an ACQ or FM solution/service or the G-Invoicing centralized service; the selected solution/service will generate any associated intra-governmental commitment, obligation, accrual, payable, and receivable FFM Transactions. |
| ACQ-7 | In the ACQ Functional Area, at the time of contract award closeout, an obligation decrease, final payable, or receivable FFM Transaction may be generated. |
| ACQ-8 | Any receivables and associated payments (collections) from vendors due to an overpayment or improper payment identified after the award is closed out will be executed using the FM solution/service, not the ACQ solution/service. |
| GRM-Specific BIE Assumptions | |
| GRM-1 | The GRM Functional Area will ensure its entity information is consistent with GSA SAM entity information before generating entity FFM Transactions. |
| GRM-2 | In the GRM Functional Area, a Federal award recipient may be another Federal agency. Federal agencies that are Federal award recipients will have a Unique Entity Identifier (UEI) assigned to them in GSA SAM. |
| GRM-3 | The GRM Functional Area allows grant award recipients to identify up to three sets of payment/bank information (e.g., payment methods, bank accounts) as part of their Legal Entity Information. A specific set of payment/bank information will be identified at time of payment request. |
| GRM-4 | In the GRM Functional Area, an entity (payee) FFM Transaction and an obligation FFM Transaction will be generated at the time of Federal grant award. |
| GRM-5 | In the GRM Functional Area, a funds commitment FFM Transaction may be generated using Notice of Funding Opportunity (NOFO) information in order to reserve funds when there is anticipated to be a lengthy period of time between NOFO and the issuance of a Federal award. |
| GRM-6 | In the GRM Functional Area, there may be a lengthy period of time between confirmation of completion of grant program's or Federal award's performance milestones and the receipt of a request for payment (i.e., when a payable FFM Transaction is generated). For grant program accruals, a journal voucher FFM Transaction will be generated without specifying Federal award recipient information; for Federal award accruals, a receipt and acceptance FFM Transaction will be generated. |
| GRM-7 | In the GRM Functional Area, at the time of Federal grant award closeout, an obligation decrease, final payable, or receivable FFM Transaction may be generated. |
| GRM-8 | Any receivables and associated payments (collections) from grant recipients due to an overpayment or improper payment identified after the award is closed out will be executed using the FM solution/service, not the GRM solution/service. |
| GRM-9 | If the government identifies real or personal property to be received based on a grant recipient's financial report or during the closeout of a Federal grant award, the Real Property Management (RPM) or Personal Property Management (PPM) Functional Area will receive and book the property and generate the appropriate FFM transaction. |
| TRT-Specific BIE Assumptions | |
| TRT-1 | In the TRT Functional Area, an entity (payee) FFM Transaction for the traveler will be generated from Travel Personnel Baseline Profile at the time of travel authorization and voucher to ensure FFM has the most current information on the traveler prior to processing an FFM Transaction. An entity (payee) FFM Transaction will not need to be generated by the TRT Functional Area for charge card issuer companies because when the government establishes the contract with the charge card issuer company, they are required to establish their entity and payment information in GSA SAM. This information can be retrieved by FFM using the Unique Entity Identifier (UEI) provided by the TRT Functional Area. |
| TRT-2 | In the TRT Functional Area, every type of Travel Authorization (i.e., Unlimited Open, Limited Open, Individual Trip-by-Trip, and Group Trip-by-Trip) will generate a funds obligation FFM Transaction. |
• Under Unlimited Open and Limited Open Travel Authorizations, there are no further travel authorizations for a specific trip; the traveler can submit multiple Travel Advance Vouchers and TDY Travel Vouchers for one or more trips against the open travel authorization.
• Under an Individual Trip-by-Trip Travel Authorization, individuals can submit multiple Travel Advance Vouchers and a single TDY Travel Voucher (subsequent TDY Travel Vouchers will amend the traveler's previously approved TDY Travel Voucher).
• Under a Group Trip-by-Trip Travel Authorization, a list of travelers will be included in the travel authorization, however estimated travel expenses will not be broken down by traveler. Therefore, the funds obligation FFM Transaction for a Group Trip-by-Trip Travel Authorization will include a generic payee. Individual travelers can submit multiple Travel Advance Vouchers and a single TDY Travel Voucher (subsequent TDY Travel Vouchers will amend the traveler's previously approved TDY Travel Voucher). The vouchers will provide the specific payee information for the associated payable FFM Transaction.
| TRT-3 | In the TRT Functional Area, once travel authorizations or TDY Travel Vouchers are approved, if subsequent changes are required, they would be amended instead of updated and the amendment will generate an FFM Transaction; in these cases, the TRT solution/service will store documentation of both the original document and amendment for traceability and auditing purposes. Travel Advance Vouchers and Local Vouchers cannot be amended (changed or updated) after approval. |
| TRT-4 | If a trip is canceled after the travel authorization is approved and expenses have incurred, but prior to trip departure, a TDY Travel Voucher will be submitted for the amount of residual fees (e.g., transaction fees, cancelation fees) and generate a payable FFM Transaction at the time the TDY Travel Voucher is approved. A travel authorization amendment indicating the trip was canceled will be created and generate a funds obligation FFM Transaction with a negative amount to de-obligate the remaining funds. |
| TRT-5 | In the TRT Functional Area, an accrual FFM Transaction will not be generated at the time a traveler incurs expenses; however, a payable FFM Transaction will be generated at the time a TDY Travel Voucher or Local Voucher is approved. |
| TRT-6 | Local Vouchers used to reimburse federal employees for expenses, such as, telephone, local transportation, office supplies, or professional liability insurance will generate a payable FFM Transaction that does not have an associated Travel Authorization (obligation) document (similar to an acquisition micro-purchase). If the business unit wants to reserve funds for Local Vouchers, it will be executed using the FM solution/service. |
| TRT-7 | Line items in TDY Travel Vouchers for travel expenses paid via a Centrally Billed Account (CBA) charge card will not generate a payable FFM Transaction (or liquidate the previous line item obligation). Payables to CBA charge card companies (and obligation liquidation) will be initiated in the FM solution/service based on government receipt of charge card issuer billing statements. |
| TRT-8 | Line items in TDY Travel Vouchers for travel expenses paid via a Government Transportation Request (GTR) will not generate a payable FFM Transaction (or liquidate the previous line item obligation). A payable to the transportation vendor (and obligation liquidation) will be initiated in the FM solution/service when the vendor submits the GTR invoice to the Federal government for reimbursement. |
| TRT-9 | Line items in TDY Travel Vouchers for travel expenses paid via an Individually Billed Account (IBA) government-issued travel card will generate a payable FFM Transaction specifying the payee as the traveler's charge card issuer company identified in the Travel Personnel Profile Information. A separate payable FFM Transaction will be generated for line items indicating cash travel expenses (e.g., tips, tolls) to be reimbursed to the Federal traveler; the method of payment to the traveler (e.g., ACH, check) and traveler's bank account information will be provided from the Travel Personnel Profile Information. |
| TRT-10 | Line items in TDY Travel Vouchers for travel expenses paid via a Non-Federal Source Payment Type of "In Kind" will not generate a payable FFM Transaction since the expense was paid directly to the vendor by the Non-Federal Source entity (e.g., hotel room expense), but will generate a funds obligation FFM Transaction with a negative amount to de-obligate the funds reserved in case the Non-Federal Source did not pay for the expense. |
When a Non-Federal Source will reimburse an agency for a travel expense, the travel expenses must first be paid via CBA, IBA, or cash and generate the associated FFM Transactions. Reconciliation of travel expenses with any reimbursement to the Federal agency will be performed outside of the TRT solution/service and any necessary payable or receivable transactions will be executed using the FM solution/service.
TRT-11 Travel Advance Vouchers and TDY Travel Vouchers may be processed before, during, or upon completion of official travel.
• A Travel Advance Voucher submitted before travel begins may be used to pay for anticipated expenses. The traveler will identify the associated travel authorization expense line item for which the travel advance is required and the payee must be the traveler (i.e., cannot be an IBA). One or more TDY Travel Vouchers will later be submitted and will indicate which Travel Advance Voucher line items have now been expensed by the traveler.
• A TDY Travel Voucher submitted before travel begins may also be used for reimbursement of expenses incurred prior to travel (e.g., payment for a room deposit) and the payee may be the traveler, an IBA, or a CBA.
• A TDY Travel Voucher may be used during travel for reimbursement of expenses incurred while in a continuous travel status and the payee may be the traveler, an IBA, or a CBA.
• A TDY Travel Voucher submitted upon completion of a trip will be used to reimburse expenses incurred and the payee may be the traveler, an IBA, or a CBA.
• All types of vouchers will generate a payable FFM transaction; however, TDY Travel Vouchers that indicate the expensing of a previously received travel advance will not result in a new disbursement of funds to the traveler but rather the expensing of the previously disbursed travel advance funds.
| TRT-12 | When a travel authorization is canceled or amended because estimated amount of expenses is decreased and a travel advance in excess of the canceled or amended travel authorization was issued to the traveler, a receivable FFM transaction will be generated in addition to the de-obligation FFM transaction. |
| TRT-13 | If an audit identifies an overpayment to a traveler, any receivables and associated payments (collections) from travelers (also known as a "Due U.S.") will be executed using the FM solution/service, not the TRT solution/service. |
| TRT-14 | Determination of Federal employee taxes and payroll deductions for long term travel will be performed by the HCM compensation (payroll) function and not the FFM Functional Area. The HCM payroll information provided to FFM will include summarized tax withholding/payroll deduction information. |
| HCM Payroll-Specific BIE Assumptions | |
| HCM-1 | In the HCM Functional Area, a journal voucher FFM transaction will be used to provide summarized payroll information to the FM solution/service. |
| GSA SAM-Specific BIE Assumptions | |
| SAM-1 | Both GSA SAM UEI and TIN will be provided as legal entity identifiers to the FM solution/service. |
| SAM-2 | Both GSA SAM physical and mailing address information will be provided to the FM solution/service. |
| SAM-3 | GSA SAM follows the GSA OGP Internal Guidance on use of GLC/GENC for country, state/province, city, and county codes and names. |
| G-Invoicing-Specific BIE Assumptions | |
| GINV-1 | G-Invoicing maintains and provides only Federal agency domestic location and contact information (e.g., no foreign delivery location or foreign phone number information) |
| GINV-2 | Intragovernmental agreement general terms and conditions (GT&C) information is established/adjusted in G-Invoicing by either Servicing or Requesting Agency and retrieved into their respective Core FS; intragovernmental order and performance completion and approval information can be established/adjusted in G-Invoicing by either Servicing or Requesting Agency and retrieved into their respective Core FS or established/adjusted in either Core FS and provided to G-Invoicing |
| GINV-3 | G-Invoicing exchanges funds transfer information with IPAC. G-Invoicing provides settlement information which can be retrieved into Servicing and Requesting Agency Core FS |
| FFM Transaction Data Groups and Data Element Hierarchy | |||||
| FFM Transaction Information | |||||
| AgencyTransactionIdentifier | |||||
| FinancialTransactionTypeCode | |||||
| TransactionIdentificationDate | |||||
| <source/proceeding document data elements> | |||||
| <payee/payor (legal entity) data elements> | |||||
| <other transaction data elements> | |||||
| FFM Transaction Line Information | |||||
| <source document line data elements> | |||||
| <other line item data elements> | |||||
| FFM Transaction Line of Accounting (LOA) Information | |||||
| FinancialTransactionLineLOAIdentifier | |||||
| FinancialTransactionLineLOAAmount | |||||
| Account Classification Structure (ACS) Information | |||||
| AgencyFundCode | |||||
| Treasury Account Symbol | |||||
| AgencyIdentifier | |||||
| MainAccountCode | |||||
| <other TAS data elements> | |||||
| FundingSourceYear | |||||
| BudgetFiscalYear | |||||
| Budget Object Class | |||||
| Major Object Class | |||||
| Minor Object Class | |||||
| SubObjectClass | |||||
| AgencySubObjectClass | |||||
| InternalOrganizationCode | |||||
| FFMProgramCode | |||||
| ProgramActivityCode | |||||
| CostCenterIdentifier | |||||
| FFMProjectIdentifier | |||||
| FFMProjectTaskIdentifier | |||||
| <other ACS data elements> |
&"Arial,Bold"DRAFT/PRE-DECISIONAL
Core FS Pre-Built BIE List
| Core FS Pre-Built BIE List |
| Release FY2024 |
| Centralized Service / Functional Area | System Exchanging Information with | |||||||
| Core FS Baseline Solution | System Description | System Information URL | System Manager | BIE Required / Conditionally Required / Future Requirement | Core FS Incoming/Outgoing Information | BIE Specification | ||
| Centralized Service | Automated Standard Application for Payments (ASAP) | ASAP is a completely electronic system that federal agencies use to quickly and securely transfer money to recipient organizations. Federal agencies enroll recipient organizations, authorize their payments, and manage their accounts. Recipient organizations then request payments from these pre-authorized accounts. ASAP is free for both federal agencies and recipient organizations. | https://fiscal.treasury.gov/asap/ | Treasury Fiscal Service | Required - at least one grants payment BIE is required (ASAP is preferred, however, HHS PMS will be accepted as an alternative) | Outgoing | TBD | |
| Centralized Service | Central Accounting Reporting System (CARS) | CARS is the electronic system of record for the government's financial data which provides streamlined agency reporting and supports government-wide standardization. It enables agencies to classify payments, collections, and intra-governmental transactions. | https://fiscal.treasury.gov/cars/ | Treasury Fiscal Service | Required | Incoming | https://www.fiscal.treasury.gov/cars/reference-and-guidance.html | |
| Outgoing | https://www.fiscal.treasury.gov/cars/reference-and-guidance.html | |||||||
| Centralized Service | Collections Information Repository (CIR) | The Collections Information Repository (CIR) is a web-based tool that gives federal agencies information on deposits and collections. Agencies use CIR to get detailed and summary-level information on revenue they receive. | https://fiscal.treasury.gov/cir/ | Treasury Fiscal Service | Required | Incoming | https://fiscal.treasury.gov/files/cir/XML5.0.1ExtractFilesSpecificationv201.pdf | |
| Centralized Service | Cross-Servicing (CSNG) | Cross-Servicing is our program to deal with delinquent debt. By law, federal agencies must transfer delinquent debts to the Bureau of the Fiscal Service. When the agency transfers the debt to Fiscal Service, we have the legal responsibility to then deal with that debt: to collect it, work with the debtor to pay it, suspend or end collection. | https://fiscal.treasury.gov/cross-servicing/ | Treasury Fiscal Service | Required | Outgoing | TBD | |
| Centralized Service | DATA Act Broker | Used by agencies accessing the web-based application to securely upload, validate, and certify financial data. | https://fiscal.treasury.gov/data-transparency/DAIMS-current.html | Treasury Fiscal Service | Required | Outgoing - File A | See FFM-DATA Act Files BIE | |
| Outgoing - File B | See FFM-DATA Act Files BIE | |||||||
| Outgoing - File C | See FFM-DATA Act Files BIE | |||||||
| Centralized Service | G-Invoicing | G-Invoicing is a Fiscal Service application designed to improve the quality and reliability of Intragovernmental |
Transactions (IGT) Buy/Sell data in support of increased transparency and enhanced government-wide financial management. G-Invoicing is the government’s long-term sustainable solution for Buy/Sell transactions. The
| application is required to be used by all FPAs and is offered at no charge. | https://fiscal.treasury.gov/g-invoice/ | Treasury Fiscal Service | Required | Incoming (Pull) - Organization, General Terms and Conditions (GT&C), | ||||
| Orders, and Performance | G-Invoicing: Resources (treasury.gov) | |||||||
| Outgoing (Push) - Orders and Performance | System Interface Specification Template (treasury.gov) | |||||||
| Centralized Service | Governmentwide Treasury Account Symbol (GTAS) | GTAS stands for the Governmentwide Treasury Account Symbol Adjusted Trial Balance System. The GTAS system is used by entities to report budget execution information and proprietary financial reporting information to the Department of the Treasury. | https://www.fiscal.treasury.gov/gtas/ | Treasury Fiscal Service | Required | Outgoing | See FFM-GTAS BIE | |
| Centralized Service | GSA SmartPay | A system used to manage agency purchase cards, travel cards, and fleet cards and associated charge card billing to the agencies | What is GSA SmartPay? | Smartpay | GSA Federal Acquisition Service (FAS) | Required | Incoming | TBD | |
| Centralized Service | Intra-Governmental Payment and Collection (IPAC) Bulk File | IPAC is a way for Federal Program Agencies (FPAs) to transfer funds from one agency to another with standardized descriptive data. | https://fiscal.treasury.gov/ipac/ | Treasury Fiscal Service | Required | Outgoing | TBD | |
| Incoming | TBD | |||||||
| Centralized Service | Invoice Processing Platform (IPP) | The Invoice Processing Platform (IPP) is a secure, web-based centralized service that more efficiently manages government invoicing from purchase order through payment notification, at no charge to federal agencies and their vendors. | https://www.ipp.gov/ | Treasury Fiscal Service | Required | Incoming | TBD | |
| Centralized Service | Pay.gov | Allows individuals, states, and businesses make non-tax payments to the federal government online. | https://www.pay.gov/public/home | Treasury Fiscal Service | Required | Incoming | https://qa.pay.gov/agencydocs/docs/web_services_data_elements.pdf |
https://qa.pay.gov/agencydocs/docs/web_services_overview.pdf
| Centralized Service | Payment Automation Manager (PAM) | Standardized payment processing system that supports federal program agencies. | https://www.fiscal.treasury.gov/pam/ | Treasury Fiscal Service | Required | Outgoing | TBD |
| Centralized Service | Payment Information & View of Transactions (PIVOT) | The Post Payment Modernization Initiative (PPMI) is the work by the Bureau of Fiscal Service to strengthen, re-engineer and modernize essential operations that support the full lifecycle of post-payment processing. |
The new system being developed by this initiative is the Payment Information View of Transactions (PIVOT) application. PIVOT will merge and replace functions now performed in several legacy applications:
Payments, Claims and Enhanced Reconciliation (PACER) Post Payment System (PPS) Treasury Check Information System (TCIS) Treasury Receivable Accounting & Collection System (TRACS) Treasury Offset Program Control System (TCS)
| There will be no cost for federal agencies to use PIVOT. | https://www.fiscal.treasury.gov/ppmi/ | Treasury Fiscal Service | Required | Incoming - Standard Cancellation File (SCF) | TBD | |||
| Centralized Service | Secure Payment System (SPS) | Application that allows government agencies to securely create payment schedules. | https://fiscal.treasury.gov/sps/ | Treasury Fiscal Service | Required | Outgoing | TBD | |
| Centralized Service | Shared Accounting Module (SAM) (Treasury) | The Shared Accounting Module (SAM) validates or derives the combined Treasury Account Symbol (TAS) and Business Event Type Code (BETC) for financial transactions. SAM helps governmentwide accounting by classifying financial transactions. | https://fiscal.treasury.gov/sam/ | Treasury Fiscal Service | Required | Incoming | https://www.fiscal.treasury.gov/data/ | |
| Centralized Service | System for Award Management (SAM) | A system used by vendors and grant award recipients to register to do business with the U.S. government and to provide vendor/grant award recipient information to Federal agencies | https://sam.gov | GSA Federal Acquisition Service (FAS) | Required | Incoming | See GSA SAM-FFM BIE tab | |
| Centralized Service | Treasury Offset Program (TOP) | The Treasury Offset Program (TOP) is a centralized offset program which collects delinquent debts owed to federal agencies and states. Agencies whose debts are not eligible for Cross-Servicing should refer to TOP. Agencies primarily refer debts to this system via file transfers using DMS standard file formats. The TOP Web Client (TWC) is a Web-based application used by federal agencies. The initial batch loading by electronic transmission of Delinquent Debtor records into TOP is accomplished by using the Fiscal Service-prescribed TOP input Enhanced Record Layouts. | https://fiscal.treasury.gov/top/ | Treasury Fiscal Service | Required | Outgoing | TBD | |
| ACQ Acquisition | Award management future state solutions | A system that provides end-to-end procurement cycle that integrates and tracks information from the initiation of a requirement, through its solicitation and award, and closeout | Federal Agencies | Future Requirement | Incoming | See ACQ-FFM BIE tab | ||
| ACQ Acquisition | Award management existing solutions | A system that provides end-to-end procurement cycle that integrates and tracks information from the initiation of a requirement, through its solicitation and award, and closeout | Federal Agencies | Required - at least one acquisition BIE is required | Incoming | TBD | ||
| GRM Grants Management | Grants management future state solutions | A system Federal agencies use to manage the full grants lifecycle – from pre-award planning through application, award, and closeout. | Federal Agencies | Future Requirement | Incoming | See GRM-FFM BIE tab | ||
| Outgoing | TBD | |||||||
| GRM Grants Management | GrantSolutions | GrantSolutions supports Federal agencies throughout the full grants lifecycle – from pre-award planning through application, award, and closeout. | https://home.grantsolutions.gov/home/about/ | HHS Program Service Center (PSC) | Required - at least one grants management BIE is required | Incoming | Vendor/implementor defined | |
| GRM Grants Management | Electronic Research Administration (eRA) | eRA provides mission-critical IT infrastructure to manage the receipt, processing, review, award and monitoring of about $34 billion in research and non-research grants awarded annually by NIH and other grantor agencies in support of the collective mission of improving human health. | https://era.nih.gov/about-era | HHS National Institutes of Health (NIH) | Incoming | Vendor/implementor defined | ||
| GRM Grants Management | Payment Management System (PMS) | PSC developed the Payment Management System (PMS) as a secure, online grants payment platform which provides awarding agency and grant recipient customers with efficient grant and grant-like payments, cash management, and personal grant accounting support services. | https://pms.psc.gov/about-us.html | HHS Program Service Center (PSC) | Conditionally Required - at least one grants payment BIE is required (ASAP is preferred, however, HHS PMS will be accepted as an alternative) | Incoming | Vendor/implementor defined | |
| HCM Human Capital Management | DFAS Payroll System | DoD DFAS-managed system used to ensure that employees are paid correctly and all taxes etc. are properly deducted | Defense Finance and Accounting Service > CivilianEmployees (dfas.mil) | DoD Defense Finance and Accounting Service (DFAS) | Required - at least one payroll BIE is required | Incoming | Vendor/implementor defined | |
| HCM Human Capital Management | Federal Personnel and Payroll System (FPPS) | DOI IBC-managed system used to ensure that employees are paid correctly and all taxes etc. are properly deducted | Federal Personnel and Payroll System | U.S. Department of the Interior (doi.gov) | DoI Interior Business Center (IBC) | Incoming | Vendor/implementor defined | ||
| HCM Human Capital Management | GSA Payroll Services | GSA-managed system used to ensure that employees are paid correctly and all taxes etc. are properly deducted | Payroll Shared Services | GSA | GSA Payroll Services | Incoming | Vendor/implementor defined | ||
| HCM Human Capital Management | NFC Payroll System | USDA NFC-managed system used to ensure that employees are paid correctly and all taxes etc. are properly deducted | HR and Payroll Client Services | National Finance Center (usda.gov) | USDA National Finance Center (NFC) | Incoming | Vendor/implementor defined | ||
| HCM Human Capital Management | NewPay | GSA-managed government-wide shared payroll service to which federal agencies can subscribe | TBD | GSA Civilian HR Transaction Services QSMO | Future Requirement | Incoming | TBD | |
| TRT Travel and Transportation Management | ConcurGov (SAP Concur) | GSA-managed system that federal employees currently use to book and expense TDY travel | https://www.gsa.gov/reference/for-gsa-employees/on-the-go/concurgov | GSA Office of Travel, Transportation and Logistics | Required - at least one travel and expense management BIE is required | Incoming | Vendor/implementor defined | |
| TRT Travel and Transportation Management | E2 Solutions (CWTSatoTravel) | GSA-managed system that federal employees currently use to book and expense TDY travel | https://www.cwtsatotravel.com/home.html | GSA Office of Travel, Transportation and Logistics | Incoming | Vendor/implementor defined | ||
| TRT Travel and Transportation Management | ETSNext | GSA-managed "next generation" system that federal employees will be using to book and expense TDY travel | https://www.gsa.gov/travel/agency-services/egov-travel-services-ets/etsnext | GSA Office of Travel, Transportation and Logistics | Future Requirement | Incoming | See TRT-FFM BIE tab |
https://fiscal.treasury.gov/cars/https://fiscal.treasury.gov/sps/https://fiscal.treasury.gov/sam/https://fiscal.treasury.gov/top/https://fiscal.treasury.gov/asap/https://www.fiscal.treasury.gov/ppmi/https://www.fiscal.treasury.gov/cars/reference-and-guidance.htmlhttps://fiscal.treasury.gov/files/cir/XML5.0.1ExtractFilesSpecificationv201.pdfhttps://www.fiscal.treasury.gov/data/https://fiscal.treasury.gov/files/g-invoice/gtc-orders-performance-pull(current).pdfhttps://era.nih.gov/about-erahttps://fiscal.treasury.gov/cir/https://home.grantsolutions.gov/home/about/https://pms.psc.gov/about-us.htmlhttps://fiscal.treasury.gov/data-transparency/DAIMS-current.htmlhttps://sam.gov/https://www.dfas.mil/civilianemployees/https://www.doi.gov/ibc/services/human-resources/fppshttps://www.gsa.gov/buying-selling/purchasing-programs/shared-services/payroll-shared-serviceshttps://www.gsa.gov/reference/for-gsa-employees/on-the-go/concurgovhttps://www.gsa.gov/travel/agency-services/egov-travel-services-ets/etsnexthttps://www.cwtsatotravel.com/home.htmlhttps://fiscal.treasury.gov/cross-servicing/https://nfc.usda.go…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .