Overview:
Input Based Selling is used by jobs that are assigned to a Charge Type with a Billing Type of Input Based. New invoices can be created through Job Sales Invoices for these jobs.
This billing type collects all job transactions including Timesheets, AP Invoice Enquiry, Plant Issues, Adjustments, Disbursements, Daily Diary Stock Issues/wiki/spaces/DARCH/pages/705527854, and optionally Purchase Orders up to the Invoice Trans To Date field. This facilitates "Cost Plus" and "Do & Charge" style jobs. If your job includes the selling of Job Outputs as well, the Input and Output Based billing type is more appropriate.
Note |
---|
For more information about pricing and sell rates, see Price Code & Input Billing Overview. |
Screen Guide:
Header
title | Header details |
---|
Job Code is the job this invoice relates to.
Client is the client Company of the invoice.
Invoice Title is the billing title, defaulting to the job description, but can be modified here or the default in Job Maintenance.
Invoice Format determines what type of report is generated when sending the invoice to the client.
Billing Address defaults to the job's default, but can be changed to any address for the Client Company.
Billing Contact defaults to the job's default, but can be changed to any person listed under the Client Company.
Additional charges to those charges generated from the Transactions on the Job being invoiced can be added at the time of billing by using Surcharges and Discounts. These can be a % of the sales value which is derived from the sales value at the time of billing or as a fixed Rate. Common uses for this can be applying discounts, adding Fuel charges, or a very particular scenario for Equipment Hire businesses where a Limitation of Liability can be charged. See details of how to configure this here.
Note |
---|
For more information about pricing and sell rates, see Price Code & Input Billing Overview. |
Screen Guide:
Expand | ||
---|---|---|
| ||
|
Details
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
This section will be populated as a result of the Get Sales process, but you can make manual additions using + New Line outside of that process.
|
Expand |
---|
|
| |
|
|
|
|
Get Sales View
Transactions Tab
|
Get Sales View
Expand | ||
---|---|---|
| ||
This tab contains all the billable transactions for this job to the Invoice Trans To Date setting, including previously deferred transactions but not previously written off. As this area contains quite a few columns, you may need to scroll horizontally or minimise the left side menu to see all fields. Or manage columns from Grid Management using ‘Input Based Sales' grid. The different status radio buttons will allow you to invoice, un-invoice or leave untouched (Pending), write-off or deffer. Include Future will display transactions on the job beyond the Invoice Trans To Date setting. Bill POs makes it possible to bill uninvoiced/outstanding Purchase Orders. Filter options are available to help narrow down the desired transactions. Type can be one of the following, and identifies the origin of the transaction: JT - Job Transaction JTAD - Adjustment Transaction The are four possible statuses for each transaction:
|
Summary This Invoice Tab
Expand | ||
---|---|---|
| ||
This tab includes a summary line for each Sales Code. The following acronyms are used:
|
Next Steps:
Once the claim has been populated, approve the claim (if necessary) and Print the Contract Claim Certificate and send it to the client. Once the client certifies the claim, Approve and send the Final Invoice to the client. If the client rejects part of the claim and there is no dispute, Unapprove (if necessary) and adjust the values in Get Sales to the approved amounts, then proceed to the Final Invoice.
|
Expand | ||
---|---|---|
| ||
This tab includes two summaries:
|
Changing Activity on Time transactions when selling:
When using Input-based billing (Cost plus) users can change the activity on a Time transaction to sell the work done by certain employees as something different. For example, work done as a Skilled Labourer to a Foreman. Typically, a Price code with a combination of activities and Employee classes would be needed so the time transaction can not only be re-costed (due to the change in Activity) but also can be re-priced based on the Price code rule for the Employee Class + the new Activity when generating the invoice.
The Invoice radio button has to be selected for the Activity to be editable.
Only users with specific permission (Edit Activity Code on Time Transactions ) can edit the Activity. And it must be someone who understands the implications of this.
The selected Activity will be validated as per usual against the Job Activity Group.
The transactions with Activity changes will be recosted and repriced on clicking Save and Generate Billing for invoice generation.
Activity changes will be logged in the invoice history.
Info |
---|
Possible implications of changing Activity: 1- If using EBA and EBA was generated for this transaction, note that the new activity vs the original activity could have resulted in different Payroll results. 2- The Job Manager should be aware that this kind of change may happen, so not to be surprised that what they have reviewed and approved, might change later. |
Another way of achieving this is by using Labour Costing Groups, which set specific rules on a Job to map an Employee Class to another Employee Class automatically at Timesheet entry.
Next Steps:
Once the invoice has been populated, print it to preview (if necessary) and once approved and finalised it can be sent to the Client.
Related Pages:
FAQs:
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|
Process Flow: