Overview
Sale runs allow you to reproduce sale shipments for customers on a regular basis. This is ideally suited to fixed non-stock charges like service fees.The process creates sale shipments not sale orders, so it does not suit cases where stock needs to be back ordered regularly. If stock does need to be back orders. You can click a button on the sale shipment to create a sale order. The sale order will track the back order quantity.
...
Field | Description |
---|---|
Type | SALRUN (Sale Run). Transaction type |
Number | Unique transaction number generated by the system |
Status | Position of the transaction, OPEN, POSTED, INPROGRESS |
Date | Date on the Sale Run. This is the date that the system will use when you generate a Invoice |
Description | Best describes the Sales run |
Sale Run Type |
|
Workflow Status | Active or Inactive |
Sale Run Set | The name of the Sale Run Set templated used |
Last Run For | The date the sale run was to run for based upon the settings on the General Tab |
Last Run Actual | The date the sales run actually ran (date created) based upon the settings on the general tab and weekend handling |
Combine Charge To | If this tick is ON and you have a range of customers with the same Charge to Cardid on the Card itself, the system will create a single shipment/invoice for each chargeto customer in that sale run |
Lines Tab
Field | Description |
---|---|
Product | Product to be Invoiced on the Sale Run |
Name | Name of the product |
Qty | Quantity to be invoiced |
Unit | Unit of measure for the product |
Unit Quantity On Hand | Stock on hand |
Price Ex | Price Ex GST |
Price Inc | Price Inc GST |
Disc | Discount percentage if applied |
Tax Code | Tax Code on the product |
Tax Value | Value of tax |
Tender | Ability to set a default tender to the run |
Value | Total Value of each product line to be invoiced |
...
Field | Description |
---|---|
Site | Default site |
Period | Derived from the date entered |
Value Ex Tax | Total Value Ex for the entire Sale Run |
Value Inc Tax | Total Value Inc for the entrie Sale Run |
Printed | If the tick is Off then the Invoices have not been printed. If the Tick is On then the invoices have been printed |
Email Batch Generated | If the tick is ON then the email batch has been generated and visa versa |
Recurrence | |
Recur JanuaryEvery Week | Will recur in the January Month if the tick is ON |
Recur February | Will recur in the February Month if the tick is ON |
Recur March | Will recur in the March Month if the tick is ON |
Recur April | Will recur in the April Month if the tick is ON |
Recur May | Will recur in the May Month if the tick is ON |
Recur June | Will recur in the June Month if the tick is ON |
Recur July | Will recur in the July Month if the tick is ON |
Recur August | Will recur in the August Month if the tick is ON |
Recur September | Will recur in the September Month if the tick is ON |
Recur October | Will recur in the October Month if the tick is ON |
Recur November | Will recur in the November Month if the tick is ON |
Recur December | Will recur in the December Month if the tick is ON |
Recur Day Of Month | The Invoice will be generated on the Day that is selected in the Month selected |
Recur Until | The task will run until the date suggested in the Recur Until fieldevery week |
Recur Every Month | Will recur every month |
Recur From | The commence date as to which you will like the sale run to commence |
Recur Until | The end date as to which you want the sale run to end |
Recur Period | This field specifies after how many weeks or months the sale run should execute |
Weekend Handling | How to handle cases where the scheduled date falls on a weekend |
Shipments
Field | Description |
---|---|
Customer | Cardid |
Transaction Number | Shipment Number |
Date | Date of the Shipment |
Status | Status of the Shipment should be POSTED |
Order | Usually blank |
Invoice | Sales Invoices number generated from the shipment |
Value | Value Inc of the Invoice |
...