A Monday meeting can open with three revenue figures for the same period: one from the CRM, one from advertising reports, and one from accounting. On its dashboards page, sverdlov.pro names that split as a typical problem: the figures in the CRM and in the ledger do not agree, and the team argues over whose number is right.

The totals are often both correct for what each system records. Under IFRS 15, Revenue from Contracts with Customers, an entity recognises revenue when (or as) it satisfies a performance obligation by transferring a promised good or service to a customer — that is, when the customer obtains control of that asset. The standard has been effective for annual reporting periods beginning on or after 1 January 2018. A performance obligation may be satisfied at a point in time or over time. A CRM usually records a deal when a salesperson marks it as won. An advertising report records what the platform attributes to a channel. Those are different events. The three figures should not be forced into one total before anyone writes down the rule behind each one.

Finance teams still meet this friction at monthly close. In a public thread on the r/FPandA forum, the question itself was how to isolate the variance when CRM and ERP revenue do not align, and whether the work is a structured reconciliation or mostly manual tracing across exports and spreadsheets.

What to fix before you automate the Monday report

A dashboard will not settle the argument if the CRM itself is messy. The same dashboards page states this directly: when figures do not agree because managers keep deals however they like, a dashboard will not fix that. The first step is a CRM with clear stages and required fields, plus one glossary of metrics for sales, marketing, and finance, with each indicator described in words.

Once the rules are written, a management summary can be useful. The approach described at https://sverdlov.pro/ is to assemble a summary from the CRM, advertising, analytics, and spreadsheets on one screen, updated automatically, so that the figures agree between systems. The founder, Alexander Sverdlov, leads the work from a process audit through later support. The firm works in Moscow and online across Russia. A process audit usually takes about three to five days. Dashboard work is priced on request, after a review of the sources and the metrics; the amount depends on the number of systems and on data quality. Software licences are paid separately, direct to the vendors, and on the client's company. These pages were retrieved on 11 November 2026. The firm says it will check each figure against the source and against an agreed rule. If the data in the systems themselves are incomplete, the dashboard will not correct that, and those gaps are described in advance.

What to do this week

  • Write one sentence for each "revenue" figure you use: booked, invoiced, collected, or recognised; which date field; which deals are included.
  • Name the system that is the source of truth for recognised revenue. That is usually the ledger.
  • For one recent week, match a sample of deals from the CRM to invoices and to recognised revenue, and list every difference by cause: timing, a missing identifier, or an incomplete record.
  • Do not automate the Monday spreadsheet until that sample either agrees or the remaining differences have names.
  • If deals are entered without required fields or consistent stages, fix that before you commission a new report.

The aim of the first pass is not a prettier chart. It is a short list of named differences, so the next automated report repeats a rule the team has already agreed.