E-Commerce Nov 19, 2026

Selling on Net Terms Online: Credit Limits, Invoices and ERP Control

Selling on Net Terms Online: Credit Limits, Invoices and ERP Control

Time to read: 11 minutes

Content

  1. Why "pay on account" online can break credit control
  2. One ledger: which system owns limits, open items and terms
  3. Checkout rules: available credit, overdue accounts and order holds
  4. Platform options: Adobe Commerce, Shopify B2B, Shopware or a custom check
  5. Invoices, partial shipments, returns and credit notes: keeping balances true
  6. Payment terms across markets: what the EU late-payment rules allow
  7. Acceptance tests before trade accounts go live
  8. What Dinarys case pages show, and what they don't
  9. Your next step
  10. FAQ
Bookmark

Approved trade accounts can order online on payment terms without loosening credit control, if one system owns credit and the shop only asks it.

Keep one owner for credit. In most B2B setups that is the ERP or finance system: it holds the credit limit, open invoices, payment terms and dunning status. At checkout the shop reads two values from it, available credit and account status, and picks one of four outcomes: place the order on terms, ask for card or prepayment, hold it for credit review, or block terms. Platform features such as Adobe Commerce company credit with Payment on Account, or Shopify B2B payment terms, fit this model when the ERP feeds them and someone reconciles them. Run them as an independent second ledger and the two will disagree. Before anyone builds, decide the hold rules, how fresh the available-credit figure must be and who releases a held order.

This guide gives heads of B2B ecommerce, credit controllers and ERP owners a responsibility matrix, a checkout decision table, the balance events to synchronize and twelve acceptance cases. It is not credit-risk or legal advice, and platform behavior is quoted from vendor documentation as checked on 19 November 2026.

Why "pay on account" online can break credit control

On the phone, someone checks the account before releasing an order. Online, the checkout decides with whatever figure it was last given. The usual failures:

Where pay on account breaks credit controlFour usual failures of online pay on account: a stale limit from a nightly sync, two definitions of exposure, payments that never reach the shop, and overdue accounts that keep buying on terms.Where pay on accountbreaks credit controlFour of the usual failuresA stale limitA nightly sync lets buyers spend allday against yesterday's balanceTwo definitions of exposureThe same order is counted twice ornot at allPayments that never reachthe shopAvailable credit only goes downOverdue accounts that keepbuyingA shop that never reads the dunningstatus lets a late payer order onterms

If you are still deciding whether to offer pay by invoice, B2B payment methods compares the options.

One ledger: which system owns limits, open items and terms

Fill this matrix with finance, the ERP owner and the ecommerce lead; each row gets one system of record.

Fictional, illustrative example. An electrical wholesaler with 2,600 net-30 trade accounts launches Shopify Plus B2B. The ERP is the credit master, but a nightly sync lets buyers exceed their limits during the day. The matrix shows its target state:

Credit fieldSystem of recordShop reads or writesRefresh triggerOwner
Credit limitERPReadsOn changeCredit control
Available credit (limit minus open invoices minus open orders not yet invoiced)ERP, calculatedReads; middleware deducts each new order at onceAfter each order, invoice, payment and credit noteERP owner
Open invoicesERPReads, to show in the buyer's accountAfter each invoice and paymentFinance
Overdue status and dunning levelERPReads as a flagAfter the daily dunning run and each paymentCredit control
Payment terms (net 30, net 60)ERP customer masterReads; offered only when the credit check passesOn changeFinance
Order hold and releaseShopify draft for reviewHolds the order as a draft; credit control releases it in Shopify, and the ERP re-checks on arrival; orders that fail the ERP re-check are held in the ERP order status and released there by credit controlOn releaseCredit control
Credit notes and returnsERPReads the effect on available creditAfter each credit noteFinance
Payment allocationERPNeverNot applicableFinance

A row with two systems of record, or none, is a defect to settle before build; so is "nightly" as the refresh for available credit or overdue status.

Checkout rules: available credit, overdue accounts and order holds

The decision table turns finance policy into checkout behavior; the thresholds are the fictional wholesaler's.

Account statusOrder vs available creditOverdueOutcomeWhat the buyer sees
Approved for termsWithinCurrent, or up to 15 daysOn net terms"Payment due 30 days from the order date."
Approved for termsExceedsCurrent, or up to 15 daysCard or prepayment"This order is above your available credit. Pay by card now or contact your account manager."
Approved for termsAnyMore than 15 daysHold for credit review; credit control alerted"Your order is received and waiting for account review."
Credit stop set by financeAnyAnyBlocked: no terms; card only if policy allows"Please contact your account manager."
New account, terms not approvedAnyNot applicableCard or prepaymentStandard checkout
Credit figure stale or unavailableAnyAnyFallback set by finance; for the wholesaler, hold for credit review"Your order is received and waiting for account review."

How the wholesaler built it: middleware pushes available credit, an overdue flag and the time of the update to each company location after every order, invoice, payment and credit note. Company locations keep Shopify's default of no payment terms, so payment is due at checkout. A payment customization function applies net 30 only when the cart fits within available credit, the account is not more than 15 days overdue and the update is no older than finance's limit; for accounts more than 15 days overdue and for stale figures it adds a review requirement, so the order arrives as a draft for credit control.

Checkout credit check with the ERP as credit master 1 The buyer checks out with a cart total and company account. 2 The shop check reads available credit and status, which come from 3 the ERP, holding the limit, open items and dunning level. Events (order, invoice, payment, credit note) update the ERP. Available credit equals limit minus open invoices minus open orders. 4 The outcome is one of four: on net terms, card or prepayment, hold for review, or blocked. 1 Buyer checkout Cart total, company account 2 Shop check Reads available credit, status 3 ERP Limit, open items, dunning Events Order, invoice, payment, credit note Available = limit − open invoices − open orders 4 Outcome On net terms Card or prepay Hold for review Blocked
Illustrative credit check. The shop reads available credit and account status from the ERP, which events keep current, and returns one of four outcomes in the order of the decision table.

Two rules keep the table honest in production. Check again when the order reaches the ERP: the shop's figure can be minutes old, and the ERP's check counts. And name who releases a hold and how fast, because a hold nobody releases becomes a lost order.

Platform options: Adobe Commerce, Shopify B2B, Shopware or a custom check

PlatformWhat the vendor documentation describesWhat you still design
Adobe Commerce B2BCompany credit per company: credit currency, a credit limit ("Maximum amount the company can owe at any time") and "Allow to Exceed Credit Limit". Payment on Account is "an offline payment method that allows companies to make purchases up to the credit limit"; it is not supported for orders with multiple shipping addresses. A REST API reads credit and changes the balance with typed operations.Feeding payments and limit changes from the ERP; an overdue or credit-stop rule, since the documented credit settings are currency, limit, allow-to-exceed and a reason for change; which balance governs
Shopify B2BPayment terms per company location: none (the default, due immediately), net 7, 15, 30, 45, 60 or 90 days from the order date, or due on fulfillment; fixed dates on draft orders. Net terms and vaulted credit cards are on the Basic, Grow, Advanced and Plus plans; deposits, partial payments and payment requests per fulfillment are Plus only. A payment customization function can hide payment methods, set payment terms and add a review requirement; the last two operations are Plus only.A credit limit and available credit, which the payment-terms documentation does not describe, stored where the function can read them; overdue handling; collection, since "Payments aren't automatically captured when the payment terms expire"
Shopware with B2B ComponentsB2B Components cover employee management, order approvals, quotes, quick orders and order lists. The Rule Builder controls payment method availability, such as Invoice, with conditions including grand total, customer tag and customer custom field.A credit check: the documented conditions compare against values set in the rule, so a per-customer available-credit comparison is custom development; an ERP-set tag can switch terms off for held accounts
Custom check, any platformA checkout call to the ERP or middleware for available credit and statusTimeouts and the fallback when the ERP does not answer

Whichever you choose, the platform's balance is a copy of the ERP's, updated by events and reconciled daily. Scope it within B2B portal development, next to B2B self-service with contract prices and approval rules, which leaves credit to finance policy.

Invoices, partial shipments, returns and credit notes: keeping balances true

Available credit stays true only if every event that changes exposure reaches the figure the shop reads, exactly once.

EventEffect on exposureAdobe Commerce credit operationWho sends the update
Order placed on termsUp by the order total (open order)PurchasedShop, at once
Order canceled before invoicingDown by the canceled amountRevertedWhichever system cancels; the other only reads
Partial shipment invoicedUnchanged: the shipped part moves from open order to open invoiceNoneERP
Return with credit noteDown by the credit-note amountRefunded (credit memo)ERP
Payment received and allocatedDown by the paymentReimbursedERP
Limit changed by financeAvailable credit moves with the limitUpdatedERP

The partial-shipment row is where balances drift. If the shop deducts at order placement and the ERP adds an open invoice at shipment, the shipped part counts twice until someone nets it off. Agree one formula, limit minus open invoices minus open orders not yet invoiced, compute it in one place, and have the shop show that number.

One formula for available creditAvailable credit is the credit limit minus open invoices minus open orders not yet invoiced; a partial shipment moves the shipped part from open order to open invoice and leaves exposure unchanged.One formula foravailable creditComputed in one place, shown by the shopCredit limitHeld in the ERP; changed by financeMinus open invoicesFrom the ERP, refreshed after eachinvoice and paymentMinus open orders not yetinvoicedEach new order is deducted at oncePartial shipment: exposureunchangedThe shipped part moves from openorder to open invoice; never countit twice

Payment terms across markets: what the EU late-payment rules allow

Directive 2011/7/EU on combating late payment frames B2B terms in the EU. In the European Commission's summary, enterprises have to pay invoices within 60 days, "unless they expressly agree otherwise and provided it is not grossly unfair"; creditors are automatically entitled to interest for late payment and a minimum of EUR 40 as compensation for recovery costs; statutory interest is at least 8% above the European Central Bank's reference rate; and member states may keep or adopt rules more favorable to the creditor. The Commission says it is working on a revision.

For the shop: net 90 is a contract decision, not a dropdown, and national rules can be stricter, so keep term options per country in the ERP customer master.

Exceptions to plan for:

Acceptance tests before trade accounts go live

The fictional wholesaler ran twelve cases before moving trade accounts online:

No.CaseExpected result
1Order within available credit, account currentNet 30 applied; available credit drops by the order total at once
2Order above available creditNo terms; buyer pays by card at checkout
3Account 16 days overdueOrder held as a draft for review; credit control alerted
4Credit stop set in the ERPNo terms at the next checkout
5Payment posted in the ERPHigher available credit shown within the agreed time
6Full shipment invoicedOpen order becomes open invoice; available credit unchanged
7Partial shipmentOnly the shipped part invoiced; shop and ERP exposure match
8Return with credit noteAvailable credit rises by the credit-note amount, once
9Order canceled before invoicingReserved amount released
10Two buyers of one company order at once, together above available creditSecond order caught at checkout once the first order's update has landed; otherwise held at the ERP re-check
11Credit figure stale or sync downOrders on terms held, per the fallback
12Finance raises a limitNew limit visible after the next update; change logged with a reason

How to check your result: name the system of record for each credit field; show the checkout outcome for an over-limit account and for an overdue account; and reconcile one account's online available credit with the ERP after a partial shipment and a credit note.

What Dinarys case pages show, and what they don't

CaseWhat the public page statesLimit
Richter Gabelstapler: Magento migration that added pay on accountMagento 1.7 to 2.0 migration for a German B2B exporter of used forklifts; a Magento 2 Invoice Payment extension added pay on account; before the project there was no invoicingPay-on-account enablement, not credit-limit enforcement
Flash Style: print-on-demand platform on Magento 2Flexible B2B payment terms alongside GoPay, bank transfer and cash; automated invoices and tax documentsNo credit-limit logic stated
Mon Tresor Bebe: wholesale sitePayment in installments, invoice editing with totals recalculation, QuickBooks synchronizationNot an ERP credit integration
SanMar: ERP integrationReal-time data exchange with the client's ERP; before the project, the lack of real-time synchronization led to incorrect pricing on the websiteNo credit scope stated

None of these pages describes credit-limit enforcement.

Your next step

Fill the matrix and the decision table with your credit controller and ERP owner, then walk cases 2, 3, 7 and 8 through your current setup on paper. If the gaps sit in how credit data moves between the ERP and the shop, Dinarys can review them with you as part of ERP integration work: which events to send, where to compute available credit and which acceptance cases to automate.

FAQ

Should the credit limit live in the ERP or in the ecommerce platform?

In the ERP or finance system, if that is where invoices, payments and dunning are recorded. The platform keeps a copy for checkout.

Does Shopify B2B have credit limits?

Shopify's payment-terms documentation describes term types, deposits and paying later; it does not describe a credit limit. A limit check needs an available-credit value from your ERP and, to apply terms or a review requirement at checkout, a payment customization function on the Plus plan.

What does "Allow to Exceed Credit Limit" do in Adobe Commerce?

It is a per-company setting for "whether companies can place orders exceeding available credit". Use it deliberately and record why in the Reason for Change field.

How often should available credit update?

After every event that changes exposure: order, invoice, payment, credit note and limit change. Keep a nightly run only as a reconciliation.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon