No migration. No new software. Writes you can scope.
Roy connects to your ERP with the permissions your IT team grants: read access, and write access only where the dispute work requires it.
Roy, our AI agent, starts preparing disputes for review.
What connecting does not require of you
Do I have to migrate my data?
No. There is no data migration. Your records stay where they are, in the system of record you already run.
Do I have to replace or change my ERP?
No. Nothing is replaced. Roy reads from the system you already have.
Does my AR team have to learn new software?
No. There is no new software for your team to learn. Your team keeps working the way it works.
What Roy reads, and what Roy writes
Roy reads broadly and writes narrowly.
Roy reads the records that decide a deduction: the purchase order, the invoice, the bill of lading and proof of delivery, the EDI 850, the remittance advice, and the chargeback notice itself.
| Record | What it answers |
|---|---|
| Purchase order and EDI 850 | What was ordered, at what price, on what terms. |
| Invoice | What was billed against that order. |
| Bill of lading and proof of delivery | What the receiver signed for. |
| Remittance advice and the chargeback notice | What was deducted, and the reason code the retailer applied. |
Together those records support the three-way match, purchase order to invoice to proof of delivery or BOL, on quantity, price, and ship or receipt. That match is what turns a disputed deduction into a documented one.
Records are read from your ERP, from the mailboxes where retailer notices land, and from the retailer portals themselves.
Roy creates the chargeback case in your ERP, records its outcome, and sets the action code on that claim.
For customers who buy order entry, Roy also writes purchase orders, which includes incrementing your ERP’s own order control-number sequence.
Those functions are the only ones that write, and none of them deletes anything.
The outer boundary is the permission set your IT team grants the login. Scope that login read-only and none of it can write.
What you actually have to do
There are no setup fees and no long-term lock-in.
The AMT ERP partnership
Optimal Business Solutions (OBS), maker of AMT ERP for fashion and general merchandise wholesalers, partnered with ROIAI One to bring chargeback dispute recovery to AMT ERP customers.
What the AMT integration reads and writes · Read the announcement
Who reviews what gets filed
| Who | What they do |
|---|---|
| Roy | Reviews each deduction, assembles the evidence and prepares the dispute. |
| 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.
Frequently asked questions
- What can Roy write into my ERP?
Roy creates the chargeback case in your ERP, records its outcome, and sets the action code on that claim.
For customers who buy order entry, Roy also writes purchase orders, which includes incrementing your ERP's own order control-number sequence.
Those functions are the only ones that write, and none of them deletes anything. The outer boundary is the permission set your IT team grants the login: scope the login read-only and none of it can write.
- Do I have to migrate my data?
- No. There is no data migration. Your records stay where they are, in the system of record you already run.