TransPost Help


The Timesheet import records timesheets in MYOB. Timesheets can only be imported using Transpost Plus or TransPost Premier.

These fields correspond to the fields on the AccountRight "Enter Timesheet" form.

Timesheets must identify an employee, and the PayRoll Category, date and total hours for each activity.

A group of records for the same employee and dates within the same pay week will be treated as that employee's timesheet for the week.

For chargeable activities, a customer must be identified. If a job is specified without a customer then TransPost will default to the customer associated with the job.

The grey fields are only shown when the All field radio button is selected. They are either alternatives to the fields shown initially or rarely used and optional.

Action code - The only valid code for timesheets is A to add detail lines to an existing timesheet.

This is because the MYOB API treats timesheet posts as replacements of whatever exists so far of the employee's timesheet for that week so, for historical reasons, i.e. consistency with version 3.3, the default is that if two separate groups of activities for the same employee week are imported the second overrides the first.

If the action code is A, to add, then TransPost retrieves whatever is there already and adds the new input. Thus if the Action code is A, possibly set as a default, new records, or later groups of records in the same input file, will not override old ones.

Employee identification
The Employee card must be identified somehow so at least one of these fields is required:
MYOB Card ID of the employee to whom the timesheet applies. If supplied this will be used and other provider identification fields will be ignored.
Name of the employee to whom the timesheet applies.
If the employee is an individual then the firstname is also required to identify them.

Timesheet Details
Each line represents a particular activity on a specific day. A group of such lines for the same employee for dates within the same working week represent a timesheet.
Date of the activity. Mandatory. If the data contains start and stop time fields in a date-time format one of them may be used for this.
A valid payroll category, applicable to the employee, is mandatory for timesheets.
Notes on the activity.
This is the units to be recorded, i.e. quantity of activity being recorded.

Note that if the supplied data does not contain this but does contain start and stop times they can be mapped instead and TransPost will calculate the difference.

The remaining fields are optional.

The time at which work started on this activity. This may be in a date-time format. For example "23:30" and "Thurs, 25/05/2023 11:00 PM" are both valid values.
The time at which work stopped on this activity. This too may be in a time or date-time format. If time format only is used then an apparently earlier time will be deemed to be the next day.

TIme Billing Details
These fields are only required if the timesheet is also providing input to time billing. As such they will be used to generate an activity slip.
This is the code which identifies the activity. It will be used to create an Activity slip for the activity. If used it must be a valid Activity in the MYOB Activities List. If the activity is billable a customer must be identified, either directly or via a Job with a Linked Customer.
This optional field should be a valid Job Number in MYOB. It is alpha-numeric and may be up to 30 characters long.

If the Job has a Linked customer and a customer is identified it must be the same customer.

If customer is not identified below for a billable activity then the Linked customer for the job will be used.

Customer Identification
If a Job with Linked Customer is not specified and the Activity is billable then Customer must be identified.
MYOB Card ID of the customer. If supplied this will be used and other Customer identification fields will be ignored.
Name of the customer. May be either a personal last-name or a company name. If the data contains both company names and personal last names, in different columns, you must use the CompanyName and LastName fields instead.
Last name of the customer if not an individual. Use this instead of CustCoLastName if customer company names and last names are in different input columns
Last name of the customer if an individual. Use this instead of CustCoLastName if customer company names and last names are in different input columns
First name of the customer if an individual.