Skip to content
Accounting and finance ⇄ CRM

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

Keep Bill and Salesforce 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 Salesforce

Sync customers, invoices, and payment status between Bill and Salesforce in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Salesforce 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 Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce 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 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 04 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.

Common sync patterns

Collections with context

Finance sees the account owner and relationship history from Salesforce when chasing a balance, and sales sees that the chase is happening.

Where Salesforce 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 Salesforce, so reps see overdue balances before they promise the next order.

What you can sync between Bill and Salesforce

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 Salesforce objects How this pairing syncs
Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. Customers is specific to Bill and Leads to Salesforce — 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. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Payments is specific to Bill and Opportunities to Salesforce — 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. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Chart of Accounts is specific to Bill and Cases to Salesforce — 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. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Bank Accounts is specific to Bill and Campaigns to Salesforce — 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. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Vendor Credits and Credit Memos is specific to Bill and Tasks and Events to Salesforce — 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. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Bills is specific to Bill and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Bill and Salesforce

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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Bill Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Bill ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Bill or Salesforce 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 Salesforce record.

Observability

Monitoring

Track your Bill ⇄ Salesforce 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 Salesforce.

How the Bill and Salesforce 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.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Bill to Salesforce — 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 Salesforce 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
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Bill and Salesforce 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 ⇄ Salesforce
    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 Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Bill and Salesforce 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
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:

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 531 integrations available for Bill and Salesforce.

Popular · 8 of 531
All Bill integrations All Salesforce 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