Upgrading from Payment on account 1.x to payment terms

This guide is only for shops that already used Payment on account (version 1.x). Version 2 keeps the module name and the payment method code, so orders placed with version 1 keep their method. It adds receivables, terms and a credit limit.

Before you start

a database backup,
access to the server for bin/magento commands.

1. What the upgrade does

The command bin/magento setup:upgrade creates the customer attribute odlog if the shop does not have it (version 1 never created it), and copies every customer with a term above zero to an approved profile with that term. The credit limit stays empty, which is the shop default and that is "no limit" until you set one. The upgrade only adds: customers who already have a profile are left alone and the attribute is not changed. You can run the same copy yourself:

bin/magento magelan:payment-terms:sync --attribute

2. Old orders have no receivable

Orders placed with version 1 have no receivable. First look at what would be written:

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

How such orders are counted is decided by a setting:

Stores › Configuration › Magelan › Payment terms › General

The field Orders paid on account before version 2 has two values: Paid (nothing owed) is the default and the safe one (Magento cannot know whether they were paid, and a mistake would block customers), and Open (owed until you mark them as paid) counts them as debt until you mark them. The upgrade imports them with this setting, and the command does too. You override the setting with a command option:

bin/magento magelan:payment-terms:sync --as=open
bin/magento magelan:payment-terms:sync --as=paid --since=2026-01-01

--as=paid|open overrides the setting, --since=YYYY-MM-DD starts with orders from that day on.

3. Check after the upgrade

Open Sales › Operations › Open receivables and check that the numbers match what you expect.
For a few customers read the line What applies now on the Payment terms tab.
Set the default credit limit and, if needed, the rules by customer group (credit limit).
Test an order with an approved test customer.

Version 2 offers the method by the cart, not by the session, so Payment on account is now also available when you create an order in the admin for an approved customer. The payment block no longer prints its own "Payment method:" line; the standard block shows the title and the rows of this extension.

Common problems

After the upgrade customers suddenly cannot pay on account

Check that the customer got a profile (the Payment terms tab) and that Payment on account is enabled under Payment Methods. The upgrade approves the old customers with a term above zero by itself.

Old orders block the credit limit

You imported them as open. Mark them as paid in Open receivables, or repeat the import with the other setting.

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.