L EAD ∙ T RANSFORM ∙ D ELIVER

G-Invoicing

GT&C Mod/Revert 

(Planned Future Enhancement)

Version 1.0 – January 28, 2022
Page 2 L EAD ∙ T RANSFORM ∙ D ELIVER

Objective: 

• Allow revert of any changes made to a GT&C during a modification and return 

the GT&C to the previous open for orders or closed state

– Option for GT&C Manager and Supervising Manager roles only

– Available only to the partner that initiated the modification

• Partner 2 has the option to reject the modification and allow Partner 1 to revert 

• Allow Order maintenance during GT&C Mod 

Changes needed:

1. Add Revert option to Pending Approval (modified) GT&Cs

2. Require Reason (gets cleared once document is moved to next state)

3. Capture audit but do not retain modification details 

4. Order creation and modification conditionally allowed during GT&C Mod

What’s not changing:

• General GT&C create/approve/modify process flow (no state changes)

Supporting GT&C Mod/Revert
Page 3 L EAD ∙ T RANSFORM ∙ D ELIVER

• Current G-Invoicing Design

– Two sets of tables for GT&Cs: Active and Archive

– The highest GT&C Modification Number is active

• Previous Mod Numbers are archived (in open for orders, closed or 

rejected status)

• API Transition

– Two partners and G-Invoicing must stay in sync

• Example: Partner 1 wants to Revert, but Partner 2 cannot interpret that 

action

– New API(s) will be backwards compatible

• Use of new feature that might “break” a partner’s GT&C will be 

controlled through Feature Management

GT&C Mod/Revert Background
Page 4 L EAD ∙ T RANSFORM ∙ D ELIVER

• Current functionality

1. Partner 1 introduces modification to open for orders GT&C

2. Partner 2 may reject the modification (with Reason)

3. Partner 1 must then attempt to restore previous values 

4. Both partners must re-approve the GT&C 

• New flows for GT&C

– Allow initiating partner to Revert a pending approval GT&C to the previous 

open for orders or closed version (with Reason)

• Accessible to GT&C Manager and Supervising Manager roles only

• Revert to previous Mod number “n-1” 

• Set the Last Update Date/Time

• Reprocessing Reason is required for Revert action

– Both partners must be able to handle the action (i.e., Feature Flags = Yes)

– UI will show previous version (i.e., the target for the Revert)

– Abandoned version is audited but not viewable or recoverable

Revert GT&C to Previous Version
Page 5 L EAD ∙ T RANSFORM ∙ D ELIVER

Ordering During GT&C Modification

• Relax validation rules for Order requests while GT&C is 

being reapproved

̶ Ordering will be allowed when all three conditions are met:

a) GT&C Mod is pending approval

b) Previous Modification Number (n -1) is open (REC status)

c) Feature flag for ‘GTC Mod’ is Yes for both partners

o Both partners must be able to handle this action

̶ Note: Ordering is still allowed when active GT&C is open

• Flow of GT&C modification remains the same

̶ G-Invoicing will validate the GT&C with each UI approval
Page 6 L EAD ∙ T RANSFORM ∙ D ELIVER

Implementation Details

• The following slides document what needs to be changed in published 

G-Invoicing specifications in order to implement this new feature

• Implementation details are provided so that:

– Product Owner(s) can confirm detailed business requirements 

– Development team(s) can visualize changes needed to support new features

• At this time, we cannot predict when development of this feature will 

begin, when it will be released into QA or Production, or in which release 

it will be included

• When the time comes to begin work on these features, the details will be 

added to the specifications, a release will be targeted, and API 

specifications will be republished

• One of the implementation details described below is a move from XML 

to JSON payloads for APIs involving GT&Cs, Orders and Performance

– Future (post-mandate) APIs will only support JSON payloads

• Note: Newer APIs (e.g., Pull Org, Remittance) are already in JSON format
Page 7 L EAD ∙ T RANSFORM ∙ D ELIVER

Changes to FIDS

• GT&C Federal Intragovernmental Data Standards

– New data element to capture Reprocessing Reason

• Definition: Explanation for an action that moves a document back to a prior 

version or status, including instructions on if/how to correct the document for 

reprocessing.

• reprocessingReason (JSON), 1024 characters

Note: This one data element will cover multiple Reprocessing Reasons, such as 

Return (for GT&C and Orders), Revert (for GT&C and Orders), and Reverse (for 

EZ).

– New data element to capture Modification Reason

• Definition: Explanation for a change to a versioned document (e.g., Order), 

significant enough to warrant reapproval of the document.

• modificationReason (JSON), 1024 characters
Page 8 L EAD ∙ T RANSFORM ∙ D ELIVER

Changes to SM&VR

• GT&C System Mapping and Validation Rules

– Document new Revert action to go from Pending to Open status

• Mod Number must be > 0

– Add new data element (row) to capture Reprocessing Reason

• Required for Revert action

– Add new data element (row) to capture Modification Reason

• Required for modification
Page 9 L EAD ∙ T RANSFORM ∙ D ELIVER

GT&C State Diagram

Partner A (Initiator) Partner B Both Partners

Closed for 

Orders

Internal

(Draft) Deleted Rejected Pending Approval (no approvals)

Pending Approval 

(one approval)

Open for

Orders

Shared 

Draft

Roles

Mgr Apprvr

Create

Delete

Modify

Modify

Reject

Save as 

Int. Draft

Approver 1

Approver 2

Approver 1

Save as 

Shared 

Draft

Approver 1 or 2

Edit & Submit

Approver 2

Close

Share

Submit

Approver 1 + 2

Approver 1 + 2

Admin 

Change

Admin 

Change

Admin 

Change

Return

Revert (no approvals or 1+)

Revert (no approvals or 1+)

Supv
Page 10 L EAD ∙ T RANSFORM ∙ D ELIVER

Version History

Version Date Release Description

v0.1 8/21/2021 TBD Original version

v0.2 10/29/2021 TBD Added detailed specifications

v0.3 11/4/2021 TBD Add GT&C state diagram and initiating partner revert rule

v0.4 11/5/2021 TBD Add initiating partner revert rule

v0.5 1/10/2022 TBD Draft of first published version for G-Invoicing website

v0.6 1/27/2022 TBD Added FIDS page, including Reason codes

v0.7 1/28/2022 TBD First published version on G-Invoicing website