Sales prices
Use this field to enter a general price list for sales purposes. This price list will be used only if the search for a sales price does not return a price or a higher-priority price list, such as a price list for the customer or customer group.
You can specify standard sales prices for parts that apply during a particular period. On sales offers and orders, the correct price will automatically be selected from this table. For Isah to be able to determine the valid price, you need to specify a date.
Use this field to set the date to be used for determining the sales price:
This field is used on sales lines of a sales offer or order. As soon as a sales line has been added, the Price currency field on the Price specification tab will automatically be filled in based on the currency code set in the Sales price currency field. The currency entered in the Sales price currency field is a default value. Therefore, enter the currency used for most of your sales prices.
The price currency specified on the sales line is used to check the search path for sales prices to find a price for the part entered on the sales line. If no price is found for the price currency specified, no price data will be filled in. If you change the price currency on the sales line, the search path for the sales prices will be checked again.
If you do not enter a currency code in the Sales price currency field, the currency specified in the sales offer or sales order header will automatically be filled in on any new sales lines.
Use this field to specify the part group to be included in the search path for purchase prices. You can choose from the following settings:
Determine preliminary cost price
Purchase origin, Stock origin, Production origin
These fields are only relevant if the following two conditions are true: On the General tab of the Financial form:
The fields determine which preliminary cost price is to be posted as 'Work in progress to be closed' (WIP TBC) when an invoice is created. The preliminary cost price of a sales line is determined by the origin of the part on the sales line. It is possible to specify different cost pricing methods for the different origins.
The preliminary costs are displayed on the Cost price tab of the Sales lines form. The preliminary costs of parts with a 'Purchase' or 'Stock' origin are filled in at the time the sales line is saved. If the part has a 'Production' origin, the costs must be calculated using the Cost pricing process.
Part origin |
Preliminary cost price |
Purchase: |
- Purchase price |
|
- Calculation price |
Stock: |
- Fixed valuation price/average purchase price |
|
- Calculation price |
Production: |
- Manual |
|
- Cost price from an assigned production file to be selected |
|
- Cost price from all production files |
|
- Cost price from the Parts module |
Periodic invoicing
Check for order sum/periodic sum difference
Specify how to check for differences between the sales order sum and periodic invoice sums:
|
Choose this setting if you do not want to check for discrepancies. |
|
Choose this setting to compare the order total with the period total. |
|
Choose this setting to check each period line for discrepancies. |
Enter the minimum difference sum to be used for the check. If the difference between the order sum and the period sums is smaller than or equal to this amount, you will not be notified of the difference.
Method of modifying periodic schedule
Use this field to specify the default modification method for period lines that have not been processed or authorized yet.
|
The new sum will be equal to the percentage on the period line, multiplied by the order sum, minus the sums of the periods already invoiced. If the order value is increased after some periods have already been invoiced, this method is likely to result in a remainder sum. |
|
The order sum minus the sums of the periods already invoiced is distributed among the period lines not yet processed, based on the weighting of the percentages of the period lines still to be invoiced. |
Lines will only be modified if:
On the Sales tab of the Basic data form, you are working with the following Periodic invoicing settings:
Now create a sales order with the following data:
Now change the sales price on the sales line from $ 1,000 to $ 1,200. Then run the Change periodic sums process to apply the changed sales price to the periods. The results will be as follows:
As the first and second period should have been $ 100 higher, you can now choose to:
Example 2: Based on weighted percentage
On the Sales tab of the Basic data form, you are using the following Periodic invoicing settings:
Now create a sales order with the following data:
The sales line has a sales price of $ 1,000.
This sales line has been marked for periodic invoicing.
Now change the sales price on the sales line from $ 1,000 to $ 1,200. Then run the Change periodic sums process to apply the changed sales price to the periods. The process is executed using the 'Based on weighted percentage' method. The results will be as follows:
Also in this example, the program will detect a difference between the newly calculated sums for the third and fourth periods and the order sum percentage. This difference is, of course, the result of the weighted percentage having been applied.
A final period to the amount of '0' will ensure that the period turnover is transferred to a provisional or final turnover ledger account.
You can also use the Check for order sum/periodic sum difference field in the basic data to indicate that you want to compare the total distributed sum with the total order sum. If you were then to look at the third and fourth periods from the second example again, no difference would be found, because after application of the weighted percentage, the distributed sum would be exactly equal to the total order sum.
Cost-plus invoicing
Unit for creating cost-plus specification
Enter the unit to be used as the basis when creating the cost-plus specification. This setting will be used when cost-plus specification lines are created based on: