Today
- 01Status is spread across workbooks, email and chat.
- 02Analysts spend time finding support and matching balances.
- 03Controllers see problems late in the close.
Work
01Finance operations
Close the books without the chase.
The finance team works from one close queue. The system gathers support, checks balances and prepares journals. Controllers keep approval.
See the employee workspace 5 connected systems Regional controller decides
Pilot targets
Validate with live work
D+4close target
One queuefor open work
Linkedsupport for every journal
01 The change
Less chasing. One clear place to work.
New way of working
- 01Open items appear in one queue, ordered by risk and deadline.
- 02Support is collected and matched before an analyst opens the item.
- 03The controller sees the journal, evidence and policy in one view.
02 How it works
The system prepares the work. People keep the decision.
01
CollectBring the record together
The system matches both entity balances, invoices and close support.
02
CheckFind the cause
It spots the monthly FX rate where the daily ECB rate is required.
03
PrepareDraft the correction
A $2,840 true-up journal is prepared with the right dimensions and support.
04
ApproveController decides
The controller can approve, change or return the journal. Nothing posts before approval.
Connected systems
Oracle ERPNetSuiteRampSnowflakeSharePoint
03 What the employee sees
A work screen, not another chatbot.
The employee sees the open work, the evidence behind the recommendation and the decisions that need their judgment.
Close queueRegional controller
Recommended next stepICR-2847
Use the daily ECB rate and release the $2,840 true-up.
Both entities agree on the invoice. The variance comes from the rate used on 31 July.
Both entity balances matchedDaily ECB rate confirmedJournal support attached
AnalystExceptions with the evidence already attached.
ControllerApprovals, exposure and blocked entities.
CFOClose readiness and material open items.
04 Systems and control
Connected to the tools you already use.
Access is limited by workflow. The system can read and prepare work; sensitive or final actions remain with a named person.
Oracle ERPBalances and journal status
NetSuiteSubsidiary ledger
RampExpense evidence
SnowflakeHistory and materiality
SharePointPolicies and support
ActionSystemPerson
Read balances and supportAllowedAssigned entities
Prepare reconciliationAllowedAnalyst can edit
Draft journalAllowedController reviews
Post journalAfter approvalController approves
05 How to begin
Start with one live queue.
Use real work in a controlled pilot. Compare the recommendation with the team’s decision before adding write access.
Map the close
Trace real items, controls and access.
Run beside the team
Prepare support and recommendations without posting.
Open controlled actions
Enable approved journal drafts for one entity.
Have a workflow in mind?
Discuss the workflow