B2B Company Credit & Statements for Magento 2

Key Features

Company-level credit limit with optional per-user (company-admin vs buyer) sub-limits, enforced at checkout

On-Account payment method (service-contract based) that only appears when available credit covers the order grand total

Automatic invoice creation on order placement via an invoice plugin/interceptor, with configurable invoice-on-order vs invoice-on-shipment

Live credit balance and available-credit display in the customer account and mini-account header block

PDF customer statements with aging buckets (current / 31-60 / 61-90 / 90+), generated on demand and on a cron schedule

Append-only credit ledger — every charge, payment, reimbursement and adjustment is an auditable row, never an in-place balance overwrite

Admin reimbursement and manual adjustment entries with reason codes, guarded by a dedicated ACL resource

GraphQL queries and REST endpoints exposing company balance, available credit and statement data for headless / PWA Studio front ends

Adobe Commerce native B2B Company entity integration (or an ECOSIRE-provisioned company model on Magento Open Source)

Configurable credit-hold behaviour: block, warn, or allow-with-approval when an order would exceed the limit

Email notifications on statement issue, approaching-limit threshold and over-limit attempts via Magento's transactional email system

System-config controls (store-view scoped) for currency, aging windows, due-date terms (NET 15/30/60) and PDF branding

Admin company-credit grid with per-company filters, exposed balances and quick links to statements and orders

Multi-store / multi-currency aware so limits and statements respect the website and currency scope

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

B2B Company Credit & Statements is a custom Magento 2 / Adobe Commerce module that turns your store into a proper revolving-credit account system for company buyers. Instead of forcing every B2B order through immediate payment, it lets a company purchase against a shared credit limit, optionally constrained by per-user sub-limits, then settle later against issued invoices and account statements.

This is built to order — ECOSIRE develops the module under app/code/Ecosire/CompanyCredit, installs it on your Magento install (Open Source or Adobe Commerce), wires it into your checkout, and supports it. It is not an instant Adobe Commerce Marketplace download; you get a delivery lead time and a real engineer.

Under the hood it is engineered the Magento way. A new payment method ("On Account / Company Credit") implemented against the payment service contracts only renders when the logged-in customer's company has available credit ≥ order grand total. An sales_order_place_after observer debits the company ledger and an invoice plugin/interceptor creates the invoice automatically. Available-credit and balance are surfaced through service contracts, a customer-account block, and GraphQL + REST endpoints so your headless or PWA front end can show real-time limits. PDF statements with aging buckets (current / 30 / 60 / 90+) are generated on demand and on a cron schedule, and a dedicated admin grid (guarded by its own ACL resource) lets your finance team post reimbursements and manual adjustments.

On Adobe Commerce it integrates with the native B2B Company entity and company-user hierarchy; on Open Source, ECOSIRE provisions an equivalent company model. Every credit movement is an auditable ledger row — no balance is ever computed by mutating a single field. You stay in control of limits, statements and write-offs from the Magento admin.

What you get

Custom Magento 2 module installed under app/code/Ecosire/CompanyCredit (composer-installable) on your store

Full source code with di.xml, ACL, system.xml config, db_schema.xml and declarative install/upgrade scripts

GraphQL schema (schema.graphqls) and REST endpoints (webapi.xml) for company balance, available credit and statements

Admin UI: company-credit grid, per-company credit configuration, and reimbursement/adjustment forms with ACL roles

PDF statement template (aging buckets) plus the cron job that generates and optionally emails statements

Deployment on your environment: setup:upgrade, di:compile, setapp:static-content:deploy and cache flush performed by ECOSIRE

Technical handover doc covering ledger model, config options, ACL resources, API examples and the upgrade path

Post-delivery warranty window for defect fixes plus an optional ongoing support and compatibility-update agreement

Who this is for

B2B Wholesale Merchant

Sells to trade accounts that order frequently on NET terms and expect to buy now and settle against a monthly statement rather than pay per order.

Finance / Accounts Receivable Manager

Needs accurate balances, aging, and a clean audit trail of every charge, payment and adjustment so reconciliation and collections are straightforward.

Distributor with Company Hierarchies

Runs companies with multiple purchasing users and wants one shared credit pool with per-buyer sub-limits and approval when an order would breach the limit.

Adobe Commerce B2B Store Owner

Already uses the native Company feature and wants real revolving credit, auto-invoicing and PDF statements layered on top of the existing company-user structure.

How B2B Company Credit & Statements for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
Company-level shared credit limit with per-user sub-limits	Included	Partial support	Partial support
Automatic invoice creation on order placement	Included	Partial support	Included
PDF account statements with aging buckets	Included	Partial support	Partial support
Append-only auditable credit ledger (no field overwrite)	Included	Partial support	Partial support
GraphQL + REST APIs for headless / PWA front ends	Included	Partial support	Partial support
Built, installed and supported on your store by the vendor	Included	Included	Not included
Works on Magento Open Source (no native B2B Company)	Included	Included	Partial support
Full source under app/code, no encryption lock-in	Included	Included	Partial support

Frequently Asked Questions about B2B Company Credit & Statements for Magento 2

How long does delivery take, and is this an instant Marketplace download?

This is a build-to-order extension, not an instant Adobe Commerce Marketplace download. After we confirm requirements (your Magento edition, B2B setup and invoicing rules), a typical build is around 2 to 4 weeks depending on scope and whether you need GraphQL/headless support or custom statement branding. ECOSIRE then installs it on your store, runs setup:upgrade and di:compile, and verifies it on your staging environment before go-live.

What kind of support and updates do I get after delivery?

Every build includes a post-delivery warranty window during which we fix any defects in the delivered functionality at no charge. Beyond that, we offer an optional ongoing support and maintenance agreement that covers Magento minor/security-patch compatibility, edition upgrades (e.g. moving from 2.4.x to a newer line), and small enhancement requests. Because you receive the full source under app/code, you are never locked in.

Does it work on Magento Open Source or only Adobe Commerce?

Both. On Adobe Commerce we integrate directly with the native B2B Company entity and company-user hierarchy. On Magento Open Source, which has no built-in company model, ECOSIRE provisions an equivalent company structure so the same shared-credit, invoicing and statement features work. Tell us your edition and version and we scope accordingly.

How are credit balances calculated — is anything just stored in one field?

No. Balances are derived from an append-only ledger: every order charge, invoice, reimbursement and manual adjustment is a separate auditable row with a timestamp and (for admin entries) a reason code and the acting user. Available credit is computed as limit minus outstanding balance at read time, so you always have a defensible audit trail and never a silently overwritten number.

Can our headless / PWA Studio front end read the credit data?

Yes. The module exposes company balance, available credit and statement data through both GraphQL queries and REST endpoints (declared in webapi.xml), all built on Magento service contracts. That lets a PWA Studio, Hyva, or custom front end render real-time available-credit and block the On-Account option client-side when an order would exceed the limit.

What happens when an order would exceed the company's credit limit?

It is configurable. You choose per store-view whether an over-limit order is hard-blocked, allowed with a warning, or routed for company-admin/approval before placement. The On-Account payment method itself only renders when available credit covers the grand total, and over-limit attempts can trigger a notification email to your finance team.