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.

Credit note service periods are now configurable to provide greater, fine-grained controls for when revenue is recorded and recognized in Orb Reports.

To try it out, head to the options menu for any paid or issued invoice. Learn more in our docs.

Simulations let you understand the impact of any price evolution before you launch. Now, the full feature richness of Orb's billing engine is fully supported in Simulations — try it now.

What's new:

1. ✅ Start from an existing plan, and easily simulate changes to optimize revenue capture (changing tier boundaries, updating rates, and more).
2. ✅ Experiment with packaging or build out new pricing completely from scratch.
3. ✅ Simulate minimums, discounts, maximums... you name it.
4. ✅ Allocations + credits — tune your included allocation and top-ups to actual customer usage and needs.
5. ✅ Dimensional price groups? Let's set it up.

Build scenarios for different pricing strategies and run them against historical usage data in Orb. Simulations allow you to visualize price changes before you make them, without any of the complicated data legwork or churn risk of live testing with customers. Learn more in our docs.

You can now include, exclude, or isolate tax amounts in the Billings report. This powerful enhancement makes it easier to record and reconcile your accounts for end-of-month close, without ever leaving Orb. 

Learn more about the Billings report in our docs.

You can now set a customizable invoice date when creating an invoice for a credit increment. By default, the invoice will use the credit block’s effective date, but you can override this by specifying a custom invoice date.

This option is available in the dashboard and via the API by setting invoice_settings.invoice_date when creating a ledger entry.

We’ve added support for displaying the invoice memo directly in the body of invoice issuance emails.

📌 The memo is helpful to annotate invoice emails - for example, adding payment instructions - so recipients can easily understand how to pay the invoice

💡 You can populate the memo for all invoices on a subscription or for specific invoices.

🛠️ Including the memo in the invoice body is a common practice among billing providers and improves clarity for end customers.

We’re excited to announce a new enhancement to our Stripe integration: Orb now supports syncing customer addresses directly from Stripe. This upgrade eliminates manual address entry and ensures your billing and tax workflows run smoothly.

🌟 Why this matters 

Many of our customers faced  billing issues and invoice failures when address data in Stripe wasn’t reflected in Orb. This gap created operational overhead and made it difficult to maintain accurate tax calculations. 

With this new feature:  
- Customer addresses will automatically sync from Stripe when an Orb customer is linked to a corresponding Stripe customer.
- Address updates in Stripe will be reflected in Orb automatically—no manual input required.
- This feature is can be toggled through the Integrations tab under Settings, so you have control over when and how syncing happens.


🔍 Use Case: Tax Integration Support 

This upgrade is part of our broader initiative to enhance tax readiness and automation. Many tax providers require accurate billing and shipping addresses for compliance and jurisdictional calculation. With synced data from Stripe, you can now:

-   Avoid misapplied taxes or missing tax data due to incomplete addresses.
-   Reduce friction in integrating Orb with tax engines.
-   Confidently support invoicing requirements.

⚙️ Configuration 

You can enable the feature with a single toggle: Settings > Integrations > Stripe > Sync customer addresses This creates a one-way sync from Stripe → Orb. Addresses in Orb will not update Stripe, and unlinked Orb customers will remain unaffected.

We've launched a new API endpoint that enables you to evaluate the output of multiple prices for a given customer and time range. This powerful endpoint supports up to 100 prices in a single request, helping you build more detailed usage dashboards and audit invoice calculations.

Key capabilities:

• Evaluate up to 100 prices in a single API call for improved performance
• Use ingested or preview events - evaluate against real usage data or test with up to 500 preview events
• Advanced filtering and grouping with computed properties for granular analysis
• Inline price definitions - test new pricing models without creating them first

Common use cases:

• Build detailed usage breakdowns for customer dashboards
• Audit and verify invoice line item subtotals
• Test pricing changes before implementation
• Display usage patterns grouped by custom dimensions (e.g., by hour, region, or product feature)

Example grouping: Group usage by hour and custom property: ["hour_floor_timestamp_millis(timestamp_millis)", "region"]

Example filtering: Filter for specific usage: product_type = 'premium' AND region = 'us-east'

The endpoint is available now at POST /prices/evaluate. Check out our Querying data with SQL page for additional details and examples.