Setting up your General Terms and Conditions
Getting started. To set up a GT&C, contact your GSA point of contact or email G-Invoicing@gsa.gov. We recommend letting the Federal Acquisition Service create the GT&C and send you a draft, but you can create it yourself. See step-by-step GT&C instructions
Who to contact for help. For support beyond your own G-Invoicing agency point of contact, reach out to your FAS point of contact. If you don’t know who that is:
Your existing agreements. If your agency is G-Invoicing ready, we will move existing Inter-agency agreements, or IAAs, 7600As and 7600Bs into G-Invoicing at a natural stopping point — like exercising an option or modifying funding — by creating a new GT&C and matching IAA in ASSIST. Options exercised beforehand keep settling through IPAC until the cutoff. If you’re not ready, GSA will accept agreements outside the system; just work with your FAS point of contact.
Working within G-Invoicing. Once G-Invoicing is in place, you won’t need separate PDF forms — the system digitizes the entire 7600A/B process.
A few things to know:
- You’ll make some selections every time. Because G-Invoicing serves the whole government, FAS-specific fields (like the Assisted Acquisition Indicator, always “Yes,” and Advance Payments, always “No”) can’t be set as defaults.
- Your GT&C number is assigned automatically using the standard numbering schema.
- Plan for a long agreement period. We recommend 20 years to cover pre-award, post-award, and closeout. You can negotiate this per project.
- Approvals happen concurrently but in order. Both agencies approve at the same time, but each partner’s initial approver signs before the final approver. If someone shares a draft with you, complete the fields and select Submit for Approval to begin.
- Track changes at a high level with the History button (created, submitted, approved dates). It isn’t all-inclusive.
- Contractors can have limited access — the GT&C create role only.
Creating and submitting an order
Follow these steps to build and submit an order. Watch the notes to avoid an automatic rejection.
- Confirm your codes are registered. Both the Funding Office Code or FOC, and Activity Address Code, or AAC — each a 6-digit identifier — must be active in ASSIST, or your order will be rejected. For a first order or a new code, ask your GSA point of contact to confirm or register it.
- Set the Assisted Acquisition Indicator to Yes. Required for all AAS orders.
- Enter the Period of Performance. Your Order POP must align with or fully cover the Award’s Base and Option Year POPs. Put contract line item POP dates in the Bona Fide Need field (or Item Description if they don’t fit). Don’t use the comments field — it can be edited after approval.
| POP reference field | Aligning with contract period of performance | Encompassing the contract period of performance |
|---|
| G-Invoicing Order POP | Apr 1, 2026 to Mar 31, 2027 | Mar 15, 2026 to Mar 31, 2030 |
| Contract/Award POP | Apr 1, 2026 to Mar 31, 2027 | Apr 1, 2026 to Mar 31, 2027 |
| Bona Fide Need field | POP not required | Apr 1, 2026 to Mar 31, 2027 |
- Set up your line items. Use the correct Product Service Code (default R707 for AAS). For mixed severability, ask the client for separate funding lines — each line carries its own severability.
- Enter unit cost and quantity. Set Unit Cost to $1.00 on every schedule (no exceptions), and use Quantity to drive the total dollar amount.
- Add Bona Fide Need and fee info. Enter all details in G-Invoicing — no separate 7600B needed. State your fee clearly (examples include GSA Fee 3% or GSA Flat fee $30,000.00) in the Bona Fide Need field (150 characters); continue in Item Description (240 characters) if needed.
- List your contract’s PIID in the Bona Fide Need, Item Description, or Schedule PIID field.
- Confirm the statutory authority. Set Fund Type Code to Revolving Fund, Title to Acquisition Services Fund, and Citation to 40 USC 321.
- Add sub-allocation for DOD “097” funds. Enter the 4-digit Sub-Allocation for any TAS with a “097” AID.
- Review and submit. Check your entries against the requirements above. For contract-specific questions, contact your FAS point of contact.
Not currently supported: SAF funding - contact Treasury at igt@fiscal.treasury.gov and cancelled schedules — leave active and set Quantity to $0.00.
Troubleshooting automatic rejections
If our system rejects your order, use this table to fix it.
| Rejection message | How to fix it |
|---|
| Unit Price must be $1.00. | Set Unit Price to $1.00 on all schedules; use quantity to drive the total. |
| BETC Error | Update the BETC on each schedule to a valid Treasury code. |
| Item Code Error | Use a valid PSC (see the Acquisition.gov table). If unsure, contact your FAS project manager. |
| Funding Office Code Error | FOC is unregistered or blank. Contact your FAS point of contact; use SAM.gov “Government Organization” search to look up entities. |
| Activity Address Code Error | AAC is unregistered or blank. Contact your FAS Project Manager. |
| Assisted Acquisition Flag must be Yes. | Set the Assisted Acquisitions Indicator to Yes. |
| UEI field must be 12 characters. | UEI is optional—enter exactly 12 characters or leave blank. |
| Cancelled schedules not supported. | Leave the schedule active and set quantity to $0.00. |
| Modification below obligated amount. | Contact the FAS project manager to coordinate reducing funds. |
| Statutory Authority must be Revolving Fund. | Set Fund Type Code: Revolving Fund; Title: Acquisition Services Fund; Citation: 40 USC 321. |
| “097” funds need a Sub-Allocation. | Enter the 4-digit Sub-Allocation for any TAS with a “097” AID. |
| “Ship to” State/Country invalid. | Shipping info is optional; if used, enter valid codes. |
Appendix: Data requirements for ASSIST
GT&C data structure - partner information
| Data block | GT&C data field | Description |
|---|
| 02 | GT&C data field | Descriptive name for easy identification. |
| 04 | Agreement Start/End Date | The GT&C’s POP. All orders and transactions are bound by these dates. |
| 01 | Requesting Agency | The agency group that is requesting the GT&C. Lead AAC manages it; subordinate members can administer orders. |
| 01 | Servicing Agency | The agency group servicing the GT&C. Lead AAC manages it; subordinate members can administer orders. |
Header and 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 | Defaults to 30; negotiable |
| 06 | Agreement Type | Multiple (for AAS) |
| 07 | Advance Payment Indicator | No |
| 08 | Assisted Acquisition Indicator | Yes |
| 09 | Enforce Total Remaining Amount | Defaults to No; can be Yes |
| 09 | Total Direct Cost and Overhead Fees | Estimated flowthrough cost/fee |
| 25 | Preparer Name, Phone, Email | Auto-populated |
Agreement information — servicing agency
| Data block | GT&C data field | Description |
|---|
| 10 | Explanation of Overhead Fees | How fees are calculated. See Appendix 1: 7600A.10 |
| 13 | Roles | Servicing Agency responsibilities. See Appendix 1: 7600A.13 |
| 14 | Restrictions | Unique/mission-specific restrictions (one field for both agencies). See Appendix 1: 7600A.14 |
| 18 | Assisted Acquisitions | Servicing Agency provisions. See Appendix 1: 7600A.18 |
| 20 | Clauses | Not applicable |
Agreement information — requesting agency
| Data block | GT&C data field | Description |
|---|
| 11 | Scope | High-level scope for all related orders. See Appendix 1: 7600A.11 |
| 12 | Requesting Agency Roles | Requesting Agency responsibilities. See Appendix 1: 7600A.12 |
| 14 | Restrictions | Unique/mission-specific restrictions. See Appendix 1: 7600A.14 |
| 17 | Assisted Acquisitions | Not applicable |
| 19 | Clauses | Additional Requesting Agency provisions, if any |
Approvals. The Requesting Agency completes its data entry and reviews all sections before submitting. Approvals are sequential and open to both agencies: the Initial Approver signs first, then the Final Approver. The GT&C is then open and you can create an order.
Order data structure
Partner information
| Data block | GT&C data field | Description |
|---|
| 04 | Assisted Acquisitions Indicator | Always Yes for AAS |
| N/A | In-Flight Order Indicator | Always No |
| 05 | POP Start/End Date | Must fall within the GT&C agreement dates |
| 08 | Group Name & Description | Organization entering the agreement or order |
| 14 | Funding Office Code | Paying office that settles the charge (BOAC1) |
| 15 | Funding Agency Code | Agency providing the requirement and funds |
Authority
| Block | Field | Description |
|---|
| 17 | Statutory Authority Fund Type Code | Revolving Fund, or RF |
| 18 | Statutory Authority Fund Type Title | Acquisition Services Fund, or ASF |
| 19 | Statutory Authority Fund Type Citation | 40 USC 321 |
Delivery and contact
| Data block | GT&C data field | Description |
|---|
| 28 | FOB Point | Source/Origin |
| 40 | Point of Contact | Requesting agency name, email, and phone |
Line
| Data block | GT&C data field | Description |
|---|
| 46 | Item Code (PSC) | Default R707 for AAS |
| 47 | Item Description | PSC description (R707 = “Support-Management: Contract/Procurement/Acquisition Support”). Add funding realignment language or Award PIID here. |
| 48 | UOM | Default DO – U.S. Dollars |
| 59 | Type of Service Requirements | Severable / Non-severable / N/A (supply) |
Schedule
| Data block | GT&C data field | Description |
|---|
| 63 | Unit Cost | Always $1.00 |
| 66 | Quantity | Total dollar amount for the schedule |
| 72 | Treasury Account Symbol (TAS) | Appropriation or fund symbol |
| 73 | Agency BETC | Select a BETC that matches the selected TAS |
| 74 | Object Class Code | Records transactions by the nature of services, when obligations first incur |
| 76 | Bona Fide Need | Brief purpose of the schedule. Must align with the Line Item POP. State the fee structure and Award PIID here. |
| 81 | Activity Address Code (AAC) | Ordering office providing the funding (BOAC2) |
| 88 | Sub-Allocation | Required for agency code 97 (DoD) only |