Sage Intacct· Testing and UAT
Sage Intacct testing and UAT
Testing shows that the configured Sage Intacct runs the client's processes from end to end. In UAT, client users confirm it with their own data and their own roles. superglue's agent writes the test scripts from the signed requirements, runs the system tests in the sandbox, and tracks UAT results and defects with the client.
How this step works
What the agent does
- Writes test scripts per process from the requirements and the design.
- Runs system tests with test transactions in the sandbox, and records the results.
- Shares a UAT tracker with the client testers and collects their results.
- Links each defect to the requirement and the setting it affects.
What you decide and approve
- Which processes go through UAT, and who tests them.
- Which defects block go-live.
- When the client signs off UAT.
What the client gets
- Test scripts with the results of each run.
- A UAT sign-off per process.
What makes Sage Intacct testing and UAT work
- 01
Test with the real roles
Log in as a test user for each role. Missing permissions and broken approvals do not show when you test as an admin.
- 02
Test every approval threshold
Submit amounts below, at and above each level. Include a department or employee with no manager assigned.
- 03
Run a full close in the sandbox
Post recurring entries and allocations, run revaluation for foreign currencies, close the books and consolidate. Compare the reports with the source for the same period.
- 04
Sort defects and sign off per process
Mark each defect as configuration, data or training, because each has a different owner. The client signs procure to pay, order to cash and close separately.
“We do 40+ Sage Intacct implementations a year, and data migration used to take half our budget on every project. superglue turned our biggest cost center into something we can scope in hours, not weeks.”
Frequently asked questions
How do you test a Sage Intacct implementation before go-live?
Test with the real roles; Test every approval threshold; Run a full close in the sandbox; Sort defects and sign off per process. The agent writes the scripts from the signed requirements and runs the system tests in the sandbox.
Do client testers need a superglue account?
No. The agent shares the UAT tracker as a link. Testers record their results there, and the agent sees them in the project.
How does superglue work with our consultants?
superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.
Can we use our own implementation method?
Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.
Which systems can we migrate from into Sage Intacct?
Common sources are QuickBooks, Sage 50, Sage 100 and Sage 200, Microsoft Dynamics GP, Xero and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.
Is client data safe?
superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.
How do we start?
Start with one live Sage Intacct project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.