Finance requirements before configuration
The system should support the operating model, not become the operating model. We start with the outputs finance, program management and leadership need, then work backward into data structure, workflows, controls and reporting requirements.
Support can complement the software implementer by representing the finance and GovCon operating requirements that determine whether the system is useful after go-live.
Typical scope
- Finance and reporting requirements
- Chart of accounts and project-structure review
- Indirect-rate configuration requirements
- Management-reporting design
- Data validation and reconciliation
- User-acceptance test scenarios
- Close-process and control design
- Post-go-live finance stabilization