Best-fit partner profile
- Serves B2B merchants, agencies, wholesalers, staffing firms, services firms, or marketplaces.
- Already supports invoicing, payments, billing, dunning, finance operations, or merchant back office workflows.
- Has merchants with overdue commercial receivables after ordinary reminders stop working.
- Can identify a pilot cohort without moving production data through an untested integration.
CSV-first pilot path
| Step | Partner action | RevRecoup action |
|---|
| 1. Select merchants | Choose a small cohort with overdue B2B invoices. | Confirm scope and merchant approval requirements. |
| 2. Export accounts | Provide debtor, invoice, amount, due date, proof links, and payment route. | Validate import, duplicates, and missing fields. |
| 3. Work first-party | Merchant remains creditor of record and owns payment decisions. | Track follow-up, disputes, proof, promises, and next actions. |
| 4. Review results | Assess merchant adoption and partner value. | Report activated merchants, scoped balance, movement, and recovery outcomes. |
Recommended import fields
- Partner merchant ID and RevRecoup organization ID.
- Debtor company name, AP contact, email, phone, and address when available.
- Invoice ID, amount, currency, issue date, due date, age bucket, and current status.
- Contract, purchase order, delivery, service, communication, and dispute evidence links.
- Preferred merchant-owned payment route and settlement approval owner.
Webhook events after pilot fit
| Event | Meaning |
|---|
| account.imported | Receivable was validated and created in RevRecoup. |
| proof.requested | Evidence gap was found and assigned. |
| dispute.opened | Debtor or merchant raised a dispute requiring owner review. |
| promise.created | Payment promise or payment plan was logged. |
| payment.recorded | Merchant recorded a payment or settlement event. |
| escalation.ready | File appears complete enough for approved escalation review. |
Integration principle
Do the minimum integration needed to validate demand. A CSV pilot is often enough to prove whether merchants want a post-dunning recovery workflow before marketplace, API, or embedded app work begins.