Linking BILL (formerly Bill.com) as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The BILL (formerly Bill.com) connector syncs bills, payments, vendors, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Connect BILL to pull your accounts payable and receivable data.
Create a developer key in your BILL developer account, then enter the email and password you sign in with, your organization ID, and that developer key. PostHog uses them to start an API session for each sync.
BILL Spend & Expense data is not included - it uses a separate API token.
You'll be asked for:
- Email: for example
you@company.com. - Password
- Organization ID
- Developer key
- Environment: choose between Production and Sandbox.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All BILL (formerly Bill.com) tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Email | Yes | |
Password | password | Yes |
Organization ID | text | Yes |
Developer key | password | Yes |
Environment | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
bills | An accounts payable bill your organization owes a vendor. | Incremental, Full refresh | updatedTime, createdTime | — |
payments | A payment sent to a vendor to settle one or more bills. | Incremental, Full refresh | updatedTime, createdTime | — |
vendors | A vendor your organization pays through BILL. | Incremental, Full refresh | updatedTime, createdTime | — |
vendor_credits | A credit issued by a vendor that can be applied against bill payments. | Incremental, Full refresh | updatedTime, createdTime | — |
recurring_bills | A template that generates bills for a vendor on a repeating schedule. | Incremental, Full refresh | updatedTime, createdTime | — |
invoices | An accounts receivable invoice your organization issued to a customer. | Incremental, Full refresh | updatedTime, createdTime | — |
customers | A customer your organization invoices through BILL. | Incremental, Full refresh | updatedTime, createdTime | — |
receivable_payments | A payment received from a customer against one or more invoices. | Incremental, Full refresh | updatedTime, createdTime | — |
credit_memos | A credit issued to a customer that can be applied against invoices. | Incremental, Full refresh | updatedTime, createdTime | — |
recurring_invoices | A template that generates customer invoices on a repeating schedule. | Incremental, Full refresh | updatedTime, createdTime | — |
bank_accounts | A bank account your organization funds BILL payments from. | Incremental, Full refresh | updatedTime, createdTime | — |
chart_of_accounts | A chart of accounts entry used to categorize bills, invoices, and payments. | Incremental, Full refresh | updatedTime, createdTime | — |
accounting_classes | An accounting class used to categorize transactions. | Incremental, Full refresh | updatedTime, createdTime | — |
departments | A department used to categorize transactions. | Incremental, Full refresh | updatedTime, createdTime | — |
employees | An employee used to categorize transactions. | Incremental, Full refresh | updatedTime, createdTime | — |
items | An item that can be added as a line item on bills and invoices. | Incremental, Full refresh | updatedTime, createdTime | — |
jobs | A job used to categorize transactions. | Incremental, Full refresh | updatedTime, createdTime | — |
locations | A location used to categorize transactions. | Incremental, Full refresh | updatedTime, createdTime | — |
users | A user in your BILL organization. | Incremental, Full refresh | updatedTime, createdTime | — |
Troubleshooting
- If the connection fails with an authorization error, the password is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.