An invoice can be mathematically correct and properly approved while still being difficult to govern. The reason is simple: invoice language often evolves independently from contract language.
Four dimensions of alignment
- Description: Does the invoice identify the contracted service clearly?
- Rate: Does the billed amount match the current authorized rate?
- Frequency: Does billing occur at the agreed interval?
- Quantity: Are units, visits, locations or treatment counts documented?
Worked example
A contract distinguishes “Weekly Maintenance” from “Weekly Proactive Service,” each with a different unit cap and price. Both invoice lines are labeled “Weekly Pest Maintenance Service.” The dollar amounts may be correct, but a reviewer without the proposal cannot tell which service occurred. That is an invoice-design governance weakness.
Why descriptions matter
Clear descriptions allow accounting, operations and future reviewers to understand what was purchased. Ambiguous descriptions transfer knowledge from the record into individual memory.
How to build an alignment test
Create a contract service dictionary: one row for each recurring and non-recurring service, with authorized description, rate, unit, frequency and source clause. Map each invoice line to that dictionary and flag unmapped or ambiguous items.
What not to conclude
Misaligned language does not prove an improper charge. It identifies a documentation condition that makes the relationship harder to review and control.
Frequently asked questions
Does unclear wording mean the invoice is wrong?
No. It means the invoice is harder to verify without additional records.
What should an invoice description include?
Enough detail to identify the contracted service, location, frequency or quantity, and any non-recurring work.
See the relationship, not just the invoice.
SGG reviews contracts, invoices, amendments and recurring service patterns across the organization.
Request a Governance Review