Adobe Commerce B2B lets a company buy on credit through two connected features: company credit, a pre-approved credit line tracked in the company profile, and Payment on Account, an offline payment method that lets the buyer check out against that credit line up to their limit. On a Hyva storefront, company credit as a payment method is supported, but Pay on Account at checkout is a Hyva Enterprise checkout feature, so you need the Enterprise checkout compatibility to render it. True net terms, invoicing on Net 30 or Net 60, usually reaches beyond the native features into ERP integration.
For B2B merchants, letting trusted buyers purchase on account is not a nicety, it is how business gets done. A distributor’s customers expect to order now and pay on terms, and a checkout that forces immediate card payment loses those orders. This guide covers how company credit and Payment on Account actually work on Adobe Commerce, what it takes to render them on Hyva, and where native features end and ERP-driven net terms begin.
Company credit: how the credit line works
Company credit is Adobe Commerce’s mechanism for extending a pre-approved credit line to a B2B customer. An administrator sets a credit limit on the company’s profile, and the company can then make purchases against that limit rather than paying immediately. The system tracks the outstanding balance, the available credit, and whether the company is allowed to exceed its limit.
The moving parts an administrator manages:
- Credit limit. The maximum the company can owe at once.
- Available credit. The limit minus the outstanding balance, updated as orders are placed and payments recorded.
- Exceed limit setting. Whether an order that would push the balance over the limit is allowed or blocked.
- Reimbursements and adjustments. Recording payments received and manual balance corrections.
This gives the merchant a controlled way to extend credit: trusted accounts get a line, orders draw it down, and recorded payments free it back up. It is the foundation that Payment on Account sits on.
Payment on Account: the checkout method
Payment on Account is the offline payment method that connects company credit to checkout. When enabled, a buyer from a company with available credit can select Payment on Account at checkout and place the order without paying immediately, drawing against the company credit line up to the limit. The order is fulfilled, the balance increases, and the merchant collects payment separately according to their arrangement with the customer.
Because it is an offline method, no payment gateway is involved at checkout. The trust and the terms are established in the company relationship, and the storefront simply lets the authorized buyer place the order on account. This is exactly the workflow B2B buyers expect, and its absence is a common reason B2B merchants outgrow a consumer-oriented checkout.
The Hyva requirement most teams miss
Here is the detail that trips up B2B Hyva projects. B2B for the Hyva theme reached general availability with its 1.0.0 release, and the core B2B features, company accounts, credit limits, purchase orders, requisition lists, quoting, and quick orders, are stable. Company credit as a payment method is supported.
But Pay on Account at checkout, along with gift wrapping, reward points, and store credit at checkout, is a Hyva Enterprise checkout feature. That means rendering Payment on Account in the Hyva checkout requires the Hyva Enterprise checkout compatibility, not just the base Hyva theme and Hyva Checkout. A team that plans a B2B build on Hyva without budgeting for Hyva Enterprise checkout can find the credit line configured correctly in the admin but no way for the buyer to actually pay on account at the storefront.
| Feature | Base Hyva | Hyva Enterprise checkout |
|---|---|---|
| Company accounts and hierarchy | Supported | Supported |
| Credit limits in admin | Supported | Supported |
| Requisition lists, quick order | Supported | Supported |
| Quoting | Supported | Supported |
| Pay on Account at checkout | Needs Enterprise | Supported |
| Store credit, reward points at checkout | Needs Enterprise | Supported |
The practical lesson: scope the Hyva Enterprise checkout licence into any B2B Hyva project that needs Pay on Account. This is the kind of requirement a seasoned Hyva development team flags at the start, not after the build. It builds on the broader picture in Adobe Commerce B2B on Hyva.
Where native features end: real net terms
Company credit and Payment on Account give you a credit line and an on-account checkout. What they do not fully give you is the invoicing and terms management that finance teams mean by net terms: automated Net 30 or Net 60 invoicing, aging reports, dunning, and reconciliation against payments received.
For a small B2B operation, the native features plus manual bookkeeping can be enough: the credit limit governs exposure, Payment on Account lets buyers order, and the finance team invoices and records payments by hand. For a larger operation, that manual reconciliation does not scale, and the real solution is integrating Adobe Commerce with the ERP or accounting system that owns invoicing and terms.
In that model, the ERP is the source of truth for credit and terms. It calculates available credit from the real accounts-receivable balance, pushes credit limits into Adobe Commerce, and reconciles orders against invoices and payments. The storefront presents the on-account option; the ERP governs the money. Building that integration well is where B2B Magento projects succeed or stall, and it is a core part of serious Magento development for wholesale merchants.
Implementation sequence for a B2B credit build
A reliable order of operations:
- Enable B2B and company accounts. Turn on the B2B features and set up the company account structure.
- Configure company credit. Set credit limits, decide the exceed-limit policy, and define who can manage credit.
- Enable Payment on Account. Turn on the offline method and confirm it appears for companies with available credit.
- Add Hyva Enterprise checkout if you are on Hyva and need Pay on Account rendered at the storefront.
- Decide your net-terms boundary. For small volume, manual invoicing may suffice. For scale, plan the ERP integration that owns invoicing and reconciliation.
- Test the full cycle. Place an on-account order, watch the balance change, record a payment, and confirm available credit updates correctly.
That final end-to-end test is the one teams skip and regret, because a credit system that miscounts available credit is a financial risk, not just a bug.
Purchase approval and who can pay on account
On-account purchasing does not happen in isolation. A company account has multiple buyers, and not all of them should be able to draw on the credit line freely. Adobe Commerce B2B supports a company hierarchy with roles and permissions, and purchase-approval workflows that route larger orders to an authorized approver before they are placed.
This matters for credit control. A junior buyer might be allowed to build a requisition list and submit an order, while a manager approves anything over a threshold, and only certain roles can select Payment on Account at all. Configuring these permissions correctly keeps the credit line under the control of the people accountable for it, and it mirrors how the customer’s own procurement process works.
The practical step is to map the customer’s real approval structure into the company account: who orders, who approves, who can spend on account, and at what thresholds. Getting this wrong either frustrates buyers with unnecessary approvals or exposes the credit line to uncontrolled spending. Neither is acceptable to a finance team, so treat the permission design as part of the credit setup, not an afterthought.
Reconciliation: keeping the credit line honest
A credit system is only as good as its reconciliation. Every on-account order increases the outstanding balance, and every payment received should decrease it, so available credit always reflects reality. When that loop is manual, errors creep in: a payment recorded late, a credit memo missed, a balance that drifts from the accounts-receivable ledger.
The failure mode is a storefront credit line that disagrees with the finance system, which either blocks a good customer whose real balance is fine or extends credit to one who has exceeded their true exposure. Both cost money. For low volume, a disciplined manual process with regular reconciliation against the ledger works. For higher volume, the ERP integration that owns invoicing should also own the balance, pushing available credit to the storefront so the two never diverge. Decide which model you are in before you launch, because retrofitting reconciliation after balances have drifted is painful.
Frequently asked questions
What is the difference between company credit and Payment on Account?
Company credit is the pre-approved credit line tracked in the company profile, with a limit and an outstanding balance. Payment on Account is the offline checkout method that lets an authorized buyer place an order against that credit line without paying immediately. Company credit is the account; Payment on Account is how you spend it.
Does Payment on Account work on a Hyva theme?
Company credit as a payment method is supported, but Pay on Account at checkout is a Hyva Enterprise checkout feature. To render it in the Hyva checkout you need the Hyva Enterprise checkout compatibility, not just the base Hyva theme. Budget for the Enterprise checkout licence in any B2B build that needs it.
Can Adobe Commerce handle Net 30 invoicing natively?
Partially. Native company credit and Payment on Account give you a credit line and on-account checkout, but not full invoicing, aging, and dunning. Small operations can manage terms manually; larger ones integrate Adobe Commerce with an ERP or accounting system that owns net-terms invoicing and reconciliation.
Is B2B company credit available on Magento Open Source?
No. B2B features including company accounts and company credit are part of Adobe Commerce, not Magento Open Source. Open Source stores that need on-account purchasing rely on custom development or third-party extensions to approximate it.
What happens when a company exceeds its credit limit?
It depends on the exceed-limit setting on the company profile. You can allow an order that pushes the balance over the limit, or block it. Blocking protects your exposure; allowing supports flexibility for trusted accounts. Choose per your risk tolerance and the account relationship.
Where this fits
B2B purchasing on Adobe Commerce is a two-layer system: company credit defines the line, Payment on Account spends it, and on Hyva the checkout rendering of Pay on Account requires Hyva Enterprise checkout. Native features cover the credit line and on-account checkout; real net-terms invoicing at scale reaches into ERP integration. Scope all three from the start and the B2B build serves buyers the way they expect to be served.
Bemeir is the first US-based Hyva partner and a full Adobe Commerce agency, with a deep technology partner ecosystem across B2B, ERP, and payments. We implement company credit, Payment on Account, and ERP-driven net terms on Hyva, and we also build across Shopify, Shopware, and BigCommerce. Read more about Bemeir and our B2B commerce work.
External references: Adobe’s guide to managing company credit, the documentation on enabling B2B features, and Hyva’s note on Enterprise B2B checkout for Adobe Commerce.
