What is Versioning?

One of the greatest features that inLOGIC has to offer is the ability to trail changes made to the data. There are two specific columns that system automatically generates and adds to the Payee and Transaction tables: Modified Date and Version. These two columns are closely related to each other leaving traces every time the information in the row of data is updated.

Modified Date and Version Columns

Modified Date and Version Columns

When does Versioning Occur?

When collecting commissionable data of payees and their transaction activities, sometimes it is inevitable to make changes, which can lead to different outcomes in payout amount. Changes can result from human errors, miscommunication between source systems, or it can be initiated by the customers.

Here’s a simple example. Let’s say your sales compensation plan is aligned to your strategy to penetrate a new market, and you designed a plan to incent those who bring a New customer. However, by the plan policy, when a customer cancel the contract within a certain period of time, commissions won’t be paid out.

Edit Transaction Data

Edit Transaction Data

In the event of this type of changes, the system will leave a footprint so that you can trace the history of all changes.

Version Updated

Version Updated

If you would like to track down the history, click View link, and the History will display the detailed revisions of what has been changed, who made changes, and when has it occurred.

Revision History

Revision History

How does Versioning Impact Payment?

Most organizations have a claw back or charge back clause in the policy in one way or another. The genuine purpose of this clause is not attempting to pay less the payees, but attempting to pay the right amount to the right payee, in right time. But, all too often, it causes both parties spending significant amount of time resolving the disputes.

We hear you, and Versioning is the solution to this problem.

When the data is saved in the table for the first time, whether they are transferred from other source systems or entered manually, their Version is 1. In order to demonstrate it, here is the simplest example.

Your Sales Rep, Malcolm sold a Blender at $100.00 on June 8, 2015, and the variable pay rate (VPR) is 15% of the sales.

Initial Transaction Data

Initial Transaction Data

By the plan design, the eligibility has been narrowed down to those transactions of New customers, and according to the qualification, rule is written as seen in the image below:

When the blood does not passes away in a good quantity you cannot possibly have affirm erection. generic cialis soft These treatment approaches are effective and cialis prices result oriented only when a man treats its underlying cause firstly. At the same time, it does not ought to be a significant wellness concern, considering cialis 60mg it comes about once in a while. If it is left untreated, the individual generic viagra in usa go to the appalachianmagazine.com experience lots of health problems and even relation crisis also.

Qualification and Plan Rules

Qualification and Plan Rules

If you run a calculation, as we all expect, the commission Malcolm earns is $15.00 (15% of sales price, $100.00).

Calculation: Version 1

Calculation: Version 1

Let’s say, the customer returned the Blender on June 29, then you, as Administrator, need to go ahead and update the transaction type from New to Cancelled. According to the 30-Day Return policy, the transaction cancelled within 30 days will be clawed-back.

Edit Transaction

Edit Transaction and Update Values

If you run a calculation after creating a Version 2, the expected earning for Malcolm should be $0 based on the qualification rule written above.

In the Plan Summary page, click Detail link for further inquiry.

Version 2 - Plan Detail

Calculation Result after Creating Version 2

The outcome is as expected, 0, and also you can see the Reversal occurred that triggered a clawback. In order to break it down even further, click Review link, then it will display the detailed feedback why the transaction or the payee failed/succeeded to receive that particular amount of earning.

Failure/Success Feedback

Failure/Success Feedback in Plan Detail Analysis Page

What are the Benefits?

Enough said. So, how can your business directly benefit from using inLOGIC’s Version Control?

First of all, it’s FREE!!!. When we say it’s free, it is life-time guaranteed FREE. There is no hidden cost or limitation for you to enjoy this amazing feature with no extra costs attached to it.

SOX Compliant

inLOGIC’s Version Control helps your business comply with Sarbanes-Oxley (SOX) Act. Since the enactment, it has become a very important role of every stakeholder in organizations to keep all the records for a certain period of time. Through Versioning, you can keep your sales compensation administration SOX compliant since it stores the whole life span of every single row of data.

Audit Trail

When it comes to auditing, it is important for keeping your business processes and procedures integral and legally defensible. The Version Control feature will definitely fortify your record keeping capability with the traces of all the changes from day one.

Transparent Administration

Since you can easily review and compare original data and its history of changes and updates, and who initiated the changes, the dispute resolutions between management and employees become so easier and faster. You don’t have to spend time looking for reasons to blame somebody else for any errors and disputes anymore. The system will tell you exactly what happened, when it happened, and who is responsible for it.