Project Billing and Work-in-Progress Tracking with GST for Indian Services Firms

The Billing Chaos Quietly Draining Your Margins

Your delivery team logs hours across five active client projects. Finance raises invoices once a month, mostly from spreadsheets that the project leads email over. Halfway through a fixed-fee engagement, nobody can tell you whether the project is profitable, whether you have already billed more than you earned, or whether the GST on the last invoice used the right rate. When the auditor asks for the unbilled revenue figure at quarter-end, your team spends three days reconstructing it from timesheets and email threads.

This is the daily reality for many Indian professional services firms. Project billing, work-in-progress visibility, and GST compliance live in disconnected tools. A timesheet system tracks effort. A separate accounting package records invoices. GST returns are filed from yet another portal export. The result is a chronic blind spot around unbilled work, cost overruns, and margin erosion that only becomes visible when a project loses money.

The pain is not theoretical. Indian small and medium enterprises face rising compliance costs and frequent regulatory changes under GST, and project-based services firms feel the strain most because their revenue depends on effort that is hard to quantify until it is billed. The core business system that served you for product sales is simply not built for billing work as it gets delivered.

What Changes When Project Billing Lives Inside Your ERP

The fix is not another point tool. It is moving project billing and tax configuration into the same environment where your general ledger, journal entries, and customer records already live. When the ERP owns the project, the budget, the cost, and the tax setup together, three things become possible.

Project Budgets That Capture Both Hours and Cost

Each project carries its own budget, expressed in two dimensions. The first is planned effort in hours, and the second is a budgeted cost in your accounting currency. These are not loose notes in a spreadsheet. They are structured fields on the project record that feed directly into the reports your finance team runs at month-end. When the engagement scope changes, you update the budget once and every downstream view reflects it.

Tasks sit underneath the project with their own planned and actual hours, assignees, dependencies, and due dates. This means the effort side of your budget is not a guess. It rolls up from real, trackable work that delivery teams update as they go.

Per-Member Billable and Cost Rates

Profitability on a services project depends on who does the work. The ERP stores a billable rate and a cost rate for each project member. The billable rate drives what you can invoice the client. The cost rate drives what the work actually costs you. When a senior architect and a junior developer log hours on the same project, the system can hold both rates against the same project so you can see margin per person, not just margin per project.

If a rate is not set explicitly, the cost rate falls back to the standard cost defined for that member's position. This keeps costing consistent even when project leads forget to pin a rate, while still allowing overrides for premium client engagements.

Budget-Versus-Actual Straight From the Journal

This is where project billing meets real accounting. The budget-versus-actual engine does not ask delivery teams to fill in a second spreadsheet. It reads actual posted spend for the period directly from your journal entries and compares it against the project budget. The output is a row per project showing budgeted, spent, remaining, a consumption percentage, and a derived status.

The status is deliberately simple. A project under 70 percent consumption is flagged as healthy. Between 70 and 100 percent it is on track and worth watching. At or above 100 percent it is over budget and needs attention. Your CFO gets a single screen that says which projects are bleeding before the margin disappears, not after.

Configurable Tax Settings for GST on Services

GST on services is not one rate. It varies by service category, by whether the supply is intra-state or inter-state, and by the place of supply rules. The tax settings in the ERP are built to handle this without code changes.

Each tax setting has a human-readable name, a rate between 0 and 100 percent, and two linked ledger accounts. One is the output tax account, which must be a liability account, and the other is the input tax account, which must be an asset account. The system enforces this separation at write time, so output and input GST never get mixed into the wrong side of your ledger. When GST rates change, your finance team updates the percentage in settings and every new invoice picks it up.

Invoices themselves carry per-line tax entries. Each line holds the unit price excluding tax, the line total after discount, and a structured set of tax amounts that the system sums to give the tax total and the grand total. This is exactly the shape you need to reconcile GST on services cleanly and to give your chartered accountant a tidy audit trail.

A Real-World Scenario

Consider a mid-sized IT services firm in Pune with around 80 employees running fixed-fee and time-and-materials engagements for clients in Mumbai, Bengaluru, and Singapore. Revenue is roughly 40 crore rupees a year. Until recently, the finance team raised invoices from a desktop accounting package and tracked project effort in a separate timesheet tool.

At the March quarter-close, the CFO discovered that two fixed-fee projects were more than 110 percent consumed on cost but had been billed for only 60 percent of their contract value. The firm had effectively delivered work it could not bill, while still owing output GST on what it had billed. Reconstructing the unbilled position took the team four days and exposed a 55 lakh rupee gap between earned revenue and billed revenue.

After consolidating project billing and tax into the ERP, the picture changed. Each project now carries a budgeted cost and a set of member rates. Actual spend flows from journal entries into the budget-versus-actual view. The finance team sees consumption status per project every week, not every quarter. Tax settings hold the correct GST rate per service line, and invoices carry structured per-line GST so reconciliation with the GST portal is straightforward.

The auditor now receives a project profitability report that traces every figure back to a journal entry. The chartered accountant gets clean output and input GST splits. And the CFO stops discovering margin leaks three months after they happen.

Why This Matters for India Businesses

GST on Services Is Getting Tighter

GST compliance remains a maze for small and medium enterprises in India despite the one-nation-one-tax goal. Project services firms face an added layer of complexity because the timing of revenue recognition and the timing of invoicing rarely line up. When your ERP separates earned cost, billed value, and output GST cleanly, you reduce the risk of under-reporting output tax or missing input tax credit reconciliation.

The enforcement direction is also clear. E-invoicing thresholds have been tightening, and GST 2.0 reforms are pushing firms toward real-time, structured invoice data. A tax settings model that stores the rate, the output account, and the input account as linked, validated records is exactly the foundation that kind of reporting demands.

MSME Audit and Working Capital Pressure

For MSME-classified firms, compliance costs can rise significantly relative to revenue, and working capital strain from GST payments on services is a documented problem. Project billing visibility directly affects both. If you cannot see which projects are over budget, you cannot price the next engagement correctly. If you cannot see unbilled earned revenue, you cannot forecast cash flow. And if your output and input GST are tangled in the same ledger buckets, your audit becomes longer and more expensive than it needs to be.

Clean Ledger Separation Protects You at Audit

The strongest feature here for an Indian CFO is the enforced split. Output GST must post to a liability account and input GST must post to an asset account, and the system rejects any tax setting that breaks this rule. That single discipline makes GST reconciliation, input tax credit claims, and statutory audits far less painful because the ledger structure is correct by construction rather than correct by accident.

Is This Right for Your Business?

This approach fits Indian services firms where any of the following are true. You run more than ten concurrent projects with mixed fixed-fee and time-and-materials billing. Your delivery cost and your invoice value regularly diverge. Your finance team spends more than a day each month reconciling project effort with invoices. Or your auditor has asked for a project profitability breakdown that your current tools cannot produce.

It is less critical if you bill a simple product catalogue with no project element, or if you operate a single-rate, single-state model with no services component. But for most growing services firms in India, the unbilled revenue blind spot and the GST reconciliation burden are real and recurring costs.

Frequently Asked Questions

How does project billing work when effort and invoicing happen at different times?

The ERP keeps project budget, member rates, and actual posted cost separate from the invoices you raise. Budget-versus-actual tracks earned cost from journal entries, while invoices record billed value and output GST independently. This separation lets you see unbilled earned revenue without forcing you to invoice before the work milestone is contractually billable.

Can the tax settings handle different GST rates for different services?

Yes. Each tax setting carries its own rate between 0 and 100 percent, a name, and linked output and input accounts. You can maintain separate settings for different service categories and apply the correct one per invoice line, so intra-state, inter-state, and exempt services each post to the right ledger.

Does the system support percentage-of-completion style revenue tracking?

The ERP provides the cost and budget foundations that percentage-of-completion tracking relies on, namely per-project budgeted cost, actual posted spend from journal entries, and a consumption percentage per project. Recognising revenue formally under Ind AS 115 is a finance policy decision your CA applies on top of these figures, but the underlying numbers are structured, current, and audit-ready.

The Bottom Line

Project billing chaos is not a tooling inconvenience. It is a direct cause of margin leakage, late GST reconciliation, and painful audits for Indian services firms. The firms that fix it are the ones that bring project budget, member rates, budget-versus-actual, and GST tax settings into one connected core business system instead of stitching together spreadsheets and desktop accounting.

Kikan System gives you exactly that foundation. Projects carry their own budget in hours and cost. Member rates hold billable and cost values per person. Budget-versus-actual reads straight from journal entries and flags over-budget projects before the margin disappears. And tax settings enforce the output and input GST split your auditor needs to see.

If you want to close the gap between earned work and billed revenue, start with Kikan System. The free plan supports up to 2 users with no credit card required, and you can begin at /en#get-started.