In the payments API response, we have introduced two new fields in the rppsDisbursement object.

In addition, we have introduced a new disbursementStatus field in the response to provide the payment disbursement status at each stage of the payment.

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

We have added new API endpoints for general ledger classification bulk operations.

Chart of accounts

Items

When you list bills (GET /v3/bills) and invoices (GET /v3/invoices), you can now filter and sort with additional fields.

Filtering bills and invoices

You can now filter bills and invoices with additional fields.

See Filterable fields for the complete list of fields you can filter with.

Sorting bills and invoices

You can now sort bills and invoices with the archived field. See Sortable fields for the complete list of fields you can sort with.

Features

User verification widget improvements

• When the partner triggers the user verification widget for a user that does not have an active, verified bank account, we now inform the user that they are not required to complete their identity verification.
• When Google Places fails to load for the address field, we enable the user to manually enter address information and continue. In this case, we now ensure that Google Places does not throw unhelpful validation errors to the user.

Onboarding widget improvements

• On the KYC/KYB screen, we have added a spinner to ensure that Google Places is available for the user when they are using the address field.
• When the user bank account is added manually, we have added a spinner on the end state screens to provide a cleaner experience. This improvement disables the ability to click multiple times while the partner integration listens to the BILL success events and navigates back to the partner experience.

Features in the next release

• Usability improvements in the Convert to ePay widget
• Miscellaneous performance improvements

Features

Manage funding widget improvements

• On the add payment method screen, we have added a spinner to provide a cleaner experience. When the user clicks Add to add a new payment method, they now see a smoother transition to the adding funding screen.
• On the bank account details screen, we no longer provide information about the default payment method. In addition, users can no longer set a bank account as the default payment method.
• We received feedback that when a user deletes an existing bank account, BILL provides an unhelpful status for the deleted bank account. We now provide the correct bank account status of Deleted.

User verification widget improvements

• At the end of the user verification flow, we have added a spinner to provide a cleaner experience. This improvement disables the ability to re-submit the verification form. In addition, we have added a spinner to ensure that Google Places is available for the user when they are using the address field.
• On the bank account details screen, we learned that the user verification banner would intermittently appear when the user is adding a new funding method. We have fixed this styling issue.

Onboarding widget improvements

When the user bank account is added with the Plaid flow, we have improved the transition from the onboarding widget to the user verification widget.

MFA widget improvements

On the 2-step verification screen, we have ensured that the radio buttons follow the chosen color theme.

Miscellaneous

We learned that the focus state on buttons is cut off on certain screens. We have now fixed this styling issue.

Features in the next release

• Usability improvements in the Onboarding, MFA, and Convert to ePay widgets
• Miscellaneous performance improvements

We have introduced a set of API endpoints for new bank account user operations. You can now nominate and archive bank account users.

When you nominate a bank account user, BILL sends the user an email asking them to sign in to the BILL web app and complete identity verification. After the verification is successful, the bank account user can pay with the specified bank account.

When you archive a bank account user, the user loses the ability to pay with the specified bank account.

When you create or update a bill, you can now set the chartOfAccountId field as the BILL-generated ID of the chart of accounts for the bill.

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

We have added new API endpoints for general ledger classification bulk operations.

Departments

Jobs

Locations

We have added new API endpoints for general ledger classification bulk operations.

Accounting classes

Employees

We have added the capability for adding general ledger classifications to different BILL operations.

Invoices

When you create or update an invoice, you can now set your choice of general ledger classifications values (Accounting class, department, job, or location). In addition, you can set classifications at the line item level (Chart of accounts, accounting class, department, job, location, or item).

See /v3/invoices in the API reference for more information.

Bills

When you create or update an invoice, you can now set your choice of general ledger classifications values (Chart of accounts, accounting class, department, location, or item). In addition, you can set classifications at the line item level.

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

Recurring bills

When you create or update a recurring bill, you can now set set classifications at the line item level.

See /v3/recurringbills in the API reference for more information.

Organization bank accounts

When you create or update a bank account, you can now set the chartOfAccountId field as the BILL-generated ID of the chart of accounts for the bank account.

See /v3/funding-accounts/banks in the API reference for more information.