Skip to content

Our applications have always been paid, so nobody has checked they're valid

Until the month somebody reads the payment clauses and finds the form, the route or the named recipient was never right.

01Before signature
02The cycle running
03The notice window
04Payment falls due
05Cycles behind you
06Dispute running
You are here: The cycle is running on habit, not on the contract.

What's happening?

Years of applications going in and money coming back feel like proof the paperwork works. It is not. It is proof the relationship works. The application format was inherited from the last job, the email goes to whoever always got it, and nobody has read the payment clauses since the contract was signed, because there has never been a reason to.

The month that changes is the month goodwill runs out: a new commercial team upstream, a funding squeeze, an account that suddenly needs managing down. The first challenge that lands is rarely about the valuation. It is about validity: was the application served to the recipient the contract names, in the form it prescribes, on the dates it sets?

An application that fails those tests may never have set the payment machinery running at all, and the rights that follow from a valid application, including silence turning into a payable sum, can fall away with it.

This is cheap to find out in a quiet month and expensive to find out in a dispute. Mapping the clauses once, and fixing the form, the route and the dates against them, is a small job that every future cycle then inherits.

The solution

One pass through the payment clauses now, before a bad month does it for you.