How Spaces helps
Your ERP's matching rules clear most bank lines. Agents research the exceptions that remain across emails and remittances, and propose resolutions with evidence.
Still manual today Unmatched exceptions still need someone to research them across emails, remittances and bank contacts.
Example Unknown credit of SGD 2,180: a remittance email from Globex Media references invoice INV-77812 as a partial payment, so the agent routes it to cash application.
Bank exceptions · SGD operating account · October
- Incoming SGD 24,600 Customer remittance email found Done
- Outgoing SGD 1,150 Bank fee notice, entry proposed Done
- Incoming SGD 7,800 Two invoices, partial match For approval
- Outgoing SGD 52,000 Vendor payment, reference missing For approval
- Incoming SGD 3,000 No context found, bank query drafted Needs review
Exceptions left after your matching rules
What the agent does
- Reads unmatched statement lines after your matching rules run
- Searches Gmail and Slack for remittances, bank notices and payment context
- Proposes a resolution: a match, a new entry or a bank query
- Drafts bank or customer queries for unresolved items
How it runs
- 01 Read exceptions Pulls statement lines left unmatched after your rules have run.
- 02 Research Looks for remittances, bank emails and internal messages tied to each line.
- 03 Propose resolution Suggests the match or entry, with evidence and reasoning attached.
- 04 Approve The treasury reviewer approves. Matches and entries are completed in your ERP.
Exceptions arrive researched
Reviewers see the likely answer and its source.
Bank queries drafted
Unresolved lines get a ready query for the bank.
Matching stays in your ERP
Approved resolutions are completed there.
- Does it contact the bank directly?
- It drafts the query. Your team decides whether to send it.
- Can the agent create entries for bank fees?
- It proposes them. A reviewer approves before anything posts.
