We have added a new Postman Notebook for the BILL expense management workflow with users, budgets, and cards. See the BILL Expense Management with Users, Budgets, & Cards Postman Notebook for details.

In this notebook, you build an API workflow that enables you to set up a Spend & Expense budget, assign a user to the budget, and create a virtual card for the user to stick to their budget.

In all, we now have 3 published Postman Notebooks.

• BILL Expense Management with Users, Budgets, & Cards
• Bill Approvals Workflow with the BILL v3 API
• BILL AP Workflow with the BILL v3 API

We have introduced a set of API endpoints for charging customers. You can now use the BILL v3 API to charge a customer for one or more invoices.

We have updated the webhooks events catalog to include a set of new events for invoices. Notifications are now triggered for these invoice events. You can now set up subscriptions to receive notifications for the new events.

See Invoice notification payloads for more information.

Features

Manage funding widget improvements

We have added a list of BILL ACH IDs in the Manage funding list. This information is required in case the user's bank account has a debit block or debit filter. The user can now easily access this information in the Manage funding list experience. The user can copy the BILL ACH ID values to clipboard.

We have introduced a set of API endpoints for customer bank accounts. You can now use the BILL v3 API to create and manage customer bank account information.

In the vendors API response, we have introduced a new paymentNetworkId field. This field provides the vendor Payment Network ID (PNI). Each vendor with a BILL account is a unique PNI.

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

We have added a new Postman notebook for the bill approvals workflow with the BILL v3 API. See the Bill Approvals Workflow with the BILL v3 API Postman notebook for details.

In this notebook, you build an API workflow that enables you to set up a bill approval policy, get the list of bills pending approval, and approve a bill for payment.

In all, we now have 2 published Postman notebooks.

• Bill Approvals Workflow with the BILL v3 API
• BILL AP Workflow with the BILL v3 API

Features

• We have moved the BILL terms of service to the beginning of the onboarding flow. In addition, we have removed the BILL terms of service from the footer of the Onboarding widget. The user now sees the BILL terms of service more prominently when they begin onboarding.
• We have added a list of BILL ACH IDs in the Add funding account experience. This information is required in case the user's bank account has a debit block or debit filter. When the user adds a funding account with the Plaid flow or with the manual setup, the user now sees BILL ACH ID values that they can copy to clipboard.

We have added two new developer tutorials in the BILL API Platform for developers YouTube playlist. See the BILL API Platform for developers playlist for the complete set of developer tutorials.

BILL API Platform authentication

In this tutorial, we walk through everything you need to authenticate with the BILL API Platform.

You’ll learn how to:

• Generate your developer key (devKey)
• Find your organization ID (organizationId)
• Use AP & AR sync token as a BILL app partner
• Use a console token for multi-org or accounting firm access
• Generate a BILL Spend & Expense API token for the Spend & Expense API

Bill approvals and S&E 3DS challenge integration example

In this tutorial, we walk you through real-time bill approvals, document fetching, and handling Spend & Expense 3DS authentication flows in your existing systems.

In the Spend & Expense Transactions API, we have added syncStatus to the list of transaction filters. In the Get list of transactions (GET /v3/spend/transactions) request, you can now filter transactions with the syncStatus field.

This field provides information about the current sync status of the transaction with your accounting system. The possible syncStatus values are PENDING, SYNCED, ERROR, MANUAL_SYNCED, or NOT_SYNCED.