General terms and conditions (GT&C)
How does my agency initiate a GT&C with GSA?
If you are looking to initiate a GT&C with GSA please reach out to your GSA point of contact. We are recommending Federal Acquisition Service (FAS) to initiate GT&C and share draft with the requesting agency. In the event that a requesting agency initiates a GT&C, FAS is still able to modify all servicing data and continue with the approval workflow.
Is there a phone number or email address that our agency can contact when/if they have trouble starting a GT&C/7600A?
If a client agency needs additional support outside of their own G-Invoicing Agency POC, please reach out to your respective FAS point of contact. If you are unsure of your FAS POC, you may reach out to G-Invoicing@gsa.gov for general questions or for Assisted Acquisition Services (AAS) specific Enterprise G-Invoicing support, please reach out to ginvoicing.aas@gsa.gov. For Office of Centralized Acquisition Services specific support, please reach out to OCAS.Agreements@gsa.gov.
Will Interagency Agreements Part A (IAAs)/7600As & 7600Bs that exist prior to the G-Invoicing rollout continue to be handled in ASSIST?
If your agency is G-Invoicing ready, GSA can transition your existing IAA agreements to G-Invoicing at a natural breaking point. For example, exercising an option, adding a task, or modifying funding is an opportunity to transition to G-Invoicing, by creating a new GT&C and corresponding IAA (in ASSIST). For the options that were exercised before the transition, we will continue to settle any invoices for those periods through IPAC until the cutoff. If your agency is not G-Invoicing ready, GSA will accept IAAs/7600As & 7600Bs outside the G-Invoicing system. Please work with your FAS point of contact.
Once G-invoicing is implemented, will we still need to use PDF forms at any point in the process? Will the whole process be executed within the G-invoicing system?
No other documents or PDF forms will be required outside of G-Invoicing. The G-Invoicing system will digitize the 7600 A/B forms and process.
Does G-Invoicing allow fields to be defaulted? Can fields that are always “Yes” (Assisted Acquisition Indicator) and always “No” (Advance Payments) just be populated instead of having to be selected each time?
Since G-Invoicing is a government-wide system, Federal Acquisition Service (FAS)-specific requirements/data cannot be defaulted. We will have to make our selection every time we are creating a GT&C.
Is the GT&C number randomly generated?
The GT&C number is system-generated as per the G-Invoicing numbering schema.
In the “Agreement Period” field, why is a period of 20 years recommended?
A longer Agreement Period is recommended to allow ample time for all pre-award, post award, and contract closeout activities. The 7600A Agreement Period can be negotiated with each agency/group based on your project needs.
Does the Treasury’s system enforce a particular signing order for the GT&C Requesting and Servicing initial/final approvals?
Both requesting and servicing GT&C approvals are done concurrently. For both trading partners, the GT&C approval process is sequential, initial approval will need to be completed before the final approver can take action. Note that if a draft GT&C has been shared with your agency, the receiver must complete the data fields and then “Submit for Approval” to begin the approval process.
Is there a way to track changes to a GT&C after it has been populated and shared with the partner agency?
G-Invoicing has a history button that shows at a high level, when the GT&C was created, submitted and approved. Changes are defined in the system and are not all inclusive.
Will contracted support personnel be given G-Invoicing user accounts? Or will it be federal employees only?
Contracted personnel can have G-Invoicing access but they may only be given the GT&C create role.
Orders
What is the required Funding Office Code (FOC) field in G-Invoicing?
The Funding Office Code (FOC) is a 6 digit client identifier (often a DODAAC for DOD/DOW agencies). GSA’s feeder system uses it in Federal Procurement Data System (FPDS) integration for its users and maps it to the vendor code required for billing.
When submitting your first order or if using a new FOC, please reach out to your GSA point of contact to see if an active FOC is established or FOC needs to be registered with GSA in ASSIST.
What is the required Activity Address Code (AAC) field in G-Invoicing?
The Activity Address Code (AAC) is a 6 digit funding agency identifier (often a DODAAC for DOD/DOW agencies). This code also must be registered with GSA in ASSIST to avoid system rejection – Please refer to the question above if you need to request a code to be added.
While not required to be the same code, the Activity Address Code will often be the same 6 digit code as the Funding Office Code for many agencies if the client group is also the funding agency.
Can I attach a 7600B/Order Appendix to provide additional information to the Order such as Bona Fide Need or Fee information?
All information relevant to the Order must be provided in the G-Invoicing system, this includes the fee structure. It is currently recommended this information be placed in the Bona Fide Need field. Please note, that while this field is restricted to 150 characters, GSA recommends using the Line Item Description field to put additional information related to the purpose, period of performance or fee. Please see the appendix below.
Examples of fee structure include:
- GSA Fee 3%
- GSA Flat fee $30,000.00
What does the G-Invoicing Order period of performance (POP) dates reflect? Where can I put the Contract POP dates that reflect the Award’s Base and Option Years?
The Order POP dates represent the first and last date the Servicing Agency fulfills the Order and delivers the goods and/or services per the Treasury G-Invoicing Program Guide. GSA recommends that the G-Invoicing Order POP dates align with or encompass the Award’s POPs for the Base and Option Years for proper performance/billing.
The contract’s line item POP dates can be placed in the Bona Fide Need field. If there is not enough space, please use the Item Description field (240 characters limit) as this field is locked down. We cannot use the comments field for any Bona Fide Need related information (purpose, time and amount) as this field can be edited at any time even after approval by all parties and obligated to the award.
Example period of performances
Order period of performance aligning with contract period of performance| POP reference field | Period of performance |
|---|
| G-Invoicing Order POP | 04/01/2026 to 03/31/2027 |
| Contract/Award POP | 04/01/2026 to 03/31/2027 |
| G-Inv Bona Fide Need field | POP not required |
Order period of performance encompassing the contract period of performance| POP reference field | Period of performance |
|---|
| G-Invoicing Order POP | 03/15/2026 to 03/31/2030 |
| Contract/Award POP | 04/01/2026 to 03/31/2027 |
| G-Inv Bona Fide Need field | 04/01/2026 to 03/31/2027 |
Note that for new or base awards when the award date is not precisely known, the G-Invoicing Order POP is recommended to both start early and end later than the “true” estimated start dates noted in the Bona Fide Need field.
I am providing incremental funding on a severable award listing the period of performance as the incremental period that the funding is designated to support. This has been accepted previously on MIPRs but was rejected in G-Invoicing. How can we overcome this issue?
In G-Invoicing the Order level POP’s are required to align with or encompass the award POP, please see full details in the answer above. If you would like to specify the incremental period the funding is designated to support, this POP information can be provided in the Bona Fide Need or Item Description fields, so long as the period falls with-in the line teams POP dates on the award.
My agency is not able to fit our purpose of the funds in the Bona Fide Need field.
The Bona Fide Need field is limited to 150 characters. If the purpose of the funds is longer than the limit, GSA recommends utilizing the Item Description field (240 characters limit) to add relevant the purpose of the funds.
I am providing an Order with funding for a supply purchase and would like to list the unit price/quantity of each commodity being purchased; however this was rejected by GSA’s system. What needs to be done to resolve this issue?
GSA requires all G-Invoicing Orders to have the unit cost listed as $1, with the quantity driving the total amount for each Order/line. This is due to the way GSA’s financial system system of record requires the financial information to be presented. At this time no exceptions can be made to this rule for G-Invoicing Orders.
How do I indicate that the funding provided is Subject to the Availability of Funding (SAF)?
G-Invoicing currently does not support SAF funding. If you require further clarification on G-Invoicing functionality, please contact the Department of Treasury at igt@fiscal.treasury.gov. Please work with your GSA project point of contact or point of contact on SAF processes.
My award has a mix of Severable and Non-Severable Contract Line Items (CLIN’s), how do I indicate this on the Order?
G-Invoicing does not support multiple severabilities listed on a single line number. If the funding provided is supporting multiple CLINs with varied severability please have the client provide multiple funding lines, as each line has the option to select its own severability.
Where should I list my contract’s Acquisition/Award Procurement Instrument Identifier (PIID)?
List under the Bona Fide Need or Item Description fields if space allows. The Procurement Instrument Identifier (PIID) field under Schedule can be used as well.
Is there a full list of all GSA’s required elements for G-Invoicing Order submissions?
While each request can have its own requirements, please see the appendix. FAS lists the general requirements for the majority of FAS Orders. Please contact your FAS point of contact for any contract specific information needed on the Order related to your requirement.
I received an automated rejection from GSA’s system regarding information provided on the Order. Do you have a full list of issues that will cause an automatic rejection from GSA’s financial systems in G-Invoicing?
Please refer to the table below for an inventory of Order values that will cause automatic rejection from GSA’s financial system.
| Rejection message | Resolution |
|---|
| Due to system limitations, we only accept orders where the Unit Price is $1.00. | The Unit Price on all schedules must be updated to $1.00. Please update the quantity field to drive the total schedule/Order amount. |
| BETC Error — One or more “Business Event Type Code” values could not be validated on our internal lookup table. | Our internal tables reference the valid Business Event Type Codes (BETC) from Treasury. Please ensure the BETC value on each schedule is updated to a valid code. |
| Item Code Error — One or more “Item Code” values could not be validated on our internal lookup table. | Please update the Item code to a valid Item/Product and Service (PSC) code. A list of all PSC codes can be found on this Acquistion.gov table. If you are unsure of which code applies please reach out to your FAS Project Manager. |
| Funding Office Code Error — One or more “Funding Office Code” values could not be validated on our internal lookup table. | The Funding Office Code (FOC) provided has either not yet been registered with GSA or was left blank. If you are unsure of your FOC code or need help registering a valid 6 digit code, please reach out to your FAS point of contact. Sam.gov search for Government Organization is a good resource for entity lookup. |
| Activity Address Code Error — One or more “Activity Address Code” values could not be validated on our internal lookup table. | The Activity Address Code (AAC) provided has either not yet been registered with GSA or was left blank. If you are unsure of your AAC code or need help registering a valid 6 digit code, please reach out to your FAS Project Manager. |
| For AAS Orders the Assisted Acquisition Flag must be Yes. | Please update the Assisted Acquisitions Indicator to “Yes”.
Any Order providing funding supporting an Assisted Acquisition must list the Assisted Acquisition Indicator to support this designation. |
| If data is provided in the UEI (Unique Entity Identifier) field, it must be 12 characters. | The UEI field is not required and may be left blank, however if a value is provided in this field it must be exactly 12 digits. Please either remove the value listed in the UEI field, or update it to a valid 12 character code. |
| Our systems do not support cancelled schedules, please reduce the quantity to $0 and activate the line or contact us. | GSA’s financial systems do not support cancelled schedules, please leave the schedule as “active” and reduce the quantity to $0.00 if you are unable to delete the schedule. |
| This modification reduced the schedule below the amount obligated by GSA please contact us if you need to reduce these schedules. | To ensure all contracts are properly funded, GSA systems ensure that funds cannot be reduced on a schedule below what is currently obligated on contract. If funding on the requested schedule needs to be reduced, please reach out to the FAS Project Manager associated with the award in order to coordinate the return. |
| Statutory Authority should be set to Type: Revolving Fund. | All funding accepted and awarded are completed under GSA’s authority, the Acquisition Services Fund (ASF). The Statutory Authority should appear on the Order as follows: - Statutory Authority Fund Type Code — Revolving Fund
- Statutory Authority Fund Type Title — Acquisition Services Fund
- Statutory Authority Fund Type Citation — 40 USC 321
|
| DOD requires that “097” funds have a Sub Allocation provided. | If funding is provided under a TAS with a “097” AID, the 4 digit Sub-Allocation must be identified and entered into the Sub-Allocation field. |
| The “Ship to” State needs to be a valid code. | Shipping information is not required on G-Invoicing Orders, however if the information is provided please ensure the “Ship to” state information is valid. |
| The “Ship to” Country needs to be a valid code. | Shipping information is not required on G-Invoicing Orders, however if the information is provided please ensure the “Ship to” Country information is valid. |
Appendix: G-Invoicing GT&C and order data requirement for ASSIST
G-Invoicing GT&C data structure
Partner information| Data block | GT&C data field | Description |
|---|
| 02 | GT&C Title | Descriptive name given to any GT&C by a Requesting or Servicing Agency for easy identification of the project. |
| 04 | Agreement Start and End Date | Period of performance of the GT&C. All Orders and all Performance Transactions will be bound by these agreement dates. |
| 01 | Requesting Agency (Agency, Group, Agency Location Code) | Agency group requesting this GT&C. Lead AAC will manage and administer the GT&C. All named Subordinate Group members can administer Order against this GT&C. |
| 01 | Servicing Agency (Agency, Group, Agency Location Code) | Agency group servicing this GT&C. Lead AAC will manage and administer the GT&C. All named Subordinate Group members can administer Order against this GT&C. |
Header/detail| Data block | GT&C data field | Description |
|---|
| N/A | Business Application | Standard order Processing |
| 03 | Order Originating Partner Indicator | Always Requesting Agency for AAS |
| 05 | Termination Days | Default is 30 days but can be negotiated |
| 06 | Agreement Type | For AAS, selection should be Multiple |
| 07 | Advance Payment Indicator | No |
| 08 | Assisted Acquisition Indicator | Yes |
| 09 | Enforce Total Remaining Amount Indicator | Default is No but can be Yes |
| 09 | Total Direct Cost and Overhead Fees | Estimated GT&C flowthrough cost/fee |
| 25 | Preparer Name, Phone, Email | System auto populate signed user’s Info |
Agreement information| Data block | GT&C data field | Description |
|---|
| 10 | Explanation of Overhead Fees and Charges | General explanation of how the overhead fees and charges are calculated. See attached in Appendix 1: 7600A.10 |
| 13 | Roles | Roles and responsibilities that the Servicing Agency must carry out to ensure the effective management and fulfillment of GT&C requirements. See attached in Appendix 1: 7600A.13 |
| 14 | Restrictions | Unique requirements and/or mission specific restrictions related to the GT&C (one restriction data field for both requesting and servicing agency). See attached in Appendix 1: 7600A.14 |
| 18 | Assisted Acquisitions | Servicing Agency provisions of the agreement. See attached in Appendix 1: 7600A.18 |
| 20 | Clauses | Not applicable for Servicing Agency |
Agreement information (request agency)| Data block | GT&C data field | Description |
|---|
| 11 | Scope | High-level scope of the work to be performed under this GT&C for all related Orders. See attached in Appendix 1: 7600A.11 |
| 12 | Requesting Agency Roles | Roles and responsibilities that the Requesting Agency must carry out to ensure the effective management and fulfillment of GT&C requirements. See attached in Appendix 1: 7600A.12 |
| 14 | Restrictions | Unique requirements and/or mission specific restrictions related to the GT&C. See attached in Appendix 1: 7600A.14 |
| 17 | Assisted Acquisitions | Not applicable for Requesting Agency |
| 19 | Clauses | Additional Requesting Agency provisions of the agreement (agency specific clauses if any) |
Approvals
Requesting agency completes requesting data entry and reviews all sections before submitting for approvals.
GT&C approvals are sequential, and approvals are open to both Requesting/Servicing:
- Initial Approver will 1st review and sign
- Final Approver will review and sign next
The GT&C is now open, and Order can be created next
G-Invoicing order data structure
Partner information| Data block | GT&C data field | Description |
|---|
| 04 | Assisted Acquisitions Indicator | Identifies whether the Order will accommodate Assisted Acquisition. For AAS Orders, always Yes |
| N/A | In-Flight Order Indicator | Always No |
| 05 | PoP Start and End Date | PoP must fall within the 7600A GT&C agreement dates |
| 08 | Group Name & Description | Organization within an agency that are entering into the agreement and order transactions |
| 14 | Funding Office Code (Requesting Agency) | Entity [XLS] provides the requirement and the preponderance of funds. Identifies the paying office, whomever settles the charge. (BOAC1) |
| 15 | Funding Agency Code (Requesting Agency) | Agency [XLS] provided the requirement and the preponderance of the funds |
Authority| Data block | GT&C data field | Description |
|---|
| 17 | Statutory Authority Fund Type Code | For AAS, select Revolving Fund (RF) |
| 18 | Statutory Authority Fund Type Title | For AAS, select Acquisition Services Fund (ASF) |
| 19 | Statutory Authority Fund Type Citation | FAS authority of Acquisition Services Fund is defined under 40 USC 321 |
Delivery| Data block | GT&C data field | Description |
|---|
| 28 | FOB Point | Source/Origin |
Point of contact| Data block | GT&C data field | Description |
|---|
| 40 | Point of Contact Name, Email, and Phone | Requesting agency point of contact |
Line| Data block | GT&C data field | Description |
|---|
| 46 | Item Code (Product Service Code) | Product Service Code/Federal Supply Code for the item or service associated with the Order. For AAS, default PSC is R707 |
| 47 | Item Description | Description of the PSC entered in 7600B block 46. For PSC R707, description is Support-Management: Contract/Procurement/Acquisition Support - Utilize this field to add any funding realignment language (use the bona fide need section if exceed character limit)
- Award PIID if known, please here or in Bona Fide Need
|
| 48 | UOM | Select appropriate value from the drop down (default selection is DO - U.S. Dollars) |
| 59 | Type of Service Requirements | Severable / Non-severable / N/A (for Supply) |
Schedule| Data block | GT&C data field | Description |
|---|
| 63 | Unit Cost | Cost of each unit is always $1.00 |
| 66 | Quantity | Total dollar amount for this schedule |
| 72 | Treasury Account Symbol (TAS) | Appropriation or fund symbol |
| 73 | Agency Business Event Type Code (BETC) | Requesting Agency to select BETC from the dropdown appropriate for the selected TAS. |
| 74 | Object Class Code | Record financial transactions according to the nature of the services provided or received when obligations first incur |
| 76 | Bona Fide Need | Brief description of the translation funded in the Schedule (purpose) - Schedule PoP must align with the Line Item PoP in ASSIST
- The Fee structure must be stated here (e.g. put %, flat amount, etc.)
- Award PIID if known, please place here or in Item Description
|
| 81 | Activity Address Code (AAC) | AAC is the ordering office providing the funding (BOAC2). |
| 88 | Sub-Allocation | Identifies an Organization to which funds have been Sub-Allocated. Needed for agency code 97 (DoD) only. |