You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > Premier Integrations > isolved Premier Integration > isolved - Scheduled Reports vs. Scheduled Transmissions
isolved - Scheduled Reports vs. Scheduled Transmissions
print icon

isolved has flexible ways to initiate transmission of data, but there are key differences between them which can have an impact with your integration to detamoov. This article will discuss the two types of transmissions that can be used and discuss the key differences between each.

 

First, the two types of transmissions are:

 

1. Scheduled Reports - these are reports tied to a payroll process which can be sent via SFTP as a result of payroll processing. 

 

2. Scheduled Transmissions - these are reports that can be sent based on a time based schedule.

 

Whether transmitting a Scheduled Report or Scheduled Transmission, isolved's data transmission settings will be used but there are key differences in the placeholder values you can use in your data transmission setup based on the type of transmission. The table below shares the placeholders that can be used based on the type of transmission:

 

Type Placeholder Support
Scheduled Reports
  • {1} Report Title a.k.a “File Name” 
  • {2} Date Stamp – or you can format in month, hour, day, year, minutes and seconds with {2:MMDDYYYYhhmmss}
  • {3} File Extension 
  • {4} Pay Date
  • {5} Period End Date 
  • {6} Run Number
  • {7} Pay Period Number
  • {8} Legal Company Code 
  • {9} Legal Company Name 
  • {10} Pay Group 
Scheduled Transmissions
  • {0} Report Title a.k.a “File Name” 
  • {1} Date Stamp – {1} or you can format in month, hour, day, year, minutes, and seconds with {1:MMDDYYYYhhmmss}
  • {2} File Extension

 

detamoov recommends creating two data transmission settings in isolved, one for each type of transmission. Below are the recommendations for your data transmission setup:

 

Type System Level Data Transmission  Client Level Data Transmission
Scheduled Reports
  • Transmission Description: detamoov Scheduled Reports
  • Protocol: SSH FTP
  • Connection URL: sftp.prod.detamoov.com/{8}_{1}_{2:MMDDYYYYhhmmss}.{3}
  • User Name: SFTP username you created in detamoov
  • Password: SFTP password you created in detamoov
  • Allow for Client Transmission: Checked
 
Scheduled Transmissions
  • Transmission Description: detamoov Scheduled Transmissions
  • Protocol: SSH FTP
  • Connection URL: sftp.prod.detamoov.com/{0}_{1:MMDDYYYYhhmmss}.{2}
  • User Name: SFTP username you created in detamoov
  • Password: SFTP password you created in detamoov
  • Allow for Client Transmission: Checked

Override the following values:

  • Connection URL: sftp.prod.detamoov.com/123456_{0}_{1:MMDDYYYYhhmmss}.{2}

 

Note: The above is assuming the isolved client code is 123456 for this client. Since detamoov uses file names to identify which moovs to execute, you should start the filename with the isolved client code.

 

detamoov Retirement Report

When utilizing the detamoov retirement report built by isolved, you will create a system level data transmission setting using the following settings:

  • Transmission Description: detamoov Retirement
  • Protocol: SSH FTP
  • Connection URL: sftp.prod.detamoov.com/{0}.{2}
  • User Name: SFTP username you created in detamoov
  • Password: SFTP password you created in detamoov
  • Allow for Client Transmission: Checked

 

The report file name that replaces the {0} placeholder, will name the generate file starting with the isolved legal company code and will include the text "401k" in the file name. Therefore if this was for company 123456, the generated export file name would be:

 

123456-401k-[datestamp]-[randomvalue].csv

scroll to top icon