Together with the client, we design a future-state process that supports the business today without unnecessarily limiting how it can grow and scale.
Hover or select a stage to see the process change.Tap a stage to see the process change.
WorkaroundBottleneckHandoffDuplicationWeak controlClient knowledgeSage Intacct expertisePreserve what worksChallenge what does notClear ownershipPractical controlRoom to grow
01 / Current state
Understand how the work gets done today.
Map the current process with the people who run it, and recognize the steps, controls and knowledge that already work well.
02 / Friction
Understand the friction.
Bottlenecks, duplicate work, unnecessary handoffs, workarounds and weak controls are identified before anything is configured.
03 / Collaborative redesign
Agree a better process, together.
Preserve what works. Challenge what does not. Simplify the flow, clarify ownership and build practical controls with the client.
04 / Future state
Design the future state before configuration.
A process that supports the business today without unnecessarily limiting how it can grow and scale.
Understand the business before designing the solution.
Start with objectives and current processes. Gather requirements, assess Sage Intacct fit and appropriate scope, establish ownership and validate detailed requirements before Design.
Requirements gathering is the backbone of Discovery. Initial requirements shape fit and scope; detailed requirements are validated before Design.
8 steps inside Discovery
Business Objectives
Current Processes
Requirements Gathering
Sage Intacct Fit
Project Team
Planning & Governance
Kickoff
Detailed Requirements Validation
02 / 06
Design
Agree how the future-state operation should work.
Translate validated requirements into a solution design with the client. Review process choices, reporting, controls, integrations and migration before configuration begins.
We preserve what works and challenge what does not, before configuration begins.
Turn the agreed design into a working environment.
Configure the core solution and workflows, establish security, build reporting and integrations, and refine the environment through configuration walkthroughs.
Master and reference data are uploaded directly to production. Historical financial data is trialled in the test instance first.
Prove the solution through real business scenarios.
Test transactions, approvals, exceptions and period-end work alongside reports, dashboards and controls. Resolve identified issues and confirm the affected processes work as intended before acceptance.
Realistic end-to-end scenarios
Routine transactions
Customized workflows
Approvals
Exceptions
Corrections
Period-end processes
Reports and dashboards
Security and internal controls
8 steps inside Validate
System & Process Testing
Integration Testing
Historical Data Validation & Reconciliation
Reporting Validation
User Acceptance Testing
Issue Resolution & Retesting
Role-Based Training
Final Readiness & Cutover Confirmation
05 / 06
Go-Live
Make the transition with financial integrity in view.
Plan toward the agreed go-live date while continuously monitoring readiness, dependencies and risks. Confirm solution, data, integration and user readiness before executing the agreed cutover plan.
Confirmed before cutover
Solution
Data
Integrations
Users
7 steps inside Go-Live
Execute Cutover Plan
Final Historical Data Migration
Reconciliation
Activate Production Processes & Integrations
Production Validation
Begin Live Operations
Transition to Hypercare
06 / 06
Support
Carry confidence into live operations.
Stabilize the environment and validate significant first cycles, such as a payment run, billing cycle, bank reconciliation or month-end close. Continue with practical Sage Intacct expertise as requirements evolve.
These disciplines run through every stage. Select a stage to see what each one contributes.
Project Management & Governance
Discovery: Confirm objectives, scope, roles and project governance.
Design: Agree design decisions and secure sign-off.
Build: Track configuration progress, decisions and risks.
Validate: Manage issue resolution and readiness decisions.
Go-Live: Execute the agreed cutover plan.
Support: Transition into hypercare and ongoing support.
Data & Migration
Discovery: Identify data sources and the history that needs to move.
Design: Design the chart of accounts, dimensions and migration approach.
Build: Map, validate and upload master data; trial historical migration in test.
Validate: Validate and reconcile historical data.
Go-Live: Complete the final historical migration and reconciliation.
Support: Reconcile first live cycles in production.
Integration
Discovery: Identify connected systems and integration requirements.
Design: Design each integration with the Integration Blueprint.
Build: Set up integrations, mappings and exception handling.
Validate: Test integrations end to end.
Go-Live: Activate production integrations.
Support: Monitor exceptions and confirm ownership.
Testing & Quality
Discovery: Capture the requirements later testing must prove.
Design: Define realistic business scenarios for testing.
Build: Walk through configuration and refine it.
Validate: Run system, process and user acceptance testing.
Go-Live: Validate production processes.
Support: Validate first cycles such as payment runs and month-end close.
Training & Change Enablement
Discovery: Identify the roles and processes affected.
Design: Map roles to future-state processes.
Build: Prepare key users and training materials.
Validate: Deliver role-based training.
Go-Live: Support users as live operations begin.
Support: Transfer knowledge and enable administrators.
Data & migration
Different data. Deliberate paths.
Master and reference records are mapped, validated and approved, then loaded directly into production. Historical financial data follows a separate test, validation and final migration path.
Hover or select a path to trace its route.Tap a path to trace its route.
Starting point
Test instance
Production
Bypasses Test
Chart of accounts, entities, dimensions, vendors, customers, bank accounts, credit cards and similar records.
Map & validate the records
Bypasses the test instance: validated and approved, then uploaded directly to production.
Approved upload to productionConfigured production environment
Historical financial data
1Trial migrationInto the test instance2Validate & reconcileCompleteness, accuracy and correctness
3Final migrationApproved data into production during Go-Live4Reconciled production balancesReconciled again after the final migration
Systems and people, prepared together
The environment is only part of readiness.
Test the connected processes and prepare the people responsible for live operations.
Integrations with clear ownership.
Agree how information moves, where exceptions are resolved and how the financial result is reconciled.
