Skip to content
Berke Tok
Back to work

Finance operations

Numera

Month-end without the fire drill

Month-end without the fire drill: day two of three, 31 entities on one calendar
Sector
Finance operations
Location
Dubai, UAE
Year
2025
Kickoff to production
14 weeks
01Overview

Close automation for a 31-entity group: reconciliations run themselves and every variance arrives with an explanation attached.

02The problem

Closing the books took twelve days across 31 entities. Four hundred manual journal entries were re-keyed each month, reconciliation lived in a shared workbook, and the CFO learned about variances in the review meeting.

Every close task owned and dated, beside the variances it has to explain
03What we built
  1. 01

    Reconcile on arrival

    Bank, intercompany and subledger reconciliations run continuously through the month, so day one of close starts from a matched position.

  2. 02

    A close with owners

    Every task has a name, a deadline and a dependency. Blocked items escalate on their own instead of surfacing on day nine.

  3. 03

    Variance with a reason

    Movements above threshold are traced to the underlying transactions and annotated before review, not during it.

A variance traced to six transactions and annotated before anyone reviews it
Three blocked approvals reaching the controller on day two, not day nine
04The result

Close now finishes in days rather than weeks, manual journal work shrank, and the review meeting discusses the business instead of chasing numbers.

What changed

Close duration
3-day
Entities on one calendar
31
Every variance
Explained
The board pack generated from the close ledger rather than typed by hand

Stack

  • Next.js
  • Postgres
  • dbt
  • NetSuite API
  • Temporal

Disciplines applied

  • Automation & operations
  • Financial technology
  • Custom software development

Closing

Do you have an idea, or a problem?

Either works. In my experience the second one goes faster.

I usually reply the same day.