Skip to main content
Skip table of contents

Preparing timesheet batches

Before you can import timesheets into a pay run, you need to:

  1. Create a timesheet batch.

  2. Map timesheet records.

  3. Check and edit records in the timesheet batch.

1. Create a timesheet batch

The steps for creating a timesheet batch depend on what your company uses for timesheets:

  • MYOB Acumatica — Workforce Management

  • MYOB Acumatica time cards

  • An external timesheet system not provided by MYOB.

After creating a timesheet batch, it's normal to see warnings about missing data. These go away once you map the timesheet records and then update the timesheet records.

Creating an MYOB Advanced Workforce Management timesheet batch

You need to commit your timesheets to payroll and include them in a finalised pay run. For more information, you can find timesheet information in the Acumatica Workforce Management help centre.

Creating an MYOB Advanced time card batch

For employees with time-based payroll expense allocations from MYOB Acumatica time cards, the data must be imported using the Import Timesheets screen. The imported time batch is always used as the source of time-based payroll expense allocations, whether the data came from MYOB Acumatica time cards or an external timesheet.

To create a time card batch, you need a data source type that's set up as a time card type.

  1. Go to the Import Timesheets screen (MPPP7030).

  2. Select the correct Data source type.

  3. On the toolbar, click the three dots icon (. . .) and choose Import Time Cards.

  4. Time cards are generated against a specific week, which is displayed for the time card on the Employee Time Card screen (EP305000). In the From Week and To Week fields, specify the range of weeks to import time cards from.

  5. Click OK. Data from all approved and released time cards within the range of weeks you selected is imported.

Creating an external timesheet system batch

Preparing a timesheet file

To import timesheets into MYOB Acumatica from an external system, you need a Microsoft Excel file with the timesheet data. The file must have the same column layout as the main table of the Import Timesheets screen in MYOB Acumatica:

Record

Description

Ext. employee ID

the employee’s ID in the external system

Ext. employee name

the employee’s name in the external system

Ext. pay item ID

the ID of the pay item in the external system

Ext. sub account

the subaccount ID in the external system

Ext. Project

the ID of the project in the external system

Ext. Project Task

the ID of the project in the external system

Ext. Inventory Item

the ID of the project in the external system

Timesheet date

the date of the timesheet entry

Quantity

the quantity (hours/days) for Rated pay items

Amount

the amount for Amount pay items

The import headers are case-sensitive. The easiest way to create an import file template is to click the Export button (

) on the main table toolbar to export a blank table to Excel—this will create a file with the required column headings in the correct order. You can delete the columns after Amount, as these columns relate to data from the MYOB Acumatica system that will be filled in by the data mapping.

Uploading a timesheet file

  1. Go to the Import Timesheets screen (MPPP7030).

  2. Select the correct Data source type.

  3. On the toolbar, click the three dots icon (. . .) and choose Upload Timesheet.

  4. In the Timesheet File Upload window, click Choose File and select the file you want to upload.

  5. Click Upload.

2. Map timesheet records

After creating a timesheet batch, you need to map the information imported in the batch to records in MYOB Acumatica.

It's mandatory to mapping pay items and employees, but optional to map subaccounts. However, if no subaccount is mapped, the default subaccount on the relevant GL Purpose code will be used.

On the toolbar, click the three dots icon and choose Map Imported Items. The remaining fields are filled in automatically based on the data map.

3. Check and edit timesheet records in a timesheet batch

Checking that all timesheet records have been imported and mapped

The summary area provides an overview of the imported record set. Use these totals to confirm that all timesheet records have been imported and mapped correctly by, for example:

  • Comparing the presented totals with the record totals of the imported timesheet file.

  • Comparing the number of imported records against those mapped.

  • Evaluating the Pay Date range.

The Summary tab provides an additional level of reporting by grouping the imported data by Employee, Pay Item and Subaccount.

The Summary tab only reports on the imported external data, and is not indicative of what will be imported into a pay run – the purpose of this view is to help you confirm that all data was correctly imported.

Resolving timesheet record warnings

If a timesheet record has missing or incorrect information, a warning appears in the affected field. The Status column also details the problem. For example, the screenshot below shows a warning about an inactive subaccount. To only show records with warnings, you can filter the Status column by “Is Not Null”.

For more details on resolving these warnings, see Error: "Missing data map(s)..." when importing timesheets.

If you've imported a timesheet batch into a pay run, you need to undo the pay run import before you can edit the timesheet batch.

What's next?

You're ready to import your timesheet batch to a pay run.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.