Frequently Asked Questions
Master Administrator Questions
The Master Administrator is the individual(s) identified formally by the CFO or Deputy CFO as trusted to authorize requests for other individual(s) at their Agency to access the IPAC system on their behalf. The Master Administrator is responsible for approving the Agency Administrator role. The Master Administrator can also approve other user requests if there is no Agency Administrator in place or available. The Master Administrator is mainly responsible for approving the Agency Administrator role and for performing review of access for recertification purposes. When reviewing the request, the Master Administrator should ensure that the least privileged access was submitted, and all fields are complete and correct. For more information, please see the IPAC Enrollment Guide or the Treasury Financial Manual Volume 1, Chapter 4000.
The Agency Administrator is the individual(s) identified formally by the Master Administrator as trusted to authorize requests for other individual(s) at their Agency to access the IPAC system on their behalf. The Agency Administrator will be responsible for approving users´ requests; they will also have the capability to run several reports. For more information, please see the IPAC Enrollment Guide or the Treasury Financial Manual Volume 1, Chapter 4000.
No, the Master Administrator cannot be a current AA or IPAC User.
Yes, the Master Administrator must be an authorizing official.
Please visit Training and Events to check for upcoming training. That page will have links to our main Training Opportunities page that lists all of the training the Bureau offers.
Currently, Form 7600B allows for input of the Component TAS, and/or a current ‘String TAS’ format.
As agencies onboard to G-Invoicing, they will need to report the Component TAS form only.
Some users have experienced issues downloading IPAC reports (PDF files) to their PCs after Windows updates. If experiencing any issues, users need to ensure their Internet Explorer security settings are correct.
- From Internet Explorer, select Tools, Click on Options/Security Tab/Custom Level button.
- Change the Security Level from Medium to Medium-Low; click on Enable and then Ok.
- Change the "Allow Web Pages to use Restricted Protocols for Active Content" from Prompt to Enable. Click on Apply and then Ok.
- Click Ok to close out the Options box.
IPAC will only provide Agencies with access to IPAC and TRACS data for a period of the last 18 months. If you need IPAC or TRACS data older than 18 months, contact the Treasury Support Center (TSC.) You can reach the TSC by calling 1-877-440-9476 - Option 2, or by sending inquiries electronically to IPAC@stls.frb.org. Requests for historical data may take up to 48 hours to process.
IPAC supports the use of Microsoft Internet Explorer versions 8.0, 9.0 and 10.0. IPAC will run on Internet Explorer Version 11.0, but only in compatibility mode. You can set your browser to compatibility mode using the following steps:
- Select Internet Explorer 'Tools' menu option
- Select 'Compatibility View Settings'
- In the 'Add this website' box, type "treas.gov"
- Click the Add button
- Click the Close button
Agency Location Code (ALC)
Sender Treasury Account Symbol (TAS)
Sender Business Event Type Code (BETC)
Receiver Treasury Account Symbol (TAS)
Receiver Business Event Type Code (BETC)
Quantity x Unit Price = Detail Amount
SGL Account Number
No. The transaction initiator must provide both a valid Sender TAS/BETC and Receiver TAS/BETC on the IPAC transaction. If the TAS/BETC that the originator uses for the receiver is incorrect, then the transaction recipient must access the CARS CTA Module to 'reclassify' the funds into a different TAS/BETC.
Correct. If a field is required, something must be in the field in order for the transaction to be processed. If the field is left blank, the user will receive an error message 'Required field is missing'. Mandatory = required.
If you are a CARS TAS/BETC Reporter, the transaction details will be automatically validated with the Shared Accounting Module (SAM) and posted to your agency´s CARS Account Statements with the TAS/BETC entered on the IPAC. You may reclassify the transaction within the CARS CTA module if necessary, but no additional month-end reporting is required.
If you have not yet transitioned to a CARS TAS/BETC Reporter, your side of each IPAC transaction must be reported to Treasury on the SF 224 or SF 1219/1220 month-end reports. If your agency is not already a Full CARS TAS/BETC Reporter, you should begin working closely with the Fiscal Service Customer Relationship team to make the transition. For more information, please refer to the this CARS link.
The IPAC Bulk File Upload will not accept positive (+) and negative (-) signs, or any other alphanumeric characters. All amounts in the Bulk File must be strictly numeric and greater than zero. If a negative sign (-) or another alphanumeric character is entered, you'll receive the following error messages: "Invalid format of amount" and "Header amount is not equal to sum of Detail amount."
Bulk Files need to be positive amounts, while any transactions with negative amounts should be entered manually.
See more information on IPAC Bulk File Formats.
For buy/sell transactions only, no IPAC(s) can be processed during the last 3 business days of the month during quarter-end. Agencies have 90 days after the billing date to enter adjustments to payments or collections.
Agencies have the option to further restrict buy/sell transactions from posting to their ALC at the end of the month or quarter by submitting a Billable Status request in IPAC.
Often times near the end of the Fiscal Year, users will originate IPACs with TASs containing an EPOA (Ending Period of Availability) five years old, before those TASs are officially closed. If a Chargeback is necessary for these IPAC transactions, IPAC will not allow the chargeback to proceed to the original TAS after it has been subsequently closed. If you try to process an IPAC chargeback to a TAS that has been closed, you will receive the following error message: "A corresponding adjustment TAS/BETC pair does not exist."
The IPAC system functionality will only allow chargebacks to the original TASs which were selected. There is no way these can be edited by you, even if the TASs have been closed or subsequently suspended.
The solution is for you to create a new IPAC transaction and include the pertinent transaction details in the "Description" and "Misc. Info" fields. The COLLAJ and DISBAJ can still be selected on the new IPAC transaction to signify an adjustment is being made.
You should contact your trading partner to see what TAS you should select in place of the closed TAS. You can also refer to the SAM Master TAS/BETC file, which provides an updated list of all active TASs every day, located at: https://www.sam.fms.treas.gov/sampublic/tasbetc.htm.
If, at the end of a fiscal year, a Non-CARS Reporter or Parallel CARS Reporter does not have sufficient time to determine the amount of an adjustment for its regular monthly reporting, the agency should report the erroneous charge to its regular appropriation or fund symbol. A CARS Reporter can reclassify the transaction within the CTA module, but if the agency chooses to correct the erroneous charge, it must coordinate the correction with the charging entity. Once the agency determines the correct amount of the erroneous transaction, it adjusts the transaction through IPAC.
You can e-mail questions related to RITS and/or TRACS to IPAC@stls.frb.org.
Questions regarding Health Benefit Codes should be e-mailed to FFSAMS@opm.gov.
What is the TAS data comprised of? Is it the accounting data (Line of Accounting information)?
The TAS is the Treasury Account Symbol. It is not your long line of accounting. The TAS looks like....
- SUBSP ATA AID BPOA EPOA A MAIN SUB
- SP = Sub level prefix
- ATA = Agency Transfer Allocation
- AID = Agency Identifier
- BPOA = Beginning period of availability (Fiscal Years)
- EPOA = Ending period of availability (Fiscal Year)
- A = Account type (A, X, or F)
- MAIN = Main account code
- SUB = Sub account code
Table may scroll on smaller screens
|Field Name (abbreviation)||Size||Format||Description||Format/Validations|
|Sub-level Prefix (SP)||2||CC||The Sub-level Prefix (if populated) is a programmatic breakdown of the account for Treasury publication purposes.||
|Allocation Transfer Agency Identifier (ATA)||3||CCC||The Agency Identifier of the agency receiving funds through an allocation transfer.||
|Agency Identifier (AID)||3||CCC||Agency Identifier of account owner. Used in conjunction with the main account code, the Agency Identifier represents the department, agency or establishment of the U.S. Government that is responsible for the TAS.||
|Beginning Period of Availability (BPOA)||4||CCCC||In annual and multi-year funds, identifies the first year of availability under law that an appropriation account may incur new obligations.||
|Ending Period of Availability (EPOA)||4||CCCC||In annual and multi-year funds, identifies the last year of funds availability under law that an appropriation account may incur new obligations.||
|Availability Type Code (A)||1||C||Identifies no-year accounts "X", clearing/suspense accounts "F", and Treasury's central summary general ledger accounts "A".||
|Main Account Code (MAIN)||4||CCCC||Identifies the type and purpose of the fund.||
|Sub-Account Code (SUB)||3||CCC||Identifies an available receipt or other Treasury-defined subdivision of the main account.||
Last modified 11/15/18