Reply taxonomy that speeds cash (late / dispute / missing PO / AP backlog)

Most teams lose time in the inbox.

They send a reminder. The customer replies. Then the reply sits. Or it gets forwarded with no clear ask. A week later, the invoice is still unpaid and everyone feels awkward.

A simple reply taxonomy fixes that. It turns replies into actions. It also keeps your tone calm, because you always know the next step.

Why reply handling is the fastest lever in receivables

Cadence matters, but cadence alone does not collect cash. Replies do.

A good reply system does three things:

• It identifies the real reason payment is stuck.
• It assigns the right owner fast.
• It sets the next follow-up date so nothing drifts.

ICAEW’s guidance on chasing debtors starts with basics: check the invoice is accurate and received, then chase informally first. That only works if someone reads the response and acts on it.

The four tags that cover 90% of replies

You can build an entire AR operation on four tags:

1. Late
2. Dispute
3. Missing PO
4. AP backlog

If you use different words internally, fine. The point is that each tag has a clear “done” condition.

Late

What it means: They agree they owe it. They will pay. They have not paid yet.

Common signals in replies:

• “Paying next week.”
• “We missed the run.”
• “Can you resend the invoice?” (and nothing else is wrong)

Fastest path to cash:

• Get a payment date in writing.
• Ask which payment method they use (ACH/bank transfer/card/portal).
• Follow up on the date, not “soon”.

Done condition:

• Payment lands, or you get a confirmed escalated route (manager/AP lead).

Dispute

What it means: They claim something is wrong (price, scope, usage, renewal, VAT, entity, contract terms).

Common signals:

• “We did not approve this.”
• “We cancelled.”
• “We were billed twice.”
• “This should be monthly, not annual.”

Fastest path to cash:

• Pause chasing language. Switch to resolution language.
• Ask for the exact issue and evidence.
• Assign an internal owner who can decide (Support, CS, Sales, Product, Finance).
• Set a target resolution date.

Done condition:

• Dispute resolved and invoice payable (or credit issued, and the case is closed).

Missing PO

What it means: They cannot pay until a PO exists or the invoice has a PO number.

Common signals:

• “Please add our PO.”
• “We need a PO raised first.”
• “This will be rejected without PO.”

Fastest path to cash:

• Identify who raises the PO and the process timeline.
• Collect the details they need (vendor name, address, tax info, banking, line items).
• Reissue the invoice with PO number if required.
• Track it like a workflow, not a reminder.

Done condition:

• PO issued and accepted against the invoice (or invoice submitted in the required system).

AP backlog

What it means: The invoice is valid. It is stuck in their queue, approval chain, or payment run.

Common signals:

• “We’re backed up.”
• “It’s in processing.”
• “Next payment run is Friday.”
• “Waiting for approval.”

Fastest path to cash:

• Get the payment run date (and cut-off time).
• Confirm invoice is approved (or ask who is approving).
• Ask for remittance advice when paid.
• If amount is material, request prioritisation politely.

Done condition:

• Payment date confirmed on their payment run, or approval owner identified with a deadline.

The BSB way: read every reply, tag the reason, push blockers

Our edge is not sending reminders. It is what happens after the reply.

We plug into your tools, read every reply, tag the reason, and push blockers to your team so cash keeps moving.

That “push blockers” step is where time disappears for most businesses. We make it concrete:

• One message.
• One owner.
• One ask.
• One due date.

The triage checklist (what to capture in 60 seconds)

When a reply comes in, capture these fields before you do anything else:

• Tag (late / dispute / missing PO / AP backlog)
• Invoice number + amount
• Who replied (name + role)
• One key detail:
  • Late: payment date
  • Dispute: dispute reason + evidence needed
  • Missing PO: PO owner + steps
  • AP backlog: next payment run date or approval owner
• Next action owner (your team or theirs)
• Next follow-up date

If you do only this, your AR will feel 10x calmer.

Copy-paste taxonomy table

Tag	What it means	What you must get from the reply	Owner (internal)	SLA	Next step
Late	Owed, just delayed	Confirmed pay date	AR owner	Same day / 1 biz day	Calendar follow-up on the date
Dispute	“We don’t agree”	Exact issue + who can decide	CS/Support/Finance	Same day	Route internally, set resolution date
Missing PO	Can’t pay without PO	PO contact + process + ETA	Sales Ops / Finance Ops	1 biz day	Provide docs, reissue invoice with PO
AP backlog	Valid but stuck in queue	Payment run date or approval owner	AR owner + exec sponsor if needed	1 biz day	Confirm inclusion in next run, follow-up on cut-off

Email snippet: “AP backlog” follow-up that gets a date

Subject: Confirming pay run date for invoice 7812

Hi Priya,
Thanks for the update. Helpful to know it’s in the AP queue.

To keep this tidy, could you confirm:

1. The next payment run date this invoice can make
2. Whether it’s approved already (and if not, who is approving)

Invoice 7812 is £9,850, due 20 November.
Happy to resend the PDF or any vendor details you need.

Thanks,
BSB AR Team (on behalf of Your Company)

Short. Two questions. A clear “why”. No heat.

What to report weekly (so founders can act)

A taxonomy is only useful if it produces decisions.

Add this to your weekly receivables report:

• Value by tag (late / dispute / missing PO / AP backlog)
• Count by tag
• Oldest item per tag (and why it is still open)
• “Stuck blockers” list with owners and dates
• Time-to-triage (median time from reply to tag)

Founders do not need more rows. They need fewer unknowns.

Pitfalls (and how to avoid them)

• Pitfall: tagging everything “late”.
  Fix: if a customer mentions a process step (PO/portal/approval run), tag it. It changes the plan.
• Pitfall: debating tags for five minutes.
  Fix: pick the best tag now. You can retag later.
• Pitfall: disputes that drag on forever.
  Fix: set a decision deadline. If it slips, escalate internally.
• Pitfall: AP backlog becomes an excuse.
  Fix: always ask for the payment run date or approval owner. “In progress” is not a date.

What your team can do this week

• Create the four tags in your tool (CRM, helpdesk, AR sheet, or inbox labels).
• Add the “one key detail” rule per tag.
• Set an SLA: every reply tagged within one business day.
• Create one internal blocker channel and a simple template:
  • “Customer / invoice / tag / blocker / owner / due date”
• Start reporting value by tag weekly.

Next step

If you want to run this without adding headcount, we can own the inbox.

We plug into your tools, read every reply, tag the reason, and push blockers to your team so cash keeps moving. If PO and portal steps slow you down, we can handle that workflow too.

Explore Lite AR Essentials, Managed AR Ops, or AR + Portals & Onboarding on services. If you are ready to talk, Get in touch via contact.

---

Compliance & clarity: This post shares general AR operations guidance. It is not legal or accounting advice. Examples are illustrative and include no private client data.