Bill

Bill

Govern BILL with Corma: per-user AP/AR pricing, six roles from Administrator to Auditor, deactivation with approval fixes, SSO on Corporate and Enterprise.

The Corma and BILL integration keeps your BILL users and their roles in line with the finance team who approve and pay bills. BILL describes itself as a financial operations platform that automates spend and expense management, accounts payable and accounts receivable. The company completed its acquisition of Divvy, now BILL Spend & Expense, on June 1, 2021, and rebranded from Bill.com to BILL in 2022. BILL AP/AR is priced per user, from $49 per user per month on Essentials to $89 on Corporate (seen on November 16, 2026).

Key takeaways

  • BILL has six pre-defined roles, Administrator, Accountant, Clerk, Approver, Payer and Auditor, and custom roles are included from the Team plan.
  • The BILL Auditor role is view only, but the standard user fee applies, and only Corporate and Enterprise charge less for approver-only users.
  • Deactivated BILL users cannot be fully removed, for auditing purposes, but can no longer log in or receive notifications.
  • BILL single sign-on requires the Corporate or Enterprise plan and supports SAML 2.0 and OpenID Connect 2.0 only.

What does deactivating a BILL user leave behind?

BILL's guide to managing users explains that when a deactivated user is a default approver or has unapproved bills or vendor credits, an Admin gets a To Do List notification to fix those records. If the deactivated user set up the accounting sync, another user with sync permissions must reconnect it. With SSO, removing a user whose login email is on the allowed domain from the identity provider stops them logging in, and BILL does not say it also deactivates them.

Admins can generate up to four developer keys, and signing in with one means signing in as a named user of the BILL organization, with sessions expiring after 35 minutes of inactivity. BILL's OAuth client credentials guide states that access tokens inherit the exact product permissions of the user who created the developer app, and client secrets expire after two years.

How Corma governs BILL

  • Per-user licences in view: BILL AP/AR users sit in SaaS subscription management, where view-only Auditors still carry the standard user fee.
  • Leavers with an approval check: a leaver workflow in the IT Workflow Builder asks an Administrator to deactivate the person, then to fix the approval policies and bills flagged in the To Do List and to reconnect the sync if they set it up.
  • Administrators under review: Administrators and custom roles with Manage Users go into automated access reviews.
  • Developer apps with an owner: OAuth developer apps and developer keys are non-human identities, so each one needs a named owner, since tokens inherit the permissions of the user who created the app.

Frequently asked questions

Does BILL support SSO and SCIM?

BILL single sign-on requires the Corporate or Enterprise plan and supports SAML 2.0 and OpenID Connect 2.0, and the request form gives Okta, Google Workspace and Microsoft Azure Active Directory as example identity providers. BILL documents no SCIM provisioning. Read how SCIM and SAML differ.

How does Corma connect to BILL?

Through the BILL v3 API where it fits, with which an Administrator can create users and manage user access, or through Corma's browser-based agents in BILL's user settings. See also how Corma covers finance tools such as Candis.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want BILL leavers' approvals reassigned the day they leave? Book a Corma demo.

Related Integrations

Check out other integrations that could help you on managing your software licences and accesses!