Blake
← Blog
revenue, moneybird, Blog, Product

Won is not paid

Your pipeline records what people said they would do. The invoice records what happened. Blake's Revenue tab syncs Moneybird hourly, matches each invoice back to the company you already know, and shows collections next to the deal. Including the unglamorous case: an overpaid invoice now says so, instead of reporting a negative amount outstanding. Won is a stage. Paid is a fact.

Your pipeline is a record of what people said they were going to do, which is not a criticism, because forecasting is the job. But there is a moment every sales team knows and very few CRMs acknowledge: the deal moves to Won, the stage turns green, the number goes into the quarter, and the CRM stops paying attention. Some weeks later finance mentions that two of those invoices have not actually been paid. Nobody lied. The deal was won. It just was not money yet.

The two systems problem

Almost every company runs this on two screens. The CRM holds the pipeline, with its stages and amounts and close dates and the story of the relationship, while the accounting system holds the truth about what was invoiced, what was collected and what is overdue. They describe the same customers and they almost never agree, because nobody ever introduced them. So you get the familiar routine where somebody exports a list, somebody else checks it against the ledger, and a third person asks whether the Acme number is the signed amount or the paid amount, to which the honest answer is that it depends which tab you are looking at. The pipeline says what should happen and the ledger says what did, and between them sits the gap where revenue quietly goes missing.

What Blake does about it

Blake has a Revenue tab and it does not ask you to type anything into it. Connect a Moneybird account and Blake pulls your invoices every hour across the whole history rather than just the current quarter, then does the boring part nobody wants to do by hand, matching each invoice back to a company already in Blake using the contact email domain and the name. Where it finds a match the invoice attaches to the company you already know. Where it does not, you can either create the company from the invoice, which is how a customer that finance knew about but sales never logged finally appears, or point Blake at the right company yourself, a decision it remembers so that every future sync gets it right without asking again. The invoice PDFs come across too, so you can open the actual document without going to find it in the accounting system. What you end up with is one screen showing revenue for this year, the last ninety days or this month, with drafts excluded, because a draft invoice is not revenue and pretending otherwise is how forecasts rot.

The unglamorous detail

An invoice can be paid for more than it is worth. A customer settles two invoices with one transfer, somebody adds a digit, a credit gets applied in the wrong direction. It is not exotic, it just happens, and most systems handle it badly. Blake used to as well: an overpaid invoice showed nothing useful in the list and the detail page reported a negative amount outstanding, which is not a thing. Minus two hundred euros open. What is anyone supposed to do with that? Now it says two hundred euros overpaid, in its own colour, kept visually distinct from an invoice that is genuinely part paid and still owed, with the open figure clamped at zero because you cannot owe less than nothing, and a summary card that appears only when there is credit actually outstanding and calls it what it is, which is credit due back. None of that goes on a pricing page. It is simply the difference between a number you can act on and a number you have to go and ask somebody about.

Blake is not an accounting system and has no ambition to be one. It does not raise invoices, chase them or do your VAT, and Revenue is admin only, because not everyone on a sales floor needs to see collections. What Blake adds is the join, and the reason it belongs in the CRM rather than in finance is simple: the person who needs to know that Acme has not paid is the person about to call Acme about renewal, and putting that fact behind a different login owned by a different department guarantees the call happens without it. A CRM that only tracks pipeline is telling you half the story and it is the optimistic half, because everything in there is a plan, while the invoice is the only object in the whole chain that records what actually occurred.

Won is a stage. Paid is a fact. The deal is not done when it is won, it is done when it is paid.