Blog · Board and management reporting · Sales teams
B2B analytics compares account buying frequency, product mix, and revenue across buying cycles. Work through an account-level sales example, reconcile it to the ledger, and identify what the account owner should investigate.
B2B analytics compares account buying frequency, product mix, and net revenue over the same buying cycle. The useful result is an account-level explanation of what changed, supported by orders and posted sales. A company total alone cannot distinguish a replenishment customer ordering more often from a project customer delaying a large purchase.
An account is the commercial relationship you want to manage. It may contain several billing locations, shipping sites, and contacts. Decide whether the review uses the legal customer, billing account, or parent group before comparing periods, and retain the underlying identifiers so a roll-up can be checked.
The buying cycle determines the comparison. A month without orders means something different for a weekly replenishment account and an annual equipment buyer. Compare equivalent periods and show the expected purchase schedule beside exceptions. A quiet period is a prompt for the account owner to investigate, not proof of churn.
This is separate from B2B marketing analytics, which owns campaign outcomes, and B2B ecommerce analytics, which owns the business purchasing channel. Here the question is what happened to the commercial account across all supplied sales records.
Use these exports, with their dates and filters recorded:
| File | Fields to retain | What it establishes |
|---|---|---|
| Sales ledger | Posting date, account ID, document ID, product, signed net sales | Recognized sales and credits |
| Order register | Order ID, account ID, order date, completion date, status | Distinct purchases and buying frequency |
| CRM account export | Account ID, parent ID, owner, segment | Account grouping and follow-up responsibility |
| Product list | Product ID, product family | A stable product mix comparison |
Keep credit memos as negative sales. Exclude sales tax and canceled orders from this example's commercial measures. Retain unmatched account IDs in an exception group so that missing CRM information does not silently remove revenue.
The IRS recordkeeping guidance describes invoices and other supporting documents as the evidence behind entries in business books. Apply that discipline to the review: an unexplained total should lead back to a document, not another summary.
Do not substitute cash receipts for sales. The IRS explanation of accrual accounting distinguishes income earned from payment received. Use your company's recognized revenue definition for the sales review; review collections separately with finance.
A US industrial distributor compares January through March 2026 with April through June 2026. The same three accounts bought in both quarters. In this illustrative case, every counted order was delivered and its sales fully recognized within the relevant quarter, so the order and revenue populations align.
| Account | Prior orders | Prior net revenue (USD) | Current orders | Current net revenue (USD) | Revenue change (USD) |
|---|---|---|---|---|---|
| Harbor Fabrication | 3 | 48,000 | 4 | 56,000 | 8,000 |
| Mesa Controls | 2 | 40,000 | 1 | 25,000 | -15,000 |
| Ridge Packaging | 1 | 12,000 | 3 | 36,000 | 24,000 |
| Total | 6 | 100,000 | 8 | 117,000 | 17,000 |
Revenue grew by 17,000 / 100,000 = 17.0%. The account changes prove it: 8,000 - 15,000 + 24,000 = 17,000. Ridge's increase more than offset Mesa's decline, which makes Mesa easy to miss in the company total.
Orders per buying account = Distinct completed orders / Distinct buying accounts
Average order value = Net revenue for those orders / Distinct completed orders
Orders per account rose from 6 / 3 = 2.00 to 8 / 3 = 2.67. Average order value fell from 100,000 / 6 = $16,666.67 to 117,000 / 8 = $14,625.00. Round displayed frequency to two decimals and money to cents; keep full precision in calculations.
The overall order value hides differences:
| Account | Prior average order value (USD) | Current average order value (USD) | Immediate question |
|---|---|---|---|
| Harbor Fabrication | 16,000 | 14,000 | Did purchases split into smaller releases? |
| Mesa Controls | 20,000 | 25,000 | Did a scheduled order move to another quarter? |
| Ridge Packaging | 12,000 | 12,000 | Is the extra purchase frequency recurring? |
Each amount divides that account's revenue by its order count in the first table. Sales operations owns these calculations; the account managers own the answers and the next contact.
An arithmetic bridge holds prior average order value constant for the order-count effect, then applies the value change to current orders:
| Bridge step | Calculation | Movement (USD) |
|---|---|---|
| More orders at prior average value | (8 - 6) × (100,000 / 6) | 33,333.33 |
| Changed average value on current orders | 8 × (14,625 - 100,000 / 6) | -16,333.33 |
| Net movement | 33,333.33 - 16,333.33 | 17,000.00 |
The bridge checks because prior revenue plus the movement equals current revenue: $100,000 + $17,000 = $117,000. It explains the two measured factors; it does not establish why order value fell. Different products, discounts, account mix, and smaller quantities can all affect the average.
From the same ledger, product families provide another view:
| Product family | Prior net revenue (USD) | Current net revenue (USD) | Prior share | Current share |
|---|---|---|---|---|
| Equipment | 60,000 | 63,000 | 60.00% | 53.85% |
| Consumables | 40,000 | 54,000 | 40.00% | 46.15% |
| Total | 100,000 | 117,000 | 100.00% | 100.00% |
Shares divide each row by its period total and are rounded to two decimals. Consumables gained share, but revenue mix alone cannot prove a margin improvement. Add matched costs and use gross profit margin for that separate calculation.
Give each material exception an owner, a question, and the evidence needed to close it. Mesa's owner should inspect its expected order dates and customer commitments. Ridge's owner should confirm whether demand increased or purchases merely arrived earlier. Harbor's owner should review release schedules before treating smaller orders as weaker demand.
Keep peer comparisons secondary. Sales benchmarks explains why a useful benchmark needs a comparable base, and the norm by industry covers the meaning of similar customers. The first comparison here is an account against its own history and expected cycle.
Bring a sales ledger and order export, with CRM account fields containing the agreed account mapping. Covirage maps the columns, and its tools compute and check account totals, order comparisons, and product shares; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data; creating the account takes about a minute.
See Covirage for sales teams for the account review context.
Use a sales ledger with account identifiers, dates, net revenue, and credit memos, plus an order export with order identifiers and product lines. Add a CRM account file for ownership and segments. Keep the ledger as the revenue control and document unmatched records.
Match the review period to the normal buying cycle. Frequent replenishment accounts can support a monthly review, while project purchases may require quarterly or annual comparisons. Review overdue expected purchases separately rather than calling every account without a recent order lost.
B2B account analysis studies what business customers bought and how that changed. Marketing analysis studies campaign spending and credited outcomes. Connect them through agreed account identifiers when useful, but keep campaign attribution separate from the accounting record of sales.
No. Revenue can change through account additions and losses, order frequency, order size, realized prices, product mix, and credits. A frequency and average-order-value bridge explains the arithmetic, but product and account rows are needed to explain the commercial cause.