Billing Interface Workshop 52504

1
(No Transcript)
2
Agenda Billing Interface

• Introduction

• Overview
• Agency / Core-CT Responsibilities
• Interface Processing Overview
• Task 105 Data Mapping Spreadsheet
• Billing Interface Assumptions
• Configuration Prerequisites
• Phase 2 Time Line for Billing Interface
• Interface Testing and Mock Conversion Process
• Error Handling and Data Cleansing
• Summary What We Covered Today
• Next Steps
• Where To Find Information and Help

3
Overview

• The State has identified a requirement (BI5501)
  to interface between legacy and third-party
  billing systems to PeopleSoft Billing
• This interface will replace current AR Open Item
  Interface (ARI108)
• The interfacing agencies identified so far are
  DOIT, DAS, DOT, DOC and DEP
• This interface will also be used as a one time
  conversion of open invoices at go-live
• For conversion, agencies will convert billing
  information with open status only. Closed bills
  will not be converted from legacy systems.

4
Agency /Core-CT Responsibilities
Agency Responsibility

• Interface file will be in XML format
• Interface will be scheduled at least nightly
• Agencies will FTP interface files to Core-CT or
  use the Portal (same as Phase 1)

5
BI5501 Interface Processing Overview

• File is received through Core-CT interface
  architecture (FTP / Portal) and is submitted for
  XML schema validation (File structure and format)
• XML Errors are sent back to the agencies- the
  file does NOT get processed
• Once the file passes XML validation, it gets read
  by BI5501 Interface. The interface reads in the
  XML file and populates Core-CT Staging tables
• Once the staging tables have been populated with
  data, a Core-CT Billing Interface program
  (BIIF001) will be run to create invoices and
  accounting distributions.
• Users will check for Billing Interface errors
  using delivered reports, and correct data online,
  allowing it to be processed successfully.

6
Task 105 Data Mapping Spreadsheet ( Contd)
7
Task 105 Data Mapping Spreadsheet
8
Billing Interface Assumptions

• Agencies will provide valid Core-CT values
  according to data mapping spreadsheet. This
  includes valid chartfield values and distribution
  codes.
• Distribution Codes for interfacing agencies will
  be configured.
• Primary error checking on interfaced bill data
  will be performed by the delivered PSFT Billing
  Interface. Agencies will confirm successful bill
  creation and repair data in error using Billing
  Interface results and data correction pages.
• Agencies will not be submitting deferred revenue
  accounting entries.
• DAS may be using a third-party billing service -
  Third party will need to provide data in the
  designated XML format. (currently on hold)

9
Billing Interface Assumptions (Contd)

• Adjustment transactions will be handled passing
  negative bill amounts to the interface, rather
  than delivered adjustment transaction handling.
• For conversion, agencies will convert billing
  information of open status only. Closed bills
  will not be converted from legacy systems.
• Standard notes associated with a customer will
  not need to be supplied and will be created by
  the PeopleSoft Billing Interface, as is the
  online process. Should custom notes or
  non-customer standard notes be needed, these
  would be passed through CTBII5501.

10
Configuration Prerequisites

• C119 Billing Business Units (required)
• C083 Bill To Customer ID (required)
• C112 Billing Type ID (required)
• C073 Sales Person (optional)
• C101 Standard Note Code (optional)
• C076 Distribution Code (optional)

11
Interface Tasks Agency Timeline for Billing
Interface
5/2004
8/23/2004
11/15/2004
9/15/2004
1/2005
Conversion Mock 1
Conversion Mock 2
Conversion Mock 3
Production Conversion
Data Mapping sent to agencies
CONFIGURATION
DATA MAPPING MAINTENANCE
CORE-CT
INTERFACE BUILD AND TEST
DATA MAPPING REVIEW - WORKSHOPS
INTERFACE TESTING (MOCKS)
EXTRACT PROGRAM DEVELOPMENT
AGENCY
LEGACY SYSTEM DATA CLEANSING
12
Interface Testing Process

• Interface Unit Test will take place at the end
  of the Build and Test phase. For inbound
  interfaces, the project development team will use
  the files provided by the interfacing Agencies to
  test their batches thoroughly and assess any
  performance issues.
• Interface Assembly Test will be conducted to
  ensure that all the different steps of the
  interface process (batch, interface structure,
  ftp accounts, etc.) work together as planned.
  The objective of the Assembly test is to verify
  that related units function properly when
  assembled into dialogs or batch strings.
  Interface data is validated by the functional
  teams and the Agency technical contacts.
• Within the Product test phase all parties will
  be prepared to fully process test data. This
  includes the source system generating the data,
  the technical architecture enabling the sending
  of the data, and the target system receiving and
  processing the data. Interface data is validated
  by the functional teams and the Agency technical
  contacts.

13
Interface Testing / Mock Conversion Schedule
14
Interface Testing / Mock Conversion Schedule
(Contd)
15
Error Handling and Data Cleansing

• Identify which data fields will be interfaced /
  converted from legacy system and populate those
  fields with as much information as possible.
• Only convert what is appropriate.
• When data errors occur make corrections in
  legacy system.
• Errors can occur at 2 stages
• XML Validation verifies data format and XML
  structure. The file will not be processed if XML
  errors are encountered. Agency needs to correct
  and resubmit the file
• Data errors are detected by the interface billing
  process (BIIF001) in Core-CT. Errors have to be
  corrected online.
• All errors will be sent back to agencies during
  Testing

16
Summary
Today we have covered

• Overview
• Agency / Core-CT Responsibilities
• Interface Processing Overview
• Task 105 Data Mapping Spreadsheet
• Billing Interface Assumptions
• Configuration Prerequisites
• Phase 2 Time Line for Billing Interface
• Interface Testing and Mock Conversion Process
• Error Handling and Data Cleansing

17
Next Steps

• Thank you for your participation today. We look
  forward to continuing our work together to make
  Core-CT a success!
• Next steps
• Complete Data Map by July 16th (Agencies)
• Develop interface extraction program (Agencies)
• Complete configuration tasks (Agencies/Core-CT)
• Establish and communicate testing FTP accounts
  (Core-CT)

18
Documentation

• Data Maps, samples and support document (FAQ,
  etc.) are posted on the Core-CT Website
  http//www.core-ct.state.ct.us/fin2/cnvintfc/Defau
  lt.htm
• Questions? Please contact us at
• Donna Camillone [phone]
• donna.camillone_at_po.state.ct.us
• Frederic Pontaut [phone]
• frederic.pontaut_at_po.state.ct.us