A closed deal that never became an invoice: where it breaks and how to check
A deal is marked won. Sales moves on. Weeks later finance notices that no invoice was ever sent, or that the invoice carries the wrong plan, the wrong amount or a start date a month too early. Nothing turned red. Every tool did what it was set up to do; the gap sat between them.
This guide lists where the hand-off breaks, a worked example with made-up numbers, and a check you can do by hand in about an hour.
Where the hand-off breaks
These are our reading of how such hand-offs are usually built, not a measured share. Check each against your setup.
1. A stage change that triggers nothing. The billing step listens for one stage, say "Closed won". Then the stage is renamed "Signed", a second pipeline is added, or deals are moved by a bulk edit or an import that the trigger does not see.
2. A renamed or retyped field. The plan field had the value "Pro". Someone changes it to "Professional". The billing side no longer recognises it, so the invoice uses a default plan or is not made. The same happens when a field is deleted and recreated. See also the guide to renamed fields.
3. A duplicate customer record. The billing tool already has "Acme Ltd" and now gets "ACME Limited". The invoice lands on the old record, or the payment history splits in two.
4. A missing contract term. Start date, term length, discount or purchase-order number is blank in the CRM, because it lives in the signed document. The invoice is built with a default, or waits for a human who does not know it is waiting.
5. A change after the deal is won. The amount is lowered or a seat is added after the stage changed. The invoice was made from the earlier number and nobody updates it.
A worked example (made-up numbers)
This is an example, not a real company. In one month a team marks 40 deals as won. The billing tool shows 37 new invoices.
- Three won deals have no invoice, worth 21,600 in total. One was moved to won by a bulk edit. One had a plan value renamed the week before. One matched a customer record that had been merged, so the invoice went nowhere.
- Of the 37 invoices, three do not match the deal. Two use the amount from before a late discount. One starts a month before the contract does.
- Nobody saw any of it until month end, when two customers asked where their invoice was.
The other 34 deals went through. That is the usual shape: mostly fine, quietly wrong in a few places.
How to check it yourself
About an hour, once a week. You need two exports and a spreadsheet.
- Export the won deals from the last eight weeks: deal ID, company, close date, plan, amount, start date, term.
- Export the invoices or subscriptions created in the same window: customer, plan, amount, start date, created date.
- Match them. Use a contract number or customer ID if both tools carry one. If not, match on company name after lowercasing it and removing "Inc", "Ltd" and the like.
- Make three lists. Won deals with no invoice. Invoices with no won deal (renewals and manual invoices are often fine, but know why they are there). Matched pairs where plan, amount or start date differ.
- Give each item a cause from the five above. The causes repeat, which makes them fixable.
- Count the blanks. What share of won deals have an empty start date, term or discount? A rising share points at the form or the stage, not at billing.
- Look for twins. Sort the billing customer list by normalised name and spot near-identical neighbours.
Do not count a deal as missing until it is past your agreed invoicing delay, say five working days.
Also note the typical days from close to invoice. A number that creeps up is an early warning.
Making it less likely
- Make the contract terms required before a deal can move to won.
- Name an owner for the stage and plan values, so a rename reaches the billing step's owner first.
- Send late changes through one visible step, so a new amount reaches finance on purpose.
Questions people ask
Why was a won deal never invoiced?
Most often nothing started the hand-off: the stage was renamed, a bulk change skipped it, or a required term was blank. Less often the invoice went to the wrong customer record.
How often should sales and finance compare the two lists?
Weekly is our suggestion. Monthly means a whole billing cycle can pass before a gap shows.
The same checks fit any hand-off
For any hand-off between tools, count what left and what arrived, compare the fields that matter, look for twins and ask what changed since last week. Navceed is built around that idea. Today you describe a workflow in plain words, and Navceed plans it and shows a dry run. Every approval and run is kept in a history. Changes inside your own tools are switched on one account at a time, early users first, and nothing changes until the person who owns the data says yes. That approval is tied to the exact change shown. A billing tool cannot be connected yet, so for this hand-off the weekly check above is the one to use. Watching it for you is coming next.
Watching this all the time
Navceed is being built to watch hand-offs like this continuously: follow each record through every step, notice when one breaks, show the cause in plain words and prepare the fix for the data owner to approve. Today it works on a demo with made-up data; you can connect your own tools (Navceed walks you through creating the key yourself), and changes inside your own tools are switched on one account at a time, early users first, and nothing changes until the person who owns the data says yes. Take the workflow break check on your own setup.