We have introduced a new mark_as_paid field on the apply subscription changes API. This new field marks all payable invoices as finalized and paid, and works in tandem with the is_payable_now field that exists on changed resources (see: https://changelog.withorb.com/api-update-is_payable_now-field-added-to-changed_resources.created_invoices-3pIhZC).

The previously_collected_amount field is optional. If not provided, we assume the amount was correctly collected and simply mark invoices as paid without touching the customer balance.

When both mark_as_paid and previously_collected_amount are provided, we mark all payable invoices as paid and decrement customer balance by (previously_collected_amount - total amount due). This should only be used when the amount collected outside the system differs from the total amount due. Note that the total amount due includes tax calculations, while the amount shown for pending changes does not include taxes (see: https://docs.withorb.com/essentials/pending-changes for more info).

Any negative customer balance will be automatically reflected on the next invoice.

We’ve introduced a new field, is_payable_now, on changed_resources.created_invoices. The created_invoices field represents the list of invoices that will be generated as part of a pending subscription change or when previewing changes with the Include-Changed-Resources header. The new is_payable_now field on invoices represent ready-to-pay invoices containing only in-advance fixed fees. You can use this field to determine which invoices should be paid to enable access to a subscription change (eg. plan upgrade).

When it applies:

changed_resources (and thus created_invoices) are only returned

• When the explicit Include-Changed-Resources header is passed in a Subscription API request
• When calling the Pending Subscription Changes APIs

We've added a created_at  timestamp field to all data export resources to provide better insight into when resources were originally created in Orb.

What is the created_at timestamp?

The created_at field captures the exact moment when a resource (customer, subscription, invoice, etc.) was first created in Orb's system, regardless of when it was last modified or when other business events occurred.

How is it different from other timestamps?

• created_at: When the resource was originally created in Orb
• updated_at: When the resource was last modified
• start_date/end_date: Business-specific dates (e.g., when a subscription starts/ends)

How to use it

The created_at timestamp is particularly valuable for:

• Historical analysis: Re-create analyses representative of a specific point in time
• Backdated actions: Distinguish between when something was created vs. when it was backdated to take effect
• Data auditing: Track the chronological order of resource creation
• Cohort analysis: Group customers or subscriptions by their actual creation date, not their business effective date

For example, if you backdate a subscription to start January 1st but create it on February 15th:

• start_date = January 1st (business effective date)
• created_at = February 15th (when it was actually created in Orb)

  This enables you to analyze "all subscriptions created in February" vs. "all subscriptions starting in January."

Availability

The created_at field is available immediately for new data export records. Historical data will be backfilled over the next 8+ weeks, so you may see null values for older resources during this period.

Documentation:

For additional details, check out our docs.

We're excited to announce enhanced invoice issuance controls that give you granular control over how invoices are issued for individual customers.

Customer-Level Auto-Issuance Overrides

You can now configure invoice issuance behavior at the customer level, allowing for mixed billing workflows within a single account. Each customer can be set to:

• Inherit from account (Default): Use your account-level setting
• Automatic issuance: Always auto-issue invoices for this customer
• Manual issuance: Always require manual approval for this customer

Retroactive Setting Application

When changing your auto-issuance settings (at both account and customer levels), you now have the option to:

• Apply going forward only: New setting applies only to invoices with an invoice date after the change
• Apply retroactively: Automatically issue all historical invoices that would have been eligible under the new setting

Use Cases

This enhancement enables flexible billing workflows such as:

Enterprise + Self-Serve Mix

• Set account default to manual issuance
• Override self-serve customers to automatic issuance
• Keep enterprise customers on manual review

High-Touch Account Management

• Set account default to automatic issuance
• Override VIP customers to manual issuance for additional review
• Let standard customers inherit automatic behavior

Orb now automatically generates receipt PDFs when an invoice is paid. This includes payments made via auto-collection, through the invoice or customer portal, or when an issued invoice reflects a $0 balance.

Receipt PDFs are:

• Included as attachments in the payment success email.
• Downloadable from the invoice portal, customer portal, and the invoice page in the Orb dashboard.
• Accessible via the API on the invoice resource, with a download link available for each successful payment attempt.

We've added additional columns to the Invoice CSV and Invoice line item CSV downloads from Orb, including:

• Credit note details
• Prepaid credit application amounts
• Pricing currency
• Gross and net line item amounts
• Net invoice amounts

Simplify invoice reporting — reconcile AR and credit notes, track adjustments and prepaid credits all in one place.

⚠️ Action required: If you rely on these CSV downloads for any downstream reporting or integrations, please review and update any dependent queries, scripts, or analyses. The new fields and formatting may affect existing workflows.

Look for it in your Invoices tab, or learn more in our docs.

You can now configure Orb to automatically roll over invoice amounts that are too small to charge.

Charges below Stripe's minimum transaction limit will be automatically deducted from the customer's balance and used to pay the invoice. Customers won't receive emails for these small invoices, and the negative balance will automatically roll forward onto future invoices issued.

Try it out now, or learn more about invoice collections in our docs.

You can now provide a custom invoice due date for tighter collections control in Orb, most notably in the case of backdated billing actions.

Additionally, control how invoice due date is calculated in Orb by default for more accurate reporting. Find this setting in the Invoices tab of your account settings. 

Try it out now, or learn more about invoice collections in our docs.

Orb's Data Exports now includes 5 new resource types:

1. Accounting period lock
2. Credit ledger entry event
3. Credit note line item event
4. Daily line item revenue event
5. Invoice line item billing event

These resources include lock adjusted timestamps, so you can attribute revenue and billings to the appropriate period based on the accounting period lock posture, and create custom or advanced revenue and billing reports outside of Orb.

Learn more in our docs, including how to get started with common financial analyses using Orb data.

You can now tailor how data is presented in the Recognized Revenue and Billings reports. Use this dropdown to configure:

1. View aggregation: rollup data monthly, or daily for shorter time horizons
2. Display properties: include additional metadata for richer reporting in one place
3. Insights: calculate % change from the prior period

To try it out, head to the display options dropdown in the top right of the Recognized Revenue and Billings reports. Learn more about revenue reporting and pivots in our docs.