Xactly is powerful.
That is exactly why it gets complicated.
Incent will model almost any plan you can describe, which is precisely the problem: the rule layer ends up holding logic nobody documented. We build it so it can be explained.
Where Xactly gets hard.
Three things that decide whether a Xactly build stays maintainable.
Rule and formula sprawl
Incent's flexibility means plan logic accumulates in rules, formulas and lookup tables. After a few comp cycles nobody can say with confidence why a given rep was paid what they were paid.
Credit and hierarchy design
Rollups, splits and indirect credit are decided early and quietly govern everything downstream. Getting the participant and territory hierarchy wrong is expensive to unwind later.
Data in and out
Xactly Connect is capable, but it only reflects whatever your CRM and ERP actually contain. Most Incent problems we are called into are upstream data problems wearing an Incent costume.
The same Xactly project, two ways.
What usually separates a Xactly build that holds up from one that quietly becomes someone’s problem.
Without specialist support
Plan logic accumulates in rules nobody has documented
Credit hierarchies designed on the fly, expensive to unwind
Xactly Connect feeds built once and never revisited
Comp analysts become the only people who understand the build
Disputes resolved by re-running calculations and hoping
Every plan change is a small act of archaeology
With OnCentive on the build
Rule and formula logic documented as it is built
Participant and territory hierarchy designed before configuration
Connect pipelines with error handling and reconciliation
Your team trained on the build, not dependent on ours
Traceable path from source transaction to payout line
Plan changes shipped without re-opening the whole model
Tell us what your Xactly has to do.
We will tell you what it takes.
First rollout, a migration on or off Xactly, or a new requirement on a system already paying people. We have done all three for more than ten years.
Start a conversation