Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 2 · Security and Data Access
Segregation of duties in project accounting
Lesson 19 of 198 · 2 min
NO SINGLE PERSON SHOULD BE ABLE TO RECORD PROJECT COST, ADJUST IT, INVOICE IT, AND RECOGNIZE THE REVENUE FROM IT. Four verbs, one person. That is the thing to prevent. The conflicts that matter. Enter or adjust expenditure items, plus generate invoices. Set bill rates, plus approve invoices. Approve a financial plan, plus report progress against it. Create a contract, plus approve its invoices. REVENUE RECOGNITION IS IN SCOPE. PROJECT REVENUE IS AN AUDITED NUMBER. The controls around who can influence revenue get looked at. Not inventory, not headcount — revenue, which is the number an audit starts from. That is what makes this module's conversation different from the equivalent in the other courses. The small-firm problem. A twenty-person consultancy has one person doing all of it, and telling them not to is not advice. Compensating controls that actually work. Exception reporting on adjustments. A second review of invoices above…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue, with a certificate on completion and a fourteen-day refund window.
In this module: Module 2 · Security and Data Access
- 1The PPM security shape
- 2Project role versus job roleFree preview
- 3The roles a PPM project needs
- 4Provisioning users
- 5Business unit data access
- 6Project unit and project-level access
- 7Segregation of duties in project accounting
- 8What breaks
- 9Lab: build the access matrix, then build to it