This can occur if the transaction is imported twice, for example, once through Leave Processing and from a Transaction Import file, or if the data is keyed and then imported.
Transactions yet to be Processed
If you haven't processed transactions yet, you can verify if a duplication exists by comparing the data in the sources.
Use the IQ, API-Leave - Leave imported via API report, for leave yet to be imported into MicrOpay. And compare this to transactions included in the MIF file for the same period end date, using a report for your T&A export or directly in the MIF file. See Import transactions from Time and Attendance for the file specifications, which explain the codes and format used in the MIF file.
Processed Transactions
If you have already processed or imported the transactions, use Employee Enquiries to verify whether the data was imported twice or whether it was keyed and imported.
Go to Payroll, Enquiries, Employee Enquiries.
Select the Employee(s) by either:
Ticking Single Employee and selecting the employee in From Employee.
Untick Single Employee and enter the range in From Employee and To Employee. Leave From Employee and To Employee blank to include all employees.
Enter the From Date and To Date.
Tick Include Unprocessed Transactions if you want to include the current period.
Click View.
Use Create Source and Create Date to verify how the transaction was entered and when. Right-click and Customise Grid Columns if the fields are not in the grid.
Transaction Import and Leave Processing will both have a Create Source of Transaction Import. If the duplication is caused by importing the same data twice, e.g. Leave, the Create Date will be different. Create Date includes the date and time.
If the data was imported and keyed, the Create Source will be different.