Real-time
Two-way sync
Changes in Microsoft 365 or Rillet instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Accounting and finance
Microsoft 365 to Rillet integration — real-time, two-way sync
Keep Microsoft 365 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 Microsoft 365 and Rillet
Connect the financial records in Rillet with the work happening in Microsoft 365, so both stay current without exports or copy-paste.
Rillet holds the financial truth: who the customers are, what they were billed, what they paid. Microsoft 365 is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Invoice Payment, Charge, Reimbursement, Custom Field in Rillet and OneDrive Files (driveItems), SharePoint Sites & Lists, Teams, Planner & To Do Tasks in Microsoft 365 in sync, bi-directionally and in real time. Whatever records Microsoft 365 keeps and whatever events it produces, the overlap with Rillet is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Common use cases
- Sync AR and collection status back to customer success tools ahead of renewals.
- Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- Sync employee records from an HR system into Entra ID users and group memberships.
- Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
Where Microsoft 365 is a docs or knowledge workspace: reference data kept fresh
Figures teams rely on, like customer status or outstanding balances, stay current wherever Microsoft 365 surfaces them instead of going stale after a one-time paste.
Where Microsoft 365 handles customer conversations: billing context in view
Front-line teams see invoice and payment status from Rillet next to the customer they are helping, without logging into the finance system.
Where Microsoft 365 collects payments or triggers charges: events land in Rillet
Payment and charge activity flows into Rillet as it happens, so the books reflect reality without manual reconciliation.
What you can sync between Microsoft 365 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.
| Microsoft 365 objects | Rillet objects | |
|---|---|---|
| OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | |
| SharePoint Sites & Lists List items read and written like lightweight database tables. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | |
| Teams Team and membership data provisioned from upstream systems. | Charge Synced with incremental and full sync per the Stacksync docs. | |
| Planner & To Do Tasks Task items synced with project and work-management tools. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | |
| Users Entra ID user accounts synced with HR and identity systems. | Custom Field Synced with incremental and full sync per the Stacksync docs. | |
| Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Account Synced with incremental and full sync per the Stacksync docs. |
What ships with Microsoft 365 ⇄ Rillet
Connect Microsoft 365 and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft 365 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 Microsoft 365 or Rillet record.
Observability
Monitoring
Track your Microsoft 365 ⇄ Rillet sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft 365 and Rillet.
How the Microsoft 365 and Rillet connectors work
Microsoft 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
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 Microsoft 365 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 Microsoft 365 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.
Microsoft 365
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft 365 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 · Microsoft 365 ⇄ 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.
Microsoft 365 RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft 365 and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft 365 and Rillet: authenticate both systems, choose the objects to sync (such as Microsoft 365's OneDrive Files (driveItems) and SharePoint Sites & Lists), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Rillet side: Invoice Payment, Charge, Reimbursement, Custom Field, plus custom fields where Rillet exposes them. On the Microsoft 365 side: OneDrive Files (driveItems), SharePoint Sites & Lists, Teams, Planner & To Do Tasks. 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 Microsoft 365 and Rillet: Where Microsoft 365 is a docs or knowledge workspace: reference data kept fresh; Where Microsoft 365 handles customer conversations: billing context in view; Where Microsoft 365 collects payments or triggers charges: events land in Rillet. Figures teams rely on, like customer status or outstanding balances, stay current wherever Microsoft 365 surfaces them instead of going stale after a one-time paste.
-
Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. 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.
-
Rillet: Rillet is built for SaaS companies, with a general ledger organized around automated revenue recognition and month-end close. Microsoft 365: Access is scoped per permission via Entra ID admin consent, so an integration only sees the workloads it was granted. Stacksync's field mapping accounts for these differences between Microsoft 365 and Rillet without custom code.
SECURITY
Security teams love 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 386 integrations available for Microsoft 365 and Rillet.
Popular · 8 of 386
-
Microsoft 365 ⇄ Stripe -
Microsoft 365 ⇄ Workday -
Microsoft 365 ⇄ Anaplan -
Microsoft 365 ⇄ Chargebee -
Rillet ⇄ NextGen Healthcare -
Rillet ⇄ Orderful -
Rillet ⇄ Resend - Rillet ⇄ ServiceNow
No integrations match .
