Contracts against billing
The commitment. What each customer agreed to pay.
The agreement says one thing. The system was told another.
In price increases due on a date, in index linkage, in discounts that were meant to expire. Billing runs on the price that was set up when the contract started. The contract said the price would move. Billing still runs on the original price.
A price increase due in April that never reached the invoices.
A customer contract sets a 3% price increase on 1 April each year.
The billing system still carries the price from the year the contract was signed.
Every invoice since April is short by 3%, and the shortfall compounds the next April.
Evenrow shows the increase clause next to each invoice and the amount you were owed and did not charge.
Every record since yesterday, against the agreement that governs it.
Every customer invoice since yesterday, against the contract in force for that customer. Invoices at the contracted price are shown as clean. Invoices below it show the clause and the amount not charged. This page is about money you are owed. Trade terms against volume is about money you give.
What we need to start
Start with one process. Three weeks from understanding it to a working system. On your data if it is ready, on sample data if it is not. Read-only, on exports, no integration. Then your team sees every record of that process against the agreement that governs it, with the clause next to each one.
- One process
- Three weeks
- Data exports
- No integration