ERP Implementation That Cut Month-End Close From 11 Days to 3

Al-Bayan Industries manufactures building materials from two plants outside Amman, employing around 240 staff. They were running an accounting package purchased in 2011, a separate payroll system, and production planning on a shared spreadsheet that only two people fully understood.

Month-end close took eleven working days, and the finance team spent most of that time reconciling figures between systems that disagreed. Inventory accuracy sat around 68% against physical count, which meant production regularly halted waiting for material the system said was in stock.

The immediate trigger was JoFotara. Their existing software had no path to national e-invoicing compliance, and the vendor had confirmed there was no roadmap for one.

This ERP implementation Jordan sets out the brief, the approach and the measured result.

This ERP implementation in Jordan ran across twenty weeks and four phases, covering finance, inventory, production and bilingual document printing.

We deployed in four phases over twenty weeks, each one delivering something usable so the business never waited months for a single launch.

Phase one: process mapping and data cleanup (weeks 1–5)

Before configuring anything we documented how work actually flowed, including the informal steps. The shared production spreadsheet turned out to encode fourteen business rules that existed nowhere else — capturing those was the single most valuable output of the phase.

Data cleanup was substantial. The item master held 3,100 records that resolved to about 2,400 real products once duplicates and variant spellings were merged. Customer records had the same problem in Arabic, where the same company appeared under three transliterations.

Phase two: finance and inventory (weeks 6–13)

We configured the general ledger, accounts payable and receivable, and inventory with per-line-item tax handling to support mixed-rate invoices. Opening balances and two years of transactions were migrated; eleven years of history was archived to a queryable store rather than loaded into the live system.

JoFotara integration was built and tested against the live service, not a sandbox promise. Invoices now submit automatically with retry handling for network failures.

Phase three: production and planning (weeks 12–18)

The fourteen rules from the spreadsheet were implemented as configurable production routing, so planners could adjust them without a developer. Bills of material, work orders and shop-floor confirmations replaced the manual process.

Phase four: bilingual documents and training (weeks 16–20)

Invoices, delivery notes and purchase orders print in Arabic with correct RTL layout while the finance team works in an English interface. This is where several vendor products had failed during evaluation, and it mattered enough to the client to shape the shortlist.

We ran parallel operation for three weeks and kept the legacy system readable for six months after go-live.