What are B2B net payment terms in wholesale?
B2B net payment terms are the agreed number of days a buyer has to pay a wholesale invoice in full, counted from a defined start date, with no early-payment discount built into the label itself. In practice, B2B net payment terms wholesale teams use labels such as Net 30, Net 60 or Net 90 so retailers, sales and finance share one due-date rule instead of negotiating every order by email.
Trade credit is the facility behind those terms: you ship now and collect later. Clear net terms turn that credit into a calendar both sides can plan around—purchase orders, goods receipt and the retailer’s payment run.
open ledger with a simple calendar page and a single due marker
How do Net 30, Net 60 and Net 90 actually calculate due dates?
Net 30 means payment is due 30 days after the agreed start date; Net 60 and Net 90 extend that window to 60 and 90 days. The label is only half the rule. The other half is the start date and whether you count calendar days in a simple way or roll to a month-end or payment-run date.
A clean policy answers four questions in one sentence retailers can reuse:
- Term length — Net 30, Net 60, Net 90 or a custom span
- Clock start — invoice date, ship date, delivery date or end-of-month
- Day count — calendar days unless you explicitly define business days
- Due-date display — the concrete date printed on the invoice and shown in the portal
Example logic (illustrative, not a legal form): invoice dated 10 March on Net 30 from invoice date → due 9 April. Same invoice on “Net 30 EOM” may roll to the end of the following month, which is a different cash date even though both say “30”.
Write the formula once. Reuse it in contracts, the storefront checkout summary, PDF or e-invoice fields and Fortnox invoicing so finance never re-interprets free text.
What payment terms are normal for Nordic and EU wholesale retailers?
Nordic payment terms B2B practice varies by sector and buyer size, but a few patterns show up often. Many independent retailers are comfortable with Net 30 when onboarding is tight and fill rates are reliable. Larger chains and distributors frequently ask for Net 60, sometimes longer seasonal windows for fashion or other pre-book heavy categories. Food, beauty and electronics accounts may sit between those poles depending on stock turn and spoilage risk.
Across the EU, statutory late-payment rules set a backstop when contracts are silent or unfair, but commercial parties still negotiate the working term. Retailer expectations in the Nordics also reflect payment run calendars: finance teams often pay once or twice a month. A due date that falls two days after their run effectively becomes the next run—unless your invoice and portal state the date clearly enough for them to schedule an exception.
Match the term to the relationship, not to a single company-wide slogan. A brand can publish a default (for example Net 30) and still grant Net 60 to named segments under a framework agreement.
simplified map of Europe with calm trade routes between hubs
How should brands choose between Net 30 and longer terms by segment?
Choosing Net 30 versus longer net 60 B2B terms is a working-capital and risk decision, not a courtesy upgrade.
Prefer shorter defaults (often Net 30) when:
- The retailer is new, thinly documented or outside your core markets
- Order values are small and frequent, so cash cycles matter more than one large booking
- Product is perishable, highly seasonal or hard to reclaim after dispute
- You lack strong credit data or insurance on the account
Consider longer terms (Net 60, occasionally Net 90) when:
- The buyer is an established chain or distributor with predictable payment-run behaviour
- You want shelf space or pre-season commitments that need a longer sell-through window
- Margin and volume support the extra days of trade credit
- Credit limits, guarantees or insurance already cap exposure
Segment in plain language: domestic independents, domestic key accounts, EU cross-border distributors, seasonal pre-order only. Publish who qualifies for which term. Tie upgrades to on-time payment history and completed onboarding—not to one rushed sales email.
If you offer early-settlement incentives, keep them separate from the net label so margin math stays visible; see how teams structure early payment discounts without margin leak.
When does the clock start: order date, ship date or invoice date?
The wholesale invoice due date should almost always be computed from a fulfilment event you control and can evidence—not from the moment the PO lands.
| Start date | What it means | Typical fit |
|---|---|---|
| Invoice date | Day the invoice is issued | Default for most finished-goods wholesale |
| Ship date | Day goods leave your warehouse | When invoicing lags dispatch and buyers want alignment to logistics |
| Delivery / POD date | Day buyer receives goods | When contracts hinge on receipt; needs reliable proof of delivery |
| Order date | Day PO is accepted | Rare as a payment clock; better for validity of quotes |
| EOM from a start event | Clock rolls to month-end rules | Common where buyer payment runs are monthly |
Invoice date is the simplest operational standard: your order-to-invoice process issues the document, the date is unambiguous and accounting systems can store it. Ship date helps when invoices are batched after multi-line picks. Delivery date only works if proof of delivery is consistent; otherwise disputes move from “how many days” to “when did the clock start”.
Avoid order date as the payment clock. It punishes buyers for your pick-pack delays and confuses anyone reconciling goods receipt to AP.
State the rule in the framework agreement and repeat it on every invoice. For annual trading setups, keep the clock definition inside the wholesale framework agreement so renewals do not silently change due logic.
How do end-of-month and fixed payment-run calendars change net terms?
End-of-month (EOM) terms change net terms by anchoring the due date to a month boundary rather than a pure day count. “Net 30 EOM” and similar phrases are easy to misread, so define them with an example in the contract and the portal.
A payment run calendar is the buyer’s internal schedule—for example, runs on the 10th and 25th. Your Net 30 due date still matters legally and in dunning, but cash often arrives on the next run after that due date. Wholesale brands that ignore runs create false “late” signals and noisy collections.
Practical habits:
- Publish your due-date formula with a worked example per term tier.
- Show the calculated due date on the portal order history and on the invoice—not only “Net 60”.
- Ask key accounts for their payment-run days during onboarding and store them on the customer record.
- Align reminder cadences to those runs so the first nudge arrives before the run, not after.
- If you use e-invoicing, ensure the due-date field matches the same formula as the PDF humans read.
Peppol e-invoice due date handling only helps if the structured field and your commercial terms tell the same story; mismatched dates are a common AP rejection cause. Operational notes for Nordic flows sit in our guide to Peppol e-invoicing for Nordic brands.
parcel and invoice joined by one continuous looping line
How do you communicate net terms in contracts, portals and invoices?
Communication fails when each channel invents a slightly different sentence. Use one master wording.
Framework agreement / T&Cs — Define term tiers, clock start, EOM rules, currencies, late-payment interest references and which document wins if portal text and PDF differ. A practical wholesale terms and conditions checklist helps you catch missing clauses before go-live.
Onboarding and credit application — Capture requested terms, approved terms, limit and billing contacts in one place. Sales should not promise Net 90 in a pitch deck if credit only approved Net 30.
Branded B2B storefront — Show the retailer’s applicable term on account pages and at checkout or order review. Self-serve only works when the due logic is visible before the PO is sent.
Order confirmation — Restate term name and, when known, expected invoice timing (for example, invoiced on dispatch).
Invoice and credit note — Print term label, start basis, due date and payment references. For Fortnox invoicing, the due date that syncs to the ledger must match the customer-facing document.
E-invoice — Map the same due date into the structured field buyers’ AP systems read.
Brandgate is one place terms, catalogues and order-to-invoice can stay aligned on a branded distributor portal with Fortnox sync, so retailers see the same due logic in the storefront and on the invoice.
Keep multi-currency catalogues honest: the term governs timing; FX and VAT rules govern amounts. Payment rails and credit workflows are covered in more depth under B2B wholesale payment solutions.
What belongs in your terms policy versus credit limits and collections?
A terms policy answers “when is this invoice due?” Credit limits answer “how much open balance may this account carry?” Collections answer “what do we do when the due date passes?” Mixing the three produces inconsistent exceptions.
Terms policy owns: default and segment terms, clock start, EOM definitions, where dates appear, who may approve non-standard terms, and how changes are announced.
Credit control owns: limits, holds, partial-ship rules when over limit, insurance and guarantees. That detail belongs with wholesale credit control and limits, not in the net-term one-liner.
Collections owns: reminder schedule, dispute desk, stop-ship triggers and handover to external recovery—always after confirming goods, pricing and due-date math.
Trade credit terms EU sellers offer should also respect mandatory late-payment protections that apply when invoices go overdue. The EU Late Payment Directive sets EU-wide rules on payment periods and late-payment remedies for commercial transactions.[1] National rules (for example Sweden’s interest rules on commercial late payment) sit alongside your contract wording.[2] Your policy can reference that interest will apply as allowed by law without turning the blog-facing T&Cs into a statute reprint.
A simple payment calendar wholesale brands can run
- Default term per segment documented and approved.
- Customer master carries approved term, clock rule and payment-run notes.
- Portal and invoice generator read that master—no spreadsheet side channel.
- Dispatch or billing event creates the invoice date used by the formula.
- Due date lands on the document, in accounting and in any Peppol payload together.
- Reminders and stop-ship rules key off that same date.
- Quarterly review of exception terms with sales and finance.
When those steps hold, Net 30 and Net 60 stop being slogans and become a shared calendar.
If you want terms, catalogue pricing and Fortnox-backed invoices to follow one rule set on a branded B2B storefront, book a demo.