The Lauranka AMA importer is accessed from the Import function on the control bar in the Pay run screen.
The AMA file can be dragged directly into the importer. No field mapping is required.
If you are using a CSV export instead, import it through Flexi-CSV. For instructions, refer to:
Prepare for the import
Before exporting from Lauranka, check that:
Employee identifiers match: The employee’s Employee Number in Lauranka must match their Badge# in SmoothPay.
Time calculations are complete: Lauranka must have already calculated the ordinary hours, overtime and other applicable transactions.
Payroll settings are correct: Pay rates and overtime multipliers are not supplied by Lauranka. SmoothPay uses the applicable payroll values.
Transaction codes are correct: The exported codes must identify the intended Work, Leave, Allowance or Sundry Deduction transactions.
Important: SmoothPay’s automatic overtime and time conversion rules are ignored for Lauranka imports. Ordinary time and overtime must already be separated in the exported data.
Check employee matching
The employee’s Badge# is located in the nested Employment tab, under the Contract tab in the Staff screen.
Check that this value matches the Employee Number used in Lauranka.
For more information about these employee settings, refer to:
Check cost centre and job codes
If the export includes costing information, configure the Cost Centre Export Code in Lauranka to match the corresponding codes in SmoothPay and, where required, your accounting system.
The Lauranka format provides six characters for the GL or cost centre code, followed by six characters for the job code.
Check the resulting allocations after importing.
Import the AMA file
Export the completed payroll data from Lauranka as an AMA file.
To open the importer in SmoothPay:
Open the Pay run screen.
Click Import on the pay run control bar.
Select Lauranka AMA.
Drag the exported AMA file into the import window and click Process once it's uploaded.
SmoothPay reads the file using the Lauranka format and creates pay inputs from valid records. You do not need to map the file’s fields.
Invalid entries are rejected, and an audit report of the processed entries is produced.
Review the imported transactions
Review the audit report and the resulting pay inputs before processing the pay.
Check that:
Transactions have been assigned to the correct employees.
Ordinary time and overtime have been imported as intended.
Pay rates and multipliers produce the expected payments.
Cost centre and job allocations are correct.
Leave payments and the quantities deducted from leave balances are correct.
Days paid are correct.
Any rejected entries have been investigated.
Overtime quantities should represent the actual hours worked. SmoothPay applies the relevant multiplier; the imported hours should not already be multiplied for payment.
For example, two hours of overtime should be supplied as 2 units against the appropriate overtime code.
For more information about Work code configuration and completing the pay, refer to:
Check leave units and import codes
The transaction code determines whether an imported leave quantity represents hours, days or weeks. Check that the code matches the intended units.
For New Zealand daily leave types, an hours-based Lauranka entry initially records one day consumed because the file does not supply a separate days-consumed quantity. Review and adjust this where necessary.
For the shared code descriptions, leave-unit explanations and days-paid guidance, refer to the relevant sections of:
The Flexi-CSV field-mapping instructions apply to the CSV alternative. They are not required when importing an AMA file through Lauranka AMA.