Suger Adds Revenue Recognition, AWS Referral Flows, and Usage Billing
Suger added multi-channel revenue operations with bank reconciliation and ASC 606 recognition schedules, plus Salesforce Flow handling of pending AWS engagement invitations. An August 17 release shipped usage-based marketplace billing and approval-gated deal registrations.
Suger has added multi-channel revenue operations with bank reconciliation and ASC 606 revenue recognition, in an August 24 changelog release. Sellers connect a bank account through Plaid or Stripe Financial Connections, match transactions to revenue using what Suger describes as AI-assisted suggestions routed through a human review queue, and generate recognition schedules on straight-line, point-in-time, usage-based, or milestone policies. The same release lets Salesforce Flows accept or decline a pending AWS engagement invitation and update a co-sell referral's business fields, which keeps an inbound AWS referral out of the Suger console and Partner Central. A week earlier, Suger launched a usage-based marketplace billing platform that meters and rates raw usage events, added AWS Partner Central Leads to the console and Salesforce, and began holding AI-parsed email deal registrations in an ISV review queue.
Our take: The reconciliation work is the tell. Marketplace money has been messy enough for long enough that a co-sell vendor is now shipping bank feeds and ASC 606 schedules, which is finance software wearing a partner-ops badge. Credit for putting a human gate in front of both the AI matching and the AI-parsed registrations, because a wrong transaction match is an audit problem and an auto-created registration is a channel-conflict problem. Worth sitting with what the email parsing concedes, though: partners are still sending registrations by email rather than using anybody's portal, and the fix here is to accept that instead of fighting it.
