For a simple time-based service, the applicable rate is multiplied by eligible hours or days. The agreement may then introduce conditions such as minimum commitments, volume discounts, permitted expenses or premium rates.
A rate card is a structured list of proposed, published or agreed prices for defined roles, services or units of work. In enterprise procurement, an agreed rate card provides a pricing reference that may be included in a contract, statement of work or pricing schedule.
Rate cards make pricing easier to compare, negotiate and apply. Procurement can use them to assess proposals; Finance can check charges against agreed terms; business teams can understand the cost of the services they request.
Professional-services rates may vary by role, seniority, location, skill or delivery model. Two suppliers can use different titles for similar work, or the same title for different responsibilities. Those differences matter when comparing rates.
Other fields may cover volume conditions, expenses, approved premiums, discounts or adjustment rules. For day rates, the definition of a billable day also matters.
Public procurement schedules provide examples of role-based personnel rate cards and maximum day rates. The particular framework rules govern those rates; they are not universal pricing rules. [1]
For a simple time-based service, the applicable rate is multiplied by eligible hours or days. The agreement may then introduce conditions such as minimum commitments, volume discounts, permitted expenses or premium rates.
An amendment or new statement of work may establish different pricing. Its effect depends on scope, precedence, approval and effective dates; a change in circumstances does not automatically authorize a new rate.
Identify the supplier, role, location, billing unit, service period and quantity. Find the relevant master services agreement (MSA), statement of work (SOW), pricing schedule and amendments. Determine which provision governs, check its conditions, then compare the applied charge with the supported calculation.
Investigate differences before treating them as overbilling. An approved exception, valid amendment or different service scope may explain the variance. Keep the evidence and decision together.
Assume an agreed Senior Consultant rate of $200 per hour from January 1. An amendment signed in May changes that rate to $225 per hour from June 1. Both invoices below cover 100 hours of the same eligible service, with no other adjustments.
The invoice issue date alone does not settle which rate applies. In this scenario, the amendment changes pricing for work performed from June 1. Teams check the service period and governing wording before resolving the May exception.
This example is hypothetical and is not a customer result. The $2,500 difference is a potential adjustment for review, not money already recovered.
Pre-signature review asks whether proposed rates are commercially reasonable and consistent with applicable existing terms. Normalize roles, seniority, location, delivery mix, currency and billing units before comparing a new SOW with relevant historical agreements or approved market benchmarks.
For example, a proposed $220 hourly rate is 10% above a comparable historical rate of $200. That difference is a negotiation signal, not proof of overbilling. Procurement should check whether responsibilities, skills, delivery conditions or other justified differences explain it.
Headline rates can also hide changes in total cost. A larger onsite share, an additional management fee or a new skill premium may increase the effective price even when the base role rate looks unchanged.
Rate validation helps teams investigate pricing discrepancies, unsupported premiums and outdated rates. A comparable history of supplier rates supports negotiations and renewal preparation. Traceable pricing evidence helps Finance explain accepted charges and questioned differences.
Two review questions should remain distinct: does a proposed rate warrant negotiation, and does an applied rate follow the governing agreement? They require different evidence and lead to different actions.
A rate card sets out pricing information. The agreement establishes the rules under which it applies, including scope, precedence, amendments, adjustments and exceptions. The rate card may be part of that agreement or incorporated by reference.
RateIQ Sentinel supports both proposed-rate review and ongoing rate adherence. It brings rate-card information into commercial context, helping teams compare incoming SOWs with relevant contract history and benchmarks, and investigate differences between agreed and applied rates.
Normalizing role labels, seniority, location and delivery conditions makes comparisons more meaningful. Findings should connect back to the rate schedule, amendment or other supporting evidence so category teams can negotiate a proposal or review an applied-rate exception.
This is part of SimpliContract's Commercial Intelligence foundation, which connects contract terms with supplier, spend and transaction context.
The analysis depends on the connected evidence and configured use case. Procurement and Finance retain responsibility for negotiations, approvals and any recovery action.
The terms can overlap. A rate card often organizes prices by role, service or unit of work. In enterprise agreements, its value depends on the conditions and contractual evidence attached to those prices, rather than the label alone.
They may be fixed for a defined period, negotiable before agreement, or adjustable under specified terms. Check effective dates, indexation provisions, scheduled changes and amendments before applying a different rate.
Determine which card governs the specific supplier, service, location and period. Contract hierarchy, scope and precedence rules may resolve the question. If the evidence conflicts, route it for review rather than choosing the newest document automatically.
Benchmarking compares a proposed rate with relevant reference rates to support negotiation. Validation checks an applied rate against the governing agreement. A benchmark difference is not automatically a contractual breach.
Yes, when the underlying responsibilities, seniority, skills and delivery conditions are sufficiently comparable. Matching titles alone can produce misleading results. Normalization should preserve meaningful differences and expose uncertain comparisons for review.
Procurement assesses proposals and supplier negotiations. Finance reviews charges and cost differences. Legal helps resolve governing terms. Operations confirms what services were delivered and which conditions applied.
[1] Crown Commercial Service RM3804 framework terms and rates schedules. An illustrative public procurement reference for personnel rate cards and maximum day rates, not a current purchasing recommendation.
What is Commercial Intelligence. SimpliContract's explanation of connected commercial evidence and governed action.
Choose an incoming SOW or a set of applied rates. Bring the relevant contract history, pricing schedules and transaction details together to identify the questions worth reviewing. See Agentic Solutions for RateIQ Sentinel.