We have introduced a new API endpoint for deleting an attachment.

You can now delete an existing attachment, A deleted attachment cannot be restored. The deleted attachment is not available in the list of attachments.

In the organizations API endpoints, we have introduced the individualTransferOut and individualTransferIn fields. In the Update an organization (PATCH /v3/organizations/{organizationId}) request, you can now set these fields to specify how ACH transfers are made with the organization funding bank account.

See PATCH /v3/organizations/{organizationId} in the API reference for more information.

We have introduced a set of API endpoints for bill approvals. With v3 bill approvals, you can now create and manage approval policies for bills based on a set of rules. In an approval policy, the approvers can be individual users or user groups.

When you create or update a bill with the v3 API, set billApprovals as true for BILL to add approvals information in the v3 bills response.

When you have approval policies set up for bills and a bill matches the policy, you now see an additional approvers array of objects in the v3 bills response. The array shows the list of individual users and/or user groups assigned as bill approvers. In addition, the array provides information about the status of the bill in the current approval flow.

For any approvers added to a v3 bill, the approvals must be complete before you can pay the bill with the API.

See Bill approvals for more information.

We have introduced a new Update an organization price plan (PATCH /v3/partner/organizations/{organization_id}/price-plan) endpoint.

When you onboard as a BILL partner, BILL works with you to set up price plans for the organizations you create. Your organizations can have up to 5 price plans. Each price plan is named in the PricePlanN format (PricePlan1 up to PricePlan5). Use this new endpoint to update the price plan for an existing organization.

See PATCH /v3/partner/organizations/{organizationId}/price-plan in the API reference for more information.

Features

• We have added block spinners across all the widget screens wherever applicable. This ensures that the user is blocked from performing any UI actions while a widget screen is loading.
• We have blocked all users from trying to access the BILL widgets in OFAC sanctioned countries. See Understand US Economic Sanctions in the BILL Help Center to learn more about OFAC sanctioned countries.

Use BILL webhooks to subscribe to and receive real time notifications for events, such as create a vendor, update a bill, or create a payment. When you get the events catalog and create subscriptions, set the required header values based on the events you want to subscribe to.

Idempotency key and notification URL for creating subscriptions

In your Create a subscription (POST /v3/spend/subscriptions) request, the X-Idempotent-Key header value must be in the UUID4 format. In addition, you can use an online service for generating a test notificationUrl value. For example, webhook.site.

Helpful links

• See BILL v3 API Postman collection to learn about working with the Postman collection.
• See Webhooks in the Guides section to learn about working with BILL Webhooks.

Features

Billing improvements

• In the Add funding, Manage funding, and User verification widgets, the user can now set a default funding and billing account method right when the bank account is eligible.
• In the Manage funding widget, we have added clarity by explaining that the default funding account method will be used for their monthly account billing and as the default payables account for vendor payments.
• In the Add funding widget, the fundingAddSuccess event is emitted when the user successfully adds a new funding payment method. We have added the defaultBilling field to the bankData payload. This field is set as true if the bank account is set a default for billing and payments.

{
  bankData: {
    status: string;
    accountNumber: string;
    userVerificationRequired: boolean;
    id: string;
    nameOnAccount: string;
    defaultBilling: boolean;
  }
}

Miscellaneous

We have replaced overlay spinners with loading buttons across all the widget screens. This is a user experience improvement.

We have introduced a new feature for accepting or rejecting a Spend & Expense transaction in response to a 3D Secure challenge triggered to verify the identity of the cardholder.

New webhook for 3D Secure challenges

We have updated the webhooks events catalog to include the spend.three-ds-challenge.created event. Notifications are triggered for this event when a 3D Secure challenge is triggered for a Spend & Expense transaction. You can now set up subscriptions to receive notifications for the new event.

See Spend & Expense 3D Secure challenge notification payload for more information.

New v3 API endpoint for responding to 3D Secure challenges

We have a new API endpoint for responding to 3D Secure challenges for Spend & Expense transactions. With the Accept or reject a transaction (POST /v3/spend/transactions/{acsTransactionId}/3ds-challenge) request, you can respond to a webhook notification you receive when a 3D Secure challenge is generated for a transaction.

See POST /v3/spend/transactions/{acsTransactionId}/3ds-challenge in the API reference for more information.

The BILL v3 API Postman collection is another way for you to test with the BILL v3 API. Simply fork the collection from the Postman API Network and begin testing with different BILL v3 API workflows.

See BILL v3 API Postman collection for more information.

In the Record AP payment endpoint, we have introduced the capability of adding vendor credits. In the Record AP payment (POST /v3/bills/record-payment) request, you can now add vendor credits in the vendorCredits object.

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