The hidden cash problem: Post 9 of 10

1.9 The Hidden Cash Problem: A Complete Guide to What's Broken in B2B AR

Short answer: Most B2B cash problems start before collections. Invoices are created late or wrong, never reach AP, stall on exceptions, get generic reminders, or are paid but not matched. This chapter maps the failure points at each of those five stages.

Most B2B companies have a cash problem that looks like a collections problem. Invoices age while follow-ups go unanswered and DSO creeps up quarter over quarter, so the instinct is to send more reminders and lean harder on the customer.

This guide walks through the contract-to-cash lifecycle one stage at a time, covering what breaks at each stage and what good infrastructure looks like there.

Stage 1: Invoice creation

Failure mode	What causes it
Wrong commercial terms	Contract parsed manually; terms not entered into billing system.
Usage data errors	Data pulled from wrong system, wrong period, or manually exported.
Missing PO number	Not captured at close; customer AP auto-rejects on intake.
Wrong billing entity	Invoice sent to parent; contract signed by subsidiary.
Late invoice	No defined owner for the sales-to-finance handoff.

What good looks like

An LLM parses the contract terms and usage data comes straight from the source systems, so the invoice goes out correct and on schedule without anyone building it by hand.

Stage 2: Delivery failures

A correct invoice can still fail to reach anyone who can pay it, and delivery failures are behind a meaningful share of structural AR problems.

Failure mode	What causes it
Dead billing contact	Contact left company; invoice delivered to deactivated inbox.
AP portal required	Customer runs on Coupa, Ariba, or bespoke F500 portal; email not accepted.
Wrong contact on file	Invoice going to someone with no AP role.

What good looks like

Delivery signals are monitored automatically and unresponsive contacts get flagged. When a customer requires a portal, the system detects it and submits there without anyone stepping in.

Stage 3: Exception handling

Every AR workflow has a long tail of exceptions that fall outside the standard process, and most tools drop them.

Exception	Why it delays payment
Missing PO number	AP auto-rejects; invoice restarts from zero.
W9 request	Payment held until tax form verified.
Out-of-office approver	No escalation path; invoice waits.
F500 AP onboarding	3–4 week supplier registration before first submission.
Wire verification call	Bank letter or phone verification required.
Approval bottleneck	Multi-level sign-off with no automation or visibility.

What good looks like

Exceptions are handled inside the standard workflow instead of landing in an inbox. Routine follow-ups run automatically, and the ambiguous cases get flagged for a person.

Stage 4: Collections

Most AR tools send the same impersonal reminder on a fixed schedule. Customers stop reading it, and the invoice keeps aging.

Approach	What it does	Where it fails
Standard dunning	Fixed cadence, same message.	Ignores root cause, treats all invoices identically.
Intelligent collections	Context-aware, configurable, sounds human.	Requires infrastructure that tracks the full lifecycle.

What good looks like

The root cause is identified before any collections activity starts. Structural failures, like a dead contact or a missing PO, get fixed rather than followed up on. Customers who are simply slow get context-aware outreach that pauses when they reply and escalates past an aging threshold, with compliance requests handled automatically. Teams using Monk see DSO drop by more than 40%, based on proprietary engineering data measured with Monk's first 100 customers.

Stage 5: Cash application

In a manual workflow, a payment can arrive and leave the invoice open for days. Until it's matched, the aging report is wrong and collections may keep chasing an invoice that's already paid.

Failure mode	What causes it
Blank wire memo	No invoice reference; matched manually or not at all.
Partial payment	No workflow for splitting across invoices.
Multi-invoice remittance	Customer pays several invoices in one transfer.
Subsidiary name mismatch	Payment entity differs from invoiced entity.
Manual reconciliation	Month-end event; ledger always slightly behind.

What good looks like

Payments are matched automatically when they arrive. The invoice is closed and the ledger updated the same day, which also stops collections on it.

The full picture

Stage	Common failure	What good looks like
Invoice creation	Manual, error-prone, terms missed.	Automated from contract, accurate on day one.
Delivery	Dead contacts, portal mismatches undetected.	Signals monitored, failures flagged automatically.
Exception handling	Falls into inboxes, resolved ad hoc.	Handled as part of standard workflow.
Collections	Same dunning regardless of root cause.	Context-aware, configurable, sounds human.
Cash application	Manual matching at month-end.	Automated on arrival, same-day close.

Monk automates accounts receivable from collections through cash application, including the edge cases and structural failures most AR tools weren't built for.

Book a demo to see how Monk handles each stage.

Up next: The last post takes on one of the questions we hear most: whether to build AR automation in-house or buy it.

Part of a 10-post series on where B2B AR loses cash, stage by stage.