Rex

Rex's pitch is narrower and more honest than most AR AI marketing: it doesn't claim to be your whole finance stack, it claims to run specific order-to-cash processes with agents and route the rest to your team. That's a real operating model, not a feature list. The strongest design decision is the Context Layer. Rex ingests years of email, ERP, CRM, portal and bank history so agents arrive already knowing the customer relationship, the payment terms you agreed with Target, and which invoices are outstanding. Anyone who has onboarded a collections tool knows the usual failure mode is a bot that emails a strategic account as if it were a stranger. Rex's account-level context — the Boeing card showing payment cadence drift of +7 days across three open invoices with an 82% risk score of slipping past 60-day terms — is exactly the kind of signal a human AR specialist would want surfaced first, and the agents act on it without being prompted. The second strength is control architecture. Policies and approval limits are set by you, procedures are authored from your own policies, VIP accounts and disputes escalate with context and a recommended next step, and every agent action lands in an audit log. SOC 2 Type II certification, AES-256 encryption, GDPR with EU data residency, and the explicit no-model-training commitment cover the compliance questions an enterprise finance buyer will ask. Enterprise SSO (Okta, Azure AD, Auth0), SCIM directory sync and role-based access mean the tooling fits an existing identity stack rather than standing beside it. The third is human delivery. A dedicated Rex finance expert leads onboarding, manages ongoing delivery, and reviews KPIs against agreed SLAs. That is the difference between a tool your team has to own and a service your team supervises. Where you should push: outcome-based pricing is aligned in principle but the trigger and measurement of each fee need to be pinned down in writing before you sign. The public site does not disclose tier pricing — it directs you to Contact or book a walkthrough — so there is no per-seat comparison to model against a traditional AR license. The vendor is early-stage, having launched on Y Combinator (S26) in 2026, so the reference base is thin and mostly one public logo story (Synthesia). Regional coverage beyond teams in London and San Francisco is not spelled out. The product pages do not surface an API or developer docs, so if your internal team needs to build on Rex rather than consume it, that needs a direct conversation. Where it fits: an enterprise AR function with high transaction volume, more than one ERP or multiple supplier portals, and a CFO who wants DSO reduced without adding collections headcount. Where it doesn't: a small business, a team without a formal ERP or supplier portal workflow, or a buyer who needs self-serve signup and predictable per-seat spend before committing.