Intragovernmental Transactions

Working Group (ITWG)

April 9, 2019
Page 2 L EAD ∙ T RANSFORM ∙ D ELIVER

Today’s Agenda

• Tentative ITWG Schedule (Alex Abshire)

• Survey Results (Alex)

• Settlement of Performance (Wes Vincent) 

• Settlement Reporting (Wes)

• Survey Questions (Alex)
Page 3 L EAD ∙ T RANSFORM ∙ D ELIVER

Tentative ITWG Schedule

 February 12 – More on Performance, changes to Order

 March 12 – Remittance Advice, Administrative Changes

 April 9 – More on Administrative Changes and Settlement

Planned Dates: May 14, June 11, July 9, Aug 20, Sept 10 ...

Future Topics:

• System of Record

• Sensitive Agency Data

• Onboarding with Open Orders

• Reporting Requirements

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

Survey Results

• Drop BPN+4 from Order FIDS?

– Results evenly split between Yes/No/Maybe

– Currently required for at least one ERP offering

– Decision: BPN+4 will remain on Schedule as optional

• Scale back on Administrative Changes to Orders?

– Authority Fund Type, Title and Citation

– Advance Payment Authority Title and Citation

– Acceptance/Inspection Point/Place

– Decision: All three will require Order Modification and Approval

– Details to be published on G-Invoicing website in Order FIDS

• Remaining questions covered on next slides

– Reporting settlement data out of G-Invoicing

– Mapping G-Invoicing FIDS to IPAC’s SCV file
Page 5 L EAD ∙ T RANSFORM ∙ D ELIVER

Survey Results – Settlement Reporting

• Many agencies (and vendors) want to continue pulling 

Transaction Download from IPAC ... More on that later

• Many agencies (and vendors) plan to pull Performance and 

Orders though APIs then report settlement on their own

• Many agencies want to report settlement from G-Invoicing

– CSV and Excel are common formats

– Some want to report daily and others less frequently

• Reporting by accomplished/settlement date is most popular

– Reporting by Organization is common (i.e., partner, ALC, 

department, business unit, cost center) 

– Reporting by document is common (e.g., “Invoice”, Order, GT&C, 

Document Reference Number)

– Reporting by TAS is common
Page 6 L EAD ∙ T RANSFORM ∙ D ELIVER

Survey Results – IPAC’s CSV File

• There appears to be some confusion regarding the future of 

the Transaction Download Report from IPAC

– Yes, the CSV file will still be available for the foreseeable future

– Yes, the CSV file could contain all buy/sell activities, both initiated 

directly in IPAC and initiated in G-Invoicing to IPAC

– However, transactions flowing from G-Invoicing will look different

• Your agency no longer controls the data going to IPAC

• Settlement requests will be generated from G-Invoicing

• G-Invoicing is limited to the Federal Intragovernmental Data Standards

• Mapping of G-Invoicing data to IPAC is government-wide, subsequently 

unlikely to match what your agency is sending IPAC today

– Your agency (and/or vendor) should assess obtaining settlement 

data directly from G-Invoicing’s APIs or CSV extracts

– IPAC’s CSV file may help you during the transitional period

• But you will have to interpret data from two different sources
Page 7 L EAD ∙ T RANSFORM ∙ D ELIVER

Performance Triggered Settlement

• Planned for a late 2019 release ...

• Settlement requests will be passed from GINV to IPAC

– Only some Performance records will trigger settlement

• Advances always trigger collections

• Some Delivered/Performed trigger collections

• Some Received/Accepted trigger disbursements

– Those that do will be flagged as “pending” settlement

• Future dated settlement to be flagged as “future” then set to “pending” 

– IPAC/GINV interface will update Performance as “settled” 

• Final version of Federal IGT Data Standards and updates 

to “Pull” specifications planned for April 2019

• Performance FIDS and the Performance Pull API will be 

extended to include settlement information from IPAC

• Remittance Advice is now considered a reporting concept
Page 8 L EAD ∙ T RANSFORM ∙ D ELIVER

Performance FIDS Extends to Settlement

• Every Performance Transaction will be assigned a Status

• Other five data elements only applicable for settlement requests

• Values for all six data elements controlled by GINV or IPAC systems

Data Element Data Element Description Level Validation Rules Type Len.

Status Tracks the status of fund transfer. 

Values: ACR = Accrual (only), FUT = 

Future (dated), PND = Pending 

(settlement), or STL = Settled

Header Not allowed for input by agencies through UI or API.

Status assigned by the System.

Char 3

Disbursing Office 

Symbol

Org ID (below ALC) used by IPAC so 

ALC/DO/DRN is unique. Also used to 

segment agency data.

Header Not allowed for input by agencies through UI or API.

Only applicable if Settlement Status <> 'A'. Char 5

Document 

Reference Number

A unique reference number used to 

identify a specific intragovernmental 

transaction. 

Header Not allowed for input by agencies through UI or API.

Only applicable if Settlement Status <> 'A'. Char 8

Settlement Date

The date upon which the funds are 

transferred. (IPAC Accomplished 

Date).

Header Not allowed for input by agencies through UI or API.

Only applicable if Settlement Status = 'S'. Date 8

Settlement 

Transaction ID

A unique identifier used to identify a 

specific transaction submission. Header Not allowed for input by agencies through UI or API.Only applicable if Settlement Status = 'S'. Numeric 16

Settlement Detail 

Line Number

Identifies the specific detail line 

number for an intragovernmental 

transaction. 

Detail Not allowed for input by agencies through UI or API.

Only applicable if Settlement Status = 'S'. Numeric 6
Page 9 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

Accrual (only)

IPAC

12

3

6

9

Bulk File (or UI entry)

Transaction Download Report

New Interface

Existing Interface

Key
Page 10 L EAD ∙ T RANSFORM ∙ D ELIVER

Sending IGT Buy/Sell Settlement Requests

Pending

Settled

Performance Payment or Collection

G-Invoicing IPAC

Open

Order in

G-Inv?

Yes No

Transaction Download

• Until all agencies 

are in G-Invoicing 

for Buy/Sell, check 

for an open Order
Page 11 L EAD ∙ T RANSFORM ∙ D ELIVER

G-Invoicing Data Required by IPAC (1 of 2)

• 12 of 17 required data elements in IPAC are straight-forward

IPAC CSV Name IPAC Type Length IPAC Description GINV Source for Data on IPAC CSV File

Submitter ALC Numeric 8 ALC submitting the Transaction Depends on what Performance triggered settlement. Req

ALC for Received/Accepted. Otherwise the Serv ALC.

Originating ALC Numeric 8 The ALC sending the Payment or 

Collection transaction

Requesting ALC for Received/Accepted. Otherwise the 

Servicing ALC.

Customer ALC Numeric 8 Agency Location Code receiving the 

Payment or Collection transaction

Servicing ALC for Received/Accepted. Otherwise the 

Requesting ALC.

Quantity Numeric 12.2 Number of units to determine total 

price Quantity in Performance Detail

Unit Price Numeric 19.2 Price per unit of product, service, 

commodity, etc. Order Schedule Unit Price

Detail Amount Numeric 14.2 Quantity x Unit Price Calculated by GINV

Pay Flag Alpha/Num 1 “F” – Final payment or 

“P” – Partial payment Final Performance Indicator on Performance Detail

Receiver Treasury 

Account Symbol Alpha/Num 27 Account number assigned by Treasury to classify Agency txns. 

8 TAS components on Order/Line/Schedule.

Receiver is the partner that did not submit Performance.

Receiver BETC Alpha/Num 8 Identifies the type of event that is 

recorded against a TAS

Derived by G-Inv depending on what Performance triggered 

settlement and whether quantity is +/-

Sender Treasury 

Account Symbol Alpha/Num 27 Account number assigned by Treasury to classify Agency txns. 

8 TAS components on Order/Line/Schedule.

Sender is the partner that submitted Performance.

Sender BETC Alpha/Num 8 Identifies the type of event that is 

recorded against a TAS

Derived by G-Inv depending on what Performance triggered 

settlement and whether quantity is +/-

Transaction

Set ID Alpha/Num 3 “820” – Payment or “810” – Collection. 

Generated by G-Inv. 810 if servicing agency performance. 

820 if requesting agency performance.
Page 12 L EAD ∙ T RANSFORM ∙ D ELIVER

G-Invoicing Data Required by IPAC (2 of 2)

• 5 of 17 required data elements in IPAC are not as clear-cut

• Order Number from G-Invoicing equates to PO Number in IPAC

– That also seems to equate to the Obligating Document Number

• No invoices per se, so Performance Number equates to Invoice Number

• We decided not to convert ISO/ANSI units of measure to Unit of Issue

• DO Symbol discussed on next slide

IPAC CSV Name IPAC Type Length IPAC Description GINV Source for Data on IPAC CSV File

Purchase Order 

Number Alpha/Num 22 Number of the document from the 

agency requesting goods or services Order Number

Invoice Number Alpha/Num 22 ID of the invoice sent by the biller listing 

the services rendered

Performance Number

Note: Cannot fit both Performance + Detail Number(s)

Unit of Issue Alpha/Num 2 Units by which goods and services are 

measured

Fixed value ... no attempt to map ANSI and ISO standards to 

UOI in IPAC

Obligating 

Document 

Number

Alpha/Num 17

Billing agency’s internal accounting 

document associated with a specific bill 

or disbursement

Would seem to indicate Order Number, but (a) we already 

have PO Num, (b) Order Num is 20 char, and (c) an Order is 

not a "bill". Could use other IDs but all > 17 chars.

Sender DO 

Symbol Alpha/Num 5

Org ID (below ALC) used by IPAC so 

ALC/DO/DRN is unique. Also used to 

segment agency data.

Generated by GINV (e.g., GINV1) ... allow it to increment 

(e.g., GINV2) when DRN maxes out (> 99,999,999).

Note: Some agencies control this today for IPAC bulk file.
Page 13 L EAD ∙ T RANSFORM ∙ D ELIVER

Disbursing Office Symbol

• DO Symbol used by IPAC to re-sequence Document Reference Number

– Doc Ref Num must be unique within ALC/DO

• DO Symbol is used by some Agencies to segment their data in IPAC

• G-Invoicing data is segmented using organizational filter(s), as part of 

the permissions model

– Cost Center

– Business Unit Org filters can be used in any way your agency sees fit

– Department ID

• Organizational filters and permissions are managed by the Agencies

– Org Administrators manage Org Filters and Data Access Groups

– User Administrators assign users to Roles and Data Access Groups

• DO Symbol will no longer be under Agency control

• G-Invoicing will now control the DO Symbol value sent to IPAC

– Meets IPAC data requirement without adding to Order FIDS

– DO Symbol will be incremented when Doc Ref Num exceeds 8-digits 

– Distinguishes source of transaction in IPAC (i.e., GINV vs direct by Agency)
Page 14 L EAD ∙ T RANSFORM ∙ D ELIVER

Optional IPAC Data from G-Inv (1 of 3)

• 8 of 17 optional data elements in IPAC are straight-forward

• All data (required, optional and more) will be available in G-Invoicing

– Pull Performance data via Application Program Interface

– View Performance/Settlement data via User Interface

– Export data to CSV file for Excel

IPAC CSV Name IPAC Type Length IPAC Description GINV Source for Data on IPAC CSV File

Receiver DUNS Alpha/Num 9 Unique identifier for individual 

business locations for federal vendors 

and federal customers

BPN in Order Header. 

Receiver DUNS+ 4 Alpha/Num 4 BPN+4 in Order Schedule.

Sender DUNS Alpha/Num 9 Unique identifier for individual 

business locations for federal vendors 

and federal customers

BPN in Order Header. 

Sender DUNS+4 Alpha/Num 4 BPN+4 in Order Schedule.

Accounting 

Classification 

Reference Number

Alpha/Num 12 ACRN – identifies a line of accounting 

on a contract

Accounting Classification Reference Identifier

on Schedule

Description Alpha/Num 320 Sufficient information to describe and 

support the adjustment transaction

Use first 320 chars of Comments

in Performance Header

Document Reference 

Number Alpha/Num 8 A unique reference number used to identify a specific iIGT

G-Inv to generate unique DRN within ALC/DO Symbol, 

used to trace between GINV/IPAC/CARS.

DODACC Alpha/Num 15 Identifies a Department of Defense 

activity location Use AAC on Order/Line/Schedule
Page 15 L EAD ∙ T RANSFORM ∙ D ELIVER

• Next 4 of 17 optional data elements in IPAC are not as clear-cut

• Is Contract Number the GT&C? Can agencies expand to 20 chars?

• CLIN cannot represent both the Line and Schedule Numbers

• Is Accounting Classification Code defined the same for all agencies?

Optional IPAC Data from G-Inv (2 of 3)

IPAC CSV Name IPAC Type Length IPAC Description GINV Source for Data on IPAC CSV File

Contract Number Alpha/Num 17

Unique number used to identify a 

contract between two trading 

partners

GTC Number is 20 characters

CLIN Alpha/Num 6 Contract Line Item Number Order Line Number

Note: Cannot fit both Line + Schedule Number(s)

FY Obligation ID Alpha/Num 1

“C” – Current fiscal year obligation or 

“P” – Prior fiscal year obligation or “ ” 

– Not applicable

N/A ... G-Invoicing does not support the concept.

Could potentially be derived from POA.

Note: Not required in IPAC

Accounting 

Classification Code Alpha/Num 16

Code/number which identifies a 

project or mission and is supplied to 

the biller by the customer on the 

original request for goods/services

Not obvious ... Could be GT&C Number or Order 

Number, but those are 20 chars. Could be requesting or 

servicing Project Number from Schedule (depending on 

who submitted performance), but those are 25 chars.
Page 16 L EAD ∙ T RANSFORM ∙ D ELIVER

• Last 5 of 17 data elements in IPAC do not align with G-Invoicing

Optional IPAC Data from G-Inv (3 of 3)

IPAC CSV Name IPAC Type Length IPAC Description GINV Source for Data on IPAC CSV File

Job Number Alpha/Num 20 Job (Project) Number Not obvious ... Could be requesting or servicing Project 

Number from Schedule, but those are 25 chars.

JAS Number Alpha/Num 30

Combination of Job Order Number, 

Accounting Classification Record 

Number and Site-ID

Not obvious

FSN AAA ADSN Numeric 8 FSN/AAA/ADSN – subdivision of ALC, 

an accounting station

Not obvious ... G-Inv uses Org Reference data (i.e., cost 

center, business unit, department ID).

ACT Trace Number Alpha/Num 15

Accounting Trace Number – user 

assigned ID enables back end systems 

to match up transactions.

Not obvious ... Could use an agency ID, but only G-Inv

IDs (e.g., Order Number, Performance Number) are 

guaranteed to be interpreted by both partners.

Miscellaneous 

Information Alpha/Num 320 Additional miscellaneous transaction 

information

Not obvious ... Could use requesting or servicing Agency 

Additional Accounting Classification, depending on 

which partner submitted performance.
Page 17 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 18 L EAD ∙ T RANSFORM ∙ D ELIVER

Recommendation 

• We’ve shown the challenges of sending all required and optional data 

from G-Invoicing to IPAC

• We’ve shown how agencies need to distinguish Performance data 

going to G-Invoicing from Invoices going to IPAC

• Agencies will continue to obtain settlement information from IPAC 

when they initiate Settlement directly through IPAC

• We recommend agencies obtain settlement information from 

G-Invoicing when Performance triggers Settlement

– Agencies may pull settled Performance through the API and construct their 

own reports

– Agencies may download a CSV file containing Order, Performance and 

Settlement data similar to IPAC’s Transaction Download Report

• G-Invoicing plans to only send required data (on slides 11-12) to IPAC

– Survey questions ask for business cases that refute this approach
Page 19 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. Does your agency see any issues with pulling settlement results separately from G-Invoicing 

and IPAC as presented here today? If so, what are those issues?

3. Would your agency want an option to also pull G-Invoicing initiated settlement results from 

IPAC, or would you rather that data be excluded from your Transaction Download Report?

4. Does your agency have a business case wherein you need to control the value of DO Symbol? 

If so, can you switch to using Cost Center, Department ID and/or Business Unit as described 

on slide 13? Please explain.

5. Does your agency have a business case wherein you need to control the value of Document 

Reference Number (e.g., for reconciliation purposes)? If so, can you send the control ID to GInvoicing as the Agency Transaction Identifier data element within the Performance FIDS? 

Please explain.

6. Are there any data elements appearing on slide 16 that your agency cannot function without? If 

so, and given that these data elements are not in the Federal Intragovernmental Data 

Standards, how can this need be met?

7. How frequently will your agency report multiple Delivered/Performed transactions against the 

same Schedule (e.g., never, rarely, commonly)? Are those multiple deliveries/performances 

done within a few days of each other, or spread out over months? Please describe the 

business cases to support this.