Skip to main content
Free 20-minute marketing audit
Limited spots available

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

Profitable Company, Loss-Making Site: How to Run Project Accounting in an ERP in Uzbekistan

How ERP project accounting works: assigning costs to each site, budget vs actual, advances and milestone billing, work in progress, margin and month-end close.

Profitable Company, Loss-Making Site: How to Run Project Accounting in an ERP in Uzbekistan

Your Tashkent subsidiary closes the year in profit. There is cash in the bank. Yet the site foreman asks for "more for materials" every month. Then one site is handed over, and it turns out its costs exceeded the contract value. Which job made money and which lived off the others — nobody can say for sure.

Sound familiar? If you have entered Uzbekistan with a construction, installation, IT services, interior design or equipment commissioning business, you have probably seen this. Local teams are often used to tracking costs company-wide, not per job. This article explains how project accounting works in an ERP. You will see how to assign costs to each site, compare budget with actuals, track advances and work in progress, and close the month as one connected process.

The overall structure of the finance block is covered in the main guide on the ERP finance module. This article focuses only on the project view.

Why the company can be profitable while a project loses money

Project accounting (often called job costing) means treating every site, order or contract as a small business of its own. It has its own revenue, its own costs and its own profit. A company-wide report throws everything into one pot.

What happens in the pot? A profitable site hides a loss-making one. The advance on a new project plugs the hole in an old one. As a result, management keeps quoting for unprofitable work, simply because it never sees the loss.

This differs from product costing. Cost accounting in an ERP calculates what one unit of an identical product costs. In projects every job is unique: its own budget, timeline and client. So the question changes: "What did this contract actually leave the company?"

Every cost needs an address: the project card and cost lines

Project accounting starts with one simple rule: no cost without a project code. In the ERP, each project gets a card. It holds the contract value, dates, the responsible manager and the budget.

Also read The Rate Moved, and Now Your Prices Differ in Three Places: Price List Management in an ERP Technology · 10 min

The budget (in local practice, the smeta) lists the planned costs of doing the work. It is split into cost lines. A typical set for an installation or construction firm:

  1. Materials — issued from the warehouse or delivered straight to site.
  2. Labour and hours — time of workers, engineers and the project manager.
  3. Subcontracting — work passed to another company.
  4. Transport and equipment — delivery, cranes, fuel, rentals.
  5. Other direct costs — permits, testing, on-site expenses.

Every document — receipt, issue, payment, completion certificate — is tagged with a project and a cost line at creation. When the system makes this field mandatory, the "we'll allocate it later" costs disappear.

The hardest part is time. A worker may spend one week on two sites. To charge payroll correctly you need timesheets or daily hour logs. This links to the HR and payroll module: hours are entered once and flow into both payroll and project costs. In an IT agency, hours are almost the entire cost base.

At a site container, a storekeeper tags a bundle of air ducts by project colour

Budget vs actual: see the variance in time, not at month-end

Once costs land on the project, the ERP shows two columns for each line: plan and actual. That is not enough. The manager needs one key answer: "What will this project cost by the end?"

Two formulas do the job:

  • Estimate at completion = actual cost to date + updated estimate of cost to complete the remaining work.
  • Forecast margin = contract value − estimate at completion.

The project manager refreshes the "cost to complete" every month. It is the only figure entered by hand, and the most valuable one: it shows a budget overrun months before handover.

How should it be estimated? Not as "budget minus actual". Re-price the remaining scope at current prices: how many metres of pipe, how many worker-days and which subcontracts are still left. A remainder calculated by subtracting from the budget always lands on plan — and hides the problem.

  • Materials — Budget: 380; Actual to date: 330; Cost to complete: 90; Forecast: 420
  • Labour — Budget: 150; Actual to date: 110; Cost to complete: 50; Forecast: 160
  • Subcontracting — Budget: 80; Actual to date: 40; Cost to complete: 40; Forecast: 80
  • Transport — Budget: 30; Actual to date: 26; Cost to complete: 10; Forecast: 36
  • Total — Budget: 640; Actual to date: 506; Cost to complete: 190; Forecast: 696

Hypothetical example, UZS millions. On an 800 million UZS contract, the planned margin was 160 million. The forecast drops it to 104 million. Most of the variance sits in materials, so that is where to look.

Advances, milestone billing and work in progress

In projects, money and work do not move together. Clients in Uzbekistan commonly pay an advance and then pay by stages. The work follows its own pace. So the ERP should show three separate figures per project.

Cash received — advances and milestone payments. Work certified — what the client has accepted under a signed completion certificate. Work in progress (WIP) — costs incurred for work not yet certified.

An advance is not revenue. It is money paid upfront for work still to be done. A company that books advances as profit ends up with "the cash is gone, but the work remains".

WIP is an important signal too. When it grows, the company is financing the client with its own money. For instance, 70% of the work is done, but certificates cover only 50%. The billing schedule is lagging behind the work.

Under IFRS 15, when the standard's criteria are met, revenue on such contracts is recognised over time by measuring progress towards completion. One way to measure progress is the ratio of actual costs to total expected costs. This approach also works well in management accounts. But confirm which rule applies to your statutory and tax reporting in Uzbekistan with your local accountant.

In an unfinished building, the client and project manager review completed installation work

Hypothetical example: three sites of an installation contractor

Hypothetical example. A Tashkent company installing ventilation and air conditioning. Three sites are open at once: a business centre, a school and a restaurant. Materials sit in one central warehouse.

The storekeeper issues pipes and ducts "for installation" without naming the site. Foremen move leftover material between sites without paperwork. Workers' wages are split equally across all three sites.

At year-end the restaurant looks the most profitable, because it carries the fewest costs. In reality, part of its materials was charged to the business centre. Management plans to cut prices on restaurant-type jobs — based on a wrong number.

What does discipline in the system change? The site becomes mandatory on every issue document. Moving material between sites requires its own document. Workers log their site daily on a phone. Within a month or two, the true margin of each site is visible and pricing rests on data.

The construction-specific side of this process is covered in detail in ERP for construction companies.

Month-end close: a 6-step checklist

Project accounting becomes reliable when it is closed once a month. This routine works for most project-based firms:

  1. Find documents without a project code. Each one goes back to its owner and is charged to the right site.
  2. Close the hours. All timesheets approved, payroll allocated to projects.
  3. Enter subcontractor certificates. Include work completed even if the invoice has not arrived.
  4. Check materials on site. Material issued to site but not yet used is stock, not cost.
  5. Update the cost to complete. The project manager refreshes each site's forecast and explains variances.
  6. Reconcile certificates with the client. Work done but not yet certified shows as WIP.

After that, the management report shows one line per project: contract value, actual cost, forecast, margin, cash received and WIP.

Common implementation mistakes

  • Budget in Excel, actuals in the ERP. They never meet. The budget must be loaded into the project card.
  • Allocating overhead by gut feeling. Either leave rent and admin costs unallocated, or split them by one fixed rule.
  • Late paperwork. A foreman hands in receipts in a stack at month-end, so actuals always lag.
  • Looking only at closed projects. Margin is managed during the work, not after handover.

Once project data accumulates, the next step is to see which types of work and clients are more profitable overall. The approach from product and service profitability analysis helps here.

Key takeaways

Company-wide profit does not mean every project is profitable. Project accounting shows each site on its own: how much cash came in, how much was spent and how much will remain.

Three habits are enough. First, no cost without a project code. Second, compare budget, actuals and cost to complete every month. Third, never treat advances as revenue, and track work in progress separately. With these in place, you price from data and see a loss-making site long before handover.

Frequently asked questions

Does a small contractor really need project accounting?

Yes, once two or three sites or orders run at the same time. That is when costs start to blend and nobody can say which job made money and which lost it. You do not need a complex system to start: a project code on every cost and a monthly comparison with the budget are enough.

Should office rent and back-office salaries be allocated to projects?

There are two options. You can leave them unallocated as company-level overhead. Or you can allocate them at month-end by labour hours or revenue share. What matters is choosing one method and applying it to every project the same way.

Can a customer advance be treated as revenue?

No. An advance is money the client paid upfront for work not yet done. In management accounts it sits as a liability and turns into revenue as work is performed and completion certificates are signed. Confirm the exact statutory and tax treatment in Uzbekistan with your local accountant.

How large a budget variance should worry us?

There is no universal threshold, but many firms set their own rule. For example, if a cost line deviates by more than 5%, the project manager explains the reason in writing. More important is seeing the variance in the week the cost appears, not at month-end.

Want a clear margin on every project?

We can walk through how costs are recorded today, where the budget lives and how the month is closed, and calmly suggest which step is the most useful place to start with project accounting.

Discuss project accounting →

Let's work out where to start

Free consultation with a DORA specialist

Message on Telegram

Let's discuss your project

Leave your number and a specialist will get in touch.

Send a request via Telegram

Your details are used only to contact you.