Accelerating the Monthly Financial Closing With Genie
Overview
| Experience | In Person |
|---|---|
| Track | Analytics & BI |
| Industry | Retail & Consumer Goods, Financial Services |
| Technologies | Genie |
| Skill Level | Beginner |
| DOWNLOAD SESSION SLIDES | |
Closing the books every month is still slow and manual for many finance teams. In this session, we will walk through a monthly financial closing for a mid‑size retailer and show how we tackle two of the most painful steps with Databricks One: reconciling gaps between CRM invoices and accounting numbers and running variance analysis to explain differences between actual results and budget.
We will follow a finance controller using an AI/BI dashboard to spot issues, Genie in natural language to investigate root causes and draft variance commentary and a Databricks app to apply the corrections safely, update the numbers and generate the final reporting deck.
Attendees will see how business users can make financial closing faster, simplify investigations and produce more reliable reports with less manual effort — all from a single, unified workspace.
Session Speakers
Christophe Chieu
/Solutions Architect
Databricks
Francis Laurens
/Solutions Architect
Databricks
Full Summary
Accelerating the monthly close with Genie: a smarter path beyond spreadsheets
Finance teams know the monthly close can stretch from days to weeks when it relies on spreadsheets, email, and manual lookups. The session shows how moving reconciliation, variance analysis, and reporting into a single governed environment with conversational analytics can shrink that cycle to hours, improve accuracy, and keep sensitive data under control.
FAQ
No. The speakers stress that Databricks is not an accounting system. You can implement accounting logic for analytics, reconciliation, and reporting, but rebuilding a full consolidation tool inside Databricks is rarely worth the effort.
Data ingestion from source systems and the design of the underlying financial data model were not covered. The focus is on what happens after data and models are in place: detection, investigation, remediation, and reporting.
Data and actions stay inside the governed environment. Unity Catalog enforces access control and lineage, and the Databricks Apps restrict which actions users can trigger. That reduces data leakage and the risk of unintended changes.
Yes for daily operations. Analysts use dashboards, ask questions in natural language through Genie, and submit fixes via an app. A data team is still needed to build the dashboards, agents, apps, and underlying data model.
Yes. The detect, investigate, resolve, and report approach also fits intercompany reconciliation, AR and AP analysis, and other repetitive variance workflows inside and outside finance.