ASAP Important Notices

Important Notice To Federal Agencies Using ASAP Regarding Changes To End Of Month Reporting - Update

The planned interface between ASAP and the FMS Payments, Claims, and Reconciliation (PACER) application for end of day reporting, originally scheduled for February 1, 2012 has been postponed until June 1, 2012.

Agencies should continue to report their ASAP transactions on the SF 224 in the same manner as they do today between February and June.

Batch agencies will continue receiving the SF 5515/SF215 end of day reports until June 1. After June 1, you must use the new ASAP Schedule Number reports downloaded from ASAP.gov. If you currently rely on the SF 5515/SF215 files in your batch for your back end processing, you will need to make accommodations to download the Schedule Number reports from ASAP.gov and upload them into your back end system until the new XML schemas are implemented.

Below is the original message sent on December 16, 2011. We are also resending the new ASAP Accounting Guide, as well as a sample the new Schedule Number Reports in a .csv format.

If your agency has any questions, please contact Carol Cole, Project Manager for ASAP Operations at 202.874.6542 or Carol Cole or Faye Allen, ASAP Operations Team, at 202.874.7113 or Faye Allen.

December 16, 2011 Original Message: "Important Notice To Federal Agencies Using ASAP Regarding Changes To End Of Month Reporting To FMS

Beginning February 1, 2012, the U. S. Department of the Treasury, Financial Management Service will change the end of day reporting process for the Automated Standard Application for Payments (ASAP).

Currently, ASAP reports SF 5515 Debit Vouchers and SF 215 Deposit Tickets to the disbursing agency’s ALC through the CA$HLINK II application. As a result of the planned decommissioning of CA$HLINK II, ASAP is required to begin interfacing with the FMS Payments, Claims, and Reconciliation (PACER) application for end of day reporting. The move to PACER will require a change in the way agencies report ASAP transactions on their monthly SF 224 Statement of Transactions.

Beginning February 1, ASAP will send daily payment transaction detail and summary accounting data to the PACER application instead of CA$HLINK II. With the PACER interface, ASAP will no longer report or provide SF 5515 and SF 215 reports. (These reports will remain available in ASAP.gov for historical inquires.) Instead, ASAP provide two new reports in ASAP.gov – The Schedule Number Summary Report and the Schedule Number Payment Transaction Report. These reports will be available in ASAP.gov beginning February 2.

With the change in accounting reporting, agencies will need to change how they report ASAP transactions on the end of month SF 224 Statement of Transactions beginning in March 2012. ASAP payments are currently reported on the SF 224 as negative collections. Beginning in March 2012, ASAP payments should be reported as Treasury Disbursed payments on the SF 224, in the same manner as payments processed through SPS and PAM. Details on how to use the new Schedule Number reports for end of month reporting are included in the attached “Accounting for ASAP Transactions” guide.

Additional Information for Batch Agencies Only - Because ASAP is converting all existing batch reports to an XML format in November 2012, the new Schedule Number reports will not be available in the current batch format. The last SF 5515 and SF 215 end of day batch files will be sent on February 1 for January 31 transactions. Beginning February 2, batch interface agencies will be required to pull the Schedule Number reports from ASAP.gov until the new batch XML reports are implemented in November 2012. The change will require your agency to modify any automated program

• Agency Accounting Procedures for ASAP
  (360 KB)
• Schedule Number Payment Transaction Report with Account Detail
  (130 KB)
• Scheduke Number Summary Report Sample
  (2 KB)

Important Notice to All Users

The Automated Standard Application for Payments (ASAP) will close early at 9:59 PM (EST) on Friday, October 28, 2011. All payments for next business day settlement must be requested prior to that time. Federal agencies that submit batch account and authorization files will not be impacted. Please pass this information along to all ASAP users. As in the past, this one-time closure do not alter the standard closing time of 11:59 PM (EST) for ASAP on normal business days. If you have any questions, please contact your servicing Regional Financial Center.

Important Notice: ASAP XML Schemas Now Available

ASAP batch files for Accounts, Authorizations, and End of Day Reports are being converted to an Extensible Markup Language (XML) format. The XML schemas are now available at the following URL: http://fms.treas.gov/eda/xml

The ASAP XML schemas can be found under "Business Messages" on the left.

• To access the Account and Authorization schemas, click "Account Services Transmission Message v 1.0"
• To access the End of Day Report schemas, click "Account Services Report Message v 1.0"

The new formats, which include the TAS/BETC fields for Accounts and End of Day Reports, will be implemented in November 2012; however, providing TAS/BETCs will remain optional until October 1, 2014. Note that ASAP will continue using Connect:Direct to transfer batch files.

Agencies will have the opportunity to test the new XML files between June and September 2012. FMS will work with your agency in developing the testing schedule.

If you have technical questions about the XML schemas and would like to speak with the FRB Richmond ASAP Developers, please contact Carol Cole at (202) 874-6542 or Faye Allen at (202) 874-7113 and they will arrange a call with the Developers.

For questions about the GWA TAS/BETC formats, contact Mike Norman of the FMS GWA/CARS Agency Liaison Team at (202) 874-8788.

Important Notice to All Users

The Automated Standard Application for Payments (ASAP) will close early at 9:59 PM (EST) on Friday, March 11, 2011. All payments for the next business day settlement must be requested prior to that time. Federal agencies that submit batch account and authorization files will not be impacted. Please pass this information along to all ASAP users. As in the past, these one-time closures do not alter the standard closing time of 11:59 PM (EST) for ASAP on normal business days. If you have any questions, please contact your servicing Regional Financial Center.

Important Notice to All Users

The Automated Standard Application for Payments (ASAP) will close early at 9:59 PM (EST) on Friday, November 5, 2010. All payments for next business day settlement must be requested prior to that time. Federal agencies that submit batch account and authorization files will not be impacted. Please pass this information along to all ASAP users.

As in the past, these one-time closures do not alter the standard closing time of 11:59 PM (EST) for ASAP on normal business days.

If you have any questions, please contact your servicing Regional Financial Center.

Effective July 1, 2010, Important Message for Federal Agencies and Recipient Organizations Serviced by the San Francisco RFC

Federal Agency

ASAP support for federal agencies previously serviced by the San Francisco Financial Center has been reassigned. The new assignments are:

Kansas City Regional Financial Center – (816) 414-2100
Food & Nutrition Service, San Francisco
Homeland Security, ICE, Dallas, TX
Energy - Albuquerque, NM
Energy - Nevada
Energy - Golden Field, CO
Energy - Idaho Falls, ID
Energy - Richland, WAv Bonneville Power Administration, Oregon
Denali Commission, Alaska

Philadelphia Regional Financial Center – (215) 516-8021
Interior – Bureau of Reclamation, Denver, CO
Interior – Bureau of Land Management, Denver, CO
Interior – Office of Surface Mining – Denver, CO
Office of personnel Management - DC
Social Security Administration, San Francisco, CA
TRICARE Management Activity - CO

ASAP support for Recipient Organizations previously serviced by San Francisco Financial Center has been reassigned. Recipient Organization support is assigned by state and the new assignments are as follows:

Kansas City Financial Center
Alaska
Arizona
California
Nevada
Oregon
Washington

Philadelphia Financial Center
Colorado
Idaho
Montana
New Mexico
Utah
Wyoming

Recipient Organization

ASAP support for Recipient Organizations previously serviced by San Francisco Financial Center has been reassigned. Recipient Organization support is assigned by state and the new assignments are as follows:

Kansas City Financial Center – (816) 414-2100
Alaska
Arizona
California
Nevada
Oregon
Washington

Philadelphia Financial Center – (215) 516-8021
Colorado
Idaho
Montana
New Mexico
Utah
Wyoming

Important Notice to ASAP Certifying Officers Using PKI Certificates

Certifying Officers with access to ASAP are required to use a Public Key Infrastructure (PKI) certificate and iKey token for two-factor authentication and to digitally sign authorizations. ASAP utilizes cryptographic authentication via an Entrust TruePass product. This product deploys a signed applet that facilitates PKI authentication and signing operations from the user’s browser. The certificate used to sign the applet will expire on December 17, 2009.

Certifying officers who currently use a PKI certificate and iKey token to access ASAP will need to upgrade the Entrust TruePass Applet Certificate. Effective December 14, 2009, when logging on to ASAP you will need to accept the certificate by following the instructions in the attached document, “Instructions for the Entrust True Pass Applet Certificate Upgrade.” You may need to contact your IT person or System Administrator to execute the steps outlined in the instructions document. Until this task is completed, you will not be able to access the ASAP application. If you have any questions relating to this notice, contact your servicing Regional Financial Center.

PKI Notification to Users for Applet Expiration December 12, 2009 
(188 KB)