Skip to content
Collections & Invoicing

Accounts receivable: why selling isn't enough if you can't see what's pending

A business can post its best sales month on record and still scramble to make payroll. The difference is almost never how much it sold — it's how much of that it can see, chase and actually collect.

July 2026 · 8 min read · Metrava Systems

In short
  • A closed sale is a promise of income; the payment is the income. Between the two runs a journey almost nobody is watching.
  • Receivables turn invisible when invoices live as loose PDFs, nobody knows what's overdue, and collecting depends on someone remembering.
  • Leadership needs three views every week: expected vs collected by period, overdue by age, and who owes what.
  • The status of each invoice — draft, sent, paid, overdue — decides which collection conversation happens today, without guessing.
The real problem

Selling fills the pipeline. Collecting fills the bank.

Think about the invoice that went out five weeks ago. The work was delivered, the client was happy, someone exported the PDF and emailed it. It has lived in the sent folder ever since — and nobody has looked at it again. The client isn't refusing to pay. Nobody has reminded them that they owe.

When cash gets tight, the first instinct is to sell more: another campaign, another channel, more pressure on the sales team. But in plenty of businesses that sell well, the problem isn't the sale — it's everything that happens, or fails to happen, between the client's "yes" and the money in the bank. Selling and collecting are two separate acts, weeks apart, and only one of them gets celebrated.

Every invoice, with or without a system, travels the same path:

When that journey isn't visible, the business ends up financing its own clients — interest-free, and without ever deciding to. These are the signs that your accounts receivable have gone invisible.

The signs

Three symptoms of invisible receivables.

01

Invoices as loose PDFs

Each invoice gets built in a document, exported to PDF and sent by email or WhatsApp. From that moment it exists in a folder — not in a living list with amount, status and due date. To know how much you're owed in total, someone has to open the files one by one and add them up by hand.

SIGNAL → Total accounts receivable doesn't exist as a number: it has to be rebuilt every time somebody asks for it.

02

Nobody knows what's overdue

Invoices carry due dates, but nobody is watching the calendar on their behalf. Without an aging breakdown — what's 15, 30 or 60 days past due — every debt looks the same, and the 60-day invoice gets exactly as much attention as yesterday's: none.

SIGNAL → You find out an invoice went overdue when you check the bank, not when it went overdue.

03

Collecting depends on someone remembering

There's no task, no date, no owner: there's an intention. "I'll message them this week" competes with everything urgent in the day — and loses. The client who would have paid at 30 days with one reminder ends up paying at 75, not out of bad faith, but because nobody asked in time.

SIGNAL → Payments arrive when the client decides to pay, not when the business decides to collect.

"What you can't see, you can't collect. And every week an invoice goes unseen, your business is financing the client without ever having decided to."

— Metrava Systems · Commercial infrastructure diagnostics

How much of what you've already sold is still waiting in a folder of PDFs? The diagnostic helps you see it in 5 minutes.

Start diagnostic
The minimum board

What leadership should see every week.

You don't need a finance department to govern collections. You need three views, kept current, in one place. If the weekly meeting can't answer these three questions in five minutes, collections are running blind:

01

Expected vs collected

How much was supposed to come in this period, and how much actually did? The gap between those two numbers is the real health of your cash — and the first figure leadership should demand every week.

02

Overdue by age

What's overdue, and for how long? Eight days is not eighty. The aging breakdown — 0–15, 16–30, 31–60, 60+ — ranks the urgency and decides where to collect first.

03

Who owes what

Which clients hold the debt? Seeing what's pending by client turns "we're owed a lot" into a list of concrete conversations: each with a name, an amount and a next step.

Status changes everything

Four statuses, four collection conversations.

An invoice without a status is a file. An invoice with a status is an instruction: it tells the team which conversation happens today, in what tone, and with what facts — no debate, no guessing.

DRAFT

It exists, but it hasn't gone out

Every day an invoice sits in draft is a day the payment clock hasn't even started ticking. The most expensive delay usually isn't the client who pays late — it's the work that was delivered and never invoiced at all.

THE CONVERSATION → It's internal: "This was delivered on Monday — why hasn't the invoice gone out?"

SENT

It's in the client's court

The due date is running. Here the tone is service, not complaint: confirm it arrived, resolve any questions, and get the agreed payment date in writing. A collection that starts well almost never ends in conflict.

THE CONVERSATION → "We sent it on the 3rd — did it come through okay? It's set for the 18th."

OVERDUE

The deadline passed and the tone shifts

Firm, specific, and backed by facts: issue date, due date, days late. Without a record, the claim sounds like an opinion and gets negotiated; with a record, it's a fact and gets scheduled. Data collects better than insistence.

THE CONVERSATION → "The invoice went overdue 12 days ago. Shall we schedule it for this week?"

PAID

The cycle closes and leaves a data point

There's now a record of how long that client took to pay. That history — who pays on time and who pays at 90 days — is what decides who gets extended terms and who gets asked for a deposit on the next contract.

THE CONVERSATION → The next negotiation over terms starts from your history, not their promise.

Where the invoice is born

The invoice shouldn't be born in another tool.

Much of the invisibility is decided at birth. If the proposal lives in a document, the contract in an email thread, and the invoice in a separate program, reconciling them is manual work — and manual work is the first thing abandoned when the week gets messy. The invoice should be born connected: from the contract that defines what was agreed, and from the client who carries their payment history.

The well-born invoice

  • Inherits the amount, terms and configurable currency from the proposal that was already approved — nothing re-typed.
  • Stays linked to the contract that justifies it and the client who owes it, with their full payment history.
  • Is born with a due date and a collection owner — not with the hope that somebody remembers.
  • Its status — draft, sent, paid, overdue — is visible in the same place where the team works every day.

When the invoice is born connected, collecting stops being an act of memory and becomes a consequence of the system: every document knows where it came from, who owes it, and what needs to happen to it this week.

From the article to the system

How Metrava OS connects it.

In this case, Metrava OS makes what is pending visible: every invoice linked to its client, with status and aging —until the money comes in.

01

Capture the opportunity

Every potential sale enters the system from the first contact, with its source and estimated amount. What you'll be collecting tomorrow starts existing as data today.

02

Assign an owner

Every account — and every pending payment — has an owner with a name. "Someone should follow up on this" becomes "this is Maria's and it's due on the 18th."

03

Create the follow-up

Collection reminders are dated tasks, not intentions. The system remembers on the team's behalf: before the due date, at the due date, and at every aging threshold.

04

Connect the proposal

The approved proposal isn't copied by hand into another tool: it's the direct basis of the invoice, with the amounts and terms the client already agreed to.

05

Link the invoice

The invoice is born tied to the contract and the client, with a visible status — draft, sent, paid, overdue — and configurable currency. No loose PDFs in folders.

06

Report to leadership

Expected vs collected, overdue by age, and pending by client — the full weekly board, without anyone having to build it by hand.

Next step

Find out how much of your sales are trapped in collections.

The diagnostic reviews how your operation captures, follows up and collects — and hands back your blind spots, prioritized. Free and with no obligation.

Start diagnostic See Metrava OS