Strawberry can turn an aged receivables list into a controlled reminder queue with the invoice number, amount, due date, and account context already assembled. A finance owner reviews the message and escalation before it affects a customer relationship.
01
The receivables list needs context before it becomes outreach.
Aged debt alone cannot tell you whether an invoice is simply late or already under discussion.
Strawberry can combine the invoice list with the customer thread, account notes, and payment history you make available.
That gives the finance team a fuller queue: send a first reminder, wait for a promised payment, investigate a dispute, or escalate internally.
02
The first reminder should remove friction, not add pressure.
The most helpful reminder identifies the specific invoice and makes payment straightforward.
Strawberry can draft a message with the invoice details, due date, payment instructions, and a clear route for correcting an error.
It should match the relationship and the account status rather than use the same wording for a new customer and a long-standing partner.
03
Escalation rules should be visible before they are used.
At a certain age or amount, a reminder may need a finance lead, account owner, or collections process. Strawberry can flag those accounts using the thresholds you define and prepare an internal escalation summary.
The people who own credit risk and the customer relationship should decide what happens next.
04
A reminder history should be easy to audit.
Keep a record of which invoice was contacted, when, through which channel, and what response followed. Strawberry can prepare that log and preserve the context needed for the next chase.
A saved skill can produce the same queue at a chosen cadence, with human review kept where a message or escalation changes the relationship.