The card-account.updated webhook notification now includes the id field.

See Card account notification payloads for more information.

The payment.updated webhook notification now includes more status values.

See AP payment notification payloads for more information.

We have introduced a set of API endpoints for general ledger classifications. These endpoints enable you to better maintain a General Ledger (GL) for bookkeeping and financial reporting.

Accounting classes

Accounting class objects enable you to set up categories unique to your business.

Departments

Department objects enable you to set up groups or divisions for your business, such as Marketing, HQ, or Asia-Pacific.

Employees

Employee objects enable you to set up employees on your payroll.

Items

Item objects enable you to set up products and/or services sold by your business.

Jobs

Job objects enable you to set up unique projects with their own set of income and expenses.

Locations

Location objects enable you to set up office locations, such as West Coast, San Francisco, or California.

We have introduced a set of API endpoints for the Spend & Expense reimbursement operations. A reimbursement is a request to be repaid from budget funds for an out-of-pocket expense. Reimbursements enable business transactions without a charge card (physical or virtual card) to be included in the Spend & Expense platform.

See Reimbursements for more information.

We have added two new recipes for showcasing more workflows with the v3 API.

You can get details about your current API session with GET /v3/login/session. In the response, we have introduced a set of improvements.

See GET /v3/login/session in the API reference for more information.

We have added a new field in the cancel payment response to confirm that BILL has received your payment cancellation request. When you attempt to cancel a payment with POST /v3/payments/{paymentId}/cancel, you now get a cancelRequestSubmitted field in the response. This field is set as true if your cancel payment request is submitted.

Note: If the payment is canceled, the payment status is set as CANCELLED.

See POST /v3/payments/{paymentId}/cancel in the API reference for more information.

We have added bill payment status information in the bills API response. When you create a bill and it goes through a payment workflow, the bills API response now includes the paymentStatus field.

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

We have introduced a new Get list of organization industries (GET /v3/organizations/industries) endpoint. Get a list of available values for the industry field for an organization. Use this information to set the industry field in your POST /v3/partner/organizations or PATCH /v3/organizations/{organizationId} request.

See GET /v3/organizations/industries in the API reference for more information.

We have introduced a new Get card funding purpose (GET /v3/funding-accounts/cards/funding-purposes) endpoint. Get a list of card funding purpose values based on the vendor and card brand.

When you create a payment (POST /v3/payments or POST /v3/payments/bulk) with a CARD_ACCOUNT funding account type, BILL requires a vendor industry value for compliance. When BILL cannot identify the vendor industry, the cardFundingPurpose field must be set in your payment request.

Use this endpoint to get the list of card funding purpose values you can set. If you get an empty 200 response, BILL has information about the vendor industry and setting the cardFundingPurpose field is not required in your payment request.

See GET /v3/funding-accounts/cards/funding-purposes in the API reference for more information.