Learning contextDemo Retail Group LLC12 stores · 2 distribution centres · AED/SAR/USD · omnichannel replenishmentChange scenario details →
Skip to content

5. Budget, timesheets and purchases ​

Back to the case study · Previous: 4. The agreement and the billing plan · Next: 6. Delivering the build

An implementation project's cost is mostly people's time, plus a few purchases. This chapter shows how both reach the project in OSERP, and how the budget tells the project manager, step by step, where the money is going.

5.1 The cost budget (Budget tab) ​

For each step, Add budget with the amount and a note. Meera entered the estimate from chapter 1, labour and purchases together, on the step that spends it:

StepBudgetNote
Process workshops53,600Labour
UX research, brand kit and app designs52,500Labour
Customization: South African VAT and VAT20140,700Labour
Android and iOS apps1,05,000Labour 30,000 + Appforge subcontract 75,000
WhatsApp and SMS notifications31,000Labour 19,000 + messaging credits 12,000
System and security testing54,500Labour 9,500 + security test 45,000
Cut-over1,75,400Labour 15,400 + go-live travel 1,60,000
Project management and governance1,87,000Labour
... 15 more steps
Total12,10,000

The header reads Budget, Cost, Committed (purchase orders placed but not yet billed) and Available = budget - cost - committed. Each phase adds up the steps below it, and a budget set on a phase controls everything under it.

The budget at the end of the project: two phases over, each overrun on the step that caused it

Budget lines are movements

A budget is never overwritten. When change order CO-001 was approved (chapter 7), OSERP added its cost of 53,000 as a second line (v2) on Customization: age verification and wine club. The original line stays, so the trail from tender to final budget survives. That is why the total budget is now 12,63,000.

5.2 Hours: from timesheet to project cost ​

Entering time ​

Each consultant books their week at People & Payroll > Timesheet (My Timesheet). + Add a project or site asks What was the time spent on?: pick the project, then the step. That adds a row, and the hours go in the day's cell. Hours can be typed as 4, 4.5, 4:30 or 90m.

FieldExample (Sanjay, week of 13 July)
RowProject KLV-ERP-2026, step 1.5.2 The Courier Guy shipping and tracking
Tuesday 14 July6
What was doneRebuilt waybill creation on the courier's new API version
Billableticked

Send for approval locks the week until someone decides on it. Meera approves the team's weeks, or sends one back with a reason. An approved entry is evidence behind an invoice and can no longer be changed. A week still in draft can.

Costing it to the project (Team & time tab) ​

Once a month, Labour costing: set Up to to the month end, then Preview shows the hours and their value at each person's cost rate. Post labour cost posts one journal:

DebitCredit
Project Labour Cost (tagged to the project and the step)value
Labour Cost Absorbed to Projectsvalue

Labour costing does not add any new cost to the company. Payroll has already posted the salaries. This journal moves the share spent on the project into the project, step by step, and the second account reduces salary expense by the same amount, so total costs do not change. Each costed hour is marked, so it can never be costed twice.

Team & time at the end: 1,126 approved hours, all costed, worth 10,12,700

PersonPlanned hoursActual hoursCost valueWhy the difference
Meera Nair2002002,20,000
Arjun Menon1501501,27,500
Kavya Pillai1701701,44,500
Rahul Varma1401401,12,000
Sanjay Kurian2202962,81,200+24 courier API rework, +12 importer feed, +40 change order CO-001
Ananya Thomas1401701,27,500+10 App Store resubmission, +20 change order CO-001
Total1,0201,12610,12,700

The panel also shows Billable, not billed hours and their Bill value at each person's bill rate: 19,24,200 here. On a fixed-price contract they are not invoiced. The figure shows what the same work would have earned at time-and-materials rates.

5.3 Purchases: order, bill, pay ​

Every purchase for the project goes through Purchasing - A/P > Unified Purchase Workspace, the same flow the company uses for any purchase. Two fields make it a project cost:

FieldEnteredWhy
ProjectKLV-ERP-2026The cost appears on the project.
WBS element (Dimensions, under Show header)the step it serves, for example 1.4.3 Android and iOS appsThe cost lands on that step's budget line.

The stages used here:

  1. Purchase Request: vendor, lines (description, quantity, unit, unit price) and Tax % (18 for an Indian supplier's GST, 0 for pass-through travel).
  2. Purchase Order: the order is placed. The amount becomes Committed on the step's budget. This is the moment to look at Available: the order is a promise, and an overspend seen at the bill is too late to change anything.
  3. AP Invoice: the supplier's bill arrives. Enter its number in Vendor ref. no. and choose the lines and quantities billed. The commitment turns into cost. The GST goes to input credit, not to the project.
  4. Vendor Payment: the bank payment, with the payment mode and reference.

Appforge's iOS subcontract: request, order, bill and payment, tagged to step 1.4.3, IGST 18%

OrderSupplierOrderedBillNet (project cost)GST (input credit)Paid
PO-2026-00001Appforge Mobile Studio LLP1 JulBILL-2026-00001, 31 Jul75,00013,500 IGST14 Aug
PO-2026-00002Signalbird Messaging Pvt Ltd15 JulBILL-2026-00002, 20 Jul12,0001,080 CGST + 1,080 SGST31 Jul
PO-2026-00003Kestrel Security Labs Pvt Ltd20 JulBILL-2026-00003, 7 Aug45,0004,050 CGST + 4,050 SGST28 Aug
PO-2026-00004Skyline Travel Services Pvt Ltd5 AugBILL-2026-00004, 25 Aug1,52,000none28 Aug
Total2,84,00023,760

Travel came in 8,000 under its 1,60,000 budget. The other three were billed exactly as ordered.

GST on an exporter's purchases

Nimbus's invoices carry no GST, so it has no output tax to set the 23,760 of input credit against. An exporter under LUT can claim the unused credit as a refund. Keep the suppliers' GSTINs correct on the vendor master (chapter 2). A bill booked against a vendor with the wrong state or no GSTIN loses the credit.

5.4 What the project cost ​

BudgetActual
Labour (1,126 hours)9,71,00010,12,700
Purchases2,92,0002,84,000
Total (budget includes CO-001's 53,000)12,63,00012,96,700
Over budget33,700

The overrun is 41,700 of extra hours (courier API 22,800, importer feed 11,400, App Store resubmission 7,500), less the 8,000 saved on travel. The Budget tab showed each extra hour on the step that caused it, in the month it was costed.

What this chapter meant for the money ​

The costs came in from two directions, people's hours and suppliers' bills, and both landed on the same budget lines. Meera never had to rebuild a spreadsheet to know where the project stood. The 33,700 overrun was visible in July, two months before the end, while there was still time to recover it (chapter 7).

OSERP™ Atlas · Understand every field. Master every workflow.