ERP Pre and Post Implementation Review

Pre-implementation: go-live readiness

Conducted before cut-over, while findings can still change the outcome. Because the system is not yet live, conclusions are on design rather than operating effectiveness — we state that explicitly in the report rather than implying assurance we cannot give.

• Programme governance, steering effectiveness and decision authority.
• Requirements traceability — whether what is being built is what was approved.
• Configuration of application controls: approval workflows, tolerance limits, three-way match, validation rules.
• Segregation of duties in the role and authorisation design, tested for conflicting combinations before they are granted.
• Data migration controls — completeness, accuracy, reconciliation and the sign-off trail.
• Interface design and reconciliation controls between the ERP and surrounding systems.
• Testing adequacy — whether UAT actually covered the control requirements, with evidence.
• Cut-over plan, fallback plan, and the criteria on which go-live will be authorised.
• Readiness of security administration, change management and support processes for day one.

Post-implementation review

Usually three to six months after go-live, once a full period cycle has run. Here we can test operating effectiveness: whether the configured controls are working, whether workarounds have emerged, whether emergency access granted during cut-over was ever revoked, and whether the segregation of duties design survived contact with reality.

Platforms

SAP including S/4HANA, Oracle E-Business Suite and Fusion, Microsoft Dynamics 365, and core banking and insurance platforms. We audit the control configuration; we do not implement, and we hold no implementation partner status with any vendor — so the finding is not shaped by a channel relationship.