The four-day monthly report
A Finance Controller at a Hyderabad-based infrastructure contractor described the moment she decided something had to change. At the end of every month, she was spending four days assembling the project cost report: pulling actuals from the accounts team's Tally ledger, physical progress figures from the PM's Excel, and plant utilization from site photos on WhatsApp. By the time the numbers were clean and consolidated, the management meeting where they mattered had already happened.
What she needed was not complicated. Actual cost against budget, broken down by cost type, for each active project. That data existed. It was just sitting in three separate places in three incompatible formats.
This guide covers what a Finance Controller actually sees in CivilBolt, how the financial data model works, and where the current limits are. We will be direct about both.
What the financial model is built on: cost codes
Every financial view in CivilBolt runs on cost codes. Before touching the budget screen, a Finance Controller or admin needs to set up the cost code structure at the organization level.
CivilBolt provides four standard import templates:
- - CivilBolt Default: general-purpose hierarchy for mixed infrastructure work
- MoRTH 5th Revision: aligned to the Ministry of Road Transport and Highways cost taxonomy for highway projects
- CPWD DSR 2024: Delhi Schedule of Rates for building and civil works under CPWD
- IRC Bridge and Structures: cost code structure for bridge and structural packages
Each cost code carries a cost type: Labour, Material, Plant, Subcontractor, or Overhead. This five-type classification is the canonical breakdown that appears in every cost report, every budget line item, and every EVM calculation. It maps directly to the MoRTH five-bucket structure used in NHAI project financial reporting.
The practical consequence: if site staff enter actual costs without tagging them to a cost code, or if codes are set up inconsistently across projects, the FC's cost reports will show unclassified entries that cannot be attributed to a type. Cost codes are the spine of the system. Getting them right at project setup determines whether the financial data is usable.
The budget screen: what the numbers mean
The budget module has nine tabs. The ones a Finance Controller will use most:
Budget Plan shows the line-by-line cost estimate. Each line has: Description, Cost Code, Cost Type, Original Budget, Modifications (approved scope changes since award), Revised Budget, Committed Cost, Actual Cost, Variance, Percentage Used, Retention Held, and Net Payable. This is the live working budget — not a snapshot, not an export.
Overview is the variance dashboard. Four KPI cards at the top (Original, Revised, Committed, Actual), a budget utilization bar, and a table of the top over-budget line items. The cost breakdown by type (Labour, Material, Plant, Subcontractor, Overhead) shows where the project is heavy relative to plan. This is the screen to open first in any monthly review.
Actual Costs is the immutable ledger: every cost entry that has been posted, in date order, with cost code and category. The FC can filter by cost type. This is the audit trail.
Baselines saves point-in-time snapshots of the budget. CivilBolt stores up to eleven baselines per project (B0 through B10). B0 is the original contract budget at award. Each subsequent baseline captures the budget after a significant scope change or variation order approval. Comparing the current budget against B0 shows the total scope movement since contract start.
Changes is the variation order log: approved modifications, pending requests, and rejections. Each entry records who requested it, the reason, the amount, and whether it was approved. This feeds the Modifications column in Budget Plan automatically.
EVM: what CPI and SPI mean for a Finance Controller
The Performance tab computes Earned Value Management across all fourteen standard PMBOK metrics. For a Finance Controller who is not a project manager, two numbers matter most:
CPI (Cost Performance Index) is actual cost efficiency. A CPI of 0.92 means the project is spending Rs. 1 for every Rs. 0.92 of work it has completed. The project is running 8% over budget on work done so far. CPI below 1.0 means cost overrun is already happening, not just forecast.
EAC (Estimate at Completion) is what the project will cost if current cost efficiency continues to the end. If the original budget is Rs. 280 crore and CPI is 0.92, EAC is approximately Rs. 304 crore. That gap is the financial exposure to report to management.
SPI (Schedule Performance Index) measures schedule efficiency — whether the project is earning value at the planned rate. SPI below 1.0 means the project is behind schedule, which usually predicts future cost overruns as the team works to recover time.
The EVM tab has a status date picker. Set it to the last day of the month for monthly performance reporting. The S-Curve shows three lines: Planned Value (what was budgeted to spend), Earned Value (what has been completed), and Actual Cost (what has been spent). The gap between Earned and Actual is the cost variance. The gap between Planned and Earned is the schedule variance.
One thing the FC needs to verify: EVM only works correctly if the PM team is keeping tasks updated with percentage complete, and if actual costs are being entered against the correct cost codes. If the task board is not maintained, CPI will look artificially good because Earned Value will be understated. The Finance Controller is the most motivated person in the company to make sure this discipline exists.
Cross-project view: Portfolio Reports
The Portfolio Reports screen is in Org Settings, not inside any individual project. It shows cost code performance aggregated across all active projects, filtered by year.
The summary shows: number of active projects, active cost codes, total budgeted across all projects, and total variance. The table breaks down by cost code: Code, Description, Budgeted, Actual, Earned, and Variance across the whole portfolio.
This is the screen for the question: "Are we over budget across the board on Plant, or is it concentrated in one project?" If Plant costs show a consistent adverse variance across six projects, the problem is not project-specific. It is in the estimating assumptions or the market rates.
The Portfolio view does not let you drill from the rollup into a specific project's line items in one click. If the Plant variance is significant, you navigate to the individual project and review it separately.
What CivilBolt does not do yet
This is the honest section.
Tally integration. There is no connection to Tally or any other accounting system. Actual costs entered in CivilBolt exist only in CivilBolt. The accounts team's Tally ledger remains separate. CSV export is available from the Actual Costs tab for manual reconciliation. A contractor looking for automatic two-way sync will not find it in the current version.
RA Bill document generation. The Billing tab captures RA bill data (amount certified, IPC number, payment date, retention), but does not generate the formal RA Bill document in NHAI or CPWD format. The bill itself is still assembled elsewhere. What CivilBolt tracks is the certified amount, outstanding balance, and retention position — useful for cash flow monitoring, but not a replacement for the billing clerk's Excel.
Automated report scheduling. All exports and reports are on-demand. There is no automated monthly email of the EVM report or a scheduled baseline snapshot. A Finance Controller who wants the EVM report on the 1st of every month needs to open it and export it on the 1st of every month.
Multi-currency. CivilBolt is INR only. Contractors with foreign-currency contracts or international joint ventures cannot use multi-currency cost tracking.
Who this actually works for
A Finance Controller at a mid-market contractor with five to twenty active NHAI or CPWD projects, using Tally or a similar accounting system, will find CivilBolt most useful as the project-level cost intelligence layer that Tally does not provide. Tally tells you what was spent. CivilBolt tells you what was budgeted, what variance looks like by cost code and project, and where EAC is tracking against contract value.
The two systems do different jobs. CivilBolt does not replace the accounting system. It fills the gap between the accounting system and the project team that most mid-market contractors currently fill with Excel.
Setting up cost codes correctly, enforcing cost code discipline across the project team, and using the baseline function at every significant scope change: these three habits determine whether the financial data is clean enough to act on. A Finance Controller who installs CivilBolt without establishing these disciplines will have a well-designed system producing unreliable numbers.
Explore the project management module to see the budget and EVM screens, or check the cost code setup guide for how to configure the MoRTH-aligned taxonomy from the start.