Real-time
Two-way sync
Changes in Bill or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ CRM
Bill to Nutshell integration — real-time, two-way sync
Keep Bill and Nutshell 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 Nutshell
Sync customers, invoices, and payment status between Bill and Nutshell in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Nutshell knows the relationship: who the contacts are and what is in motion with the account. Bill knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Payments, Chart of Accounts, Bank Accounts, Vendor Credits and Credit Memos in Bill to Users, Leads, People, Companies in Nutshell with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Common use cases
- 01 Write Vendors created during ERP onboarding into BILL so new payees are ready to pay without manual re-entry.
- 02 Read Payments and payment status into a reconciliation database once bills are marked paid in BILL.
- 03 Mirror tasks and activities into ops tools for cross-team visibility.
- 04 Sync Nutshell leads into a warehouse or Postgres so small B2B teams can report on pipeline without exports.
Common sync patterns
Where Nutshell tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Bill with the right billing details, so invoicing starts without re-keying.
Payment status on the account
Invoice and payment status from Bill appears on the account in Nutshell, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Nutshell, Bill gets the update before the next invoice goes out.
What you can sync between Bill and Nutshell
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 | Nutshell 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. | People Individual contacts, kept consistent with marketing and outreach tools | Invoices is specific to Bill and People to Nutshell — 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. | Companies Account records that group people and leads for account-level syncs | Customers is specific to Bill and Companies to Nutshell — 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. | Activities Logged calls, meetings, and emails used for engagement reporting | Payments is specific to Bill and Activities to Nutshell — 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. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Chart of Accounts is specific to Bill and Tasks to Nutshell — 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. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Bank Accounts is specific to Bill and Notes to Nutshell — 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. | Products Line items attached to leads, used to sync sold products into billing | Vendor Credits and Credit Memos is specific to Bill and Products to Nutshell — each maps to any object or custom field on the other side. |
How changes propagate between Bill and Nutshell
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 Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Nutshell Bill Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
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.
- Nutshell: Subject to the platform's API rate limits.
What ships with Bill ⇄ Nutshell
Connect Bill and Nutshell for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bill–Nutshell connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bill or Nutshell 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 Nutshell record.
Observability
Monitoring
Track your Bill ⇄ Nutshell 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 Nutshell.
How the Bill and Nutshell 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.
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Bill to Nutshell — 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 Nutshell 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
Nutshell
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bill and Nutshell 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 ⇄ NutshellCustomers 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 NutshellCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bill and Nutshell integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bill and Nutshell: authenticate both systems, choose the objects to sync (such as Bill's Invoices and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Nutshell: Where Nutshell tracks deals: closed-won creates the finance record; Payment status on the account; Billing detail changes flow back. A won opportunity creates or updates the customer in Bill with the right billing details, so invoicing starts without re-keying.
-
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. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Stacksync manages authentication, retries, and rate limits on both sides.
-
Bill: Rate limits are enforced per developer key: 20,000 requests per hour, login capped at 200 per hour, and a maximum of 3 concurrent requests per developer key per organization. Nutshell: Nutshell's most full-featured API is JSON-RPC: each call names a method such as findLeads or editLead instead of hitting resource URLs, though a newer REST API is also available. Stacksync's field mapping accounts for these differences between Bill and Nutshell without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Bill and Nutshell records are not retained after a sync operation.
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
CSA STAR
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 414 integrations available for Bill and Nutshell.
Popular · 5 of 414
No integrations match .
