Invoice and payment tracking: where the money leaks between an accepted quote and your bank account

Invoice and payment tracking almost never starts life as a software problem. Sales go well, the quote is accepted, the work gets done, the invoice goes out. Then one month cash gets tight and somebody asks the question: "How much are we owed?" The answer is assembled from three places (the bank statement, the invoice folder, somebody's memory) and comes out different every time. The cause is not laziness. Money is leaking quietly out of specific links in the chain that runs from a sale to a payment.

This guide follows that chain end to end, from the moment a quote is accepted to the moment cash lands. The scenario continues the one in our automated follow-up guide: the 24,000 EUR facade panel quote sent to Northgate Building Supplies has been accepted. (Demo data.) That is where the real work starts, because an accepted quote is not collected cash.

The five leaks in the chain

There are six links between a quote and your bank account, and the money does not disappear inside the links. It disappears in the gaps between them. The diagram below shows one month of leakage at an eleven-person wholesaler.

What the five have in common is that none of them is a mistake. Every one is a missing record. Nobody typed a wrong number; a step simply never got written down.

• 1. The quote was accepted, the order never opened. Approval usually arrives as one sentence in an email: "Looks good, go ahead." If that sentence does not become a record, the work sometimes starts and the invoice never does. The rule is simple: every approval, spoken or written, becomes an order record the same day.
• 2. The invoice went out with an untracked due date. The date is printed on the document and lives on no list. A due date only means something where something counts days for you.
• 3. The due date passed and nobody called. If the first week of a delay is silent, the customer starts deciding where you sit in their payment queue. No bad faith required: the supplier who follows up gets paid first.
• 4. A partial payment was never recorded. The customer sent 15,000 EUR against a 28,800 EUR invoice and nobody put it on the record. Two weeks later they are either treated as paid in full or chased as if they had paid nothing. The first costs money, the second costs the relationship.
• 5. Nobody knows who owes what at month end. The sum of the other four. Without one list there is no receivables management, only the receivables somebody remembers.

What to record at every link

You do not close these leaks with more discipline. You close them by deciding in advance what gets recorded at each step. The table below is the trail a job should leave on its way from accepted quote to collected cash.

Row five is the one everyone skips. If the call is not written down, two weeks later the same customer is either called twice or not at all. "We will pay on the 20th" is not a promise, it is a date, and until it is on the record it does not exist.

Ageing: how late are we, at a glance

Receivables management has one foundational report and it is called ageing: it splits open invoices into buckets by how far past the due date they are. Your total may be 128,400 EUR. The question that matters is which bucket that total is sitting in.

Read it right to left, not left to right. Starting with the total is misleading because it is reassuring. Start with the rightmost bucket: anything past 90 days has stopped being a collections issue and become a decision. Here is what each bucket means and what it asks of you:

Open the ageing report weekly, on the same day. The direction of travel matters as much as the number: if the 31 to 60 bucket grows two weeks running, the problem is not one customer, it is your reminder discipline.

The reminder discipline: from polite to formal

The tone of a collections conversation should be set by the number of days late, not by who happens to be sending it. The five tiers below make two different people say the same thing, which is what actually protects the relationship.

Three rules keep this table standing. First, reminders must not depend on a person: nothing should stop when someone goes on holiday. Second, every contact goes on the record, so the second call starts from what was said on the first. Third, you should know before quoting a customer who already has an overdue invoice. The long version of making follow-up the system's job is in the automated reminders guide; for the document at the start of the chain, see how to write a business quote.

Partial payments and reconciliation

Back to Northgate Building Supplies: 24,000 EUR of line items, 28,800 EUR with 20% VAT, payable in 30 days. The customer sends 15,000 EUR. In a business without a recording habit that one transaction opens three different errors: it is treated as paid in full, it is chased as if nothing arrived, or the remaining balance is calculated wrong.

The correct handling is simple: every payment is recorded as a line attached to the invoice it paid. Amount, date and method go in; the remaining balance falls out of the total minus the payments. In this case the balance is 13,800 EUR and the invoice moves to partially paid. It looks like a small distinction, and the entire month-end answer to "who owes what" rests on it.

The monthly reconciliation is a five-minute job that looks at three numbers:

1. Total invoiced this month. What did the business produce?
2. Total collected this month. What came in? These two do not need to match, because collections include invoices from earlier months.
3. The change in total outstanding since the start of the month. If it grew, either sales sped up or collections slowed down. The ageing report tells you which.

With larger customers, reconcile in writing twice a year: send your list of open invoices and compare it to theirs. Most disputes come not from bad faith but from two people looking at two different invoice numbers.

The e-invoice question, answered honestly

A boundary is worth drawing here, because this is where small businesses get confused most often. Ohana360 has no e-invoice or tax-authority integration. The invoice record in the system is a commercial tracking document: it carries the line items, the tax, the due date and the payments, it saves to PDF from the browser print dialog, and its footer says plainly that it does not replace a legally issued invoice.

In practice you run the commercial tracking and the collections discipline in the CRM, and issue the official document from your accounting setup. If you want both numbers on one record, add a custom field called "Official invoice no" to the invoice.

The first 7 days: a setup plan

The most common way this migration fails is trying to move every historical invoice at once. One hour a day for seven days is enough.

On day eight, every new invoice comes out of the system. Running both in parallel helps in week one and hurts in week two: nobody writes things down twice.

How the flow works in Ohana360

Finance360 owns the order, invoice and payment links of this chain; the quote lives on the opportunity record in Sales360. Here is what it does, without inflation, and what it does not do, without hiding it.

• The quote document: generated with Create Quote from the line items on an opportunity. It carries a quote number, the customer and contact, the quote date, validity (from the "Quote Validity (days)" setting in Setup), the preparer, the items, subtotal, VAT and grand total. Print / PDF saves it for sending. Note: a quote is not stored as a separate record; it is the opportunity's document.
• Orders: in the New Order screen, "Fill from opportunity" pulls a won opportunity and its line items in automatically. The order keeps a number, a date and a status (Draft, Approved, Invoiced, Cancelled).
• Invoicing: the Invoice button on the order list opens a modal that asks two things only, payment terms in days and the tax rate. Subtotal, tax, grand total and the calculated due date appear instantly. The invoice number and the line items carry over from the order.
• Due dates and statuses: invoice statuses are Draft, Sent, Partial, Paid and Cancelled. An invoice past its due date with a balance left is shown as Overdue automatically, with the number of days late next to the due date.
• Add Payment: amount, method (bank transfer, card, cash, cheque) and date. The remaining balance is recalculated at once; while a balance remains the status is Partial, and it becomes Paid at zero. Every payment is also listed on the Payments tab with date, invoice, customer, method and amount.
• The home page: two blocks. The due-date strip lists invoices falling due in the next 7 days, flagging today and anything already late. The Invoices needing attention list ranks open invoices by reason: days overdue, days until the due date, or a large remaining balance.
• Printable invoice: a clean document with your logo and company details, a payment breakdown, the remaining balance and a footer stating that it is for information and does not replace a legally issued invoice.
• Not included: e-invoice or tax-authority integration, automatic bank statement matching, ledgers and customer account statements. Those stay where they are today.

Want to see the flow in 57 seconds?

Putting the reminders on rails

The flow engine ships with one collections template: "Overdue invoices to a collection task". It is a scheduled flow, it runs at 09:00 every morning, its condition is "due date in the past and status is not Paid", and its actions open a call task due today for the record owner and send them a notification. It fires once per record, so the same invoice does not generate a new task every morning.

You build the remaining tiers yourself on the same screen. Date conditions in scheduled flows offer three options: "in the past", "within the next X days" and "older than X days". The polite pre-due reminder uses the second (next 3 days); the 15 and 30 day tiers use the third.

Which reports to build

Two finance reports come ready in the report list: "Invoice amount by status" and "Order amount by status". You build the rest in the report builder, drop them on a dashboard and add an email subscription. The reportable fields on the invoice object are: number, status, amount, VAT, issue date and due date. Date fields group by day, week, calendar month, quarter and year.

One honest boundary: the remaining balance is not a field in the report builder, it is a calculated value. You see it on the invoice list and on the invoice record; the ageing buckets come from sorting that list by due date, or from exporting it and splitting it in a spreadsheet. The figure you report on is the invoice total.

If your customer records still live in spreadsheets, start the migration there: the Excel customer tracking guide includes a template and a migration order. If sales are moving into the same place, the sales tracking software guide is a good starting point. Current numbers are on the pricing page, and you can request a demo to try it with your own data.

Frequently asked questions