Skip to content
All connectors
BILL logo

BILL

Accounting, billing & payments

Keep BILL in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

43 ways to read, 14 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
BILL with Nexra

Connected, approved, proven.

The things teams do most with BILL, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create billApproval by rule
  • Create accountApproval by rule
  • List accounting classesRead

Example flow

  1. BILL · List accounting classesDone
  2. BILL · Create billNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches BILL.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to BILL
  • BILL's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect a BILL Holdings test account before you go live.

For developers

Technical detail

Read, search and write BILL vendors, customers, contacts, unpaid bills, unsent invoices, accounts and items; read classifications, terms, credits, recurring templates and payments.

BILL Holdings API docs
Source actions
43
Destination actions
14
Data types
20

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Accounting classes2
  • Get accounting classSource

    One accounting class by ID.

  • List accounting classesSourceIncremental

    Accounting classes, optionally updated since a timestamp.

Bills5
  • Create billDestinationNot retried automaticallyApproval before production

    Records an unpaid vendor bill with line items. Paying bills is never automated.

  • Get billSource

    One bill by ID.

  • List billsSourceIncremental

    Bills, optionally updated since a timestamp.

  • Search billsSource

    Bills by vendor, payment statuses, due-date range, classification or created and updated time.

  • Update billDestinationProvider duplicate protectionApproval before production

    Updates supplied bill fields with PATCH. Omitted fields are unchanged.

Chart of accounts4
  • Create accountDestinationNot retried automaticallyApproval before production

    Creates a account in BILL.

  • Get accountSource

    One account by ID.

  • List chart of accountsSourceIncremental

    Chart of accounts, optionally updated since a timestamp.

  • Update accountDestinationProvider duplicate protectionApproval before production

    Updates supplied account fields with PATCH. Omitted fields are unchanged.

Credit memos2
  • Get credit memoSource

    One credit memo by ID.

  • List credit memos (read only)SourceIncremental

    Credit memos (read only), optionally updated since a timestamp.

Customer contacts4
  • Create customer contactDestinationNot retried automaticallyApproval before production

    Creates a customer contact in BILL.

  • Get customer contactSource

    One customer contact by ID.

  • List customer contactsSource

    Customer contacts.

  • Update customer contactDestinationProvider duplicate protectionApproval before production

    Updates supplied customer contact fields with PATCH. Omitted fields are unchanged.

Customers5
  • Create customerDestinationNot retried automaticallyApproval before production

    Creates a customer in BILL.

  • Get customerSource

    One customer by ID.

  • List customersSourceIncremental

    Customers, optionally updated since a timestamp.

  • Search customersSource

    Customers by name prefix, exact name, account type, country, currency, archive state or created and updated time.

  • Update customerDestinationProvider duplicate protectionApproval before production

    Updates supplied customer fields with PATCH. Omitted fields are unchanged.

Departments2
  • Get departmentSource

    One department by ID.

  • List departmentsSourceIncremental

    Departments, optionally updated since a timestamp.

Employees2
  • Get employee classificationSource

    One employee classification by ID.

  • List employee classificationsSourceIncremental

    Employee classifications, optionally updated since a timestamp.

Invoices5
  • Create invoiceDestinationNot retried automaticallyApproval before production

    Creates an AR invoice without emailing it or enabling card charges.

  • Get invoiceSource

    One invoice by ID.

  • List invoicesSourceIncremental

    Invoices, optionally updated since a timestamp.

  • Search invoicesSource

    Invoices by customer, statuses, classification, archive state or created and updated time.

  • Update invoiceDestinationProvider duplicate protectionApproval before production

    Updates supplied invoice fields with PATCH. Omitted fields are unchanged.

Items4
  • Create itemDestinationNot retried automaticallyApproval before production

    Creates a item in BILL.

  • Get itemSource

    One item by ID.

  • List itemsSourceIncremental

    Items, optionally updated since a timestamp.

  • Update itemDestinationProvider duplicate protectionApproval before production

    Updates supplied item fields with PATCH. Omitted fields are unchanged.

Jobs2
  • Get jobSource

    One job by ID.

  • List jobsSourceIncremental

    Jobs, optionally updated since a timestamp.

Locations2
  • Get locationSource

    One location by ID.

  • List locationsSourceIncremental

    Locations, optionally updated since a timestamp.

Organization1
  • Get organizationSource

    The connected organization's profile. Owner details and tax identifiers are not returned.

Payment terms2
  • Get payment termSource

    One payment term by ID.

  • List payment termsSource

    Payment terms.

Payments2
  • Get paymentSource

    One payment by ID.

  • List payments (read only)SourceIncremental

    Payments (read only), optionally updated since a timestamp.

Received payments2
  • Get received paymentSource

    One received payment by ID.

  • List received payments (read only)SourceIncremental

    Received payments (read only), optionally updated since a timestamp.

Recurring bills2
  • Get recurring billSource

    One recurring bill by ID.

  • List recurring bills (read only)Source

    Recurring bills (read only).

Recurring invoices2
  • Get recurring invoiceSource

    One recurring invoice by ID.

  • List recurring invoices (read only)Source

    Recurring invoices (read only).

Vendor credits2
  • Get vendor creditSource

    One vendor credit by ID.

  • List vendor credits (read only)SourceIncremental

    Vendor credits (read only), optionally updated since a timestamp.

Vendors5
  • Create vendorDestinationNot retried automaticallyApproval before production

    Creates a vendor in BILL.

  • Get vendorSource

    One vendor by ID.

  • List vendorsSourceIncremental

    Vendors, optionally updated since a timestamp.

  • Search vendorsSource

    Vendors by name prefix, exact name, account type, country, currency, archive state or created and updated time.

  • Update vendorDestinationProvider duplicate protectionApproval before production

    Updates supplied vendor fields with PATCH. Omitted fields are unchanged.

Access and limits

Authentication
BILL developer key with an AP & AR sync token (or user sign-in)
Plans and access
BILL Accounts Payable and Accounts Receivable plans with a developer key from the BILL developer program. An AP & AR sync token (recommended) can manage vendors, customers, bills, invoices and classifications but cannot pay, void or send; user logins follow the user's role.
Test environment
BILL sandbox organizations use gateway.stage.bill.com with a sandbox developer key.
Rate limits
20,000 requests per developer key per hour, 200 sign-ins per hour, and 3 concurrent requests per developer key and organization (BDC_1144 and BDC_1322).
Pagination
max (up to 100) with nextPage tokens; filters and sort are fixed by the first request.
Provider events
BILL webhook subscriptions for vendor, bill, invoice and payment events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Payments are read only: Nexra never creates, schedules, cancels or voids payments, and never records payments.
  • Bills are created unpaid without approvals; invoices are created without emailing (processingOptions.sendEmail is false).
  • Sessions expire after 35 minutes idle (48 hours for sync tokens); Nexra signs in again after a 401.
  • Archive, restore, bulk endpoints, vendor bank accounts, sending invoices and MFA flows are not automated.
  • Rate-limit errors are returned as BILL error codes; Nexra treats them by HTTP status.
  • Approving bills, recording AP or AR payments, sending invoices, charging customers, invoice payment links, bank and card accounts, budgets, vendor cards, reimbursements, BILL Network invitations, archive and restore, and all deletes are intentionally excluded.
  • Search operations build filters only from fields and operators BILL documents as filterable (https://developer.bill.com/docs/filterable-fields). Name filters reject quotes, commas, colons and backslashes.
  • received_payments reads /connect/v3/receivable-payments, the path BILL's API reference documents for its list of received (customer) payments.
  • Journal entries: BILL's API has no journal entry or general ledger endpoint (BILL syncs those to the customer's accounting system), so journal reads are not available.
  • Bank transactions: BILL's API has no bank statement or bank transaction endpoint (its bank account endpoints only manage payment funding accounts, and Spend & Expense card transactions are a separate product), so bank reconciliation reads are not available.
  • Orders: BILL's API has no sales order or purchase order endpoint, so order reads are not available.
  • Recurring invoices have no documented filterable fields, and recurring bills, payment terms and customer contacts have no documented updatedTime filter, so their lists are full reads.
  • Organization reads omit owner details and tax identifiers.
  • BILL has no idempotency key; uncertain creates are not repeated automatically. Duplicate vendor invoice numbers on bills are rejected by BILL.

Developer reference

  1. Create the BILL Holdings credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose BILL, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/bill and the Connections API.