# Presentation: 425550

## Payment Automation Manager (PAM)

**AFC CAB Meeting**
- San Diego, CA
- April 3-4, 2008

## Today’s Objectives

- PAM Project Recap and Milestones
- Production Release Schedule
- PAM File Formats
- PAM Support of GWA
- PAM Process Flow
- Agency’s View of PAM
- PAM vs Legacy
- PAM Support

## PAM Project Recap

- Develop and deploy a standardized application, Payment Automation Manager, employing new technologies
- Replace 30+ applications currently used to process payment requests
*Payments made through the system are done right the first time: on time, every time*

## PAM Milestones

- January 2006 – Development began
- April 2007 – Construction began
- August 2007 – QA/UA testing began
- October 2007 – C&A Kickoff
- December 2007 – Agency testing begins
- March 2008 – First Production Release

## Estimated PAM Production Release and Payment Volume Timeline

**Production Release 1**
**(SSI ACH—April 1 dated payments)**
**March 2008 **
**51.2M Payments Annually**
**Valued at $23.8B**

**Production Release 2**
**(SSI Check & Daily Payments) **
**October 2008**
**38.1M Payments Annually**
**Valued at $18.8B**

**Production Release 3**
**(OPM Payments) **
**30.5M Payments Annually**
**Valued at $50.8B**

**Production Release 4**
**(Daily/Vendor Payments)**
**164M Payments Annually**
**Valued at $722.5B**

**          ****4Q/2007**
***Annualized Volume Conversion**

**1Q/2008**
** ****51.2M**
**  ****5.27%**

**   ****2Q/2008**

**3Q/2008**

**4Q/2008**
** ****89.4 M**
**  ****9.20%**

**1Q/2009**

**2Q/2009**

**3Q/2009**
** ****119.9M**
** ****12.33%**

**4Q/2009              1Q/2010****	****    4Q/2011**
**                            ****283.9M****	****      ****972M**
**                            ****29.20%****	****      ****100%**

**	**
**	****Production Release 2 includes interface with COMBO & TCIS**
**	****Production Release 3 includes interface with TOP, TCS and receiving SPS certifications via XML**
**	****Production Release 4 includes interface with SPS receiving Type B via XML                                                            ****	****         ****	****          ***Note: Agencies sending TAS / BETC data MUST coincide with future SPS Production Release.*
**	****Production Release 5 thru 11 - The remaining releases of PAM will focus attention on implementing the outstanding ****	****Payment Types/File Formats (e.g., VA, tax, etc), as most of the functionality for the system will have been implemented                                                                                                                                                                                      ****	****as part of the first four releases**
**  % Annualized Volume Conversion is based upon 972 Million total check and ACH payments for the period July 2006 through June 2007*

**Final Legacy Application Converted**
**688.5M Payments Annually**
**Valued at $779.1B**

*Revised as of March 17, 2008*

## Production Release 1

- Implementation March 15, 2008 for April 1, 2008 SSI ACH payments
- Kansas City Regional Financial Center will support the payments
- 51.2 Million Payments Annually
- Two interfaces
- PACER & FedACH
- Minimal User Interface (UI) for RFCs
- Will not include holds, offsets, partial payments, TCS, or TCIS

## Future Production Releases

- Release 2
- SSI Check & Daily Payments
- 38.1 Million Payments Annually
- Interface with COMBO & TCIS
- Auto-match with SPS Certification
- Release 3
- OPM Payments
- 30.4 Million Payments Annually
- Includes interface with TOP & TCS

## Future Production Releases

- Release 4
- Daily/Vendor Payments
- 164 Million Payments Annually
- Includes interface with SPS (certifications bearing TAS/BETC information) and IPP
- Includes requirements for all payment types
- Releases 5 – 11
- Transition remaining Legacy payments to PAM
- 688.3 Million Payments Annually
- Approximate two year transition

## PAM Formats and Support of GWA

## PAM Standard Formats for Agencies

- Why a Standard Format
- Consistency in data between types of payments
- Ability to provide GWA reporting without changing 30+ file formats
- GWA reporters must use Standard file format
- Flat files vs. XML format
- PAM payment format is ready for the Release 4.0 January 2010 implementation
- There will be one common record that will accommodate every type of payment

## PAM File Formats

- For those types of payments with unique information necessary to issue the payment, a secondary record that includes that information will be provided
- Within one file, a schedule can only include one type of payment
- Multiple schedules can be received in one file but only for ACH or check within a single file
- Each schedule can have a different type of payment

## PAM File Formats

- PAM format will need a schedule number to be provided in the file for ease in matching to the certifications received
- 100 appropriations records will be allowed for each payment being received
- This meets the GWA Requirement

## PAM Formats: Flat File Structure

- Fixed Length Records
- Structure Expected from Agencies
- File Header
- One per file
- Agency Information
- Schedule Header
- Multiple per file
- Schedule Information
- Schedule Trailer Records
- One for each schedule header
- Provides Control Totals
- File Trailer
- One per file
- File Control information

## PAM Formats: Flat Files cont.

- Between the Schedule Headers and Trailers
- Common Data Record
- Information needed for every type of payment
- Includes both Check and ACH Information
- Addenda Record for ACH Payments
- Stored and passed to FedACH
- No validations performed on the data
- Appropriations Record for TAS/BETC Reporting
- Up to 100 Records per payment request (common record)
- Stored and passed to PACER for GWA reporting
- Payments are not rejected if information does not pass validations
- Errors will be reported to Agency and GWA
- Secondary Records
- Agency Unique Information

**Notes:**
PAM is expecting to only receive data elements that are necessary to make the actual payments and report to accounting systems downstream

For those types of payments with unique information necessary to issue the payment, a secondary record that includes that information will be provided

## PAM Formats: XML

- What is XML
- Extensible Markup Language
- Allows users to define their own elements
- Facilitates the sharing of structured data across systems
- Designed to be relatively human-legible
- Data is “tagged” with a start and end tag
- PAM XML format will follow the bulk file format and will be developed by the PAM Business Requirements Group (BRG) in conjunction with the Software Development Group (SDG)

**Notes:**
PAM XML format will follow the bulk file format and will be developed by the PAM BRG in conjunction with the PAM SDG.

XML format will be defined and PAM should be able to accept in 2010

## SPS
3rd Party 440 formats and DEO upload into SPS
On-line screens will be modified 
Certified amounts at schedule level are official Agency Accounting entries
Validates TAS/BETC with the Shared Accounting Module (SAM)
PAM
PAM will derive TAS/BETC and send to PACER
PAM will not validate, rather just pass them along to GWA
Same Day Payment Schedules will need TAS/BETC
Difference Report
PACER
Processes accounting entries based on TAS/BETC information provided by PAM
Provides schedule/document level TAS/BETC information to GWA
Will calculate accounting entries for aftermath transactions based on Treasury Account Symbol (TAS) / Business Event Type Code (BETC) information provided by PAM

- SPS
- 3rd Party 440 formats and DEO upload into SPS
- On-line screens will be modified
- Certified amounts at schedule level are official Agency Accounting entries
- Validates TAS/BETC with the Shared Accounting Module (SAM)
- PAM
- PAM will derive TAS/BETC and send to PACER
- PAM will not validate, rather just pass them along to GWA
- Same Day Payment Schedules will need TAS/BETC
- Difference Report
- PACER
- Processes accounting entries based on TAS/BETC information provided by PAM
- Provides schedule/document level TAS/BETC information to GWA
- Will calculate accounting entries for aftermath transactions based on Treasury Account Symbol (TAS) / Business Event Type Code (BETC) information provided by PAM

**Notes:**
PACER
Will provide schedule level/document level TAS/BETC information to Café/GWA

## Slide 17

**Notes:**
Do we need to think about a picture for the interfacing application?

## PAM Process Flow &Agencies View

## PAM Process FlowGeneral Process

- PAM Process FlowGeneral Process

- Submitting Agency

- Accept
- Payment
- Requests

- Certify
- Payment
- Requests

- Collect
- Delinquent
- Debt

- Process
- Holds

- Generate
- Payments
- (ACH,
- CHECK,
-  WIRE)

- Generate
- System
- Of Record
- Information
- (PACER
- TCS)

- Group
- Payments

- GWA Reporting

- SPS

## PAM Process Flow

- Changes occurring to the process flow:
- Validation report will replace pre-edit report
- 100% of edits completed by upfront processing
- Process flow will still start with an agency submitting their Payment Request File (PRF) or SPS Certification

## PAM vs Legacy

- Differences between PAM and Legacy:
- All validations will be conducted upfront
- When you certify your payments, they will be processed immediately
- Validation reports from PAM can be expected shortly after the time of receipt from interfacing reports
- Time could vary depending upon internet speed

## PAM Home Page: Gates & Stages

## Agency’s view of PAM

- PAM will provide the status of your PRF via email, fax or Connect:Direct file transmission
- Email will include verification of:
- Type of payment request
- Date and time the request was accepted
- Email will also detail:
- PRF:  files, items and total amount received
- ACH:  items and total amount received
- Received file status will also be provided including:
- Control Number
- Date and Time Validation were performed

**Notes:**
Provide us an e-mail group name that you create and maintain and we will send the notification to your agency’s group

## Email notification for a file containing no invalid records that was successfully validated

## Email notification for a file containing two invalid records that was successfully validated

## Email notification for a rejected PRF

## PAM and SPS

- Information received from PAM notifications will be used for SPS certifications
- This includes:
- Agency Dataset
- Control Number
- Item Count
- Total Payment Amount

## PAM and SPS

- Agency Dataset
- Not necessary for entry to SPS
- It identifies the file for the agency
- Agency will know what is being certified and what schedule number to use

- FRYU5.SSI.SSIMDD.PAUL.INV50

## PAM and SPS

- Control Number
- Will be required for SPS entry
- Relates directly to Control Number on SPS Certification

- C000583

## PAM and SPS

- Item Count
- Will be included with the schedule number and account symbol entries
- Can be associated with an account symbol

- 50

## PAM and SPS

- Total Payment Amount
- Will be included with the schedule number and account symbol entries
- Can be associated with an account symbol

- $22,082.38

## PAM and SPS

- Total Payment Amt

- Control Number

- Item Count

## PAM Website

- _[http://fms.treas.gov/pam/index.html](http://fms.treas.gov/pam/index.html)_
- Contains information on
- PAM Project Updates
- PAM File Formats
- Formats can be downloaded from the website
- TAS / BETC information
- Related websites
- Frequently Asked Questions
- Do I have to use the PAM File Format?
- Who will be my RFC Contact after my agencies payments are processed by PAM?

## PAM Website

## Any Questions?

## Contact Information

- Jesse Chavez, FMS Program Analyst
- 816-414-2108
**    **