Supplier agreements against invoices
The commitment. Prices, discounts, rebates and payment terms agreed with each supplier.
The agreement says one thing. The system was told another.
In amendments, in price updates sent by email, in index-linked prices that were meant to move both ways. The system holds the price someone keyed in on the day the agreement was signed, and every invoice since has been checked against that, not against the agreement.
An index-linked price that only ever went up.
A packaging supplier's price is linked to a resin index, reviewed quarterly.
The index rose in the first quarter. The supplier sent a new price by email and the system was updated.
The index fell in the second and third quarters. No email came. The invoices kept the higher price.
Evenrow shows the index clause next to each invoice line and the difference for the two quarters.
Every record since yesterday, against the agreement that governs it.
Every invoice line that arrived since yesterday, against the supplier agreement in force for that line. Lines that match are shown as clean, with what was checked. Lines that do not match show the clause and the gap in money, waiting for a ruling.
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