UNPAID INVOICES · CUSTOMIZED FOLLOW-UP
Unpaid? Not so fast.
Before following up, check the payment and exchanges. BM gathers this information in your tools and prepares the rest according to your rules.
Overdue.
But really unpaid?
The invoice, payment and exchanges are often separated. Before restarting, let's bring them together.
Same deadline.
Five different next steps.
Choose the observed signal. The follow-up can only be prepared when the conditions defined with the team are met.
What sequence is permitted?
Prepare, then validate.
The invoice is overdue, with no reconciled payment or known exchange. A follow-up can be prepared according to the agreed rule; a person validates the shipment.
Illustration of operation. The rules, access to data, deadlines and validations are defined on a case-by-case basis. No emails are sent from this page.
Your tools stay.
The information is coming together.
We start from the reliable source for each information, available access and exceptions for your activity.
Invoice
Due date, customer, amount and status in the reference tool.
Which data is authentic?Payment
Signal received, reconciliation confirmed or doubt to be verified.
What constitutes “paid”?Conversation
Latest dated reminder, response, promise or known dispute.
Who sees the exchange?A next assigned action.
Prepare, wait, stop or create a human task: the rule is chosen with the company, not deduced from a single date.
The follow-up is progressing.
You keep control.
Consolidate states · identify a deadline · suggest a reminder · create a task · trace the action
Check an ambiguous payment · handle a dispute · adapt the relationship · validate a shipment · decide on an escalation
“Reminder prepared” and “send validated” are two distinct states. Only a shipment actually made and confirmed can be logged as sent.
The rules first.
The connection then.
A first workshop maps states, rights and stopping points. Then the flow is tested on controlled cases before being extended.
01Which source is authentic for the invoice?+
Identify the reference tool and the person who corrects the discrepancies.
02When is a payment reconciled?+
A banking signal alone can remain ambiguous; the reconciliation rule must be explicit.
03What delay, what channel, what tone?+
The recall conditions depend on the customer and are validated by the team.
04When does the sequence stop?+
Closed payment, response, promise, dispute and exception trigger a defined hold or stop.
05Who takes over a sensitive case?+
Assign a contextualized task rather than forcing automatic sending.
06Who can see payment data?+
Limit access and define useful traces before any connection.
Shall we review
your follow-up process?
Let's take a real case: invoice, payment, last exchange. We will define together who decides, when to stop and what to automate.
Talk about your follow-up Or write to BM →What deserves
a clear answer.
Can we act without replacing our invoicing software?+
Yes, if access and data permit. BM is exploring how to link existing software, payment signals and exchanges. The scope is defined according to your operation.
How to avoid a reminder after a payment?+
The scenario must distinguish between close payment and a simple signal to be verified. The first stops the restart; the second suspends the action until the planned check.
Is an automatic reminder suitable for a dispute?+
No. A known dispute suspends the sequence and creates a human handoff with its context. The commercial or legal follow-up is decided with the competent people.
Does BM do collections?+
BM designs an information and monitoring flow around your tools. BM does not provide recovery services or legal advice.