What data can be imported and exported from EARNIE?
The available importable/exportable fields are listed in a file
called Fields32.xls which can be found in the folder where
Earnie/32 is installed.
Can I create just one import file for use with several
companies?
No, you will need to use a separate file for each company.
How does EARNIE recognise and then subsequently deal with a new
starter in the import file?
If the code does not already exist in EARNIE, it will create a
new employee and treat them as a new starter.
How does EARNIE recognise and then subsequently deal with a
leaver in the import file?
To make someone a leaver you will need to import an Active
Status of 2 (Leaver this month) and a leaving date.
What format does the data need to be in for importing?
There are several predefined import structures that come with
EARNIE but you can also define your own. You can import in
either:
- Fixed length
- CSV (Comma Separated Value) or
- Microsoft Excel formats
When you choose fixed length you need to specify the start position
and length for each field. We usually recommend using CSV as these
are the easiest files to read and diagnose if there are problems.
All import files must be in a simple column based format with a row
for each employee. The first column is always the employee code and
the remaining columns are defined by the structure.
Can you accept a fixed format file, which only includes
changes?
Yes, EARNIE will hold all data already imported so it is
preferable to only import changes.
My clock-in details are not coming through to the payroll run.
Why?
Check the Clockin file is in the EARNIE program folder and it is
named correctly:
It will be either Clockin or Clockin.XXX, where X represents the
company ID number. The Clockin file will also not come through to
the payroll if it is a re-run.