← All articles

Blog

How a Jakarta Trading Company Closed Its Books 5 Days Faster with Odoo Accounting

A Jakarta trading company cut its monthly close from eight days to three after moving to Odoo Accounting. Here is what changed and why it worked.

3 min read
  • narrative
  • odoo

A trading company in Jakarta — importing and distributing building materials, about forty staff — used to dread the first week of every month. Closing the previous month’s books took eight working days. By the time the numbers were final, they were nearly two weeks stale, which made them useless for any decision that mattered.

Where the time went

The cause was not laziness; it was architecture. Their setup was three disconnected systems plus spreadsheets:

  • Sales recorded orders in one app.
  • Inventory lived in a separate stock program.
  • The official books sat in a standalone accounting package.
  • The glue between all three was a finance staffer with a heroic set of Excel files.

Every month-end, someone manually reconciled stock movements against sales, re-entered sales totals into the accounting system, chased down which bank transfers matched which invoices, and hunted for the inevitable mismatches between stock value and the balance sheet. Eight days, most of it spent making systems agree that should never have disagreed.

What changed

They moved Sales, Inventory, Purchase, and Accounting into one Odoo database. The change that mattered was not any single feature — it was the elimination of re-entry. When a sales order was confirmed, the delivery, the invoice, and the journal entry already existed and already agreed. Stock value and the balance sheet were two views of the same underlying data, so they could not drift apart.

Three specific things did the heavy lifting:

  • Reconciliation models absorbed recurring bank lines — fees, recurring supplier payments — automatically.
  • Invoice-reference matching cleared most customer payments without manual intervention, after they asked customers to quote the invoice number on transfers.
  • Lock dates meant a closed month stayed closed; no more “the numbers changed since Friday.”

The result

The monthly close went from eight days to three. Not zero — there is still real work in reviewing the awkward 20% of transactions, foreign-currency rounding on imports, and final sign-off. But the five days that used to vanish into reconciling disconnected systems simply disappeared, because the systems were no longer disconnected.

The more valuable outcome was timing. Finance now hands management a P&L and cash position by the third working day. Decisions about restocking, pricing, and which slow-paying customers to chase are made on numbers that are days old, not weeks. The owner described it as “finally driving by looking through the windscreen instead of the rear-view mirror.”

What made it work

Two things, honestly. First, they fixed the chart of accounts and the tax setup before migrating, so the foundation was right. Second, they ran one month in parallel against the old system to catch configuration errors while they were still cheap. The parallel month found two misconfigured tax accounts — exactly the kind of mistake that would have been expensive to unwind after go-live.

This is a fairly typical result for a trading or distribution business with disconnected systems. The win is rarely a single clever feature; it is removing the manual reconciliation that disconnected tools force on you.

If your month-end close is eating a week and your stock value never quite matches your books, the cause is usually structural — and worth an hour’s conversation to diagnose. We are happy to have that chat at no cost.