Operational Information

Businesses can lose revenue in small, hard-to-spot ways: failed recurring payments, unpaid invoices, mismatched contract values, overlooked billing changes, or gaps between a customer record and what is actually being billed. Recoupant is designed to bring these signals together, help teams prioritize the ones worth investigating, and organize the next steps.

The operating model follows a straightforward path: connect relevant systems, analyze available records, identify potential discrepancies, review opportunities, and coordinate approved actions. Recovery estimates are estimates—not guarantees—and should be evaluated against the source records and business context.

Use the Revenue Assessment to explore potential leakage, the Knowledge Center for deeper explanations, and the Learning Center for practical guides.

Recoupant's subscription structure is designed to scale from foundational assessment and auditing to larger, more complex operational environments. Plan names and entitlements are organized around the needs and scale of the business.

• Audit Flow: A foundational entry point focused on revenue-recovery assessment, reconciliation gaps, and identifying opportunities. Advertainment is being considered for public website access, with placement and format still being worked out; it may be explored as a future addition to the Audit Flow experience. No specific dashboard ad placement is being defined here.
• Business Pro and Business Max: Designed for growing businesses managing recurring billing, past-due invoices, involuntary churn, and recovery workflows.
• Industry Pro and Industry Max: Intended for organizations with higher-volume or more specialized operating requirements, including sector-specific reconciliation and reporting needs.
• Enterprise Pro and Enterprise Max: Designed for complex, high-volume operations, with deeper API access, custom integrations, advanced AI assistant tools, and expanded Automated Recovery Unit (ARU) allowances.
• Franchise Pro and Franchise Max: Designed for multi-location and franchise operations that need to review revenue performance and discrepancies across a broader network.

Across higher-tier environments, Recoupant's product direction includes autonomous background execution within configured limits, and high-volume, multithreaded processing to support larger workloads. Plan allowances, features, and pricing are described on the Plans & Pricing page.

Automated Recovery Units are designed to represent an account's allowance for qualifying operational workflows during a billing period. Each subscription tier has an allowance suited to its intended workload. ARUs help define how much workflow activity an account can run under its plan.

The intended model separates identifying a potential issue from carrying out a qualifying operational workflow. A detected opportunity is information to review; it is not automatically the same thing as an executed recovery action. The precise ARU accounting rules—including which operations count, how unsuccessful attempts are handled, and how limits reset—belong with the plan and workflow rules as those details are finalized.

When an account reaches its allowance, the design goal is to preserve visibility into its available information while limiting further ARU-governed activity until the allowance resets or an authorized plan or allowance change takes effect. Consult the pricing and plan details and the Learning Center for related guidance.

Recoupant is designed to connect relevant financial and customer information so teams can compare what business systems say should happen with the billing activity recorded in connected systems. Available connectors include Stripe, HubSpot CRM, Salesforce CRM, and Custom API connections, subject to connector configuration and permissions.

Payment and billing data can provide information about customers, invoices, subscriptions, and transactions. CRM records can provide business context such as account relationships, opportunities, and contract information where the integration supports those records. Custom API connections can help fit Recoupant into a business's wider systems architecture.

Connector capabilities and required permissions can differ. Use the Integrations area to review available connections and the Learning Center for setup guidance. Grant only the permissions needed for the workflows you intend to use, and follow the connector's current instructions.

The following example illustrates how a business might compare payment data with CRM contract information. The exact fields and matching methods depend on the connected systems and the workflow being used.

1. Ingest relevant records. A billing connector provides supported invoice, subscription, or transaction details. A CRM connector provides related account or contract context where available.
2. Match records. Explicit shared identifiers—such as a business account ID stored in supported metadata—can provide a direct matching path. Where those identifiers are absent, additional matching methods may be considered, with ambiguous matches flagged for review rather than treated as certain.
3. Compare values. Recoupant can be designed to compare relevant billing activity with expected amounts or account details to identify a potential variance.
4. Present the finding. A potential discrepancy can be organized as an opportunity for a team to investigate, validate against source records, and prioritize.
5. Apply the appropriate authorization. Any consequential recovery action follows the configured permissions and authorization requirements for that workflow.

Recoupant is designed to keep consequential financial workflows behind defined authorization and permission controls. Detecting an opportunity and carrying out an action are separate steps. The intended safeguards include permission checks, plan-entitlement checks, authorization boundaries, and audit records appropriate to the operation.

Recoupant should not be treated as permission to move funds, change a live subscription, or contact a customer simply because a discrepancy has been detected. Any action must be supported by the relevant connector, enabled for the account, and authorized through the applicable workflow. Human review remains an important control for validating unusual or consequential findings.

For the applicable legal and data-handling framework, read the Terms of Service, Privacy Policy, and Terms, Privacy & Security overview.

Recoupant uses subscription billing with plan-specific features and usage allowances. The selected plan determines the applicable subscription price and entitlements. Review the Plans & Pricing page before subscribing and consult the applicable terms for subscription management and cancellation details.

For U.S. customers, Recoupant's published refund policy describes a 14-day discretionary refund window and the conditions that may affect eligibility, including successful revenue recovery activity. Cancellation and refunds are separate processes; the full conditions are set out in the Refund & Cancellation Policy.