How Spaces helps
Your ERP runs the allocations. Agents capture the driver and policy decisions made in meetings, Slack or email, and link them to each run as evidence.
Still manual today Driver and policy changes are agreed in meetings or email and rarely recorded with the run.
Example Shared IT cost of SGD 240,000 moves from revenue share to headcount from October, as the CFO and controller agreed in #fin-ops on 12 Oct.
Allocation runs · October · shared services
- IT cost by headcount Driver unchanged, prior decision linked Done
- Facilities by floor area New area split agreed 14 Oct Done
- Finance shared services Driver changed, no decision found Needs review
- HR services by entity Memo awaiting controller For approval
- Cloud costs by usage Usage report attached Done
One run needs a decision recorded
What the agent does
- Captures driver and policy changes from Slack, Gmail and Notion
- Links each decision to the allocation run it affects
- Flags runs whose drivers changed without a recorded decision
- Produces a run memo listing drivers, sources and approver
How it runs
- 01 Observe decisions Listens in finance channels and meeting notes for agreed driver or policy changes.
- 02 Record the change Logs what changed, who agreed and when, with the source cited.
- 03 Link to run Attaches the recorded decision to the matching allocation run.
- 04 Approve memo The controller approves the run memo before results are relied on.
Drivers with a paper trail
Every driver change is tied to who agreed it and why.
Unexplained changes surface
Runs without a recorded decision are flagged for follow-up.
Shared understanding
Business partners see the agreed basis for their charges.
- Does this change our allocation rules?
- No. Rules stay configured in your ERP. Agents capture and link the decisions, and every memo needs approval.
- Where do allocation decisions come from?
- Ops reviews, Slack threads and emails between finance and budget holders, captured with citations.
