How do you enforce a rate card without invoice disputes?
Enforce it at submission rather than at invoice. A rate validated before anyone reviews a profile is a rule; a rate questioned after the work is done is a negotiation you will usually lose. Define the unit and the inclusions before any figure is agreed, name who can approve an exception, and count the exceptions you approve.
Why enforcement at invoice always fails
By the time an invoice arrives, the work has been done, the worker has been paid by the supplier and your hiring manager has someone productive they would rather not lose. Every piece of leverage has moved to the other side of the table, and the conversation is no longer about what was agreed but about who blinks. Disputes settled at this stage tend to end in a credit note if you are lucky and a quiet concession if you are not, and either way the concession becomes the new reference point for the next assignment. The rate has to be checked at a moment when nothing has happened yet, which means at submission.
What has to be defined before any figure is agreed
The unit and the inclusions, and disputes almost always trace back to one of them being left implicit. The unit is what a rate buys β an hour usually, sometimes a day, and parties disagree about what a standard day contains more often than they expect. The inclusion list has to address every category that produces month-end arguments: statutory employer costs, insurances, any paid leave the engagement carries, overtime and unsocial hours, whether travel time is billable, how expenses are handled, and who supplies equipment. A rate card whose figures look competitive because it silently excludes several of these is not comparable with one that includes them, and a buyer comparing headline numbers alone will pick the least transparent supplier.
Where the check belongs in the submission flow
In front of the reviewer. A supplier proposing a rate outside the agreed band should meet a blocked field or a forced exception request at the point of entry, not a note somebody notices later. That single placement decision separates two very different products: blocked at entry means the card governs, while flagged for review afterwards means the card is advisory and the negotiation still happens, just with more paperwork. It is worth exercising deliberately in any evaluation β try to submit above the card and see what the system actually does β because it is described identically in most demonstrations and behaves very differently in practice.
Who is allowed to approve an off-card rate?
Somebody named, and not the person under pressure to fill the role. A scarce specialism, an urgent start, an unusual location or a requirement the card never contemplated will all arrive eventually, so the card should say what happens rather than leaving the parties to improvise. A workable exception route names the approver, states what evidence is required, and says whether the exception applies once or resets the reference point for that role. Leaving approval with the hiring manager who wants the person tomorrow is how a card erodes without anyone deciding to change it, and the erosion is invisible until somebody compares rates paid for equivalent work.
How do you tell a card has drifted out of date?
Count the exceptions. A card with a steady trickle of approved departures is doing its job, absorbing the cases no schedule can anticipate. A card where most assignments are exceptions has stopped describing the market it was built for, and the honest response is to revise it rather than to keep approving departures from it. Tracking the exception rate by category is the cheapest early warning available, because it distinguishes a card that is broadly right from one that is right in two categories and fictional in the rest. Level inflation is the quieter version of the same drift: if nobody can say what separates a mid-level from a senior person, the card gets repriced without anyone renegotiating it.
What the system cannot settle for you
Whether the rate is the right rate. A platform can hold the card, validate against it, force an exception through an approver and report what has been paid for comparable work across the organisation, and that visibility is often the real reason a buyer wants a card at all. What it cannot tell you is whether your figures reflect what the market currently pays, whether a supplier's margin is reasonable, or whether a category has moved since the card was set. Those are commercial judgements that need market evidence and a negotiation, and a system that enforces stale numbers precisely will simply produce a well-documented failure to fill roles.
Related glossary terms
Frequently asked questions
Should the rate card be visible to suppliers?
How often should a rate card be reviewed?
What if a supplier refuses to work at the card rate?
Does a rate card stop margin drift?
How many dimensions should a card have?
See how this works in a real applicant tracking system
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user Β· No credit card Β· Talk to a real hiring expert
See how much faster your team could hire
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan Β· No credit card Β· Talk to a real hiring expert