Real-time
Two-way sync
Changes in Bill or Greenhouse instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Human resources
Bill to Greenhouse integration — real-time, two-way sync
Keep Bill and Greenhouse 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 Greenhouse
Keep the employee, department, and cost records that Bill and Greenhouse 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. Greenhouse 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 Invoices, Customers, Payments, Chart of Accounts in Bill with Applications, Jobs, Offers, Scorecards in Greenhouse 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 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
- 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
Common sync patterns
Department and cost-center alignment
The org structure maintained in Greenhouse keeps the departments or cost centers in Bill current, so spend and headcount roll up the same way.
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 Greenhouse side flow into Bill for posting, so the books reflect what people actually cost without manual re-entry.
What you can sync between Bill and Greenhouse
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 | Greenhouse objects | How this pairing syncs | |
|---|---|---|---|
| Payments Outgoing vendor payments and received customer payments; read for reconciliation and created to schedule bill pay. | Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. | Payments is specific to Bill and Users to Greenhouse — 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. | Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. | Chart of Accounts is specific to Bill and Departments and Offices to Greenhouse — 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. | Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. | Bank Accounts is specific to Bill and Candidates to Greenhouse — 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. | Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. | Vendor Credits and Credit Memos is specific to Bill and Applications to Greenhouse — each maps to any object or custom field on the other side. | |
| Bills Accounts-payable amounts owed to vendors, with bill line items; read and created via /v3/bills and pulled incrementally by filtering on createdTime/updatedTime. | Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. | Bills is specific to Bill and Jobs to Greenhouse — each maps to any object or custom field on the other side. | |
| Vendors Payee master records; synced two-way with vendor/supplier tables in an ERP or accounting system so new payees don't have to be re-keyed. | Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. | Vendors is specific to Bill and Offers to Greenhouse — each maps to any object or custom field on the other side. |
How changes propagate between Bill and Greenhouse
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 Greenhouse 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 Greenhouse through its API, with automatic retries and rate-limit backoff.
Greenhouse Bill Sub-second propagation
DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.
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.
- Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
What ships with Bill ⇄ Greenhouse
Connect Bill and Greenhouse for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bill–Greenhouse connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bill or Greenhouse 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 Greenhouse record.
Observability
Monitoring
Track your Bill ⇄ Greenhouse 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 Greenhouse.
How the Bill and Greenhouse 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.
Greenhouse
- Integration surface
- Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
- Authentication
- HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
- Change detection
- HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
- Capabilities
- read · write · webhooks
- Rate limits
- Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
How it works
How to connect Bill to Greenhouse — 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.
- 01
Connect your apps
Authenticate Bill and Greenhouse with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bill
connected
Greenhouse
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bill and Greenhouse 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.
objects · Bill ⇄ GreenhouseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Bill GreenhouseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bill and Greenhouse integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bill and Greenhouse: authenticate both systems, choose the objects to sync (such as Bill's Payments and Chart of Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Bill side: Invoices, Customers, Payments, Chart of Accounts, plus custom fields where Bill exposes them. On the Greenhouse side: Applications, Jobs, Offers, Scorecards. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Bill and Greenhouse: Department and cost-center alignment; Status changes propagate; People-driven costs land in finance. The org structure maintained in Greenhouse keeps the departments or cost centers in Bill current, so spend and headcount roll up the same way.
-
Bill: 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. Greenhouse: Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import). Authentication: HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user. Stacksync manages authentication, retries, and rate limits on both sides.
-
Bill: BILL exposes separate AP and AR object sets plus a distinct Spend & Expense API that uses its own token and a lower 60-calls-per-minute limit. Greenhouse: Pagination is Link-header (RFC-5988) based with per_page between 1 and 500 (default 100). Stacksync's field mapping accounts for these differences between Bill and Greenhouse without custom code.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 500 integrations available for Bill and Greenhouse.
Popular · 8 of 500
-
Bill ⇄ Jobvite -
Bill ⇄ Lever -
Bill ⇄ Namely -
Bill ⇄ Paylocity -
Greenhouse ⇄ Anaplan -
Greenhouse ⇄ Chargebee -
Greenhouse ⇄ Hyperline -
Greenhouse ⇄ Pigment
No integrations match .
