Click here to skip navigation

Detailed. Perceptive. Always Vigilant.

Submitting Financial Information (TAS)

Providing Valid Financial Codes and Agency Identifiers

NBIB does not determine billing information invoiced to customer agencies. Instead, customer agencies provide all billing information invoiced during the initial investigative submission to NBIB. Therefore, it is the requesting customer agencies responsibility to ensure that accurate information is initially provided. Specifically, customer agencies are required to ensure accurate Submitting Office Number (SON), Security Office Identifier (SOI), Agency Location Code (ALC), Treasury Account Symbol (TAS), and any other internally required billing information are provided.

Be aware that once an SON/SOI/ALC combination is billed for an investigative request, these codes and any associated case billing details cannot be changed by NBIB. They will continue to be billed throughout the life of the investigation, which may cross multiple invoicing cycles. Therefore, it is critically important that these codes are properly determined prior to billing, internally validated with appropriate financial officials, and accurately included within each investigative submission.

Concerns or problems arising from inaccurately submitted billing details will not be grounds for continued invoice chargebacks. The NBIB invoicing process provides sufficient controls and details for the impacted agency to reach out to the requesting customer agency contact(s) and resolve the issue. Any associated billing corrections for inaccurately provided ALC details must be handled between the losing and gaining entities without the involvement of NBIB.

Treasure Account Symbol (TAS)

All customers that NBIB initiates an IPAC transaction for payment are required to populate the Treasury Account Symbol (TAS) field within e-QIP, which identifies the submitting agencies fund account that will be used to pay for the requested background investigation. 

It is critically important that the TAS fields are accurately populated because they identify the fund account that will be used to pay for the investigation. If you do not know your agency's TAS code you will need to consult with your local finance or budget office.

If upon obtaining your TAS you experience TAS error messages within e-QIP, please contact a member of the NBIB Billing Oversight Team:

Email:  BillingOversightTeam@nbib.gov
Phone:  (724) 794-5612 ext. 4490

The component TAS is a financial code, assigned by the Department of the Treasury, comprised of many separate, component pieces/sub-fields. However, not all fields are used with certain fund accounts and thus are not required to be populated (highlighted in grey in the examples listed below).

The image below shows the TAS block on the AUB for the SF-86.

SPATAAIDBPOAEPOAAMainSubFormat
# # # 2 0 1 8 2 0 1 8 # # # # # # # C

The examples below are to help illustrate the TAS sub-fields utilized by most NBIB customers for three types of fund accounts.

These examples are for illustrative purposes only and are not real TAS accounts.

  1. TAS fund type 1: "One-Year" Expiring Fund Account (will change annually)
    SPATAAIDBPOAEPOAAMainSubFormat
    # # # 2 0 1 8 2 0 1 8 # # # # # # # C

    (This example is for illustration only. This is not a real TAS code.)

  2. TAS fund type 2: "Multi-year" Fund Account (may change annually)
    SPATAAIDBPOAEPOAAMainSubFormat
    # # # 2 0 1 8 2 0 1 9 # # # # # # # C

    (This example is for illustration only. This is not a real TAS code.)

  3. TAS fund type 3: "No-year" or "Revolving" Fund Account (likely will not change annually)
    SPATAAIDBPOAEPOAAMainSubFormat
    # # # X # # # # # # # C

    (This example is for illustration only. This is not a real TAS code.)

Component TAS Sub-Fields:
SP – Sub-level Prefix Code
ATA – Allocation Transfer Agency Identifier
AID – Agency Identifier
BPOA – Beginning Period of Availability
EPOA – Ending Period of Availability
A – Availability Type Code
Main – Main Account Code
Sub – Sub Account Code

Below are additional helpful tips for entering your TAS:

  • Not all of the 8 Component TAS fields and 24 character spaces displayed in e-QIP will be used. The SP and ATA fields are only used in rare circumstances where fund transfer authority exists. In nearly all applications for NBIB serviced background investigations, the SP and ATA fields should be left blank (do not populate with any data unless directed to do so by your local finance office).
  • As you can see, in nearly all applications only 4 or 5 of the e-QIP Component TAS fields should be used/populated with data by the user (Either AID/BPOA/EPOA/MAIN/SUB or AID/A/MAIN/SUB). If the TAS account you are using is associated with expiring funds then both of the BPOA and EPOA fields will need to be populated and the Availability Type field (A) should be left blank. If not, the A field will be populated with an alpha character (likely an X or an F) and the BPOA and EPOA fields should be left blank.
  • Each component TAS sub-field (if used) contains a defined and required number of characters (e.g. SP-2; ATA-3; AID-3; BPOA-4; EPOA-4, A-1; Main-4; Sub-3). The AID field will likely include a leading zero.
  • If the TAS code you are attempting to use is less than 11 characters in length then it is not in the component format currently required by Treasury for processing intergovernmental transactions. Most common lengths are 18 and 11 total characters. 
  • The main and sub field should always be populated with data. It is very common for the sub field to be populated with all zeroes. The sub field is the only field that could potentially be populated with all zeroes.
  • The "C" displayed at the end of the TAS code within e-QIP is required by Treasury and cannot be modified.

Please refer to the Component TAS Helpful Tips and e-QIP Format Conversions document for additional information and example TAS formats and component field definitions.

Back to Top

Submitting Office Number (SON)

NBIB assigns a unique four-character alphanumeric code, known as the Submitting Office Number (SON), to each office that requests investigations from NBIB. The SON identifies the office that initiates the investigation and is recorded in the appropriate Agency Use Block (AUB) of the standard form. 

To update an existing SON or to obtain a new SON from OPM, please complete a PIPS 12 form.

Back to Top

Security Office Identifier (SOI)

Each security office is issued a unique alphanumeric four-character identifier from NBIB, the Security Office Identifier (SOI), which is used to identify the appropriate agency official who will receive case results, data, or other information from NBIB.

To update an existing SOI or to obtain a new SOI from NBIB, please complete a PIPS 11 form.

Back to Top

Intra-Governmental Payment and Collection (IPAC)

The Intra-Governmental Payment and Collection (IPAC) field collects the Agency Location Code (ALC), which is assigned to your agency by the U.S. Department of Treasury. The IPAC system provides a standardized interagency fund transfer mechanism for Federal Program Agencies (FPAs).  IPAC facilitates the intragovernmental transfer of funds, with descriptive data from one FPA to another. The code is required for all investigative requests. The IPAC is also commonly referred to as the ALC.  

Back to Top

Accounting Data and/or Agency Case Number

The accounting data field on the Agency Use Block (AUB) is an optional field (25 character limit) that can be populated on the standard form. This block can be used by the requesting agency to note any information that the agency needs for its own internal processes, such as an internal case number or any other specific agency identifier. This field will appear on your monthly invoice and can be useful for internal invoice reconciliation.

Back to Top