We have introduced two new API endpoints for BILL export operations.

You can now get a list of exported BILL records available for you to download. You can export records, such as vendors, customers, bills, and invoices. In addition, you can export AP payments and AR payments.

With the Get list of exported BILL records (GET /v3/exports) API request, you get a list of exported BILL records available for you to download.

In the response, the exportId is the BILL-generated ID of the exported record file. Use this value to get the download URL for the exported record file with the Get exported record download URL (GET /v3/exports/{exportId}/download-link) API request.

The Import and export section in the BILL web app (Settings > Import & export > Custom File Integration) provides the complete list of entities that you can export. In this section, you can set up a schedule for BILL exports. For example, on a weekly schedule, you can have BILL export records for your choice of BILL entities.

Each exported record is in the CSV format. If you are using an accounting system that does not sync with BILL, you can use these CSV files to export records from BILL, and then import the data into your accounting system.

See Export BILL records in the Guides section to learn about setting up a schedule for BILL exports and sample responses.

We’re thrilled to announce that BILL v3 API recipes are now on developer.bill.com! 🚀

Whether you’re streamlining back-office operations or building the next big fintech solution, these recipes provide the blueprint for success. You now get a real-time showcase of the power of the BILL Accounts Payable (AP), Accounts Receivable (AR), and Spend & Expense (S&E) products.

Ready to start building?

Simply select a recipe, enter your sanbox account credentials, and watch the BILL v3 API in action as it handles complex business processes for your solutions.

BILL has introduced webhook subscription limits. You can create up to 10 webhook subscriptions per organization. In addition, BILL does not allow duplicate subscriptions for the same set of events and same notification URL.

In the Spend & Expense transactions API responses, we have introduced a new status field. This field provides the current status in the lifecycle of the transaction. Status values include APPROVED, COMPLETE, DECLINED, and DENIED.

See GET /v3/spend/transactions in the API reference for more information.

BILL has removed the ability to add or use a secondary phone number for the BILL v3 API MFA operations.

Add phone for MFA setup

In the POST /v3/mfa/setup API endpoint, BILL has removed the ability to add a secondary phone number for MFA operations. In the API request, primary can be set only as true. In addition, this field is no longer required in the API request.

When you set primary as false in your API request, you will get an HTTP 400 response and an error message.

Generate MFA challenge

In the POST /v3/mfa/challenge API endpoint, BILL has removed the ability to use a secondary phone number for generating an MFA challenge. In the API request, useBackup can be set only as false. In addition, this field is no longer required in the API request.

When you set useBackup as true in your API request, you will get an HTTP 400 response and an error message.

Features

Payments widget

In the Payments widget, we have added configuration settings that control whether the user has access to certain operations.

• On the list of payments made to a vendor screen, you can now control whether the link to the complete list of payments is available. In addition, you can control whether the user can schedule a payment from this screen.
• On the schedule a payment screen, you can now control whether the user can add a new vendor.

See Payments Element: Implementation in the Guides section for more information.

Bug fixes

Vendor setup widget

We learned that when the user entered international vendor information, the Vendor setup widget flow was not working as expected. We have fixed this issue. The widget now correctly provides the list of international vendors that match the user entered information. In addition, the user is able to manually enter the international vendor information.

Hello Developers,

We are writing to notify you about upcoming changes in the BILL v3 and v2 API to comply with new NACHA Risk Management rules.

What is changing?

Starting March 20, 2026, NACHA requires that all ACH payments sent to consumer bank accounts for compensation (including wages, salaries, bonuses, and 1099 contractor payments) must include a standardized PAYROLL description.

Current status

Your organization is not liable for any NACHA violations related to this specific rule until the BILL API updates are officially released. When the updates are live, you will have 180 days to implement changes in your integration.

Developer actions

1. Audit your payments: Determine if your application initiates ACH payments that are classified as PAYROLL.
2. Watch for follow-up communications: We will send you follow-up communications when the API updates are available for testing in the sandbox environment. We will share detailed documentation about the API updates.

Why does this rule matter?

As outlined in the Compliance with Law, Agreement, Policy section of the BILL Developer Terms, your organization is responsible to comply with applicable regulations. When these API updates are rolled out, failure to properly classify these payments could result in compliance violations, financial penalties from NACHA, or restrictions on your customers' ability to send ACH payments through BILL.

Questions

For questions or concerns, email us at [email protected].

In the payments API response, we have introduced a new trackingInformation field for BILL Pay Faster check payment disbursements. This field is available in the response in the checkDisbursement object when BILL processes the BILL Pay Faster check payment.

This field provides the UPS tracking number for the check. You get a tracking number only for a BILL Pay Faster check payment.

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

In the Get list of event notifications (GET /v3/events/subscription/{subscriptionId}) API request, we have introduced a new set of fields for filter and sort operations for events sent to you for a subscription.

You can now filter events sent to you based on notification created date with the new createdTimeFrom and createdTimeTo fields. In addition, you can now sort events based on notification created date with the new ​​ascending field.

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

We have introduced the ability to filter invoices by invoice status. In the Get list of invoices (GET /v3/invoices) API request, you can now filter invoices with the invoice status field. With this operation, you can filter invoices that are OPEN, SCHEDULED, PARTIAL_PAYMENT, or PAID_IN_FULL.

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