Obero CEA User
June 13, 2019
Obero CEA User
Manager in Finance and AccountingComputer Software Company, 1001-5000 employees
Score 6 out of 10
Overall Satisfaction with Xactly Commission Expense Accounting (CEA)
The accounting department owns CEA. We have both a 605 and a 606 instance, with different rules set up in each instance according to our policies under the different standards. Our financials for the year ended January 31, 2019. That was the first year we were live with 606, so now we use the 606 instances exclusively. CEA provides us with automated amortization waterfalls and journal entries. In a perfect state, we would be able to download the journal entries and upload directly to NetSuite. However, due to the state our ICM system where commissions are not calculated accurately or timely, this is not possible. In addition, we are a publicly traded company and the system is not in compliance with our ITGCs, so there is a lot of additional manual checks that I must perform before booking entries.
- Amortization waterfalls
- Locked periods & PPA adjustments
- Journal entries
- Not possible to make back-end changes to amortization schedules independently (for example, if departments need to be changed).
- Impossible to change rules without customer support, for example, if a new plan is added.
- Have to run separate amortization schedules for each subsidiary rather than at a consolidated level.
- No longer need to calculate amortization of deferred commissions.
- With CEA, it takes 60 hours per month to do a commissions accounting close. This is due to manual controls needed for SOX compliance and the poor state of ICM.
Clean up existing data before uploading it! Consider the fields used to create a unique identifier and whether this will cause problems— manual adjustments often need to be adjusted because of duplicates. Consider what is needed on the ICM side to ensure accurate accounting and ease of configuration on the CEA side.
Xactly Commission Expense Accounting Feature Ratings
Journals and Reconciliations
Centralized Rules Framework
Role-based user permissions
Single sign-on capability