I was wondering about this "new" Kronos integration. Do what? You mean I can see my employee data in more than one system?! It has been so long since I talked about integration a.k.a. interfacing, I almost had to wiki "API"! Integration is not always easy, but some things can be.
One-time imports (as opposed to regularly run imports) often come out of a desire to save time and labor for manual entry. As a manager, I don't want the monotonous task of entering a badge number for each employee currently in WTK. I do however have a text file with the employee number and badge #. The timing for the badge import need may need to be planned alongside consideration of a new badging system. The badge # field only needs a linkage in between the employee id (i.e. person number) and the badge itself. It's a one-to-one relationship (potentially it could be a very small file and relatively simple import!). Also, some customers may choose to import badge numbers on a regular basis as part of a person import.
There are more complex relationships to consider as part of any import or export. That comes down to interface logic. Improvizations can help you with that. Perhaps I need to import my accrual rules based on the pay rule the employee uses. Some examples: SAP, Oracle, BPCS, PeopleSoft, ADP, Lawson, and yes, even Paychex). Where there is an import specification, almost any integration need can be satisfied. Pick what you like or maybe what your company uses. What provides value? Would you like to see a call list with telephone numbers within Kronos? Perhaps your other system's employee accrual balances in Kronos? Once an import has been written and tested, it can also be scheduled to happen automatically as well!