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

What it countsMix of Customer.Payment Terms Code values: Net-30 / Net-60 / Net-90 / COD / Prepay. Counts and revenue %.
Tax treatmentn/a.
CurrencyReporting Currency.
Time window30D
Alert trigger-
Rolesowner, finance

​
Calculation

Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

US distributor: Net-30 (62% of revenue), Net-60 (24%), Prepay (10%), COD (4%). Net-30 dominance keeps DSO target around 35-40 days.

​
Sibling cards merchants should reference together

CardWhy pair
DSOMix shapes DSO.
Top B2B AccountsConcentration.

​
Reconciling against the vendor’s own dashboard

Where to look in Business Central:
Customer List > Payment Terms Code column + group by
Why may differ:
ReasonDirectionWhy
Custom terms codesEitherCard recognises standard; custom mapped via field map
Cross-connector reconciliation: No commerce-side counterpart.

​
Known limitations / merchant FAQs

Healthy mix? Depends on industry. Wholesale electronics: predominantly Net-30 with some Net-60 for top accounts. Custom Payment Terms Codes? Mapped in field map. BC’s standard codes (1M, 30D, COD, etc.) recognised by default. Migrating customers from Net-60 to Net-30 to reduce DSO? The card tracks the mix shift over time. A successful migration shows higher Net-30 share and falling DSO.

​
Tracked live in Vortex IQ Nerve Centre

B2B Payment Terms Mix is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 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.