Page History

...

1. Contact SITE SOFTWARE provider, to have the PT 3.0 update scheduled.
   1. Try to avoid Friday Saturday or Sunday dates so as to not have support availability gaps.  If you have to schedule a Friday, Saturday or Sunday. Irely will not be able to help with the transaction file until the Monday or Tuesday following. So keep that in mind.    
   2. If the Site controller update cant be finished on the date chosen.  Notify FleetCor and iRely as soon as you know, so adjustments can be made.
   3. schedule you to the next Business Day available.    
2. Contact FleetCor to have the NETWORK update scheduled.
   1. Call FleetCor and get a NETWORK date scheduled to match the SITE controller change date. Again You will want to make this a Monday to Thursday date, so as to not have the Transaction file change on a Saturday or Sunday. 
3. Call/Log into  iRely HELP DESK: 
   1. Once you have a date with FleetCor and the Site controller software company. Log onto iRely Help desk and update your Help Desk ticket. (  https://helpdesk.irely.com    ). The Ticket name will be “FleetCor PT 3.0 Conversion for : (Your company name) “.
   2. Update the information in the Ticket Description box under Steps to Complete with the dates.  The BILLING (iRely Date) will be the next business day after the network change.   Again avoid Friday and weekend dates if at all possible.   
   3. iRely will fill in the Billing date, and will also place that date in the CUDE date at the left of the help desk ticket for scheduling programs.

 Image Removed

1. Update the Description Section Steps with the dates for SITE, NETWORK and BILLING
   1. . This will be the next available Business day available.
2. If your SITE schedule date changes, immediately contact FleetCor to change the NETWORK date. Then please log onto the Help Desk Ticket and change the due date the Dates in the ticket description We will reschedule the iRely Date to the first working day after the new SITE/NETWORK change date. 
3. Review NACS code sheet changes in this link: 

   1. The most common product codes have been highlighted in yellow.  Find your usual codes in the column for your network. then look at the code in the Column titled "New Conexxus 4.0 Product Code"  This will be the new code sent for the code in the original network column.   If it is different, then add that line to your list.  If

   that date is already full, we will bump you to the next available day

   1. the description does not match to your current product code. Look at the new product description and choose one that does match.  add the new product to your list with the old code you cirrent use and the new more distinct code.

      
      

      
      

1. Site Controller Change Date arrives:
   1. When the Site controller has been changed, the PT file is 24 hours behind, so it the new format will be in the next day’s pull that has the new file format. So if you change the site controllers Friday, the data wont show up in the new format until Saturdays file pull. Avoid Friday and weekends if at all possible. 
   2. Once you have downloaded your first new PT 3.0 transaction file from the website. (Do not try to import/process it). Make sure that all pre PT 3.0 transactions have been posted, and that the unposted transaction tab in CF>TRANSACTIONS is empty.
   3. Logon to the iRely Help Desk, open your ticket and bump the Priority to (Blocker). This will alert the PT 3.0 Team that you are ready for a call and conversion process.
   4. If your Site controller software did not change on the date it was supposed to,
      1. Immediately call FleetCor to have them stop the NETWORK change. You will have to reschedule all 3 dates.
      2. Log on to the iRely HELP DESK and change the Due date in the ticket to reflect when it will be changed.        
      3.    

1. The iRely Team iRely will call, and will connect to the server to update the Card table to 8 digits, update the file import mapper(s) to handle the new PT 3.0 format. We will add any NACS codes to the cross reference file noted in the attachments tabTicket.  When we have completed that you will be ready for the first PT 3.0 file to be imported.  We will call and have you import the new PT file.   The rest of the Process is the same as before.   

...

1. Import New file, Check for errors. We anticipate some possible NACS code mis matches on the initial first imports.  We will work through those with the NACS spread Code sheet in the attachment Ticket tab .

1. After the update, when you enter new Cards for your customers, they will require that they be 8 digits so zero fill the left side until the number is 8 digits long. E. card number 123456 will require to be entered as 00123456. Same for seven digit card numbers. 1234567 enter as 01234567. If you do not then the card will not be found on the transaction import when it tries to match up the card number.. 

...