FinanceA manufacturer that installs what it makes

Collections, with every conversation on the account

The ERP held the invoices, but collections lived in people’s heads and inboxes. We built a workbench that puts every call, email, and promise on the customer’s timeline, turns an invoice’s age into the right next step, and drafts the letters for a person to approve.

Built
A customer timeline, a work queue, reminder and demand letters, and statements
Replaced
Collections that were largely reactive
Connected to
The ERP (invoices, payments, customers, contacts), read-only, and the company’s AR mailbox
Used by
The finance team, every day
Rule
Nothing goes to a customer without a person’s OK
Result
Outstanding AR down more than 50%
A customer’s page in the collections tool: open AR, the oldest days past due, average days to pay, and an activity timeline of calls, emails, a meeting, and a note, each with who made it, the contact, what was said, and the outcome.

Ironwood Mechanical Contractors

Terms Net 30 · Salesperson Marcus Webb · AR contact: ap@ironwoodmech.example · Statement with interest ↓ · Statement without interest ↓ · exempt from interest

Open AR

$132,645.50

Deposits held (not netted)

$0.00

Oldest days past due

38

Worst stage

30 Days

Pending notices

1

Avg days to pay

34.3

On-time rate

25%

Worst lateness

11d

Payment history from 4 payment-backed closed invoices · worst: invoice 45640.

Expand allCollapse all

▾ Activity Timeline7 entries · last 10/15/2026

WhenTypeInvoiceWhoContactNotesOutcome
10/15/2026email_out45688Alex KimKaren Liu (AP)Sent copies of 45688 with the signed delivery tickets, as asked.—Edit
10/15/2026call45702Alex KimKaren Liu (AP)Karen confirmed 45702 is approved and on next Thursday’s check run. 45688 is waiting on the PM’s sign-off; she’s chasing him today.promiseEdit
10/12/2026email_inwhole accountsystemKaren Liu (AP)Asked for the delivery tickets on 45688 before it can go to the PM.—Edit
10/08/2026call45702Alex KimKaren Liu (AP)Left a voicemail about 45702, now past 30 days.left_voicemailEdit
10/07/2026notewhole accountSam Rivera—Marcus says the job closed out clean and the GC is happy. No reason to hold payment.—Edit
10/04/2026email_out45702systemKaren Liu (AP)30-day reminder sent after approval in the Outbox.—Edit
09/25/2026meetingwhole accountSam RiveraTom Becker (Controller)Walked the account at the job site. Agreed to send invoices with tickets attached from now on.—Edit
One customer’s account: the figures, then every contact, newest first.

The problem

Collections had been largely reactive: an overdue invoice got attention when someone noticed it. The ERP had every invoice and payment, but no way to run collections: no work queue, no history of who called whom, no record of a promise to pay, no reminder letters, and no view of lien deadlines. Whoever picked up the phone had to remember the last conversation, or dig through email to find it.

What we built

  • One timeline per customer. Every call, email, meeting, note, promise, and dispute, newest first, with who made it, the contact, what was said, and the outcome.
  • A ladder from the company’s policy. On day 10 a call confirms the invoice arrived. Day 30 sends a reminder, day 45 asks the salesperson to call, day 60 is a demand letter, and day 75 is a referral to counsel. Calls become tasks for the right person; letters are drafted.
  • Letters a person approves. Each letter is drafted with the statement and the invoices attached, lists every invoice with its age, and waits in an outbox until a person approves, edits, or holds it.
  • One letter per customer. A customer with invoices at two stages gets the letter for the later one, never a friendly reminder and a demand the same morning.
  • Promises and disputes pause the clock. A promise to pay holds the ladder until a few days after the promised date, and two broken promises go straight to a demand. A dispute pauses only the amount in dispute.
  • Statements in a click. On letterhead, with or without the interest the terms allow.
  • Repeat late payers, flagged. A customer who reaches day 45 twice in a year is flagged for deposit terms on their next quote.
  • Follow-ups across every account, overdue first, on the dashboard.
  • Synced from the ERP every four hours, read-only. The one thing it adds there is a new AP contact on the customer’s account.
The follow-ups band on the collections dashboard: five follow-ups, one a day late, two due today, each with the customer, the invoice, the amount, the note, and who it is assigned to.

Follow Ups everyone · overdue first

EveryoneMine
  • 1d late · 10/15/2026Riverbend Construction45610$14,705.00Confirm the half payment on 45610 is in the mailAlex KimDone
  • Due todayIronwood Mechanical Contractors45688$41,250.00Check that the PM signed off on 45688Alex KimDone
  • Due todayHarborview Medical Center45630$58,975.00Call AP about 45630 before it reaches 60 daysAlex KimDone
  • 10/17/2026Bluewater Seafood45652$26,780.00Second call on 45652Sam RiveraDone
  • 10/22/2026Ironwood Mechanical Contractors45702$68,420.00Thursday check run: confirm 45702 clearedAlex KimDone
Follow-ups across every account, overdue first.

What changed

50%+drop in outstanding AR after it went in

The finance team works from it every day. Every open invoice has its next step, every customer has one history, and every letter goes out on schedule with a person’s OK.

Questions

Does it send letters on its own?
Not unless you turn that on. Every letter waits for a person to approve, edit, or hold it. Each kind of letter has an automatic switch, and it stays off until you decide otherwise.
Does it change anything in our ERP?
No invoices, payments, or adjustments. It reads them, and the one thing it adds is a new AP contact on a customer’s account.
Can it follow our collections policy?
That’s where it starts. The days, the steps, who calls, and what each letter says all come from your policy.

Every screen shows sample data. The company isn’t named here, and we’re glad to put you in touch: ask us for a reference.

What should your first tool be?

Tell us about the workflow that eats your team’s week. We’ll listen, then sketch the first tool with you.