Platform

Roy, and the systems it reads and writes

The shape of it

Roy is ROIAI One's AI agent for retailer deductions.

It reaches the records that decide a case in your ERP, in the mailboxes where retailer notices land, and in the retailer portals themselves.

It reads broadly and writes narrowly, and ROIAI One's own analysts review and release what it prepares.

The work

What Roy does with a deduction

Done by hand, every deduction is worked one at a time, a different portal, reason code, and evidence pack for each retailer.

Roy reads the chargeback, gathers your documents and drafts the dispute, ready for review. After review, packets are filed to the retailer portal or emailed to the right contact.

The surfaces

Where Roy works, and what it does there

Roy reads broadly and writes narrowly.

The three surfaces the ROIAI One platform works across, what Roy reads on each, and what Roy writes on each.
SurfaceWhat Roy reads thereWhat Roy writes there
Your ERPThe records that decide a deduction: the purchase order and its EDI order record, the invoice, the bill of lading and proof of delivery, the remittance advice, and the chargeback notice itself.Roy creates the chargeback case, records its outcome, and sets the action code on that claim. Today, those functions are the only ones that write, and none of them deletes anything. Order entry is in early access. Ordy will prepare emailed purchase orders for an analyst to approve. It's in build, and it isn't running in any ERP or for any customer yet. Penny, our cash application digital employee, is in early access for design partners. It's in build, and it isn't running for any customer yet.
The mailbox where retailer notices landThe retailer's own deduction notice and the remittance that carried it, which is where the authoritative reason for a charge lives.Where a retailer takes disputes by email, the finished packet is emailed to the right contact rather than filed to a portal.
Your retailer portalsDeductions that arrive by portal and never touch your ERP.The finished dispute packet, filed the way that retailer accepts filings. Each retailer takes disputes its own way.

The outer boundary is the permission set your IT team grants the login. Scope that login read-only and none of it can write.

The review layer

Who checks what gets filed

Roy reviews each deduction, assembles the evidence and prepares the dispute, and ROIAI One’s own analysts review and release it. That review is selective and exception-based. This is our AI-native Service-as-a-Software model: the review burden is ours, not yours.

Roy is also not always a yes. Where the evidence says the charge is valid, Roy says so. The security and access overview covers how that access is scoped in practice.

In detail

The two platform pages, and what each answers

For what the platform is pointed at rather than how it is built, the solutions pages route by problem, and the retailer intelligence library covers the channel, evidence, and reason codes for a specific retailer.

See it against your own deductions

The platform is easier to judge on your own book than in the abstract. We look at your deduction history and tell you what is worth recovering.

Chat with Roy