In the bills API endpoints, we have introduced the purchaseOrderNumber field. You can now set this field as a purchase order number linked with the bill.

See POST /v3/bills in the API reference for more information.

Vendor notifications

The vendor webhook notifications now include the shortName field. This field is the vendor short name. When you receive notifications for the vendor.created, vendor.updated, vendor.archived, or vendor.restored events, the notifications now include the shortName field.

See Vendor notification payloads for more information.

Bill notifications

The bill webhook notifications now include the purchaseOrderNumber field. This field is the purchase order number linked with the bill. When you receive notifications for the bill.created, bill.updated, bill.archived, or bill.restored events, the notifications now include the purchaseOrderNumber field.

See AP bill notification payloads for more information.

Features

Onboarding widget improvements

• In the sign-up flow, we have made theming improvements in the UI elements.
• On the KYC/KYB screen, we have removed the empty list items in the Business type list.

MFA widget improvements

On the MFA setup screen, when the user enters and international (not US) phone number and selects Voice call to receive a verification code, we have ensured that the correct information banner is displayed on the screen.

Manage funding widget improvements

• When the user clicks Close in the user verification flow, we have ensured that the user is correctly navigated to the manage funding list screen.
• On the manage funding list and funding method details screens, we have made UX enhancements on how a funding method is displayed as default.
• On the funding method details screen, we have further simplified the bank account status values.

User verification widget improvements

• We have made UX enhancements on the identity questionnaire screen
• We have improved error handling in the user verification widget

In February 2025, BILL introduced UUIDs in the Spend & Expense API for further improving its security standards. All API responses include both id and uuid values.

As of July 9, 2025, the Spend & Expense id values are being deprecated. Both id and uuid values will continue to be available in all API responses. We strongly recommend that you use uuid instead of id in all your Spend & Expense API operations.

Webhooks Time To Live (TTL)

BILL maintains an event history for each subscription. We have now upgraded the webhooks TTL from 90 days to 180 days. You can get the list of event notifications sent to you for a subscription with GET /v3/events/subscription/{subscription_id}. You can now get the list of events for the last 180 days.

See Webhook API notification rules for more information about the complete set of rules.

Get list of event notifications improvements

We have added the capability for filtering event notifications by an entity ID. For example, to get notifications for a specific bill, you can now filter with the ID of the bill.

In the Get list of event notifications (GET /v3/events/subscription/{subscription_id}) request, you can now filter event notifications with the entityId field.

See GET /v3/events/subscription/{subscriptionId} in the API reference for more information.

We have introduced a set of API endpoints for getting billing statement information for an organization. BILL generates a monthly billing invoice statement for all the billing activities in the organization.

See Organization billing statements for more information.

We have introduced a new API endpoint for recording an AP payment.

You can now record a bill payment made outside your BILL system. You can apply the recorded payment amount to one or more bills for a vendor.

See Record AP payments for more information.

We have introduced a new API endpoint for getting the current BILL foreign exchange rate.

You can now get the current BILL foreign exchange rate for a payment made to an international vendor. The BILL foreign exchange rate changes periodically. Use this endpoint to get the current exchange rate based on the payment amount and vendor payment currency.

Features

MFA widget improvements

The mfaSuccess event is emitted when the MFA setup or MFA challenge is submitted successfully. We have added rememberMeId and deviceId in the event payload.

{
  setup: boolean;
  required: boolean;
  rememberMe?: boolean;
  rememberMeId: string;
  deviceId: string;
}

Note that rememberMeId is available in the payload only when MFA rememberMe is set as true for the user.

We have introduced a set of API endpoints for recurring invoice operations. A recurring invoice is a template for creating identical invoices for accepting recurring payments from a customer. Each invoice represents an amount that you are owed by a customer for goods and services that your organization provides.

See Recurring invoices for more information.