Real-time
Two-way sync
Changes in Active Directory or Bill instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Active Directory to Bill integration — real-time, two-way sync
Keep Active Directory and Bill 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 Active Directory and Bill
Keep the people who can act on financial records in Bill matched to their identities in Active Directory, so access is provisioned, updated, and revoked in real time.
Bill runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Active Directory is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.
Stacksync keeps Customers, Payments, Chart of Accounts, Bank Accounts in Bill aligned with Organizational units, Organizational contacts, Users, Groups in Active Directory, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.
For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.
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 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
- 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
Common sync patterns
People attributes for allocation and approvals
Department, manager, and employee identifiers carried in Active Directory flow to Bill, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.
Where Active Directory is the identity source: offboarding reaches the books
When a person is deactivated in Active Directory, their matching user in Bill is disabled in the same motion, so departed employees keep no standing access to financial records.
One user roster across both systems
People, their status, and their contact details stay matched between Bill and Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
What you can sync between Active Directory and Bill
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.
| Active Directory objects | Bill objects | How this pairing syncs | |
|---|---|---|---|
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Bank Accounts Funding and deposit accounts; read to reconcile payments and posted transactions against the ledger. | Service principals & applications is specific to Active Directory and Bank Accounts to Bill — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Vendor Credits and Credit Memos AP and AR adjustments applied against bills and invoices; synced so balances stay accurate on both sides. | Organizational units is specific to Active Directory and Vendor Credits and Credit Memos to Bill — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | 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. | Organizational contacts is specific to Active Directory and Bills to Bill — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | 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. | Users is specific to Active Directory and Vendors to Bill — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Invoices Accounts-receivable invoices sent to customers; created and read via /v3/invoices to keep billing status aligned with the ERP or CRM. | Groups is specific to Active Directory and Invoices to Bill — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. | Group memberships is specific to Active Directory and Customers to Bill — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Bill
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.
Active Directory Bill Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is written to Bill through its API, with automatic retries and rate-limit backoff.
Bill Active Directory 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 Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- 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.
What ships with Active Directory ⇄ Bill
Connect Active Directory and Bill for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Bill connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Bill 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 Active Directory or Bill record.
Observability
Monitoring
Track your Active Directory ⇄ Bill sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Bill.
How the Active Directory and Bill connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
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.
How it works
How to connect Active Directory to Bill — 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 Active Directory and Bill with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Bill
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Bill 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 · Active Directory ⇄ BillCustomers 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.
Active Directory BillCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Bill integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Bill: authenticate both systems, choose the objects to sync (such as Active Directory's Service principals & applications and Organizational units), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Bill: List endpoints support filtering and sorting on createdTime and updatedTime with ISO 8601 date-time ranges, which sync engines use to pull only incremental changes. Active Directory: On-premises AD DS has no Graph API and syncs over LDAP/LDAPS using the DirSync control, which needs the DS-Replication-Get-Changes right on the partition. Stacksync's field mapping accounts for these differences between Active Directory and Bill 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 Active Directory and Bill records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and Bill connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Bill integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Bill. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On Bill: Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 498 integrations available for Active Directory and Bill.
Popular · 8 of 498
-
Active Directory ⇄ Chargebee -
Active Directory ⇄ Hyperline -
Active Directory ⇄ Pigment -
Active Directory ⇄ QuickBooks -
Bill ⇄ Okta -
Bill ⇄ Onelogin -
Bill ⇄ Auth0 -
Bill ⇄ Jumpcloud
No integrations match .
