How Spaces helps
Rules in your ERP handle high-volume, repeatable journals. Agents draft the one-off entries that need judgment, with linked support and reasoning, ready to post after approval.
Still manual today Rules suit repeatable events. One-off, judgment-based entries are still prepared offline in spreadsheets.
Example Q4 tax advisory, services delivered in October: Dr Professional fees, Cr Accrued liabilities, SGD 12,000, with the SOW, the Slack approval thread and the partner's hours email attached.
- Reclass marketing to R&D TechCo IN · INR 1,240,000 Done
- Bonus true-up HoldCo SG · SGD 42,000 For approval
- Vendor credit note release OpsCo HK · HKD 36,800 Done
- Lease modification adjustment HoldCo SG · support incomplete Needs review
- FX gain reclass OpsCo HK · HKD 9,150 For approval
Nothing posts without approval
What the agent does
- Detects requests for manual entries in Slack, Gmail and Jira
- Drafts journal lines with accounts, dimensions and amounts from cited sources
- Attaches the reasoning and supporting documents to each draft
- Submits approved journals to your ERP through its own approval process
How it runs
- 01 Capture request Picks up an adjustment request from a Slack thread, email or Jira ticket.
- 02 Gather support Collects the contracts, invoices and prior decisions that justify the entry and its amounts.
- 03 Draft journal Builds ERP-ready lines with accounts, dimensions and a written rationale.
- 04 Approve, then post A reviewer approves in the Space. The journal then enters your ERP's own approval process.
Spreadsheet adjustments become drafted, cited journals.
Auditors see why an entry was made, not only who approved it.
Approved drafts enter your ERP's own journal approval process.
- Can the agent post journals directly?
- Only after maker-checker approval, and then through your ERP's own journal process and security.
- What about recurring journals?
- Keep them in your ERP. Agents attach updated support when the inputs behind a recurring entry change.