A selling price is a rate set per product. This rate will apply, except where a contract price is set up for a client's contract. Refer to Contract Prices for more information. A selling price can be increased via the "Selling Price Increases" screen.
Before You Start:
- Create a product (Products)
Selling Price Attributes Explained:
Select the product for which you are setting up a selling price. If the product is not available in the drop down you, can create it by selecting the button next to the field.
The selling price applies to all contracts with this term. The options available are displayed based on terms set up via the “Contract Terms” screen. If the term is not available in the drop down you, can create it by selecting the button next to the field.
A pricelist is a grouping of prices. A selling price is set up per pricelist. If you would like a selling price to apply to more than one pricelist you will have to recreate it per pricelist. If the pricelist is not available in the drop down, you can create it by selecting the button next to the field.
Billing Data Type
The billing data imported will be seen to be of this unit type.
This is the selling price per unit. The quantity of products / services rendered, per client, will be multiplied by this unit price, depending on the billing principle selected for the product. Refer to Products for more information.
A selling price will only be effective from this date.
A system generated code is allocated to each selling price created. This code can be overwritten with a unique code. This code will be used to uniquely identify selling prices created and is not used during billing validation, billing processing or updating your accounting system.
Integrate Source Systems to maintain selling prices
Please refer to this  link to view the complete list of Varibill entities currently readable using OData . To view the Varibill entities and parameters of each entity follow this  link. Only the create, read, update and delete of selling prices and products are currently available, although all the entities listed can be read using the same method. You can refer to OData  to read more about how it can be used to maintain your Varibill data.
When maintaining your Varibill data using this method, you will be authenticated against an existing Varibill user or a system user. The system user makes use of the Tenant name as username and service key, on the Tenant Details screen, as the password. You will also need to set up IP/s allowed to post to your Varibill account on the Tenant Details screen under the "Service IP Address Configuration" section which will be validated when receiving system user posts.
OData allows you to create (post), read (get), update (put) and delete (delete) data. Refer to OData operations  for more information.
Once your integration is in place and posts are made from the source system to your Varibill account, results are returned to the source. Refer to OData for more information on error codes returned.
Varibill will validate all posts received from your source systems using the same validation that is available on the application. This means that all fields, as displayed on the application for the specific entity, must be submitted and must match the formats and rules as would be expected when capturing the entity manually on the application.
One item can be posted at a time. Therefore your integration must loop through multiple items to post more than one item. A result will be produced per item posted.