RightRev RightAgents: AI revenue agents, human sign-off first

RightRev just shipped seven AI agents for revenue accounting, and the design rule is the story: nothing posts to the ledger until a person approves it. The agents are called RightAgents. They pull contract terms, draft revenue rules, reconcile systems and explain variances. And they are reachable from Claude and ChatGPT over MCP, per RightRev's announcement. That is the right shape for any AI agent that touches your books.

What actually happened

RightRev, an Austin revenue-recognition platform, announced RightRev AI on November 12. The key parts:

• Seven agents. Anomalies, Contract Checklist (checks terms against ASC 606 or your own checklist), Revenue Assistant, Architect (drafts rules from plain English), Use Case Modeling, Flux (explains period-over-period changes) and Reconciliation.
• Approval gates everywhere. Architect rules need team approval before they go live. Contract Checklist and Flux output goes to sign-off. RightRev says "a person approves everything before it posts."
• MCP access. All the agents are available through MCP, so teams can run them from Claude, ChatGPT and other AI tools "within each person's existing permissions."
• Rules engine underneath. The revenue number is calculated by rule from the contract. The agents work against that number. They do not invent it.
• Availability. RightRev AI is available to RightRev customers and works alongside any billing system or ERP. RightRev did not publish pricing.

RightRev says it processes more than $44 billion in annual customer revenue. Named customers include William Reed, ChiliPiper and Duck Creek Technologies.

Why it matters for your business

You are probably not buying RightRev. If you run on QuickBooks and Stripe, it is likely more tool than you need. Steal the architecture instead. It is the pattern we push on every finance automation we build:

1. Math by rule, not by model. Let deterministic code calculate the numbers. Use the AI to gather, match, flag and draft.
2. The AI drafts. A human posts. An agent that writes journal entries straight to your books is a liability, however good it is.
3. Permissions follow the person. If a bookkeeper can't see payroll in QuickBooks, their AI assistant shouldn't see it through MCP either.
4. Every entry traces back. Contract, data, rule. If you can't show an auditor where a number came from, the time you saved doesn't count.

MCP makes this easier. Your finance tools can show up inside the AI chat your team already uses, without a new login. But "the agent can reach it" and "the agent can write to it" are two separate decisions. Make the second one on purpose.

Sources: RightRev via PR Newswire, RightRev.