
BILL
Read and write BILL vendors, customers, unpaid bills, AR invoices, chart of accounts and items, and read departments, locations, payments and received payments.
Feed approved spend and receivables into BILL from ERP, procurement and CRM systems without exposing payment execution.
Source actions
20
Destination actions
12
Data types
10
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
bills
- Create billDestinationNot retried automaticallyApproval before production
Records an unpaid vendor bill with line items. Paying bills is never automated.
bills.create - Get billSource
One bill by ID.
bills.get - List billsSourceIncremental
Bills, optionally updated since a timestamp.
bills.list - Update billDestinationProvider duplicate protectionApproval before production
Updates supplied bill fields with PATCH. Omitted fields are unchanged.
bills.update
chart of accounts
- Create accountDestinationNot retried automaticallyApproval before production
Creates a account in BILL.
chart_of_accounts.create - Get accountSource
One account by ID.
chart_of_accounts.get - List chart of accountsSourceIncremental
Chart of accounts, optionally updated since a timestamp.
chart_of_accounts.list - Update accountDestinationProvider duplicate protectionApproval before production
Updates supplied account fields with PATCH. Omitted fields are unchanged.
chart_of_accounts.update
customers
- Create customerDestinationNot retried automaticallyApproval before production
Creates a customer in BILL.
customers.create - Get customerSource
One customer by ID.
customers.get - List customersSourceIncremental
Customers, optionally updated since a timestamp.
customers.list - Update customerDestinationProvider duplicate protectionApproval before production
Updates supplied customer fields with PATCH. Omitted fields are unchanged.
customers.update
departments
- Get departmentSource
One department by ID.
departments.get - List departmentsSourceIncremental
Departments, optionally updated since a timestamp.
departments.list
invoices
- Create invoiceDestinationNot retried automaticallyApproval before production
Creates an AR invoice without emailing it or enabling card charges.
invoices.create - Get invoiceSource
One invoice by ID.
invoices.get - List invoicesSourceIncremental
Invoices, optionally updated since a timestamp.
invoices.list - Update invoiceDestinationProvider duplicate protectionApproval before production
Updates supplied invoice fields with PATCH. Omitted fields are unchanged.
invoices.update
items
- Create itemDestinationNot retried automaticallyApproval before production
Creates a item in BILL.
items.create - Get itemSource
One item by ID.
items.get - List itemsSourceIncremental
Items, optionally updated since a timestamp.
items.list - Update itemDestinationProvider duplicate protectionApproval before production
Updates supplied item fields with PATCH. Omitted fields are unchanged.
items.update
locations
- Get locationSource
One location by ID.
locations.get - List locationsSourceIncremental
Locations, optionally updated since a timestamp.
locations.list
payments
- Get paymentSource
One payment by ID.
payments.get - List payments (read only)SourceIncremental
Payments (read only), optionally updated since a timestamp.
payments.list
received payments
- Get received paymentSource
One received payment by ID.
received_payments.get - List received payments (read only)SourceIncremental
Received payments (read only), optionally updated since a timestamp.
received_payments.list
vendors
- Create vendorDestinationNot retried automaticallyApproval before production
Creates a vendor in BILL.
vendors.create - Get vendorSource
One vendor by ID.
vendors.get - List vendorsSourceIncremental
Vendors, optionally updated since a timestamp.
vendors.list - Update vendorDestinationProvider duplicate protectionApproval before production
Updates supplied vendor fields with PATCH. Omitted fields are unchanged.
vendors.update
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. Nexra event triggers are not yet available; flows run on demand or on a schedule.
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.
- Department and location classifications are read only in this adapter.
- BILL has no idempotency key; uncertain creates are not repeated automatically. Duplicate vendor invoice numbers on bills are rejected by BILL.
Developer reference
- Create the BILL Holdings credentials described above with the narrowest permissions your flows need.
- 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
- 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.