Skip to content
Merulan

BILL setup

What an operator supplies to connect the BILL Source, and the verification the provider requires.

Connecting BILL accepts a named secret bundle the operator fills in. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

BILL refuses the connection until every item holds.

  • A BILL account with AP and AR access for the organization a Pipeline reads.
  • A BILL developer key for the environment, issued by BILL rather than by the operator.
  • An operator who can renew the sign-in material, because a BILL session expires after 48 hours without use.

Credentials

BILL stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • A sync token name and its value, which are sign-in material rather than a password and carry no second factor.
  • A BILL developer key.

Scopes

BILL requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • bills:read
  • vendors:read

BILL grants reach through the signed-in user rather than a consent screen. The names above are the read set the adapter exercises.

Verification

Workspace-issued credential governs the BILL connection. BILL issues the developer key and the sync token to the customer, so no application review stands between them and production data.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.