payment reminders
WhatsApp Payment Reminders: Due Dates and Credit Rules
An accounts team needs to know which invoice is outstanding and whether it is actually due. Separate a scheduled follow-up from a credit-limit rule, and stop or defer reminders when payment, a dispute or stale data makes the message inappropriate.
Confirm the enabled Busy connector or other accounting source, rule controls, sender/template eligibility and plan scope. The rules below are hypothetical designs to validate against your accounts data; they are not default schedules or proof of automated collection.
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Illustrative workflow
Obtain the account context
Select company, party, invoice, agreed credit terms and reconciled balance. Establish source freshness.
Evaluate the chosen rule
Use due date or invoice age as explicitly configured; apply any agreed threshold, exclusions and schedule.
Prepare the permitted reminder
Map the recipient, invoice reference, amount and date into the eligible template or reply format.
Reconcile and stop
Review failures, claimed payments and disputes with accounts. Stop or defer follow-ups when the agreed stop condition is met.
Define eligibility before a reminder
Agree whether the rule uses invoice age, a stored due date, total outstanding or a credit limit. These answer different questions. Confirm the financial year, company and party mapping so a reminder refers to the intended account.
Customer terms
Use the credit period or due date agreed for that customer. Define day counting, timezone, grace period and which invoices are included.
Credit-limit check
If enabled, compare the chosen balance with the configured limit. Decide how disputed invoices, partial payments and adjustments change the calculation.
Exclusions
Scope minimum amounts, selected customer groups, opt-outs and accounts needing human review. Agree who can override a rule and how that choice is recorded.
Scheduled follow-up or a conditional rule?
Choose the operating mode for the business policy rather than treating every outstanding balance as overdue.
On a narrow screen, scroll the table horizontally to read every column.
| Mode to scope | Input | Control and limitation |
|---|---|---|
| Scheduled | Selected invoice cohort and agreed daily/weekly/monthly schedule | Recheck payment and permission before each eligible message |
| Invoice aging | Invoice date and customer credit period | Age from invoice date is different from days past due |
| Credit threshold | Defined outstanding balance and configured limit | Crossing a threshold is not proof of non-payment or delivery |
| On-demand | Authorized accounts request and current data | Confirm access, validation and duplicate handling before enabling |
Examples of credit rules
Hypothetical examples: these amounts and dates explain a rule, not a customer account, a default policy or a sent reminder.
Example A: ₹1,00,000 credit limit
If the chosen rule sends only when the defined outstanding exceeds ₹1,00,000, an amount at or below that threshold does not trigger that rule. Confirm which balance is compared and whether due-date conditions also apply.
Example B: 15-day invoice-age credit period
If the configured rule allows a strict 15-day credit period counted from the invoice date, the first eligible evaluation is day 16. Day 16 is not 16 days overdue. Confirm day counting, due-date basis, timezone, reconciled payment state and exclusions; eligibility is not a promise of a message being sent or received.
Template values
Map [name], [amount], [bill number] and [due date] to the approved template. A day-1, day-15, day-30 or day-45 follow-up sequence would require an explicitly chosen schedule; none is assumed here.
Recheck the balance at the decision point
The freshness of a Busy record depends on the enabled connector and synchronization arrangement. Define how stale or unavailable data stops a reminder. A saved receipt, a customer saying “paid”, an accepted message request and a delivered message are separate states.
Before dispatch
Check the account match, latest payment/adjustment state, chosen rule, recipient permission, template status and duplicate-event handling.
After a reply
Route a claimed payment or dispute to accounts with the invoice reference. Reconcile in the accounting source before describing a balance as settled.
Text or document
Confirm whether an eligible template can include the mapped invoice/statement PDF. Review company, party and period before sharing it.
Set access and review boundaries
Confirm company/party access, authorized roles, credentials, logs, retention and recipient verification for the actual integration. This description does not establish accounting-grade security, zero data mixing, a certification or legal compliance. Review privacy terms before providing production records.
Match the reminder to the account question
Illustrative uses: a distributor follows agreed customer terms; a manufacturer checks an invoice dispute; a logistics business needs the mapped bilty reference; a retailer checks a reconciled balance. The fields and permitted workflow depend on the source and enabled setup.
Prepare the rule with your accounts team
Bring the accounting source/version, company/party mappings, credit-policy definition, sender and template draft with private values removed. Agree scheduling, reconciliation freshness, exclusions, an exception owner and permitted test cases. Obtain actual scope and timing; no fixed go-live period or collection result is promised.
Messaging and setup conditions
A customer message opens or resets the 24-hour reply window. Outside it, an approved template is needed. Permission to use a message format does not determine its price; confirm the effective category, allowance and account conditions separately.
Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
Onboarding, verification, template review and integration timing depend on the account, provider, workflow and outstanding approvals. Confirm the scope and schedule with the team; no instant approval, fixed waiting period or go-live deadline is promised.
Questions about payment reminders
Does any outstanding balance trigger a reminder?
Only the explicitly enabled rule could do that. Define due date, invoice age or credit threshold, and recheck payments, exclusions and permission first.
What does the 15-day example mean?
It is a hypothetical credit period counted from the invoice date. If configured that way, day 16 is the first eligible evaluation. It is not a default schedule, 16 days past due or a delivery guarantee.
Can I send immediately from this website?
No reminder is sent by this page. Confirm on-demand controls and authorized access in the actual setup before enabling that mode.
What happens after a payment or dispute?
Agree a stop/defer rule. Verify payment in the accounting source; route disputes and uncertain matches to the accounts team.
Are company isolation and audit logs guaranteed?
Confirm the implemented access boundaries, roles, logging and retention with the integration owner. No assurance is established by this workflow illustration.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support in your signed service agreement.
Discuss your payment reminders setup
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Send an enquiry