NEWFlows V2 has been releasedSee what shipped
INTEGRATIONSSAAS
BL
BILL28 OF 28 CAPABILITIES ASSESSED

Who can pay from BILL, with roles granted and archived from Ploy

BILL organisation users and their role, with new users, role changes, archiving and restoring written back.

TYPE · SAAS
BILL connectorHOURLY SYNCCAPABILITIES
WHAT PLOY DOES
Sync BILL organisation usersEvery user of the connected BILL organisation arrives in Ploy as an identity, archived users included, read from the complete user list.
READ
Read archived usersArchiving is how BILL takes access away, so an archived user is marked blocked and their BILL access is revoked on the same scan.
READ
Read each user's BILL roleThe role type, from Administrator to Clerk, rides as the entitlement on the user's access to BILL. When a role changes, the old one is archived on the next scan.
READ
Map each role as a resourceEach role in use lands as its own resource with the people who hold it, keyed by the role itself so two custom roles stay apart.
READ
Register BILL as an app in useBILL lands in the app inventory with its active users attached.
READ
Create BILL usersPloy creates a user in the organisation with the role the request named. A role is always required, so a flow never creates an Administrator by default.
WRITE
Change a user's BILL rolePloy moves a user to another BILL role and checks the role BILL returns before it reports success.
WRITE
Archive usersPloy archives a user, which takes away their BILL access, and records the revocation straight away.
WRITE
Restore archived usersPloy restores an archived user, who comes back with the role they held before.
WRITE
2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

LEAVERS

Offboarding archives the BILL user

When someone leaves, Ploy archives their BILL user and records the lost access at once, so nobody keeps the right to approve or pay after their last day.

ROLES

Payment roles granted for the work in hand

An approved request creates the user with the role it named, or moves an existing user to it, and the role is changed back through the same path.

REVIEWS AND EVIDENCE

Who holds each role, custom roles included

Every role in use has its own page with its holders, so a finance review sees who can approve and who can pay, organisation by organisation.

2.3

SETUP

TYPICALLY 10 MINUTES
STEP 01

Get a BILL developer key

Create a BILL developer account to get a developer key, and note the ID of the organisation to connect. It starts with 008.

STEP 02

Create a user for Ploy

Add a dedicated BILL user with the Administrator role, then enter the environment, developer key, organisation ID, username and password in Ploy. Ploy signs in as that user to start each API session.

STEP 03

Watch the first sync

Ploy tests the sign-in against the user list, then users, their roles and their archived status land in the graph.

2.4OFTEN CONNECTED TOGETHER
XEXeroSAASOktaIDENTITY SOURCESlackAPPROVALS
BROWSE ALL 83 INTEGRATIONS

Connect BILL, see it in 10 minutes.