Is revenue work actually landing?

Group ERP — Financials says Revenue arises when the performance obligation is satisfied and the entry posts. Customer Relationship Management says Revenue arises when the opportunity is marked closed won.

Commercial reporting and statutory reporting move the same money into different periods, and the commentary written on the gap treats it as performance rather than timing. Not sized. Nobody has run the two populations side by side for a period.

Customer Relationship Management says A customer is a buying organization rolled to its ultimate parent. Group ERP — Financials says A customer is a payer, and a payer exists once per company code.

Customer counts, concentration analysis and credit exposure all depend on which one is asked, and no reconciliation exists between them. Not sized.

Customer Relationship Management says A customer is an organization. Contact Center Platform says A customer is the person on the line.

Service reporting counts people and commercial reporting counts organizations, and the two are placed on the same slide as though they measured the same thing. Not sized.

Core HR and Payroll says Contracted hours over the country standard for full time. Workforce Management says Scheduled hours over a fixed forty-hour week.

The same person is worth a different fraction in each system. The 2,219 figure carried on the transaction towers is a third thing again, because it includes contractors who appear in neither definition. Not sized. Three populations, no reconciliation between any pair of them.

IT Service Management says An incident is a service interruption raised as a ticket by a person. This platform says An incident is one of the sixteen agentic failure records this platform keeps.

Two non-overlapping populations share one word. A reader told there are sixteen incidents and a reader told there are several thousand are both being told the truth, and neither is told which population they are looking at. Not sized. The two have never been placed on the same page until this one.

Enterprise Data Warehouse says A transaction is a completed unit landed from a tower into the warehouse. This platform says A transaction is whatever each tower declares it processed.

This is the estate disagreement already published on the throughput pages: 200,240 items a week declared against 1,463,698 summed. The gap is a definition problem, not an arithmetic one, and nothing on either page resolves it. Sized and published. 1,263,458 a week between the two, which is 86.3 percent of the summed figure.

IT Service Management says The target is the resolution time held against the priority band. Contract Lifecycle Management says The target is the number written into the service schedule of the contract.

Where the two differ the group reports itself against the softer of them without saying so. Twelve of the twenty-eight service levels this platform carries have no function attached at all, so nobody owns the comparison. Not sized. No extract of contractual thresholds exists to compare against.

Customer Relationship Management says Each opportunity counts once, at its expected value. Marketing Automation says Each program that touched an opportunity is credited with its full value.

Influenced pipeline summed across programs exceeds real pipeline several times over, and it has been quoted in that summed form in marketing performance reviews. Not sized. The double count has never been unwound.

Reporting Semantic Layer says A measure is one governed object holding formula, population and period together. Enterprise Data Warehouse says A measure is whatever the view computes, and several views compute the same one.

The same named measure is calculated in two places with no test that the two agree. Which report a reader opened decides which answer they were given. Not sized. No comparison of the duplicated calculations has been run.