Overview:

As a tab of the Job Enquiry screen, Transactions offers the deepest look at cost transactions of your Job. You can independently filter for any transaction you are looking for, making this a powerful tool to find anything you wish related to Job costs.

Job Transactions contain numerous columns of information, causing horizontal scrolling to be necessary to display it all. Below you will find information for each field. The columns can be managed using Grid Management to show (or hide) information that is relevant to you. Columns like Markup, Markup%, Margin% are common examples that can be managed from Grid Management.

Screen Guide:

Image Added

• Job is the Job level and default sorting column.

• Work Centre displays the Work Centre of the transaction.

• Cost Category is a custom way of categorising Activities into useful groupings. You can add more categories in Cost Categories

•  and then group individual Activities

•  into them. Note that Cost Category grouping is a global setting, and an Activity can only belong to one Category. If you do not wish to use Cost Categories, you can remove the column from the display using Grid Management.

• Activity displays Activities for the transaction, first the code followed by the description. Usable Activities are determined by the Activity Group in Job Maintenance.

• Date is the date that the transaction was entered for, but not necessarily the date that it was entered.

• Year/Period displays the finacial period in which the transaction has been included.

• Type shows the underlying activity type, and also serves as a link to the actual location of the transaction in Workbench, providing the unparalleled ability to delve to the deepest level of the transaction - its origin. These are the available types:

  • Time - links to the Timesheet that this transaction was entered in.

  • Plant - links to the Plant Issue that this transaction was entered in.

  • Subclaim - links to the Subcontract Claim that this transaction was entered in.

  • Purchase - pops up the AP Invoice that this transaction was entered in.

  • Docket - does not currently provide a link to the Dockets Only Entry, but can be traced using the Batch field.

• Reference changes depending on the transaction Type, but will display either the AP Invoice number, Subcontract Claim number, Docket number, or the Timesheet or Plant Issue week ending date.

• Description shows the employee, plant, or company name involved in the transaction.

• Qty is the quantity of hours/units entered for this transaction.

Image Added

• Cost is the total cost value of the transaction.

• Retail is the total selling value of the transaction. This is used for Input Based Selling and Input and Output Based Invoices, and is ignored for other types.

• The following columns are relevant when using  Input Based Selling and Input and Output Based charge types, and reflect the values from the Job Invoices where these transactions have been sold. Sell Qty, Selling,

•  Markup, Markup%, Margin%:

  • Markup= Selling-Cost

  • Markup%= (Selling-Cost)/Cost, in a % format.

  • Margin% = (Selling-Cost)/Selling, in a % format.

• Batch shows which batch number the transaction belongs to. If the transaction has not been batched, it will remain blank. You can refer to Export Control and filter for the number to review individual batches.

• AR Invoice shows which invoice the transaction was used in for Input Based Selling and Input and Output Based Invoices. Otherwise this field will display "0".

• Details shows any details that were entered for the transaction. This will change based on the transaction Type and how the data was entered.

• Allow Qty is a field used only for Timesheet transactions and only for lines that were marked as allowances. This allows for analysis of Qty of hours versus allowances.

• Log No is used with the Service Desk module, making it easier to track which transactions belong to which Service Log.

Next Steps:

If you identify any errors in transactions, you can follow the Type link to the transaction itself to attempt to make changes, otherwise you may need to use Adjustments or Job Transactions Transfer to fix the error.