Revenue by Business Central segment dimension (line of business, channel, or division).
At a glance
Revenue split by BC’s Dimension dimension (configured per merchant: Department, Brand, Channel, Project). The most actionable cut on consolidated revenue.
| What it counts | SUM(G/L Entry.Amount) for revenue accounts, grouped by primary Dimension Value (typically Dimension 1 = Department or Brand). Field map specifies which Dimension to slice on. |
| Tax treatment | Net of VAT. |
| Currency | Reporting Currency. |
| Time window | 30D |
| Alert trigger | - |
| Roles | owner, 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
UK apparel brand on BC, Dimension 1 = “Channel”, 30D window 14 Mar to 12 Apr 26.| Channel (Dim 1) | Revenue (GBP) | % | vsP |
|---|---|---|---|
| DTC Web | £2,140,000 | 44% | +8% |
| Wholesale B2B | £1,820,000 | 37% | -2% |
| Retail Stores | £620,000 | 13% | +4% |
| Marketplace (Amazon) | £308,800 | 6% | +24% |
| Total | £4,888,800 | 100% | +3% |
Sibling cards merchants should reference together
| Card | Why pair |
|---|---|
| Revenue Booked into GL | The total. |
| Revenue by Company | Different cut. |
| Revenue by Currency | Currency mix. |
| Margin by SKU | Profitability per Dimension. |
Reconciling against the vendor’s own dashboard
Where to look in Business Central:Reports > Finance > Trial Balance by Dimension Account Schedules with Dimension Sets Power BI > Finance Performance with Dimension slicerBC’s Dimension feature is powerful but requires saved Account Schedules to surface as KPIs. Card automates. Why may differ:
| Reason | Direction | Why |
|---|---|---|
| Dimension Value coverage | Either | Postings without Dimension Value default to “(unassigned)”; some reports filter, some include |
| OData freshness | Card 15 min behind | |
| Multi-Company aggregation | Card sums |
Known limitations / merchant FAQs
Which Dimension does the card use? Dimension 1 by default, or workspace-configured. Most BC tenants use Dim 1 for primary slice (Department, Brand, Channel). Multiple Dimensions: can I see crossing? Card defaults to single Dimension. Cross-Dimension (e.g. Channel × Brand) is on the roadmap. Postings without Dimension Value? Counted under “(unassigned)”. A high unassigned bucket suggests a Dimension Posting Setup gap; see field map for filtering. AL Extension custom Dimensions? Yes if registered in Dimension Setup. The card uses BC standardDimension table, AL Extensions extend without modification.
Power BI parity?
Power BI’s Finance Performance pack with a Dimension slicer matches per Company.