Skip to content
Accounting and finance ⇄ Human resources

Bill to Lever integration — real-time, two-way sync

Keep Bill and Lever in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Bill and Lever

Keep the employee, department, and cost records that Bill and Lever share consistent in real time, so the finance system and the people system stop drifting apart.

Bill runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Lever runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Customers, Payments, Chart of Accounts, Bank Accounts in Bill with Postings, Requisitions, Offers, Users in Lever bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Sync Customers and Invoices from BILL AR into a CRM or ERP so sales and finance see billing and payment status on the account.
  • 02 Write Vendors created during ERP onboarding into BILL so new payees are ready to pay without manual re-entry.
  • 03 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.
  • 04 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.

Common sync patterns

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the Lever side flow into Bill for posting, so the books reflect what people actually cost without manual re-entry.

New person becomes a known record in finance

When someone is added in Lever, a matching employee or payee record appears in Bill, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

What you can sync between Bill and Lever

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Bill objects Lever objects How this pairing syncs
Invoices Accounts-receivable invoices sent to customers; created and read via /v3/invoices to keep billing status aligned with the ERP or CRM. Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Invoices is specific to Bill and Postings to Lever — each maps to any object or custom field on the other side.
Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Customers is specific to Bill and Requisitions to Lever — each maps to any object or custom field on the other side.
Payments Outgoing vendor payments and received customer payments; read for reconciliation and created to schedule bill pay. Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Payments is specific to Bill and Offers to Lever — each maps to any object or custom field on the other side.
Chart of Accounts GL accounts used to code bills and invoices; typically mastered in the accounting system and written into BILL for consistent coding. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Chart of Accounts is specific to Bill and Users to Lever — each maps to any object or custom field on the other side.
Bank Accounts Funding and deposit accounts; read to reconcile payments and posted transactions against the ledger. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Bank Accounts is specific to Bill and Stages to Lever — each maps to any object or custom field on the other side.
Vendor Credits and Credit Memos AP and AR adjustments applied against bills and invoices; synced so balances stay accurate on both sides. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Vendor Credits and Credit Memos is specific to Bill and Feedback to Lever — each maps to any object or custom field on the other side.

How changes propagate between Bill and Lever

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Bill Lever Sub-second propagation

DetectionBill notifies Stacksync of record changes through webhook events. Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on.

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Lever Bill Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to Bill through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Bill: 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with Bill ⇄ Lever

Connect Bill and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bill–Lever connection.

Real-time

Two-way sync

Changes in Bill or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Bill or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Bill or Lever record.

Observability

Monitoring

Track your Bill ⇄ Lever sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Bill and Lever.

How the Bill and Lever connectors work

Bill

Integration surface
REST/JSON (BILL v3 Connect API)
Authentication
Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps
Change detection
Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback
Capabilities
read · write · webhooks
Rate limits
20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide
How it works

How to connect Bill to Lever — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Bill and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Bill connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Bill and Lever objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Bill ⇄ Lever
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Bill Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Bill and Lever integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 500 integrations available for Bill and Lever.

Popular · 8 of 500
All Bill integrations All Lever integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own