Real-time
Two-way sync
Changes in Active Directory or Rillet instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Active Directory to Rillet integration — real-time, two-way sync
Keep Active Directory and Rillet 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 Rillet
Keep the people who can act on financial records in Rillet matched to their identities in Active Directory, so access is provisioned, updated, and revoked in real time.
Rillet 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 Vendor, Invoice, Credit Memo, Bill in Rillet aligned with Organizational contacts, Users, Groups, Group memberships 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 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
- 02 Sync AR and collection status back to customer success tools ahead of renewals.
- 03 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
- 04 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
Common sync patterns
Where Active Directory is the identity source: offboarding reaches the books
When a person is deactivated in Active Directory, their matching user in Rillet 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 Rillet and Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
Group and role membership drives finance permissions
A person's group or role in Active Directory maps to their permission set in Rillet, so who can approve, post, or view is governed from one place instead of maintained twice.
What you can sync between Active Directory and Rillet
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 | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Organizational contacts is specific to Active Directory and Invoice Payment to Rillet — 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. | Charge Synced with incremental and full sync per the Stacksync docs. | Users is specific to Active Directory and Charge to Rillet — 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. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Groups is specific to Active Directory and Reimbursement to Rillet — 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. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Group memberships is specific to Active Directory and Custom Field to Rillet — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Account Synced with incremental and full sync per the Stacksync docs. | Devices is specific to Active Directory and Account to Rillet — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Customer Synced with incremental and full sync per the Stacksync docs. | Directory roles is specific to Active Directory and Customer to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Rillet
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 Rillet 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 Rillet through its API, with automatic retries and rate-limit backoff.
Rillet Active Directory Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
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.
- Rillet: Subject to the platform's API rate limits.
What ships with Active Directory ⇄ Rillet
Connect Active Directory and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Rillet 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 Rillet record.
Observability
Monitoring
Track your Active Directory ⇄ Rillet 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 Rillet.
How the Active Directory and Rillet 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.
Rillet
- Integration surface
- REST API (OpenAPI-specified, with production and sandbox environments)
- Authentication
- API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
- Change detection
- Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Subject to the platform's API rate limits.
How it works
How to connect Active Directory to Rillet — 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 Rillet 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
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Rillet 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 ⇄ RilletCustomers 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 RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Rillet: authenticate both systems, choose the objects to sync (such as Active Directory's Organizational contacts and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Rillet side: Vendor, Invoice, Credit Memo, Bill, plus custom fields where Rillet exposes them. On the Active Directory side: Organizational contacts, Users, Groups, Group memberships. 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 Active Directory and Rillet: Where Active Directory is the identity source: offboarding reaches the books; One user roster across both systems; Group and role membership drives finance permissions. When a person is deactivated in Active Directory, their matching user in Rillet is disabled in the same motion, so departed employees keep no standing access to financial records.
-
Active Directory: 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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
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 425 integrations available for Active Directory and Rillet.
Popular · 8 of 425
-
Active Directory ⇄ Braintree -
Active Directory ⇄ Navan -
Active Directory ⇄ Ramp -
Active Directory ⇄ Recurly -
Rillet ⇄ Auth0 -
Rillet ⇄ Jumpcloud - Rillet ⇄ Azure Active Directory
-
Rillet ⇄ Okta
No integrations match .
