How Spaces helps
Your ERP records who approved what and when. Agents add the why: decisions, policies and reasons captured with citations and maker-checker records.
Still manual today Systems record who approved what and when. The reasoning stays in Slack or email.
Example JE-104233: proposed by the accrual agent with 3 sources, reviewed by J. Tan (matches SOW hours), approved by the controller with the segregation-of-duties check passed, posted, and the audit pack retained for 7 years.
Control evidence · Q4 · journal approvals
- JE-104233 manual journal Approval reason cited, Slack thread Done
- JE-104118 accrual Maker-checker record complete Done
- JE-104377 reclass Reviewer decision pending For approval
- Supplier bank change Callback evidence attached Done
- JE-104402 top-side adjustment Approved, reason not captured Needs review
Who, when and why, together
What the agent does
- Captures the reasoning behind approvals from Slack, Gmail and Notion
- Links each reason to the transaction or approval step it supports
- Keeps maker-checker records for every agent-prepared output
- Assembles control evidence with sources for auditor requests
How it runs
- 01 Observe approvals Watches the decision threads and emails around each approval.
- 02 Capture reasoning Records the decision, the policy applied and the reason, with citations.
- 03 Link records Ties each record to the transaction and its approval step.
- 04 Review evidence The controls owner reviews evidence before it goes to auditors.
Why, not just who
Approvals carry the reasoning auditors ask about.
Evidence assembled
Control evidence is gathered with sources attached.
Clear accountability
Maker and checker are recorded for every output.
- Can one person prepare and approve?
- No. Maker-checker is enforced, so a different person approves every agent-prepared output.
- Does this replace our ERP's security or segregation of duties?
- No. Your ERP's security and segregation of duties stay in force, and agents follow those permissions.
