Subscription modification endpoints now support an optional boolean parameter: allow_invoice_credit_note_or_void.

    •    Defaults to True (maintains existing behavior).

    •    Set to False to prevent modifications that would create a credit note or void an invoice. Instead, such requests will fail with a validation error.

When to use this

Certain modifications, like canceling a subscription mid-period with an in-advance fixed fee, typically generate credit notes. If you’re confident your modifications shouldn’t create these, set allow_invoice_credit_note_or_void=False as a safeguard.

Equivalent to a Dry-Run

This functions similarly to sending a dry-run request and previewing changes first, which allows for more precise validation of side effects.

Supported Endpoints

 - Cancel subscription

- Add or edit price intervals

- Trigger phase

- Update price quantity

We have launched a new endpoint to update a customer's payment methods in Orb from their Stripe payment methods. (And a second endpoint using the customer's external ID.)

This endpoint can be called before taking an action that may cause the customer to be charged, ensuring that the most up-to-date payment method is charged.

Orb now supports the ability to login to multiple Orb organizations with the same email. For customers with multiple Orb organizations included in your plan, this means that you will be able to easily login and switch between Orb organizations using one central email.

As always, the login security for these organizations can be configured in the Security tab within your Orb settings.

For more information, please check out our docs! 

Orb’s CPQ integration streamlines processes like provisioning and contract management, using custom triggers and flows built in SFDC’s Flow Builder. Use it to automate provisioning and quote-to-cash workflows within Salesforce. 

The Orb CPQ integration is installed via a Salesforce managed package and includes Apex actions that connect to Orb’s API. These actions can be triggered manually or automatically (e.g., when an opportunity is moved to "closed-won"). These actions are compatible with Flow Builder and can also be used in custom code if needed, offering flexibility for Salesforce admins and developers.

Supported workflows: 

1. Provisioning new contracts: New contracts can be created for existing customers on paid plans, users on free plans, or new customers.
2. Amend contracts: Existing contracts can be modified, such as adjusting usage quantities or adding new products.
3. Cancel and replace contracts: Contracts can be canceled and replaced, typically in upsell scenarios where the customer wants to renegotiate terms.
4. Renewing contracts: Contracts can be renewed at the end of their term, with sales teams negotiating new terms.
5. Early termination: Customers can end contracts early and be moved to different plans (paid or free).

To check if your plan includes the CPQ integration and receive the installation link, please reach out to Orb. The package should be installed by a Salesforce Admin following the installation instructions in this guide.

Learn more about the integration in the product documentation.

You can sync Orb data back into Salesforce using Orb's CRM integration. Syncing Orb data back into Salesforce can empower your sales and customer-facing teams to gain a more holistic view of account health by giving them insights into Customers, Plans, Invoices and Subscriptions.

They can use it to quickly answer questions directly from Salesforce, such as: 

• What’s included in my customer’s current subscription? What products are they using?
• What invoices has my customer received? How do those invoices differ month over month?
• Has there been an increase in usage for this account recently that might motivate an upsell conversation? Or a decrease that could indicate a churn risk?
• What is my customer’s usage in the current month? 
• How does my customer’s credit usage compare to their pre-purchase commitment?

Learn more about the integration here. If the integration is included in your plan, head over to Settings and click on the new Integrations tab to set up the integration in just a few clicks. 

In-arrears fixed fees can now be denominated in virtual currencies (custom credits). These fees will automatically deduct from customers' prepaid credit balances, similar to usage-based fees.

This enhancement enables new pricing scenarios — for example, you can now set enterprise support fees in credits that draw from the customer's prepaid enterprise commitment rather than triggering a separate charge.

We’re excited to share that Orb now allows users to remove credit blocks from the credit ledger. This can be done by voiding the original credit block amount through the “adjust credits” workflow on the customer page within the UI. This new capability is particularly helpful for correcting errors in credit block creation or removing a block in case of a refund for a credit grant.

We have launched a new API endpoint for creating credit notes, enabling you to issue credit notes for specific line items on an invoice. This feature allows for programmatic issuance of credit notes, supporting bulk actions for multiple customers and enhancing customer experience by providing faster processing for refunds or adjustments.

For detailed information on how to credit an invoice, refer to the credit notes section in our documentation.

You can now synchronously issue and invoice via the API using the `synchronous: true` request body parameter in the issuance endpoint.

The synchronous option is currently only supported for invoices containing only fixed fees. If the invoice is configured to sync to an external provider, a successful response from this endpoint guarantees the presence of the invoice in the provider.

We are now showing plan phases in subscription timelines, allowing you to see when the given phase of a plan starts and ends.