Case Studies

How a Riyadh trading company cut month-end from three weeks to five days

Moving a two-branch distributor from Tally and Excel to Zoho Books and Zoho Inventory.

Axiora team · 20 November 2026 · 3 min read

The business

A distributor of building materials based in Riyadh, with two sales branches, one central warehouse and around 15 people across finance, sales and stores. The company imports a large share of its stock and sells mainly to contractors on credit terms, with some walk-in cash sales at the branches.

Like many growing distributors, it had built its processes over years on a mix of Tally for accounting and Excel for almost everything else: stock tracking, branch sales, price lists and the owner's reports.

The challenge

A three-week month-end

Closing each month took about three weeks. Branch sales came in as spreadsheets, bank lines were typed in by hand and stock movements were reconciled manually at the end of the month. By the time the owner saw the results, the next month was half over.

Stock that did not match the warehouse

Quantities in the system rarely matched what was on the shelves. Transfers between the warehouse and branches were recorded late or not at all, and the sales team often promised stock that was not available.

Margins that ignored import costs

Freight, customs duty and clearing charges were booked as general expenses. Product margins looked healthy, but the real profit on imported lines was much lower, and some items were being sold close to cost.

ZATCA Phase 2 approaching

The company had received its integration date for ZATCA e-invoicing Phase 2. Its existing setup could not integrate with the FATOORA platform, so a change was needed within a fixed timeline.

What we did

  1. Requirement study: we spent time with the owner, finance, sales and stores to understand how the business ran and which reports mattered.
  2. Design: a new chart of accounts built around branch reporting, with reporting tags for product groups, and clear user roles and approval limits.
  3. Setup: Zoho Books and Zoho Inventory configured for two branches and one warehouse, with transfer orders, reorder levels and landed cost on every import.
  4. Migration: customers, suppliers and items cleaned and imported; opening balances and every open invoice and bill brought across from Tally and reconciled line by line.
  5. ZATCA: Phase 2 integration onboarded for each invoicing unit, tested with every document type and live before the deadline.
  6. Training: recorded, role-based sessions for finance, sales, purchasing and stores, using the company's own data.
  7. Owner reports: key reports set up as plain-language commands with Claude, such as "Get me TB 2026" and "Sales by branch this month".

Typical outcomes

3 weeks → 5 daysMonth-end close
2 branches, 1 warehouseIn one system
On demandOwner reports

With transactions recorded at the source and bank feeds in place, month-end became a review of numbers that were already largely complete. Stock transfers were recorded as they happened, so branch stock became reliable and sales teams could check availability before promising delivery.

Landed cost changed the picture on margins. Several imported lines turned out to be far less profitable than they appeared, which led to price adjustments and a review of shipping arrangements. E-invoicing ran smoothly from the first day, with rejections handled quickly in the first weeks.

The owner no longer waited for month-end reports. Instead of asking the team to export and format figures, he could request the trial balance, branch sales or overdue receivables in plain words and get them in seconds.

What made the difference

  • Starting from the reports the owner needed, then designing the system to produce them.
  • Cleaning data in Tally before migration, rather than fixing it afterwards.
  • Bringing across open items, not just totals, so collections continued without disruption.
  • Testing ZATCA integration with real document types well before the deadline.
  • Involving each team in training on its own tasks.

Projects like this usually take a few weeks from requirement study to go-live, depending on data quality and the number of apps involved. Support after go-live continues through the client portal, where every request and the time spent on it is visible.

Want this working in your business?

Book a free 30-minute call and we will show you how it applies to your setup.

Chat on WhatsApp