Production and Staging use different accounts and developer credentials.
Before you start
- A Bill.com login email and password.
- A Developer Key and Organization ID for the chosen environment.
1. Open Bill.com developer settings
In Bill.com, open Sync & Integrations → Manage Developer Keys.
2. Copy the key and organization ID
Generate a Developer Key and copy the Organization ID shown at the bottom of that page.
Find the key and organization
In Bill.com, open Sync & Integrations → Manage Developer Keys. Generate a Developer Key for the environment you will connect. The Organization ID appears at the bottom of that page. Copy both values before opening Permute.
Production and sandbox have separate credentials. A production key cannot stand in for a staging key, so set Permute’s environment to match the Bill.com account and key.
Use the matching Bill.com login
Bill.com API sign-in uses a username, password, Organization ID, and Developer Key together. Enter a user who can access the organization identified by the Organization ID. Keep the environment consistent across the credentials.
Bill.com sessions expire after inactivity. If sign-in keeps failing, check the current login credentials.
3. Add Bill.com in Permute
In your workspace, open Connectors, select Add Connector, choose Bill.com, and name the account.
Under Sync which data?, choose an option:
| Choice | What it does |
|---|---|
| Everything | Selects all discovered data available to this connection. |
| Select manually | Choose the tables Permute syncs. |
Connection details
| Field or access | What to use |
|---|---|
| Environment | Choose Production or Staging for the Bill.com account. |
| Username and Password | Use a login for the chosen organization and environment. |
| Developer Key | Copy it from Sync & Integrations → Manage Developer Keys. |
| Organization ID | Copy it from the same Bill.com environment. |
- Choose Production or Staging (sandbox) to match the Bill.com account.
- Enter Username, Password, Developer Key, and Organization ID. Select Connect.
4. Choose tables (manual selection)
If you chose Select manually, open the connector after connecting. Use the checkboxes to select at least one table, then select Save selection.
5. Check the first result
- Choose a bill in the selected Bill.com organization and environment.
- Compare its vendor, amount, due date, and payment status with the source bill.
Available data
| Data group | What the setup screen covers |
|---|---|
| Payables | Bills and vendors. |
| Receivables and payments | Invoices, customers, and payments. |
Distinguish bills from customer invoices
In BILL, a bill records money owed to a vendor for goods or services. Its vendor ID links it to the payee; due date and bill line items describe when and why payment is owed. The bill can also carry the vendor’s invoice number and date.
When comparing bill data, use the bill ID and vendor rather than invoice number alone. An invoice number on a bill comes from the vendor’s document. The setup screen also names customer invoices as a separate group, so confirm which side of the transaction you are checking.
Check bill detail and status
BILL bills can include several line items. A line has an amount and may use quantity and price to calculate it. The bill response also includes payment and approval status. Compare the bill total with the line items, and check status before treating an unpaid bill as a missing payment.
Use a known bill in the organization you entered in Permute. Confirm its vendor, due date, amount, and status in BILL first. This is more precise than checking only whether a table has rows.
Access and source details
Keep sandbox and production separate
Bill.com issues developer credentials for each environment. Its sandbox is for testing and its production account holds live business data. Select Staging only when the login, Developer Key, and Organization ID are for the sandbox.
A successful sandbox test does not connect live data. When you move to production, repeat setup with the production organization and key.
Troubleshooting
| Problem | What to check |
|---|---|
| Sign-in is rejected | Check all four credentials and the selected environment together. |
| Live records are absent | Check whether Permute is connected to Staging instead of Production. |