Case Study 03 — From 35-day close to 3-day close | SatyaHQ
CASE 03 Finance operations · Reporting & close

From 35-day close to 3-day close.

A leading finance company's monthly close crept into the middle of the following month, and any ad-hoc report took two weeks. We rewired the close cycle end-to-end — closing books 12× faster and dropping the report TAT from 15 days to overnight.

Monthly close cycle
35 days3days
Books closed within 3 working days of month-end — every month, on rails.
Reporting TAT
15 days1day
Any P&L cut, any dimension. Overnight refresh replaces the weekly PDF pack.
Cycle time reduction
91%
Days saved on the close
Reports on-demand
120+
Pre-built dimensional cuts
Manual journals
↓ 78%
Automated adjustments & accruals
Data freshness
T-1
From T-14 monthly pack
The client
A leading finance company with 40+ business lines, five legal entities and a consolidation cycle that ran into the middle of the next month.
Industry
Diversified financial services
Scope
Close automation + reporting layer
Timeline
16-week build · 6-week stabilization
The problem

The books closed after the decisions were already made.

By the time the CFO saw last month's numbers, the current month was almost over. Reporting requests took 15 days because every cut required a fresh pull, reformat and reconciliation.

Where the 35 days went.

The close was a relay race with too many handoffs. Data-collection alone took 12 days because five entities emailed workbooks to a single consolidation team. Reconciliation ate another 10, and every review cycle bounced numbers back to the source.

Reporting was worse. Ad-hoc requests joined a queue that ran on Excel, PDF and calendar time — 15 days average, hitting 22 in month-close weeks.

Manual consolidationExcel handoffsLate accrualsNo single truth

Anatomy of a 35-day close

Stacked days per phase · pre-automation baseline
Data collection 12 d Reconciliation 10 d Adjustments & accruals 6 d Review cycles 5 d Final sign-off 2 d 35 days · target: month-end + 3
The approach

Continuous close, not month-end close.

We stopped treating the close as a monthly project and made it a nightly job. Sub-ledgers reconcile daily, accruals post automatically, and by day-3 the only work left is sign-off.

1

Direct-connect sources

Sub-ledgers, bank feeds and operational systems replace Excel handoffs. Data lands nightly.

2

Daily soft-close

Reconciliation, adjustments and accruals run every night. By month-end the delta is small.

3

Rule-based journals

Standard adjustments, allocations and inter-company eliminations are code, not tickets.

4

Reporting layer

Semantic model + dashboards mean any cut is a click, not a two-week Excel exercise.

Reporting cadence — before & after

Each dot is a reporting event · one month shown
BEFORE Monthly PDF pack, days later Pack M+15 AFTER Daily dashboard, always fresh M-1 M+3 close · sign-off CLOSED
The results

32 days off the calendar. 14 days off every report.

Two headline numbers moved, and everything downstream moved with them — cash-flow forecasting, board pack, audit prep.

Where the 32 saved days came from

Waterfall from 35-day baseline to 3-day steady state
Days on the close cycle
40 d 30 d 20 d 10 d 0 35 d baseline 35 −12 d Direct-connect sources −10 d Daily reconciliation −6 d Rule-based journals −4 d Fewer review cycles 3 d steady state 3 START Sources Recon Journals Review END
Baseline (35 d)
Days removed
Steady state (3 d)

Reporting TAT — 15 days to overnight

Average time from request to answer · P&L cuts
0 4 8 12 16 d BEFORE 15 d AFTER 1 d ↓ 93%

Close-day trend, month over month

Working days from month-end to books-closed
40 30 20 10 0 d M-6 M-4 M-2 M0 M+2 M+4 Go-live 35 d 3 d
The impact

Faster books changed the operating cadence.

Close cycle
35 → 3
Days from month-end to sign-off
Report TAT
15 → 1
From request to answer
Board pack lead time
↓ 22 d
Available on day 4, not day 26
Finance team hours
↓ 58%
Spent on the close · redeployed to FP&A

"We used to steer the business with rear-view numbers. Now the board sees the previous month by day-4 — and any question about the current month gets a real answer the next morning."

— Group CFO, [Client name]
Deliverables

What they own after go-live.

A living close pipeline and a semantic reporting layer — everything shipped as owned artifacts.

Close pipeline

  • Direct-connect source adapters
  • Nightly reconciliation jobs
  • Rule-based journal engine
  • Inter-company elimination

Reporting layer

  • Semantic model (entities, dimensions, metrics)
  • 120+ curated dashboards
  • Self-serve report builder
  • Auto-refreshed board pack

Controls

  • Journal-level approvals workflow
  • Full audit trail with drill-through
  • Variance detection & alerts
  • Sign-off dashboard for controllers
PythondbtAirflowSnowflakeMetabaseStreamlitSAP / Oracle adaptersSlack alerts
See more

Three studies. One playbook.

Invoice automation · Reconciliation · Close cycle compression — all for the same client.

Back to overview →