Intragovernmental Transactions

Working Group (ITWG)

May 14, 2019
Page 2 L EAD ∙ T RANSFORM ∙ D ELIVER

Today’s Agenda

• Tentative ITWG Schedule

• Implementation Plans

• Survey Results

• Settlement of Performance

• Survey Questions

• Questions and Answers
Page 3 L EAD ∙ T RANSFORM ∙ D ELIVER

Tentative ITWG Schedule

 March 12 – Remittance Advice, Administrative Changes

 April 9 – More on Administrative Changes and Settlement

 May 14 – Mapping FIDS to IPAC, Settlement Rules

Planned Dates: June 11, July 9, Aug 13, Sept 10 ...

Future Topics:

• Loading Active Orders

• Reporting Requirements

• Authoritative Source 2-3 pm ET
Page 4 L EAD ∙ T RANSFORM ∙ D ELIVER

Implementation Plans

• Implementation Plans and Attachment A’s are due to Fiscal 

Service by June 28, 2019

• Fiscal Service will be creating a dashboard to display the 

results and publish on the G-Invoicing website

- Visibility between Trading Partners

• Submit to IGT@fiscal.treasury.gov

• Questions regarding either Implementation Plans or 

Attachment A? 
Page 5 L EAD ∙ T RANSFORM ∙ D ELIVER

Agency IGT Buy/Sell Overview

• Section 2.2 of template, Agency IGT Buy/Sell Overview, 

asks for data of how agencies conduct transactions today

• Supporting statistics is preferred as it provides a clear 

understanding of an Agency’s annual workload and the 

impact of implementing G-Invoicing 

• Example Statistics 

- Average new Agreements each Fiscal Year

- Average new Orders each Fiscal Year

- How Settlement Occurs Today (Collection vs Payment IPACs)

- Average total value of agreements with Trading Partners 
Page 6 L EAD ∙ T RANSFORM ∙ D ELIVER

Overview Example – DOI 

• DOI Shared that they received an average of 6K new 

reimbursable Agreements each FY as a Seller
Page 7 L EAD ∙ T RANSFORM ∙ D ELIVER

Overview Example – DOI 

• Analysis included a Summary breakout of FY 18
Page 8 L EAD ∙ T RANSFORM ∙ D ELIVER

Overview Example – DOI 

• DOI reviewed their current transaction level to project what 

their FY 18 would look like in G-Invoicing
Page 9 L EAD ∙ T RANSFORM ∙ D ELIVER

Survey Results

• Mapping FIDS to optional IPAC data elements

– Agencies use Miscellaneous Information (320 chars)

– Agencies need a way to differentiate their partners’ organizations

(6) G-Invoicing Options (2) IPAC Targets

- Order Header: Comments (1000)

- Requesting Agency Additional Info (1000)

- Servicing Agency Additional Info (1000) - Misc. Info. (320)

- Req Agency Additional Accounting Classification (320) - Description (320) 

- Serv Agency Additional Accounting Classification (320)

- Performance Comments (1000) ?

(6) G-Invoicing Options

- Organizational Reference Data for both Requesting and Servicing Agencies

- Business Unit (20) and Description (100)

- Cost Center (35) and Description (100)

- Department ID (20) and Description (100)

Schedule

?
Page 10 L EAD ∙ T RANSFORM ∙ D ELIVER

G-Invoicing

Performance 

Detail

Performance

Header

Settlement Data Exchanges 

Order

Header

Order Line

Order Line 

Schedule

Detail 

Settlement

Pending

Settled

Performance

Settled

Informational

IPAC

12

3

6

9

Bulk File (or UI entry)

Transaction Download Report

New Interface

Existing Interface

Key
Page 11 L EAD ∙ T RANSFORM ∙ D ELIVER

Settlement Rules

• Performance reported to G-Invoicing release 2.3 

will be set to ‘PRE’ (Pre-Settlement) status

- Settlement will not occur

• Beginning later in 2019

- Schedules with Advance Payment Indicator = True

o Advance Payment by servicing agency triggers settlement

- Schedules with Advance Payment Indicator = False

o FOB Point = Source

· Delivered/Performed by servicing agency triggers settlement

o FOB Point = Destination

· Received/Accepted by requesting agency (or constructive receipt) 

triggers settlement

- No settlement at month-end (3 days) or year-end (5 days)
Page 12 L EAD ∙ T RANSFORM ∙ D ELIVER

Determining Settlement Status

• Performance which will trigger settlement immediately will 

be set to ‘PND’ (pending) status

• Performance which will trigger settlement on a future 

Performance Date will be set to ‘FUT’ (future) status

• Performance for which settlement has occurred will be set 

to ‘STL’ (settled) status

• Performance which does not trigger settlement will be set to 

‘INF’ (informational only) status

• Performance for which settlement has failed will be set to 

‘ERR’ (error) status

• Future dated Performance transactions that have been 

logically deleted will be set to ‘DEL’ (deleted) status
Page 13 L EAD ∙ T RANSFORM ∙ D ELIVER

Performance FIDS for Settlement

Data 

Element

Data Element 

Description

Level Validation Rules

Settlement 

Status

Tracks the status of 

performance through 

settlement, when 

applicable.

Header Not allowed for input by agencies. Status assigned by the System:

PRE (settlement) for performance reported in R2.3, prior to settlement.

INF (informational) if Performance does not trigger settlement.

FUT if Performance triggers settlement and Perf Date in future.

PND if Performance triggers settlement, but not yet settled. 

STL if settlement has occurred.

DEL if (future) performance transaction was (logically) deleted.

ERR if settlement failed. Actionable only by G-Inv Prod Support.

Disbursing 

Office 

Symbol

Organization identifier 

assigned to an agency 

which is disbursing funds 

from the Treasury 

General Account.

Header Not allowed for input by agencies.

Only applicable if Status is FUT, PND or STL. 

First 4 chars are 'GINV'. Fifth char is variable: 1, 2, 3 ... 9, A, B, C ... Z.

Fifth char is incremented when DRN reaches 99999999.

Each ALC is assigned one DO Symbol to be used for IPAC.

Document 

Reference 

Number

A unique reference 

number used to identify 

a specific 

intragovernmental 

transaction. 

Header Not allowed for input by agencies.

Only applicable if Status is FUT, PND or STL. 

Assigned by system as 00000001, 00000002 ... 99999999.

Recycled back to 1 when it reaches 99999999 and new DO Symbol 

assigned. 
Page 14 L EAD ∙ T RANSFORM ∙ D ELIVER

Obtaining IGT Buy/Sell Settlement Results

Pending

Settled

Performance Payment or Collection

G-Invoicing IPAC

Open

Order in

G-Inv?

Yes No

Settlement Download

Pull (API)

Transaction Download
Page 15 L EAD ∙ T RANSFORM ∙ D ELIVER

Survey Questions for Today

1. Please provide your agency name and (ideally) your contact info so we 

can address your concerns.

2. Is your agency okay with mapping Performance Comments in GInvoicing to Description in IPAC? (Y/N)

3. Is your agency okay with mapping Additional Accounting Classification 

in G-Invoicing to Miscellaneous Transaction Information in IPAC? (Y/N)

4. If you answered No to either question 2 or 3, what data elements in GInvoicing (shown on slide 5) should be used to populate Description 

and Miscellaneous Information in IPAC?