Check a Business Central customer reminder before sending
Key facts
Review the created reminder before it is issued. Verify the recipient and attachment before it is sent.
This guide is not legal advice and laws/rules may change; consult a qualified professional for personalized assistance. Use at your own risk.
Separate creating, issuing and sending
Microsoft documents Create, Issue and Send as distinct reminder automation actions. Check the customer’s reminder terms and levels, and the Create settings for on-hold entries and non-overdue invoices. A disputed invoice may still appear in the proposed reminder. Open the generated lines to verify what the customer would see before Issue and Send. Issuing creates reminder entries in the customer ledger. If the current sequence issues and sends in the same scheduled process, validate the selected customers and settings in a controlled run before enabling broader use.
Check the create, issue and send steps in Microsoft’s reminder automation documentation.
Example: a receipt arrives before a scheduled reminder
A fictional wholesaler has two overdue invoices for $2,400 and $800. A $2,400 transfer appears in the bank but has not been applied. The customer also questions the delivery on the $800 invoice. Pause that customer’s reminder while finance matches the receipt and the dispute owner confirms what should be said about the second invoice.
Verify what was sent
Check the issued reminder and automation log, then keep the reminder number, customer and included invoices with the follow-up history. Check the sending evidence separately where your workflow records it. If an invoice was excluded for review, give it an owner and date so it does not disappear from the worklist. If a verified B2B balance remains overdue after follow-up, keep the invoice, delivery evidence and reminder history together for a collection handoff.
If the reminder surfaced an unresolved deduction or delivery question, see the accounts receivable dispute resolution guide.


.webp)