Orb now supports reverse charge with every tax provider that supports non-US taxes. When a sale qualifies for reverse charge under VAT or GST rules, Orb reflects the shifted responsibility for reporting and paying the tax in the tax calculation as well as the invoice.

In addition, we're rolling out improvements related to taxes:

• Multi-jurisdiction tax now always appears on invoices for every provider that supports it. To hide the per-jurisdiction breakdown, turn it off in your invoice settings on the Settings page.
• When a tax line is $0, the tax amount in the API response now includes the reason in tax_reason alongside it.

Learn more about tax in our docs.

Invoices now include a payment_received_at field that records when payment was actually received. Your AR and collections reporting can use the date the cash arrived instead of the date the invoice status changed in Orb.

Previously, the API only returned paid_at, which is the time the invoice moved to paid in Orb. For invoices marked as paid manually, that can be a different day from the one your customer actually paid on.

payment_received_at is set as follows:

• Invoices marked as paid manually: the payment date you enter.
• Invoices paid through a payment provider: the time the provider recorded the payment.
• Invoices automatically marked as paid: null.

paid_at hasn't changed and still shows when the status transition happened.

Learn more about payment_received_at in our docs.

You can now void multiple invoices at once from the Invoices page in the dashboard. Select the invoices you want to void, or select all invoices matching your current filters, then click Void.

This makes it faster to clean up a batch of incorrectly issued invoices without opening and voiding each one individually.

Learn more about voiding invoices in our docs.

Orb now sends Adyen enhanced scheme data with every Adyen charge, so eligible commercial card payments from your customers can qualify for lower Visa and Mastercard interchange rates. Level 2 data includes the invoice number and tax total, and level 3 adds line item detail.

• Applies to payments made through the invoice portal and to charges during auto-collection.
• There is nothing to turn on in Orb. Adyen validates the data and submits the level each card qualifies for.
• Set the default commodity code for level 3 data in Settings > Integrations > Configure on your Adyen connection.
• If your merchant account or the card isn't eligible, Adyen processes the payment without it. Enhanced scheme data never blocks a charge.

Note that you should contact Adyen to confirm your merchant account is enabled for level 2/3 data.

Learn more about enhanced scheme data in our docs.

You can now sync invoices with a customer balance applied to NetSuite. Previously, Orb held these invoices back in an Action Needed state, because syncing them automatically could leave your Orb and NetSuite records out of step.

Now you can force sync the invoice yourself from its Action Needed error, and Orb tells you what to do in NetSuite to reconcile it.

• Force sync directly from the sync error, without contacting Orb support.
• After syncing, apply the standalone credit memo that holds the customer balance to the synced invoice in NetSuite.
• Available to all customers using the NetSuite integration.

Learn more about NetSuite sync reconciliation in our docs.

When you create or edit a collections automation schedule, each step now has a Developer options section. Use it to label the step's webhook and to preview the payload it sends.

• Custom webhook labels: the label you set is sent as properties.label on the invoice.automation_schedule_step_executed event. Your systems can route each step's webhook, for example to a Slack notification, without mapping step IDs.
• Sample payloads: click View sample payload to see and copy an example event for that step, so you can build and test your webhook handler before the schedule runs.

Collections automations are available on Enterprise plans.

Learn more about collections automations in our docs.

There’s sending an invoice, and then there’s getting paid. Companies lose as much as 5% of revenue to leakage from overdue invoices. Orb can help with Collections Automations -- now available for Enterprise accounts.

With Collections Automations, you can:

• build multi-step collections workflows with configurable retries, emails, and webhook actions
• tailor collections paths to different invoice cohorts
• get more visibility into what is happening on each invoice

Try it now, or learn more in our docs.

Orb now displays your merchant tax ID (VAT, GST, or other applicable tax registration number) directly on invoices — a requirement for compliant invoicing in most international jurisdictions and a common ask from enterprise finance teams. This ensures your invoices meet local compliance requirements out of the box -- no workarounds, no manual edits to PDFs.

To get started, add your tax registration number(s) under Invoice Settings. Your merchant tax ID will appear on all invoices going forward.

Learn more in our docs, or reach out to Orb with additional questions or feedback.

You can now update the memo on an issued invoice without voiding and reissuing it, so adding a PO number or fixing a typo no longer means sending a new invoice. From an issued invoice in the dashboard, select Regenerate invoice PDF, edit the memo, and optionally refresh the customer tax ID. The invoice keeps its invoice number, and the change applies to the PDF, customer portal, API, and data exports.

• Available for issued invoices that haven't been paid or synced to an external system.
• Regenerating also refreshes company details, the invoice footer, and the customer address to what's currently on file.
• Changes don't sync to third-party systems like Stripe, NetSuite, or QuickBooks.
• Note that invoices with tax generally shouldn't be regenerated, since the final tax amount may change.

When you create a subscription or schedule a plan change in the dashboard, the Subscription preview step now shows the full invoicing impact before you confirm. Previously, these flows previewed only the next upcoming invoice.

The preview matches the one used when editing a subscription or migrating plan versions, and covers the next 12 months of changes:

• Invoices that will be added, updated, deleted, or voided
• Credit notes the change will issue
• Proration and its effect on downstream invoices