Intra-governmental Transactions

Working Group (ITWG)

September 14, 2021
Page 2 L EAD ∙ T RANSFORM ∙ D ELIVER

Today’s Agenda

• Program Updates

• Release 4.3 Coming Soon

• Post-Mandate Work Underway

• Monitoring Compliance in G-Invoicing (Draft)

• New IPAC Data Element and Timing

• Progressing Towards the G-Invoicing Mandate

• Knowledge and Training Offerings

• August Survey Results
Page 3 L EAD ∙ T RANSFORM ∙ D ELIVER

Tentative ITWG Schedule

 July 13– Program Updates, Release 4.3, GF BETC Mandate, What 

Needs to be Done to be Ready, Office Hours, and Connecting with 

your TP’s

 Aug 10 – Program Updates, Release 4.3, GSA Rent Activity, New 

IPAC Data Element and Timing, Progress towards the G-Invoicing 

Mandate, Office Hours, Connecting with your TP’s, August Survey

 Sept 14 – Program Updates, Release 4.3, Post-Mandate Work, 

Monitoring Compliance/Draft Thresholds, New IPAC Data Element & 

Timing, Progress towards the G-Inv Mandate, Knowledge and Training 

Offerings, August Survey Results

Planned Dates: Oct 12, Nov 9, Dec 14

Future Topics:

• Post-mandate enhancements

2-3:30 pm ET
Page 4 L EAD ∙ T RANSFORM ∙ D ELIVER

Program Updates

• Q4 FY21 Implementation Plans are due to Treasury by September 30th

‒ These submissions will be reflected on your Q4 Scorecard

‒ Reminder: Pull templates from G-Invoicing webpage each quarter to ensure you 

are submitting the most up-to-date version.

• https://www.fiscal.treasury.gov/g-invoice/training.html

• G-Invoicing Program Guide – Under review for updates

‒ Guide for Basic Accounting and Reporting

• G-Invoicing Rules of Engagement Guide – Under review for updates

‒ Guide detailing the appropriate protocols for entities to follow within the 

application and leading up to the implementation of G-Invoicing

• TFM Chapter 4700 Publication – Published on June 30th

‒ Agencies can expect a TFM Bulletin later in the year to address the policy and/or 

system controls to address Measuring & Enforcing G-Invoicing Compliance, 

once we have reached a final decision
Page 5 L EAD ∙ T RANSFORM ∙ D ELIVER

Release 4.3 Coming Soon

• Upcoming Program Objectives (R4.3)

‒ GT&C Workflow (Shared Draft)

‒ User Recertification 

• Restoring Recert Official/User Admin maintenance to the application in 

time for year-end mass user recertification

‒ BETC Changes 

• Removal of DISB with R4.3 in G-Invoicing

• IPAC will not be changed until SAM file is updated to remove DISB 

BETC

‒ Performance UI Features

• Targeting late September for QA-C release (training)

‒ External Remittance Advice API

‒ R4.3 deployment planned for Sept 16th (Production) 

and Sept. 24th (QA-C)
Page 6 L EAD ∙ T RANSFORM ∙ D ELIVER

Post-Mandate Work Underway

• Working on post-mandate API Specifications

• Proposed changes:

‒ Correct rounding issues

‒ Allow Performance against an open Order while it’s being modified

‒ Revert a modified GT&C back to open status

‒ Prohibit non-printable characters

‒ Low dollar purchases (7600-EZ)

‒ Budget Object Class – required (Requesting Agency Only)

‒ In-flight Orders

‒ Validate Line Item Code using Product Service 

Code

‒ Allow agencies to assign new TASes to Orders 

prior to Oct 1st
Page 7 L EAD ∙ T RANSFORM ∙ D ELIVER

• Fiscal Service to leverage G-Invoicing and Governmentwide Treasury Account Symbol Adjusted Trial Balance 

System (GTAS)

• GTAS data to compare the dollar amount of compliant 

Buy/Sell activity

– This is a comparison of FR Entities’ activity reported in G-Invoicing to 

that Entities’ GTAS submission of trial balances.

– Will be displayed on the Significant FR Entities’ Quarterly IGT 

Scorecards

– This metric will be displayed in a green, yellow and red format.

– A FR Entity is deemed fully compliant if this metric is green, partially 

compliant if yellow, and non-compliant if red.

Monitoring Compliance
Page 8 L EAD ∙ T RANSFORM ∙ D ELIVER

• Fiscal Service is developing specifications for these postmandate enhancements:

– Low Dollar/High Volume transactions (EZ invoice process)

– GSA Rent (Constructive Order Acceptance)

• The deadline for the transition of this activity (along with the 

transition of in-flight Orders) is FY 2024.

– GSA Rent

– GSA Fleet Leasing

– GSA Global Supplies

– GPO Print Orders

– Buy/Sell Orders under $10,000

• The threshold ranges have accounted for these exceptions.

FY 2024 Buy/Sell Activity
Page 9 L EAD ∙ T RANSFORM ∙ D ELIVER

• Ranges are based on the dollar amount of Buy/Sell 

activity in G-Invoicing as compared to the FR Entities’ 

GTAS submission and will increase each fiscal year.

**Note: These percentages are subject to change (increase/decrease) based on agency feedback and ongoing analysis

 FY 2023 (Only new TAS with a BPOA of 2023 would be measured)

 Green: 75-100%

 Yellow: 65-74%

 Red: 64% and below

 FY 2024 (All TASs would be measured) 

 Green: 80-100%

 Yellow: 70-79%

 Red: 69% and below

 FY 2025 (All TASs would be measured) 

 Green: 85-100%

 Yellow: 75-84%

 Red: 74% and below

Draft Threshold Ranges 
Page 10 L EAD ∙ T RANSFORM ∙ D ELIVER

New IPAC Data Field Option

 To include a new drop-down menu of categories to select

 Fiscal Service will accommodate agencies during the transition to the new IPAC Bulk File format by temporarily 

accepting both versions of the file.

New IPAC Data Element

Buy/Sell Transfer

Non-Exchange Expenditure Transfer

Benefits Transfer

Non-Exchange Custodial Transfer

Exchange Custodial Transfer

Investments

Borrowings

Other
Page 11 L EAD ∙ T RANSFORM ∙ D ELIVER

• Targeted Timeline for new IGT sub-category data element:

– October 2021 – publish Bulk File specifications

– December 2021 – Optional through UI

– October 2022 – Required through UI

– October 2023 – Required through Bulk File and reject Buy/Sell 

transactions submitted via the Bulk File

– October 2024 – Remove Buy/Sell option within the IPAC application 

through the UI

• The solution requires enhancements to the IPAC User Interface (UI) and 

Bulk File

• Modifications are needed for the IPAC reports to accommodate the new 

IGT sub-category selection

• Fiscal Service will coordinate with ERP vendor community on 

implementing functionality needed

Timeline and Next Steps
Page 12 L EAD ∙ T RANSFORM ∙ D ELIVER

Organize a 

CrossFunctional Team

Review Data 

Elements, 

Inventory 

Processes, and 

Data

Plan, Design, 

and Strategize

Pilot in QA-C

Establish 

Production 

Account

Process 

Transactions

Sprinting Towards the October 1st, 2022 G-Invoicing Mandate

Progress Towards the G-Inv Mandate

• Many agencies today are actively planning for G-Invoicing implementation and 

are actively process and data mapping as well as testing in QA-C 

• With the Mandate just over 12 months out, all agencies should

focus on establishing Production Accounts by 10/01/21
Page 13 L EAD ∙ T RANSFORM ∙ D ELIVER

Knowledge and Training Offerings

G-Invoicing Learning Opportunities

• Our Agency Implementation Team hosts a variety of training options.

• Independent Training Resources including pre-recorded G-Invoicing training 

videos are available through the G-Invoicing website: 

https://www.fiscal.treasury.gov/g-invoice/training.html

• Register for Webinar-based Training and access to On-Demand Financial 

Management Training Videos here: https://www.fiscal.treasury.gov/training/
Page 14 L EAD ∙ T RANSFORM ∙ D ELIVER

Office Hours

• G-Invoicing Program conducts virtual Office Hours sessions twice monthly where we host targeted 

discussions as well as “open-mic” styled discussions

• Future Topics Include:

‒ Round Table Discussion on Lessons Learned thus far (August 10th)

‒ Round Table Discussion on Phased Implementations and How Agencies are Implementing G-Invoicing (August 24th)

‒ Round Table Discussion on Working Capital Funds in G-Invoicing (September 7th) 

‒ Round Table Discussion on Operating in a Continuing Resolution Environment in G-Invoicing (Sept 21st) 

‒ Snap Shot: Trading Partner Status as of FY 22 (October 5th) 

• Register for Office Hours here: https://www.fiscal.treasury.gov/g-invoice/training.html
Page 15 L EAD ∙ T RANSFORM ∙ D ELIVER

August Survey Results

1. Once you’ve transitioned your Buy/Sell activity to G-Invoicing, do you 

anticipate still needing the IPAC Bulk File for non-Buy/Sell transactions 

facilitated through IPAC?

‒ Majority indicated a continued need for the IPAC Bulk File.

• Yes (15 responders), N/A (6 responders), No (4 responders)

2. Please explain any remaining hurdles not already included in your 

Implementation Plan that may prevent your agency from meeting the 

G-Invoicing mandate.

‒ Half of responders identified no additional issues outside of their plans.

‒ Other half of responders provided a variety of agency specific issues.

• Concerns included: ERP Vendor product availability, system upgrades & 

integration with G-Invoicing, resource constraints, training, and a number 

application functionality enhancement requests that won’t be available before the 

mandate. 
Page 16 L EAD ∙ T RANSFORM ∙ D ELIVER

August Survey Results Continued

3. Post-mandate, do you have any concerns with the Budget Object Class 

(BOC) becoming a required field in G-Invoicing? If yes, please explain.

‒ 70% of responders indicated no concerns.

‒ Some of the concerns noted include:

• Potential for multiple BOCs to be used.

‒ Agencies can utilize multiple schedules, if needed

• This field is often inaccurate given that agencies use it differently.

• OMB publishes a three-character BOC list. Many customers use the full sixcharacter BOC to be more specific and must list it under SLOA section due to 

data field restrictions. 

‒ Current data field is limited to four-characters.

• Making this a required field may impact G-Invoicing timelines as financial 

systems may need adjustments.

• Servicing Agency should not be required to provide the BOC.

‒ Clarification: It would only be required for the Requesting Agency
Page 17 L EAD ∙ T RANSFORM ∙ D ELIVER

August Survey Results Continued

4. Post-mandate, do you have any concerns with a validation being added 

in G-Invoicing for the Line Item Code to ensure that a valid code is 

selected? If yes, please explain.

‒ 70% of responders indicated no concerns.

‒ Some of the concerns noted include:

• Optional field in agency financial systems & would lead to validation issues 

when interfacing with G-Invoicing. 

• Inability to validate this code in agency financial systems.

• Trading Partners don’t always use it, would need a pick list.

• Concerns with selecting an appropriate code for agency specific activity.

5. Post-mandate, do you have any concerns with a required comments 

field being added in G-Invoicing for agencies to supply the reason(s) for 

modifying the GT&C and/or the Order? If yes, please explain.

‒ Nearly all responders indicated no concerns.
Page 18 L EAD ∙ T RANSFORM ∙ D ELIVER

G-Invoicing Program Contacts

For IGT Program Management and Agency Outreach Support

Andy Morris

Manager, Intragovernmental Transaction & Reconciliation Branch (ITRB)

Bureau of the Fiscal Service – Fiscal Accounting

andrew.r.morris@fiscal.treasury.gov

Jeff Board

G-Invoicing Product Owner, ITRB

Bureau of the Fiscal Service – Fiscal Accounting

jeffrey.board@fiscal.treasury.gov

Keith Jarboe

IGT Agency Outreach, Engagement & Onboarding

Bureau of the Fiscal Service – Fiscal Accounting

keith.jarboe@fiscal.treasury.gov

For Intragovernmental Transactions Working Group Information

IGT@fiscal.treasury.gov

https://www.fiscal.treasury.gov/g-invoice/