The phrase "this is just our standard paper" is the tell. True Forward and broad audit rights are the most negotiable, and most overlooked, clauses in a financial-services ITSM contract, because they convert your own growth into the vendor's revenue on the vendor's timetable. The buyer-side job is to treat them as commercial terms, not legal furniture: cap them, define usage tightly, and put a reconciliation window in your control. This article sits under our overview of ITSM contract negotiation by industry.
What is True Forward and why does it target banks?
True Forward, used most visibly by ServiceNow, reconciles your actual usage up to your entitlement at each anniversary and bills the increase forward for the rest of the term. The catch is that it is one-directional: if usage rises you pay more, and if it falls you get nothing back. Banks are the ideal target because their estates spike with seasonal hiring, M&A, regulatory programmes and project surges, and every spike that crosses your entitlement gets captured and locked into the run rate. The full mechanism is explained in the ServiceNow True Forward mechanism and how to protect against it.
Book a contract negotiation review →What the vendor argues versus what to counter with
| What the vendor argues | What it really costs a bank | What to counter with |
|---|---|---|
| "True Forward is standard, non-negotiable" | Every usage spike billed forward, no credit when it falls | Cap the annual True Forward percentage and add a true-down right. |
| "A user is anyone who touches the platform" | Service accounts, contractors and transient logins all counted | Define a user precisely; exclude system and short-lived accounts. |
| "Audit rights protect both parties" | Open-ended audits and surprise true-ups mid-term | Cap frequency, require notice, confine findings to forward terms. |
| "You can true up at any time" | Reconciliation on the vendor's schedule, at list price | Fix a single annual window at your negotiated rate. |
How does a bank cap True Forward?
You rarely strike the clause out entirely, but you can blunt it until it stops being a threat. Cap the annual True Forward at a fixed percentage so a hiring surge cannot reset your run rate without limit. Secure a true-down or carry-credit right so a fall in usage is recognised rather than pocketed by the vendor. Fix a single annual reconciliation window at your negotiated rate, not list. And require written notice before any reconciliation so finance is never surprised. The detailed playbook is in how to negotiate True Forward protection.
Why does the definition of a user decide the bill?
In a bank, the largest hidden cost in True Forward is not headcount, it is the definition. If "user" sweeps in service accounts, integration accounts, contractors and one-time logins, your counted usage balloons far past your real fulfiller population, and the True Forward bills the gap. Pin down what counts as a user in the contract: named, active, human fulfillers, with system and transient accounts excluded by name. This single definition often saves more than any rate discount, and it is the quiet lever banks most often leave on the table.
Where do audit clauses bite a bank?
Audit rights and True Forward work as a pair. An open-ended audit gives the vendor the route to find the usage, and True Forward is the mechanism that bills it. Banks grow through acquisitions and absorb other institutions' estates, which is exactly when an uncapped audit becomes expensive. Cap the audit frequency, require notice, and confine any finding to forward terms rather than retroactive penalties. The general method is in how to protect against ITSM audit clauses, and the combined treatment of both clauses sits in our gated ITSM contract terms and True Forward guide.
The buyer-side sequence for a bank
- Define the user. Named, active, human fulfillers only; exclude service and transient accounts.
- Cap True Forward. Fix the annual percentage and add a true-down or carry-credit right.
- Control reconciliation. One annual window, your negotiated rate, written notice required.
- Limit the audit. Cap frequency, require notice, confine findings to forward terms.
- Cap the uplift and close. Lock a capped annual increase so the saving survives renewal.
This is the same Map · Benchmark · Leverage · Close method behind every engagement. Across 500-plus ITSM negotiations and more than $420M in contract value, the firm averages a 30% reduction, and bank deals land in that range once True Forward is capped and the user definition is pinned down.
Our gated contract terms and True Forward guide includes the cap language, true-down clauses and user-definition wording banks use to defuse the mechanism.
What to do next
If your bank is renewing an ITSM contract, do not accept True Forward and audit rights as standard paper. Pin down the user definition, cap the True Forward, control the reconciliation window, and limit the audit before you sign. We run this end to end on fixed fee or gainshare through our contract negotiation service.
Frequently asked questions
- What is True Forward and why does it hit banks hardest?
- It reconciles usage up to entitlement each year and bills the increase forward with no credit when usage falls. Bank estates flex with hiring and M&A, so spikes get captured and locked in. Cap it and define usage tightly.
- Can a bank cap or remove True Forward?
- Rarely removed outright, but you can cap the annual percentage, define what counts as a user, add a true-down right, and require notice and a fixed reconciliation window.
- How much can a bank reduce an ITSM contract?
- It varies, but across our engagements we average a 30% reduction from seat right-sizing, True Forward and audit limits, usage definitions and a capped uplift.
Book a contract negotiation review.
We cap True Forward, pin down the user definition, and limit the audit clause before you sign. Fixed fee or gainshare.
Book a contract negotiation review →