FAQs

Confirm whether your username and password is correct. In addition, confirm whether the username and password belong to the correct environment: sandbox or production.

Note that the BILL sandbox and production environments do not share any data.

Confirm whether your username and password is correct. In addition, confirm whether the username and password belong to the correct environment: sandbox or production.

Note that the BILL sandbox and production environments do not share any data.

If the HTTP status code of the response is 404, confirm that you have the correct API endpoint path without any spelling errors or capitalization errors.

Confirm whether your concurrent API requests per developer key per organization is not more than three.

When you receive this error, all subsequent API requests fail until one concurrent request is completed. Implement exponential backoff in your code to address concurrent rate limits.

See API rate limits for more information.

When you add a vendor bank account, BILL requires 2 business days to complete a one-time verification of the bank account. To pay such a vendor, you must set a processDate that is 2 business days from the current date.

Yes. BILL enables you to delete a vendor bank account or vendor while BILL is processing a payment. If an ACH payment is in progress but has not reached the SENT state, BILL switches the payment disbursement method from ACH to CHECK.

BILL does not display BILL Network vendor bank account information to maintain system privacy. Review vendor details in the vendor record to ensure you are connected with the correct vendor. You can also use the vendor Payment Network ID (PNI) to confirm the vendor and payment destination.

With the BILL v3 API, you can get the PNI of a connected vendor with GET /v3/vendors. See Get list of vendors in the API reference for more information.

BILL has business logic to determine if a BILL Network vendor is eligible to be auto-connected. The system automatically connects with a BILL Network vendor only when there is high confidence in the BILL Network match.

No. BILL considers previous disconnections when determining whether BILL auto-connects with a BILL Network vendor.

When a vendor accepts a BILL Network invitation and joins BILL, the vendor is on the Advanced Receivables or Basic Receivables plan. The payment disbursement method for this vendor is set as WALLET. When you pay this vendor, BILL typically deposits funds directly into the vendor bank account (unless the vendor opts in to the BILL Wallet feature).

Yes. You can get a scanned copy of a check with GET /v3/payments/{paymentId}/check-image. The check image is available when the vendor bank processes the check payment. BILL checks in with the bank every 30 minutes to get the check image. The image file format is determined by the vendor bank.

See Get check image data in the API reference for more information.

The final cut-off time for BILL processing a payment is 6:00 PM Pacific Time (PT) each US business day.

• Before 6:00 PM PT: BILL processes the payment on the same day.
• 6:00 PM PT onwards: BILL processes the payment on the next business day.

The FUNDS_ESCHEATED payment status indicates that the disbursed payment funds are not claimed by the vendor. BILL takes the necessary regulatory actions for FUNDS_ESCHEATED payment.

Start building with the BILL v3 API. We keep adding new features to the v3 API. See API release notes for information about new features and updates in the v3 API. You can also subscribe to the RSS feed.

BILL has no plans to deprecate the BILL v2 API. As you continue building and find a useful v2 API feature, note that each version has its own API base URL.

For example, POST https://gateway.stage.bill.com/connect/v3/login is v3 sandbox API login, and POST https://api-stage.bill.com/api/v2/Login.json is v2 sandbox API login.

In the sandbox environment, BILL does not charge you for any pricing plan or subscription. When you sign up to create your sandbox developer account, you are on a trial subscription plan. Upgrade your subscription plan to make sure you have access to all the BILL features in sandbox.

See Add a test credit card in sandbox for more information.

When you generate a developer key, the key is available for you to use with any of your test organizations and test users.

When you sign in with POST /v3/login, the generated sessionId in the response is available only for the selected devKey in your request. This sessionId does not work with another devKey.

We do not recommend that you move any of your production data to sandbox. There can be unintended consequences. For example, you may be testing with your production data in sandbox, but the vendors and customers will receive emails based on your testing with bills and invoices.

In the BILL web app, navigate to Settings > Import & Export to move any required information between your development environments.

Money movement objects enable you to view BILL money movement information for a bill, invoice, or payment. Currently, you cannot link a MoneyMovement object with any other BILL object.