DFAS Transportation Global Edit Tables TGET

The Transportation Global Edit Table (TGET) is the Department of Defense's authoritative repository of transportation Lines of Accounting (LOAs) and their associated Transportation Account Codes (TACs) for all Military Services and Defense Agencies. The Defense Finance and Accounting Service (DFAS) maintains the software and database supporting TGET within its Business Enterprise Information Services (BEIS) environment, while each Service or Agency is responsible for keeping its own LOAs and TACs current in the table.

What it is

A Transportation Account Code (TAC) is a short alphanumeric code that stands in for a full Line of Accounting (LOA), identifying the DoD Component and appropriation chargeable for a shipment moved through the Defense Transportation System. Because a full LOA can run 50–65 characters, using LOAs directly on bills of lading produced high error rates and payment delays; TACs were adopted to reduce those errors. A TAC is valid for use only if it is currently loaded into TGET, which functions as the single authoritative, live listing of TACs and LOAs — letting carriers, shippers, and finance staff verify current applicability, validity dates, and descriptions before a shipment moves. TAC/LOA data recorded in TGET is reviewed against the Third Party Payment System (TPPS) so transportation bills are charged to the correct account.

Who operates it

DFAS, through its BEIS program, maintains the TGET software and database. TGET account administration and technical support are handled by the BEIS Operations Support Office. TAC assignment and structure guidance for Service-specific codes comes from the Defense Transportation Regulation (DTR 4500.9-R), Part II, Appendix V, and each Service maintains its own TAC coordinator to help units request or update codes.

Access

TGET is not a public lookup tool. Access requires a completed DD Form 2875 (System Authorization Access Request) and a Rules of Behavior form, submitted to the BEIS Operations Support Office, before a username and password are issued. The application entry point is the BEIS front page, which presents a PKI/CAC login; from there, authorized users select the TGET Web application. TGET accounts that go unused for an extended period are deactivated and must be reinstated through BEIS Operations Support. The directory's prior "public" access designation was inaccurate — TGET requires a sponsored, form-based account request, consistent with a SAAR-gated tool.

How logisticians use it

Transportation, finance, and logistics personnel use TGET to confirm that a TAC is currently funded and valid before citing it on a bill of lading or transportation document, to look up the LOA a given TAC maps to, and to resolve billing discrepancies when a Transportation Service Provider's invoice does not match an expected account. Because TPPS relies on accurate TAC/LOA data from TGET, keeping Service-level entries current in TGET is what keeps downstream transportation bills charged correctly.

Related systems

TGET is referenced by the Third Party Payment System (TPPS) and is governed by TAC procedures in the Defense Transportation Regulation, Part II, Appendix V. It sits alongside Service-specific TAC guidance documents (e.g., annual Marine Corps and Army TAC guidance addenda) and complements broader Defense Transportation System documentation and shipment paperwork references.