Ask the owner of a project-based business — a machine builder, a fabrication shop, an engineering contractor — how much money the last big order actually made, and you will usually get a confident answer followed, a few weeks later, by a quieter correction. The confident answer is the quoted margin. The correction comes after someone adds up the material actually issued, the overtime actually paid, the subcontracting that crept in, the extra work the customer asked for that nobody billed. By then the project is delivered, the customer has paid, and the gap between the quoted margin and the real one is gone for good.
This is the defining problem of project and job-order businesses, and it is almost never a problem of effort. The team works hard and delivers. The problem is visibility: cost is tracked for the company as a whole, but never for the individual project while it is still running. Tally knows the firm spent eighteen lakh on steel this month; it does not know that four lakh of it went to a job quoted with three lakh of steel. The truth lives in Excel sheets updated late and WhatsApp messages about extra work that was done but never costed.
Project management and costing in an ERP exist to close exactly this gap — to make every project a live bucket that collects its own material, labour, machine, subcontracting and overhead cost, compares the running total against the quoted budget, and tells you whether you are making money while you still have time to do something about it. This blog walks through how that works, the capabilities behind it, and a real rupee case study of an Indian manufacturer who stopped guessing and started seeing project margin in real time.
Why Project Costing Decides Whether Project Businesses Stay Profitable
A project business lives or dies on one thing — whether each project finishes at or above its quoted margin. The whole model is a series of bets: you quote a price based on an estimated cost, you execute, and the difference is your profit. If you cannot see the actual cost accumulating against the estimate during execution, you are flying every project blind and only learning the result after landing.
The danger is that the losses are individually small and collectively fatal. One project overruns on steel by two lakh, another absorbs a week of unbilled change-order work, a third quietly pays for overtime that was never in the budget. Each looks survivable alone, and the company-level P&L still shows a profit because the good projects subsidise the bad ones. But the owner never learns which were good and which were bad, so the next quotes repeat the same mistakes — and the subsidy shrinks year on year until a bad quarter exposes it.
Project costing breaks this cycle by making profitability visible per project, in real time. When every purchase, stores issue, job card and expense carries a project code, the ERP can show — today, at 40 percent completion — that this project's material cost is already at 60 percent of budget. That is a number you can act on: it feeds the next quote, a change-order conversation with the customer, a decision to tighten material control. It turns project profitability from a post-mortem into a steering wheel. If your projects run heavy on production, the production planning and scheduling module is where the project plan meets the shop floor.
The Project Lifecycle in ERP: 7 Stages From Estimate to Profit Review
Estimate & Quote
Build the cost estimate line by line — material from the BOM, labour hours, machine time, subcontracting, overhead and margin. The quote the customer sees is derived from this structured estimate, so the budget and the price are the same numbers, not two disconnected documents.
Open the Project & Set the Budget
When the order is won, the estimate becomes the project budget. The project gets a code, a planned cost per head, a timeline of milestones and a billing schedule. Every cost from here on is tagged to this code so it lands in the right bucket automatically.
Plan Tasks, Materials & Resources
Break the project into tasks and phases, attach the material requirement to each, assign people and machines, and set dependencies and dates. This plan is what actuals are measured against and what tells you whether the project is on schedule as well as on budget.
Execute & Capture Actual Cost
As work happens, cost flows in against the project code — purchase orders, stores issues, job cards with labour and machine hours, subcontracting challans and expenses. Nothing is re-keyed into a separate sheet; the cost is captured once, where it occurs, tagged to the project.
Track Planned vs Actual & Manage Change
The live dashboard shows budget versus actual per cost head and the variance. Overruns surface early. Extra work requested by the customer is logged as a change order with its own cost and price, so scope creep becomes billed work rather than a silent margin leak.
Bill by Milestone & Track WIP
Invoices are raised at defined milestones — advance, design sign-off, dispatch, commissioning — rather than once at the end. Work-in-progress is valued so unbilled effort is visible, and the ERP tracks which milestones are billed, due and overdue per project.
Close & Review Real Profitability
On completion the project's actual cost, total billing and real margin are compared against the estimate. The variance per cost head feeds the next quote. The post-project review turns one project's lessons into better estimates for the next ten.
The Costing Capabilities That Make Each Project Visible
The features below separate a project module that genuinely shows live margin from a glorified to-do list. Each answers a question the owner asks constantly — what will it cost, what has it cost so far, what have we billed, and where is the margin leaking.
Structured Cost Estimation
Build the quote from a real cost breakdown rather than a gut figure, so the budget and the price are born from the same line items.
- Material estimate pulled from the BOM with live rates
- Labour, machine, subcontracting and overhead as separate cost heads
- Margin applied transparently on top of total estimated cost
- The won estimate becomes the project budget in one click — no re-entry
Planned vs Actual Tracking
The single most important number in a project business — budget against actual, per cost head, live, so overruns are caught early.
- Cost captured once at source and auto-tagged to the project code
- Variance per head: material, labour, machine, subcontracting, overhead
- Percentage-of-budget consumed against percentage-of-work complete
- Early-warning flags when a head crosses its budget threshold
Milestone Billing & WIP
Get paid as value is delivered instead of funding months of work out of pocket, and see unbilled effort before it becomes a cash problem.
- Billing schedule linked to project milestones and the plan
- Auto-raised invoices when a milestone is marked complete
- Work-in-progress valuation so unbilled cost is never invisible
- Billed / due / overdue milestone tracking per project
Change Order Control
Turn the extra work the customer keeps asking for into budgeted, approved and — most importantly — billed work, closing the biggest silent leak.
- Change orders logged with their own cost, price and approval
- Revised budget and timeline reflected in the live project view
- Audit trail of who approved what scope at what price
- No extra work executed without a costed, billable record
The Margin Leaks Project Businesses Bleed From
Every project business loses margin in a small, repeatable set of ways. None of them feel like a crisis in the moment — that is exactly why they survive for years. Naming each one turns it from an invisible drain into something an ERP can be set up to catch.
Material issued to the wrong project
In a shop running several projects at once, steel, components and consumables move between jobs constantly — borrowed from one project to keep another moving, never reconciled. One project's costing then looks healthy while another carries cost that was never its own. The fix is disciplined project-coded stores issues, so every kilogram leaves stores tagged to a project. This is where project costing leans on solid warehouse and inventory management — the cost is only as accurate as the issue record behind it.
Unbilled change orders — the biggest leak of all
The customer asks for a modification mid-project. The team, wanting to keep the relationship good, does the work. Material is issued, labour is spent, and then — nothing. No revised quote, no change order, no extra invoice. Multiply this across a year and a project business can be giving away weeks of free work it never noticed. Logging change orders formally, with their own cost and price, is the single highest-return discipline project costing enforces — it does not slow the relationship, it simply ensures the extra value is paid for.
Overtime and subcontracting creep
Labour quoted at single shift quietly becomes overtime to hit a deadline. A process planned in-house gets sent out to a job worker because capacity ran short. Both are sometimes the right call — but if they are not captured against the project, the overrun is invisible and the next similar project is quoted on the original, wrong assumption. Tagging overtime hours and subcontracting challans to the project makes the true cost of hitting deadlines visible.
Overhead absorbed nowhere
Power, supervision, factory rent, consumables, machine depreciation — costs that belong to no single material line but absolutely belong to the project. Quotes that ignore overhead look competitive and lose money on every job. A defined overhead rate per project — per labour hour, per machine hour, or as a percentage — ensures the quoted price covers the cost of running the place, not just the visible materials.
Projects declared "done" before the cost is counted
The most human leak of all: the project is delivered, everyone moves to the next fire, and the final costing is never completed. The numbers that would have improved the next quote are never compiled. An ERP that forces a close-out step — actual versus estimate, real margin, variance per head — turns every finished project into a lesson. The BI dashboards are where these margins become a trend the owner watches, not a number buried in a folder.
| Costing Activity | Without Project Costing | With ApicalERP Project & Costing |
|---|---|---|
| Cost Estimate | Gut-feel figure; budget and quote are disconnected documents | Line-item estimate; the won quote becomes the budget directly |
| Cost Capture | Re-keyed late into Excel; never matches the ledger | Captured once at source, auto-tagged to the project code |
| Margin Visibility | Known only after delivery, when nothing can be changed | Live planned-vs-actual per cost head while work is running |
| Change Orders | Extra work done but never billed; free work nobody tracks | Logged with cost and price; scope creep becomes billed work |
| Billing | One invoice at the end; months of WIP funded out of pocket | Milestone billing; paid as value is delivered |
| Work-in-Progress | Invisible; unbilled effort surfaces only at year-end | WIP valued and visible per project at all times |
| Overhead | Ignored in quotes; jobs lose money invisibly | Applied per project at a defined rate, covered in the price |
| Post-Project Review | Never done; the next quote repeats the same misses | Actual-vs-estimate close-out feeds sharper future quotes |
| Outcome | Good projects silently subsidise bad ones, year after year | Each project's true margin known and acted on |
Benefits of ERP-Driven Project Costing
Project Costing Best Practices
The project businesses that genuinely protect their margin tend to follow the same handful of disciplines. None of them are technical — they are about capturing cost honestly, at source, against the right project, every time.
1. Quote from a structured estimate, not a gut figure
- Break every quote into material, labour, machine, subcontracting and overhead — never a single round number
- Pull material cost from the BOM at live rates so the estimate reflects today's prices, not last year's
- Apply margin transparently on top of total cost so you always know your floor
- Make the won estimate the project budget directly — a separate budget invites disconnection from day one
2. Tag every cost to a project at the moment it occurs
- Project code on every purchase order, stores issue, job card, subcontracting challan and expense
- Capture cost once, where it happens — never re-key it into a parallel Excel sheet later
- Make project tagging mandatory on stores issues so material cannot leave untracked
- Reconcile borrowed material between projects rather than leaving the lending project to carry it
3. Log every change order before the work is done
- No extra work executed without a costed change order — even for a trusted customer
- Each change order carries its own estimated cost, price and approval, and revises the project budget
- Treat the change order as a billing trigger, not just a record — the leak is the unbilled work, not the missing paperwork
- Keep the audit trail so the customer conversation about extra cost is grounded in documented scope
4. Bill by milestone and watch WIP
- Define billing milestones at quote time — advance, design sign-off, dispatch, commissioning
- Raise the milestone invoice the moment the stage completes, not at month-end "when there's time"
- Review work-in-progress per project regularly so unbilled effort is caught while it is still small
- Track billed, due and overdue milestones so cash collection keeps pace with project progress
5. Close every project with an honest review
- Make actual-versus-estimate close-out a mandatory step, not an optional one nobody gets to
- Review variance per cost head — where did this project beat or miss the estimate, and why
- Feed the lesson straight into the estimating templates so the next quote is sharper
- Watch project margin as a trend across jobs and customers, not as one number per project in isolation
Real-World Success Story
🎯 Case Study: Ahmedabad Special-Purpose Machine Builder
Company Profile: A ₹38 crore turnover special-purpose machinery manufacturer near Ahmedabad (Gujarat) building custom automation and material-handling equipment to order for clients across pharma, packaging and auto-component sectors. Every order is effectively a project — designed, fabricated, assembled, wired and commissioned over three to six months, with values ranging from ₹20 lakh to over ₹2 crore per machine. A team of 96 — a design office, a fabrication shop, an assembly and wiring bay, a small machine shop, a stores team, a project-management desk and an accounts team running on Tally — typically with eight to twelve projects live at any time. Project planning lived in a master Excel sheet maintained by one project manager, project costing was reconstructed in a separate workbook by an accountant weeks after delivery, and change requests from customers were tracked over email and on the project manager's notepad.
Challenges Before ApicalERP Project Costing:
- Real project margin was unknown until months after delivery: Costing was reconstructed by an accountant from Tally ledgers and the stores register weeks after a machine shipped; by the time a project's true margin was known, three or four more had been quoted on the same flawed assumptions, and nobody could say with confidence which machines made money
- Material moved between projects with no reconciliation: Steel, motors, drives and bought-out components were routinely borrowed from one project to keep another on schedule and never tracked back; one project's costing looked excellent while another silently carried ₹3-5 lakh of cost that was never its own
- Change orders were done but rarely billed: Customers regularly requested mid-build modifications — an extra guarding panel, a different drive, a layout change — and the team did the work to keep the relationship warm; an internal estimate later suggested ₹35-40 lakh a year of such extra work was being executed but never raised as a supplementary invoice
- Everything was billed at the end, choking cash flow: Despite three-to-six-month build cycles, most machines were invoiced only on dispatch, so the company funded months of material and labour out of its own working capital and frequently ran the cash-credit limit hard mid-quarter
- Overhead was guessed, not applied: Quotes covered material and direct labour but applied overhead as a rough percentage the owner adjusted by feel; lower-value machines, where overhead was proportionally heavier, were quietly losing money on a near-routine basis without anyone being able to prove it
- No post-project review ever happened: Once a machine shipped, the team moved straight to the next; the lessons that would have sharpened the next estimate — where steel overran, where assembly took longer than planned — were never compiled, so the same estimating errors repeated job after job
The Project Costing Setup That Was Implemented:
- Every order became a structured project with a real budget: The estimate was built line by line — material from the BOM at live rates, design hours, fabrication and assembly labour, machine time, bought-out items, subcontracting and a defined overhead rate — and the won estimate became the project budget directly, so the budget and the quoted price were the same numbers from day one
- All cost was tagged to the project at source: Purchase orders, project-coded stores issues, job cards capturing labour and machine hours, subcontracting challans and expenses all carried the project code; material could no longer leave stores untagged, which immediately ended the silent cross-project borrowing
- A live planned-versus-actual dashboard replaced the reconstructed workbook: The project manager and owner could see, per project and per cost head, budget versus actual and the variance, with early-warning flags when a head crossed its threshold — turning costing from a post-mortem into a daily steering tool
- Change orders were made mandatory before extra work: No modification was executed without a costed, approved change order that revised the project budget and triggered a supplementary invoice; the previously invisible extra work became visible, budgeted and billable
- Milestone billing was defined at quote time: Each project carried a billing schedule — advance on order, on design sign-off, on material procurement, on dispatch and on commissioning — and the ERP raised the milestone invoice the moment each stage completed, with work-in-progress valued so unbilled effort was always visible
- A close-out review became a mandatory final step: No project was marked complete until actual cost, total billing and real margin were compared against the estimate, with variance per cost head fed back into the estimating templates for the next quote
Results After Implementation (within the first year):
- The unbilled change-order leak was largely closed: With change orders mandatory before any extra work, supplementary billing rose by roughly ₹32 lakh in the first year — work the team was already doing for free, now properly priced and invoiced, with no additional effort on the floor
- Cross-project material cost stopped distorting margins: Project-coded stores issues ended the untracked borrowing; costing per machine became trustworthy, and an estimated ₹18-20 lakh of material that had previously been mis-allocated across projects was now landing on the right job, giving honest per-project margins for the first time
- Cash flow improved sharply through milestone billing: Moving from end-only invoicing to advance, design, procurement, dispatch and commissioning milestones pulled roughly ₹1.4 crore of billing forward across the year's projects, easing the mid-quarter cash-credit pressure and cutting interest cost on the working-capital line by an estimated ₹6-7 lakh
- Loss-making low-value machines were identified and re-priced: With overhead applied properly per project, the owner could finally prove which machines were losing money; two product configurations were re-priced and one was quietly dropped, lifting blended project margin by an estimated 3 percentage points
- Quoting accuracy improved job over job: The close-out reviews surfaced consistent under-estimation of assembly and wiring hours; correcting the estimating templates narrowed the average gap between quoted and actual cost from around 11 percent to under 4 percent within three quarters
- Project visibility ended the firefighting: Live planned-versus-actual and milestone tracking meant overruns and schedule slips were caught at 30-40 percent completion instead of at delivery, and the project-management desk stopped spending its days reconstructing where money and time had gone
Total Annual Financial Impact: Roughly ₹32 lakh of previously unbilled change-order work recovered as supplementary billing; about ₹18-20 lakh of material cost correctly re-allocated to the projects that actually consumed it, giving honest margins; approximately ₹1.4 crore of billing pulled forward through milestone invoicing, with an estimated ₹6-7 lakh of interest saved on the working-capital line; a blended margin lift of around 3 percentage points from re-pricing loss-making machines once overhead was applied honestly; and quoting accuracy improving from an 11 percent average gap to under 4 percent. The managing director's summary at the year-end review captured it best: the business had never had a profitability problem it could see — it had a profitability problem it could not see. The day the team could watch each project's margin move in real time, the leaks that had been bleeding the company quietly for years simply stopped being invisible — and most of them stopped soon after.
Key Success Factors: Building every quote from a structured, line-item estimate that became the project budget directly — so price and budget were never disconnected. Tagging every cost to the project at source, especially making project codes mandatory on stores issues, which ended the silent cross-project material borrowing. Making change orders compulsory before any extra work, turning the single biggest leak into billed revenue. Milestone billing tied to the project plan, which transformed cash flow without changing the work. And a mandatory close-out review on every project, which turned each finished machine into a sharper estimate for the next one.
Common Project Costing Mistakes to Avoid
Project costing fails in a predictable handful of ways. Naming them in advance is the cheapest insurance a project business can buy.
- Quoting from a single round number. If the quote is not broken into cost heads, there is no budget to measure actuals against and no way to learn from variance later.
- Letting material leave stores untagged. Untracked issues are how one project's cost ends up on another's books and why per-project margins become fiction.
- Doing change-order work before logging it. The extra work is rarely the problem — the missing invoice is. Log and price it before the floor touches it.
- Billing only at the end. On multi-month projects, end-only invoicing means funding the whole build out of pocket and running cash tight for no reason.
- Ignoring overhead in quotes. Quotes that cover only visible material and direct labour lose money silently, especially on lower-value jobs where overhead bites hardest.
- Reconstructing costs weeks after delivery. Costing that arrives after the project is gone is a history lesson, not a steering tool — and the next quotes are already wrong.
- Skipping the close-out review. Without an actual-versus-estimate review, every project's lessons die with it and the same estimating errors repeat indefinitely.
- Treating the project module as a to-do list. Task tracking without cost capture tells you whether work is happening, never whether it is profitable.
Frequently Asked Questions
What is project costing in an ERP and how is it different from normal accounting?
Normal accounting tells you whether the business as a whole made money this month. Project costing tells you whether each individual project made money — by tagging every material issue, labour hour, machine cost, subcontracting charge and overhead to a specific project and comparing the running total against the quoted budget. In an ERP the project becomes a cost-collection bucket: purchases, stores issues, job cards and expenses all carry a project code, so profitability per project is live, not reconstructed at year-end from ledgers.
Why do project-based Indian SMBs lose margin without ERP project costing?
Because cost is tracked at the company level in Tally and at the project level only in scattered Excel sheets updated weeks late. Material gets issued to the wrong project, extra customer-requested work is done but never billed as a change order, overtime and subcontracting creep past the quote unnoticed, and the project is declared finished before anyone adds up what it cost. The loss is invisible until year-end — by which point the next ten projects have been quoted on the same wrong assumptions.
What is planned-versus-actual cost tracking?
Planned cost is the budget built when the project was quoted — material, labour, machine, subcontracting and overhead as line items. Actual cost is what the project has consumed so far, captured live as purchases, stores issues, job cards and expenses are booked against the project code. Planned-versus-actual tracking shows the variance per cost head while the project is still running, so an overrun is caught at 40 percent completion when it can still be managed, not discovered after delivery.
What is milestone billing and why does it matter for cash flow?
Milestone billing means raising invoices at defined stages — advance, design sign-off, procurement, dispatch, commissioning — rather than a single bill at the end. For project businesses this is the difference between funding months of work-in-progress out of your own pocket and being paid as value is delivered. An ERP links milestones to the project plan so a bill is raised when a stage completes, and tracks which milestones are billed, due and overdue per project.
How does an ERP handle change orders and scope creep?
A change order is extra work the customer requests after the project starts. In an ERP it is logged as a formal addition to the project — with its own estimated cost, price and approval — so the extra material and labour are budgeted, executed and billed. Without this, scope creep is the single largest silent margin leak in project businesses: the team does the extra work because the customer asked, but it never reaches an invoice. Logging change orders turns free work into billed work.
Conclusion
Project businesses do not usually fail because the work is bad. They struggle because they cannot see, while a project is running, whether it is making the margin it was quoted at. Cost is tracked for the company as a whole but never for the individual job, change orders are executed but not billed, material drifts between projects untracked, and the real number arrives weeks after delivery. The losses are small enough to survive and invisible enough to repeat — which is why they persist for years.
Project management and costing in an ERP close that gap by making every project a live bucket that collects its own cost and compares it, in real time, against the quoted budget. Structured estimates that become budgets, cost tagged at source, planned-versus-actual visibility per cost head, change orders that turn free work into billed work, milestone billing that protects cash flow, and a close-out review that sharpens the next quote — together they turn project profitability into a steering wheel. The financial management and reporting and BI modules show how project margins roll up into the numbers the owner watches, and the full ApicalERP feature set and manufacturing solution show what the costed, tracked projects go on to power.
ApicalERP is built for project and job-order businesses — structured estimating, project-coded cost capture, live planned-versus-actual dashboards, change-order control and milestone billing — so you see each project's true margin while you can still act on it. Bring us a recent project that you suspect lost money and we will show you exactly where the margin went, and how to keep the next one.