Controllership · the ERP blueprint audit11
Activate the prior blueprint as-is? Don’t.
🧩 Project-System Module · Blueprint & Config AuditERP project accounting · WBS · milestone billing · rev-rec · IND AS 115 BLUEPRINT
Implementation partner’s prior blueprint — on file, ready to switch on
Project-system module for long-running contracts: work breakdown, cost planning, milestone billing, revenue recognition. The path of least resistance is to activate what already exists.
Existing blueprint · project accountingPARTNER DRAFT
SCOPEWork-breakdown structure & costing · project hierarchy, cost planning
BILLINGMilestone billing plan · dates entered manually per project
REV-RECRevenue account determination & results analysis · carried over as-is
⚑ Activate as-is — fastest go-live, zero rework on the partner’s config. Activate →
User-requirements spec — written precise enough to build from
1Work-breakdown structure & cost planningProject hierarchy, capacity / cost plan per work package.
2Milestone billing driven by project finish datesBilling dates derive from project dates — kills manual date mismatches that cause missed billing.
3Revenue account determinationWhere each milestone posts — P&L revenue vs contract-liability until the obligation is met.
4Results analysis & settlementSplit revenue earned, contract asset and contract liability under IND AS 115.
Gap analysis vs the prior blueprint — auditing every config line…
Not gaps — errors — would post IND AS 115-non-compliant entries
Error 1Revenue account determinationIND AS 115
✗As-isUp-front milestone → straight to P&L revenue
✓CorrectUp-front milestone → contract-liability account until the obligation is met
Error 2Results analysis / settlementIND AS 115
✗As-isCredits revenue in a way that double-counts earned vs unearned
✓CorrectCleanly split: revenue earned · contract asset · contract liability
Flagged before configuration — mandatory sign-off, not a silent carry-over
✓ Revenue account determination — route up-front milestone to contract-liability. Sign-off
✓ Results analysis / settlement — split earned · contract asset · contract liability. Sign-off
✓ Caught at the blueprint: a config change is a line in a document now — not a year of mis-posted entries to unwind in a restatement later.