UAT Is Not a Technical Test. It Is a Finance Sign-Off. And You Are the Signatory.
In your finance career you have signed off a lot of things.
The management accounts. The statutory accounts. The audit file. The year-end journals. The grant return.
You sign because you understand what you are certifying.
UAT — User Acceptance Testing — is the same principle applied to an ERP system.
Before Oracle Fusion goes live, the finance team must confirm:
Can we process an AP invoice from receipt to payment with the correct approval workflow, the correct GL coding, and the correct payment terms?
Can we run the period close from AP cutoff through to a signed trial balance — in the system — with the correct journal sequence?
Can we run payroll, post the journals to GL, and reconcile the payroll creditor control account?
Can we produce the management accounts from Oracle — and do they agree to what we would expect to see?
Can we run the CIPFA SERCOP return from Oracle without manual manipulation?
If you can answer YES to all of those — in a test environment, with test data — the system is ready for go-live.
If you cannot — it is not. And a Finance BA who understands what each test is proving is the person who can make that call.
Not the Oracle consultant.
Not the Programme Director.
The accountants who understand what these reports and processes are supposed to produce.
**Discussion question:** If you had to test your current finance system from scratch, what would be the three processes you would test first — and why?
Fall4U FCA FCCA — Future Defined Academy