Skip to main content
Card class: Card
Mix of Net-30 / Net-60 / Net-90 / COD / Prepay across B2B customers. Drives DSO planning.

At a glance

Distribution of B2B customer payment terms (Net-30, Net-60, Net-90, COD, Prepay) by revenue. Drives DSO planning and credit-policy review.
What it countsRevenue grouped by payment_terms field on the customer record / SO.
CurrencyReporting ledger.
Time window30D
Rolesowner, finance

Calculation

Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A US Fortune 500 distributor on Oracle ERP Cloud. 30D window.
TermsRevenue shareCustomer count
Net-3062%1,140
Net-6022%380
Net-908%84
COD5%168
Prepay3%48
Five things to notice:
  1. 62% Net-30 is the workhorse.
  2. Net-60 / Net-90 (30%) drives DSO above textbook 35 days.
  3. Prepay (3%) = customers paying upfront; usually new accounts or risky customers.
  4. Mix shift signals credit policy moves.
  5. Pair with DSO to confirm terms-mix-driven calc.

Sibling cards merchants should reference together

CardWhy pair
DSOTerms drive DSO.
Customer Credit UtilisationCredit risk.

Reconciling against the vendor’s own dashboard

Where to look in Oracle ERP Cloud:
OTBI → Receivables Real Time group by payment terms
Why our number may legitimately differ:
ReasonDirectionWhy
Custom payment termsEitherImplementation-specific term names.
Cross-connector reconciliation: Oracle-internal terms metric.

Known limitations / merchant FAQs

Custom terms? Card respects whatever terms are configured. Multi-BU? Yes via filter.

Tracked live in Vortex IQ Nerve Centre

B2B Payment Terms Mix is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.