Payment on account reminders

Reminders are polite e-mails before and after the due date. Each stage is sent once. Reminders never cancel or change an order.

Before you start

the stages you want (how many days before and after the due date),
the payment details (for example the bank account) and an accounting address for a copy, if you want one.

1. Set the reminders

Stores › Configuration › Magelan › Payment terms

In the Reminders group:

Send reminders: the on switch.
Send reminders at: the time of the daily run (time zone of the cron). Default 07:40.
Stages (days from the due date): at most 6 numbers separated by commas. A minus is before the due date: -3,1,7,14 (the default) is three days before, then one, seven and fourteen days after.
Most reminders per daily run: a safety limit.
Sender: which store e-mail identity sends the reminders.
Copy to (accounting): optional. Reminders also go to the e-mail for invoices of the customer or company, if there is one.
Payment details: for example the bank account; shown in the reminders.

The General group also has Mark overdue receivables at: the time (default 00:10) at which receivables whose term has passed become overdue.

2. How reminders are sent

Each stage is sent once per receivable, with at most one message per receivable per run. If the cron was off for a day, only the latest matching stage goes out.
The customer receives them; separate copies go to the e-mail for invoices of the customer or company and to the accounting address.
Paid, written-off and cancelled receivables get no reminders.

3. Adjust the e-mail templates

Marketing › Communications › Email Templates

The module brings three templates: Payment on account: reminder before the due date, Payment on account: first reminder after the due date and Payment on account: further reminders after the due date. A stage with offset 0 uses the "before the due date" text. If you want different wording or a translation, create your own template based on the default one.

4. See what would go out next

On the server you can list, without sending, the reminders the next run would send:

bin/magento magelan:payment-terms:sync --reminders-dry-run

The module charges no interest and no reminder fees. The term counts calendar days, with no working days or holidays.

Common problems

Reminders do not go out

Check that Send reminders is on, that the cron is running and that the receivable is still open or overdue. The preview command shows what would go out.

The customer paid but got a reminder

Mark the payment as soon as the money arrives; the message itself says the customer can ignore it if they have already paid.

Was this article helpful?

Badges and labels on productsExtensions Product questions and answersExtensions Product enquiry formExtensions Product attachments (data sheets, manuals)Extensions Back in stock notificationExtensions

Cookie name	Cookie purpose
PHPSESSID	Preserves the visitor's session state across page requests.
magelan_geo	Remembers that the visitor closed the suggestion of the other language version of the store, so it is not shown again.
form_key	Protects visitor's data from Cross-Site Request Forgery Attacks.
guest-view	Stores the Order ID that guest shoppers use to retrieve their order status. Used in “Orders and Returns” widgets.
login_redirect	Preserves the destination page the customer was loading before being directed to log in.
mage-banners-cache-storage	Stores banner content locally to improve performance.
mage-cache-sessid	The value of this cookie triggers the cleanup of local cache storage.
mage-cache-storage	Local storage of visitor-specific content that enables ecommerce functions.
mage-cache-storage-section-invalidation	Forces local storage of specific content sections that should be invalidated.
mage-messages	Tracks error messages and other notifications that are shown to the user, such as the cookie consent message, and various error messages. The message is deleted from the cookie after it is shown to the shopper.
private_content_version	Appends a random, unique number and time to pages with customer content to prevent them from being cached on the server.
section_data_ids	Stores customer-specific information related to shopper-initiated actions such as display wish list, checkout information, etc.
user_allowed_save_cookie, cookie_consent	Stores the user's cookie consent state for the current domain.
X-Magento-Vary	Configuration setting that improves performance when using Varnish static content caching.

Cookie name	Cookie purpose
product_data_storage	Stores configuration for product data related to Recently Viewed / Compared Products.
recently_compared_product	Stores product IDs of recently compared products.
recently_compared_product_previous	Stores product IDs of previously compared products for easy navigation.
recently_viewed_product	Stores product IDs of recently viewed products for easy navigation.
recently_viewed_product_previous	Stores product IDs of recently previously viewed products for easy navigation.
_fbp	This cookie is installed by Facebook to store and track visits across websites.

Cookie name	Cookie purpose
dc_gtm_*	Throttles request rate when Google Analytics is deployed with Google Tag Manager.
_ga, _gat, _gid, _ga_, _gat_	This cookie is installed by Google Analytics. They are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone.