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 > moovs > Integrating with detamoov: Essential File Requirements and Examples
Integrating with detamoov: Essential File Requirements and Examples
print icon

detamoov offers a powerful solution to enhance your data management by seamlessly integrating your data. By utilizing detamoov, you can significantly improve data workflows and streamline the transfer of critical information into your system.

 

This guide outlines the specific information needed to build a moov for any integration, empowering you to fully leverage detamoov's capabilities. Throughout the onboarding process, you will receive thorough training designed to help you build your own moovs and integrations. If your integration requirements grow more complex, our expert team is ready to collaborate with you to custom-build your moov—ensuring it aligns perfectly with your vision and needs.

 

detamoov is here to simplify your tasks and boost your productivity.  Let’s get started on mooving your data. To assist you in building the moov for an integration, we will need specific information outlined in this guide.

 


Essential File Requirements needed for an Integration

 

1.  Example Source File

2.  Example Output File

3.  Mapping Instructions

4.  File Naming Convention

5.  Additional Considerations

6.  Frequency of File Transfers

 

To ensure a seamless integration process, we will provide clear guidelines and illustrative examples for each essential requirement.

 

Example Source File 

 

We will need an example of the source file.  In this example, we are using a Toast file; however, the same requirements apply to all source and output files. This file should include all the fields and data that are expected to be processed. The source file is crucial as it will allow us to create a precise File Definition in detamoov, which will map how the data from Toast will be handled.

 

Example Fields in the Source File:

 

Employee ID

Pay Rate

Regular Hours

OT Hours

Pay Date

Department

Pay Class

 

The format of the source file (e.g., CSV) is important, as this will determine how we set up the File Definition in detamoov.

 

Detailed Example - Source File Data:

 

EmployeeID, EmployeeName, PayRate, RegularHours, PayDate, Dept,

12345, John Doe, 15.00, 40, 10/10/2024, Front of House,

 

Example Screenshot

 

 

Example Output File 

 

In addition to the source file, we require an example of the expected output file. This file is the result of the processed data from detamoov and should meet your specific format and field requirements.

 

You must also provide notes for mapping the fields from the source file to the output file. If there are any differences between the field names in the source and output files, these should be clearly documented. This mapping ensures that we fully understand how to convert the data during the moov process to meet your expect file output requirements.

 

Important: The output file must be created directly from the source file to ensure accuracy and consistency.

 

Detailed Example - Output File (Expected Format): 

 

EmpID, FullName, Rate, TotalHours, PayrollDate, DepartmentCode, Company Code

12345, John Doe, 15.00, 40, 10/10/2024, FOH, XYZ

 

 

Mapping Notes Example

 

EmployeeID - in the source file maps to EmpID in the output file.

PayRate - in the source file maps to Rate in the output file.

Dept - in the source file maps to DepartmentCode in the output file, with the specific conversion of “Front of House” to "FOH."

 

The clearer and more detailed your mapping instructions, the easier it becomes for us to configure your moov flawlessly and ensure everything runs smoothly and the output file meets your requirements.

 

Additional Considerations 

 

File Name: Please specify the file name format for the output file (e.g., XYZ_10182024_Time_Import.csv).

 

Field Formatting: If specific formatting rules apply to any fields—such as date formats (MM/DD/YYYY or DD/MM/YYYY), currency, or decimal precision—please provide these details to ensure accurate formatting.

 

Filter Data: Specify any particular information about the data you wish to remove.

 

Frequency of File Transfers: Indicate how often these file transfers should occur (e.g., daily, weekly, or after every payroll run).

 

Next Steps 

 

Once we receive the source file, the output file, and the detailed mapping notes, we can begin creating and configuring the moov in detamoov.

 

We are here to assist every step of the way, ensuring the integration runs smoothly.

 

If you have any questions or need further clarification on the information required, feel free to reach out.

 

Explore Our Knowledge Base: Helpful Articles at Your Fingertips 

 

scroll to top icon