Developers - Commissions

Functional description

Allows the calculation, allocation and settlement of commissions on sales of the salesmen of a company. To do this, it generates commission movements in the recording of invoices and sales credit memos, which can finally be settled by means of a purchase invoice, in the case of external vendors.

Before reading this document, it is recommended that you read the help documentation of configuration and use of the extension, as most of the concepts described and defined in will be necessary to understand the contents of this document.

Implementation

Configuration tables

The tables 13 Salesperson/Purchase, 18 Customer, 23 Vendor, and 27 Item add new fields to setup the groups to which each of the elements belongs (for rate calculation), as well as to link the Supplier that corresponds to each external Seller (if any). These are all a few setup fields for defining the generation of commissions.

Pages 14 Salespersons/Purchasers, 21 Customer Card, 22 Customer List, 26 Vendor Card, 30 Item Card, 31 Item List and 5116 Salesperson/Purchaser Card accompany the above tables, displaying and giving the option to edit these changes. In addition, and especially pages 14 and 5116, the action bar for each of them has been expanded with links to the most relevant setup and reporting pages for the product.

Within the range of addon objects, tables 7142105, 7142106 and 7142107 allow you to setup the different groups of vendors, products and customers, respectively. These groups can be assigned to the corresponding tabled (the customizations mentioned above on standard tables), and used in the commission rate setup of table 7142101 IDP Commission Rate

In addition to the tables above, the 7142102 IDP Salesperson Posting Groups table is used to setup the accounting accounts to which the purchase/credit memo invoice lines are assigned, when they are settled to an external vendor, and the 7142109 IDP Commission Setup table gives the general product setup, including the parameters that will define the selection of the commission rate to be applied in each case.

Accompanying the above tables, pages 7142102 and 7142105 - 7142109 are used to create and modify records in them.

Tracking fields

The tables 37 Sales Line, 111 Sales Shipment, 113 Sales Invoice Line, and 115 Sales Cr.Memo Line have two new fields in which the commission group of the product and the customer are stored at the time the line is generated for the calculation of commissions. In addition, a new field IDP Current Price is added, which stores the price of the product that corresponded to the line, independent of discounts and modifications it may have undergone.

Finally, table 83 Item Journal Line contains an extra field that identifies the code of the seller who originated the line.

All the fields described are for internal use and have no visibility on any of the associated pages.

Comissions movements

Tables 7142102 IDP Commission Entry and 7142103 IDP Commission Detailed Entry store all commission movements generated by the application. The first one contains the commissions generated for each combination of document-seller, and the second one contains the detail of the movements generated by each line.

Pages 7142104 and 7142100 allow you to view each of the tow tables above.

External vendor liquidation

When an invoice or credit memo is created for settlement, two actions have been added to pages 55 and 98 (the row subpages) to select the movements (table 7142102) to be added to the document. These pages are 7142101, in purchase invoices, and 7142103, in purchase vouchers.

In addition, a fields has been added to tables 123 and 125 in which the commission flow number that was settled with the invoice/credit memo line in stored.

Customization

At this time the extension is designed to be self-sufficient and does not require customizations. We are sure, that cases will arise in which some setup or feature not supported by the product is required.

For those cases, please open a support request through the corresponding channel, so that we can assess if it is a need that we consider should be added within the standard, or if it is a customization that requires us to add an event or events to implement it.