Skip to main content
A sync token cannot do everything a password sign-in can. BILL blocks these on this connection: creating or cancelling payments, sending invoices, reading, creating or deleting vendor bank accounts, and creating bank accounts. You also cannot turn on bill approvals when creating or updating bills. BILL allows bills, bulk bills, bill documents, vendors, customers, invoices and classifications on this connection.

​
Sign in to BILL

BILL runs production and sandbox on completely separate hosts, each with its own credentials. Sign in to the environment you are connecting. The sync token replaces your email and password in StackOne, so SSO users can connect without a password.

1

Sign in to the BILL web app

Open the sign-in page for your environment, enter your email and click Continue. SSO users are sent to their company login after clicking Continue.

BILL Sign in page with the Email field and Continue button highlighted

​
Create a sync token

The sync token has two parts: the name you give it and the token value BILL generates when you save it. You need both.

1

Open Tokens

In the left navigation, click Settings, expand Sync & Integrations and click Tokens.

Expanded Sync and Integrations section showing App Center, Manage Developer Keys and Tokens
2

Create the token

Click NEW, enter a name such as StackOne, and click SAVE. Paste the name into the Sync Token Name field in StackOne Hub, then copy the generated token into the Sync Token field.

  • Keep the token somewhere safe, such as a password manager.
  • A sync token is tied to the organization you created it in. To connect a second organization, create a token in that organization and connect it as a separate account.

​
Generate and copy the Developer Key

The Developer Key identifies your integration to BILL. It lives on the Manage Developer Keys page, in the same Sync & Integrations menu. Generate one if the table is empty.

1

Generate a developer key

On the Manage Developer Keys page, click Generate developer key.

Manage Developer Keys page with the Generate developer key button highlighted
2

Generate the key

Tick I agree to the BILL developer terms of service., then click Generate key.

  • It takes up to a minute for BILL to generate the key. Click Reload page after a few moments to see it.
Generate developer key dialog with the terms of service checkbox and Generate key button highlighted
3

Copy the Developer Key

In the Developer key column, click the eye icon (Show developer key) to reveal the value, then copy it into the Developer Key field in StackOne Hub.

Developer keys table with the masked key value, its reveal control and the Rename button highlighted

​
Copy the Organization ID

The Organization ID tells BILL which organization to sign in to. It is on the same page.

1

Copy the Organization ID

Scroll to the bottom of the Manage Developer Keys page. The value after Organization ID: is your organization identifier. Copy it into the Organization ID field in StackOne Hub.

  • Format: 008 followed by 17 alphanumeric characters
  • Example: 00801ABCDEFGHIJKLMNO
Bottom of the Manage Developer Keys page with the Organization ID line highlighted

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • Sync Token Name
  • Sync Token
  • Developer Key
  • Organization ID
3

Connect

  • Click Connect
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.