(USF) Submitting Transactions Between Agencies Using the IPAC System

The Intra-governmental Payment and Collection System (IPAC) was designed by the U.S. Department of Treasury as an automated, standardized, interagency funds expenditure transfer mechanism for Federal Program Agencies (FPAs). It facilitates intra-governmental federal e-commerce by transferring funds, with related descriptive data, from one FPA to another on a real-time basis. IPAC supports three types of transactions:

  • Collection - A transaction that an agency initiates to transfer money, in the form of an online transfer, to FPAs within the IPAC System

  • Payment - A transaction that an agency initiates to pull money, in the form of an online transfer, from FPAs within the IPAC System.

  • Adjustment - A transaction that an agency initiates to adjust an erroneous or incorrect payment or collection.

PeopleSoft Receivables enables users both to create IPAC transactions for uploading to the IPAC system ("outbound" IPAC transactions) and to receive information about payments initiated by other agencies through the IPAC system for entry into PeopleSoft Receivables ("inbound" IPAC transactions).

The following diagram shows the flow of outbound and inbound IPAC information in Receivables.

This diagram shows outbound and inbound IPAC processing in PeopleSoft Receivables. It shows the flow for creating IPAC transactions for uploading to the IPAC system ("outbound" IPAC transactions) and for receiving information about payments initiated by other agencies through the IPAC system for entry into PeopleSoft Receivables ("inbound" IPAC transactions).

Outbound and Inbound IPAC Processing in Receivables

Outbound IPAC Processing

The flow of outbound IPAC information in Receivables is as follows: Your agency creates an item, runs ARUPDATE, reviews the IPAC information, and creates an IPAC file, which is sent to the Treasury Department and updated in the IPAC system.

If an IPAC transaction has been processed, the item and the group of items it belongs to cannot be unposted. If IPAC items are bundled and posted, but the file is not sent immediately to the Treasury Department, the bundled items can be unposted only in the time frame before sending to the Treasury Department. A suggestion would be to group all IPAC items into one group to be processed by IPAC on the same date. If the items were posted and a period of time elapsed before sending to IPAC, in this window, the group could be unposted.

To create IPAC Adjustments for AR credit items to refund money previously collected via IPAC, see Processing Outbound IPAC Transactions in Receivables.

Inbound IPAC Processing

This section discusses the high-level business process flow for inbound IPAC. The inbound IPAC process in PeopleSoft Receivables is similar to the flow for inbound IPAC in PeopleSoft Payables.

An agency manually creates and downloads the IPAC .csv file from the Treasury’s IPAC system. The data retrieved in the IPAC download contains all payment, collection, and adjustment transactions received by and sent by the requested ALC for a given time period. For PeopleSoft Inbound IPAC, the system needs to process transactions received by an agency’s ALC only, unless your IPAC transactions are entered manually into the IPAC system.

Then the agency runs the Load Inbound IPAC process to load the received IPAC payment, collection, and adjustment transactions to the IPAC staging tables. During this process IPAC records are sorted into AP or AR. In addition, IPAC transactions are cross-referenced to previously entered PeopleSoft AP vouchers or AR items to facilitate transaction processing in the next step.

In the next step users review and correct the IPAC transactions in the IPAC Workbench. Payables users are able to view only payments and payment adjustments on the AP IPAC Workbench, whereas Receivables users are able to view only collections and collection adjustments on the Receivables IPAC Workbench. Managers can view collections, payments, and adjustments on the Manager Workbench, and have permission to correct errors that Payables and Receivables users cannot correct. IPAC transactions that cannot be sorted into AP or AR appear on the IPAC Manager Workbench. The manager must determine how to classify them, and update them manually as AP or AR, using the status.

The final step in the workflow is to create AP and AR transactions from the IPAC Workbench. Payables users can create payment vouchers or adjustments, depending on the type of IPAC transaction, whereas Receivables users can create deposits or credit direct journals, also depending on the type of IPAC transaction.

For more information about inbound IPAC in Receivables, see Processing Inbound IPAC Transactions in Receivables.