Claude-powered agents on top of Salesforce · Resolve · Snowflake · Great Plains — human-in-the-loop on every dollar out.
Notifications
No notifications yet — run the Live Demo to see updates from the agents.
Powered by Attri Agents
IFS's money moves through two pipes.
📥 Money In
Carrier payments arrive by email & bank — sometimes unidentified, sometimes one payment for many cases.
match & split▶
IFS
Salesforce · Resolve · Snowflake
check & approve▶
📤 Money Out
Periodic payments to claimants, carriers & vendors — where one wrong DOB or payee is costly and hard to undo.
We put a Claude agent on the two spots that hurt most — as a light layer on top of the systems IFS already uses. No ERP change. Nothing ripped out.
Every Claude agent follows the same loop.
1
Reads
A forwarded email, a messy remittance PDF, a payment file.
2
Shows its thinking
Its reasoning is on screen — verifiable in seconds.
3
Proposes
A clear action with a confidence score.
4
Person approves
Approve, tweak, or block. Money-out always stops here.
5
Acts & logs
Posts the result and writes an audit trail.
📥 Money in — four features
Automatic intake no re-keying
A payment arrives by email or bank and is captured automatically — no one re-keys it by hand.
Auto-match to the case with confidence
Each payment is matched to the right case and shows its confidence; the reviewer just confirms.
Needs-review list one short list
Anything it can't match goes to one short list, with a one-click email to the carrier asking who it's for.
Split bulk payments one → many
One payment covering several cases is split across them automatically, with a record of how.
📤 Money out — four controls
Check data, block errors pre-flight
Before money leaves, it checks DOB, payee & bank details and stops anything that looks wrong.
Quick approval dual control
Fast sign-off so no single person can push a bad or unauthorized payment through alone.
Payments on schedule recurring
Recurring claimant payments run automatically, with alerts if something needs attention.
Verified payee list anti-fraud
One clean list of payees & bank details — an emailed request to change bank info is flagged before anyone acts.
See it run.
Five short beats — money in, money out, and the payoff in one screen.
Pick a beat to run.
Five short, self-contained interactions. Run them in any order.
0 / 5 run
All five beats run.
See the rolled-up totals, autonomy split and audit ledger.
Items handled / pre-checked
0
Staff hours removed
0.0h
Costly errors caught
0
Dollars matched, split & protected
$0
Autonomy split
—%
auto-handled
Agent handled & logged Escalated to a person
Money-out items always escalate — by design.
Audit ledger
No activity yet. Run the live demo to populate the ledger.
Demo figures are illustrative, modeled on the five sample items; real numbers depend on IFS volumes. Benchmark basis: manual AP ≈ $10–18/invoice vs $2–4 automated; cash-app auto-match 90%+ best case; BEC average loss ≈ $122k per incident.
Integrations — what the agents touch.
The agents sit as a light layer on top of the systems IFS already uses. Nothing is ripped out, no ERP change.
Reads come from governed data; writes go back through native APIs and stop at a person whenever money moves.
WritesLimited write-back via eConnect for matched cash-app entries — gated by reviewer approval.
AutheConnect · service account · scoped to AR posting
＋
Add another tool
DocuSign, NetSuite, Datarails, PowerBI, bank feeds — any system with an API can plug in. Each new connector is additive.
How the layer fits.
Sources of truth
Salesforce
Resolve
Snowflake
Great Plains
Email inbox
▶
Attri Agents
Cash-Application Agent
Disbursement Guard Agent
Reporting Agent
Reasoning on screen · human-in-the-loop on every dollar out.
▶
Writes back via
Salesforce API
Resolve API
eConnect (GP)
Audit log (Snowflake)
Architecture is additive — read from Snowflake via MCP, write back through native APIs.
A future GP → NetSuite swap touches mainly the connector, not the agents.