Starting from the general ledger and account balances is the easiest way to make leadership charts that “look the part”: revenue, cost, expense, profit—accounts tidy, auditors familiar. The problem is that operations questions do not stop at accounts. Leadership asks which product line, which document, which store ate the margin. A finance island can give the variance. It cannot give an owner.
Three predictable things follow. Operations will not own the number, because their world is documents, not accounts. Finance will not drill, because voucher grain does not reach SKU. The weekly meeting becomes two packs colliding again. The path gap of with vs without a dashboard replays as “finance charts, no operations entry.” See With vs without an operations dashboard: how the decision path changes. A finance chart that will not open a document is close to decoration; see If a number cannot open a document, what is the dashboard for. If the implementer only knows a finance warehouse and not operations tables, the project instinctively stops on the island. When you select a vendor, ask whether they have ever wired orders to profit—not only whether account charts light up.
That does not mean finance subjects should not be built. They should, and they are often the yardstick. What is missing is the bridge: how revenue maps to shipment or invoice, how cost maps to lot or work order, how expense maps to a project. The bridge needs master data and APIs, not an accountant allocating by hand in Excel. Once an allocation sheet becomes evidence of “finance-ops unity,” swings get flattened and ownership dilutes. The risk of each system calculating its own: When every system calculates its own numbers, what breaks. Without master data, allocation lies; see Without master data, visualization lies. Leadership’s operations entry should still put revenue, margin, collections, and turns, and declare each chart’s document source; see Which KPIs belong on the leadership dashboard first.
Connect the three documents that can explain a swing first
You do not have to open every operations system at once. Pick the three most often asked “why”: sales order or shipment, purchase receipt or payables, store day-close or production report. If finance KPIs can click into those three, the island becomes a peninsula. Other subjects wait for phase two. Intercompany vouchers, expense accruals, and FX gains should not be forced into store daily profit to “tie out.” Put the part that will not tie on the chart as its own line. That is more honest than pretending finance-ops unity. DaXi does not argue for finance BI in place of an operations dashboard, and does not argue for throwing away the ledger to invent an irreconcilable “ops profit.” The two must share a window and a definition. To assess which shore your finance charts are stuck on, submit account and operations-system lists on the Data service page. Shipping reports without reaching a problem: Reporting vs analysis: which one is a data capability.
Put accruals and FX that will not tie on their own line
Intercompany vouchers, expense accruals, and FX gains should not be forced into store daily profit to “tie out.” Put the part that will not tie on the chart as its own line. That is more honest than pretending finance-ops unity.
On permissions, finance can see all accounts; operations only sees its line’s documents. Using permissions as a substitute for the bridge makes operations feel buried in accounts and less willing to own the number.
If the implementer only knows a finance warehouse and not operations tables, the project instinctively stops on the island. When you select a vendor, ask whether they have ever wired orders to profit—not only whether account charts light up.