Two-way sync
Changes in Oracle Fusion Cloud HCM or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Oracle Fusion Cloud HCM 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.
Rillet runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Oracle Fusion Cloud HCM runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.
Stacksync syncs Custom Field, Account, Customer, Vendor in Rillet with Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments, Jobs in Oracle Fusion Cloud HCM bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.
That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.
When someone is added in Oracle Fusion Cloud HCM, a matching employee or payee record appears in Rillet, ready for payroll, expenses, or cost allocation without anyone rekeying the details.
A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.
The org structure maintained in Oracle Fusion Cloud HCM keeps the departments or cost centers in Rillet current, so spend and headcount roll up the same way.
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.
| Oracle Fusion Cloud HCM objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Locations Physical work locations referenced by assignments; synced so downstream provisioning and directory tools resolve the same location codes. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Locations is specific to Oracle Fusion Cloud HCM and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Grades and Salaries Grade, grade-rate, and worker compensation records; usually read out for compensation and headcount analytics, and written back for corrections. | Bill Synced with incremental and full sync per the Stacksync docs. | Grades and Salaries is specific to Oracle Fusion Cloud HCM and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Absences (workerAbsenceEntries) is specific to Oracle Fusion Cloud HCM and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| Workers (publicWorkers) Person master with personNumber, names, national IDs, and work relationships; synced two-way via the /workers resource, which replaced the desupported /emps resource. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Workers (publicWorkers) is specific to Oracle Fusion Cloud HCM and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| Assignments Child of a worker's work relationship carrying job, position, department, location, grade, and manager; effective-dated, so writes go through PATCH with an effective date. | Charge Synced with incremental and full sync per the Stacksync docs. | Assignments is specific to Oracle Fusion Cloud HCM and Charge to Rillet — each maps to any object or custom field on the other side. | |
| Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Jobs is specific to Oracle Fusion Cloud HCM and Reimbursement to Rillet — each maps to any object or custom field on the other side. |
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.
DetectionChanges in Oracle Fusion Cloud HCM are captured at the source via change data capture — no polling loop against its API. Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change).
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
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 Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Oracle Fusion Cloud HCM–Rillet connection.
Changes in Oracle Fusion Cloud HCM or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Oracle Fusion Cloud HCM or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Oracle Fusion Cloud HCM or Rillet record.
Track your Oracle Fusion Cloud HCM ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Oracle Fusion Cloud HCM and Rillet.
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.
Authenticate Oracle Fusion Cloud HCM 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.
Pick the Oracle Fusion Cloud HCM 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Oracle Fusion Cloud HCM and Rillet: authenticate both systems, choose the objects to sync (such as Oracle Fusion Cloud HCM's Locations and Grades and Salaries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Oracle Fusion Cloud HCM and Rillet: New person becomes a known record in finance; One employee identity; Department and cost-center alignment. When someone is added in Oracle Fusion Cloud HCM, a matching employee or payee record appears in Rillet, ready for payroll, expenses, or cost allocation without anyone rekeying the details.
Oracle Fusion Cloud HCM: REST API (/hcmRestApi/resources), Atom feeds, and HCM Data Loader (HDL) for bulk. Authentication: OAuth 2.0 bearer tokens via Oracle Identity Cloud Service (IDCS/IAM); HTTP Basic and SAML/JWT bearer over SSL are also accepted, enforced by Oracle Web Services Manager (OWSM). 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: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Oracle Fusion Cloud HCM: Assignments are date-effective; reads and writes must specify an effective date, and updates create new date-effective rows rather than overwriting history. Stacksync's field mapping accounts for these differences between Oracle Fusion Cloud HCM and Rillet 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 Oracle Fusion Cloud HCM and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Oracle Fusion Cloud HCM and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Oracle Fusion Cloud HCM–Rillet integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 426 integrations available for Oracle Fusion Cloud HCM and Rillet.