How Spaces helps
Your ERP or your own review rules flag unusual entries. Agents investigate each flag, gather context from your tools and record the resolution for review.
Still manual today Flags still need someone to investigate, explain and document a resolution.
Example INV-2231 and INV2231 from Acme Cloud: same amount and PO, three days apart. The vendor's email confirms a re-send, so the agent proposes voiding the duplicate before the payment run.
- Software spend to travel account Reclass proposed, invoice cited For approval
- Round-sum manual entry Confirmed by CFO email Done
- Weekend posting, OpsCo HK Scheduled batch, expected Done
- Vendor coded to wrong entity Intercompany recharge proposed For approval
- Unusual credit to revenue No support found, escalated Needs review
Every flag closed with a recorded reason
What the agent does
- Picks up flagged journal lines for investigation
- Gathers related emails, tickets and messages for each flagged entry
- Proposes a resolution with reasoning: confirm, reclassify or escalate
- Records the outcome and reviewer decision against the original entry
How it runs
- 01 Receive flags Reads flagged lines from your ERP or your own criteria, such as round sums or weekend postings.
- 02 Investigate Searches Slack, Gmail, Jira and Drive for context on the entry and who prepared it.
- 03 Propose resolution Drafts a resolution with cited evidence and, if needed, a correcting journal.
- 04 Reviewer decides The reviewer accepts, edits or escalates. Corrections post only after approval.
Each flag ends with a decision and reason on record.
Reviewers start with the evidence already assembled.
Any correcting entry follows maker-checker approval.
- Does the agent correct entries itself?
- It drafts corrections only. A reviewer approves before anything posts to your ERP.
- Can we add our own review criteria?
- Yes. Criteria such as round sums, weekend postings or recent bank detail changes sit alongside your ERP's flags.