A month-end close your auditors can read and your team can follow.
The close lives in one person’s head and a checklist nobody updated. Simetta turns it into an approved, versioned procedure, keeps the walkthrough video with it, gives your auditors read-only access, and trains the accounting team on it, step by step, on your ERP’s screens.
From the controller’s head to the audit binder
The demo company’s close runs nine steps across P21, the bank’s portal and the close folder, by the fifth business day.
- 1
Write it down, or record it
Upload the close checklist you have, or have your controller record the close on a Teams call and talk it through. Simetta writes the procedure from what was said, and asks only what it can’t tell, like the dollar limit for a reconciliation difference.
- 2
Approve it
The controller approves version 1 with an effective date. Every later change is a new version with a change note, and the approved text stays exactly as it was approved until the next approval.
- 3
Train on it
Each step becomes a guided lesson and a scored test on your ERP’s screens: cash receipts, statements, vouchers, the check run, journal entries, the bank reconciliation, closing the period. Steps in the bank’s portal or the close folder are practiced too.
- 4
Show the auditors
Give your auditor read-only access until the end of fieldwork. They see the approved procedures, every version, who approved it and when, and can download the whole binder as one PDF. They never see a draft, and they never appear on your team.
What changes for finance
The close doesn’t leave with one person
A new staff accountant learns your close on the screens before their first month-end, and the test shows they can do it.
Audit requests answered in minutes
Approved procedures, versions and approvals in one place, for the auditor to read themselves, or as one PDF binder.
Changes are controlled
A change to the procedure is a new version with a note; training built from the old version is flagged and updated.
Questions from finance
What does the auditor actually see?
The approved procedures only: the approved text of each, its version history up to the approved version, who approved it and when, the change notes, and the walkthrough video if you kept one. Drafts, training results and your people are not shown. Access ends on the date you set, a year at most, and you can withdraw it any time. Every procedure they open is recorded in your audit log.
Does the video stay with the procedure?
Your choice. Keep the recording with the procedure, stored encrypted and deleted with your company’s data, or link to your own copy in Teams or Stream. Either way it opens beside the procedure it explains.
Our close happens partly outside the ERP.
Most do. Downloading the bank statement, emailing the close package to the controller and the controller’s approval are steps in the procedure and in the training: the trainee does them beside the ERP screen, and the test checks they happened, in order, to the right person.
We already have Epicor’s training.
Keep it for how the screens work. Simetta trains your close: your deadlines, your approval limits, your folder, your order of steps, and keeps the procedure and the training in step when the procedure changes.
Who writes the questions it can’t answer?
The person who knows. Questions about the ERP itself Simetta answers from the ERP’s own documentation; questions only your team can answer go to the procedure’s owner or the department manager in one click, as a link they answer without an account.
Five minutes on the demo will tell you more than this page can.
Play a real lesson, take the scored test, then see what your manager would see.