Enterprise integration, priced like a subscription.
Every price below is per integration pair (e.g., Workday ↔ Sprout) — not per employee. Annual term, in USD. Pay the year up front and save 20%.
Why the price is on the page
We can publish prices because the service is the same shape: scope, build, run in parallel against a real payroll cycle, then operate on an SLA — per pair. And a published price is only useful if it travels: this page is built to be forwarded — the numbers, the term, what's included, and what the SLA pays back when we miss — so finance can read it without you in the room. The scoping call adds what this page can't know: a fixed quote for your exact systems, within a week, whether or not you buy. What can move that quote is published below, not sprung in the call.
what moves the number →Standard & Premium
| Standard | Premium | |
|---|---|---|
| Setup | from $10,000 | from $15,000 |
| Monthly | $2,249 — or $1,799/mo paid annually | $3,749 — or $2,999/mo paid annually |
| The platform — identical on both tiers | ||
| Full implementation — discovery, field mapping, build, parallel-run UAT | ✓ | ✓ |
| Scheduled syncs, hourly–daily | ✓ | ✓ |
| All four data domains | ✓ | ✓ |
| Dashboard, alerts, reconciliation reports | ✓ | ✓ |
| 99.5% SLA with service credits | ✓ | ✓ |
| Connector maintenance & minor mapping changes | ✓ | ✓ |
| The service tier — where Premium differs | ||
| Custom transformation & business logic — multi-entity rules, derived fields, conditional routing | — | ✓ |
| Support hours | Mon–Fri 9:00–18:00 PHT | Daily 7:00–22:00 PHT |
| First response | Next business day | 4 hours |
| Payroll-window emergency on-call | — | ✓ |
| Support queue · success manager | Standard queue · shared | Priority queue · dedicated |
Every platform capability is identical on both tiers; the tiers differ in custom logic and support depth.
Full SLA and support detail →Which tier is yours?
Standard is the default. Straightforward field mappings — code tables, formats, field-to-field, no custom business logic — and business-hours support fits how your team works. It isn't the teaser tier: the whole platform half of the table above, the same 99.5% SLA, the same service credits.
Premium earns its price in two situations. Your data needs custom business logic. Or your payroll window can't wait for tomorrow: on either tier a failed sync is re-run the same business day — Premium adds a human on the line now, on the support terms in the table, plus the priority queue and a dedicated success manager.
The tier is named in your fixed quote, and it holds: if custom-logic needs surface mid-implementation that scoping should have caught, absorbing them is our problem — not your change order. And if Standard covers you, the quote will say Standard.
What the setup fee pays for — and why it's a number
Integration builds are usually quoted in day rates, which means the real price is known when the work is done. Ours works the other way: published starting prices, one scoping call, a fixed quote before the work starts. The setup fee is the implementation, not a license activation: the discovery and data audit, the field-mapping document that's versioned, signed off, and yours to keep, the build run in parallel against a real payroll cycle — nothing writes to production until the outputs match — then cutover and 30 days of hypercare.
How implementation works →And the fee is priced like the promise: invoiced half at signing, half at go-live. If the parallel run can't be made to match, the go-live half is never invoiced.
Premium — from $15,000 — adds the design and build of your custom business logic as part of the same implementation.
Pricing this against a quote from your Workday partner? Please do. We publish ours so you can.
What the monthly fee pays for — and where it stops¶
The setup fee builds the integration. The monthly fee keeps it true at every cutoff — an operations function, not a software license.
In the fee, on both tiers:
- Every scheduled run, watched to completion. Failures alert our engineers first and re-run the same business day.
- Connector maintenance when vendors move. Vendor releases and API changes on either side are ours to absorb — updating and re-testing, inside the fee.
Change management, on the Product page → - Minor mapping changes. A new department, a new allowance, a code-table addition — not a change order.
- The dashboard, alerts, and reconciliation reports your cutoff sign-off runs on.
- An SLA with money behind it. Miss 99.5% and the service credits come out of this same fee.
No metered hours, no per-ticket fees — support is never billed by the hour, on either tier.
Scoped and quoted as it arises: a new data domain or a new entity after go-live. And complex conditional or multi-entity logic isn't a change order — it's Premium's custom-logic feature, covered by that tier above.
Cutoff comes every month. The monthly fee is the part of the price that shows up for it.
The first term, added up
Per integration pair, at the published starting prices — the number to take to finance:
| First 12-month term | Standard | Premium |
|---|---|---|
| Paid annually | $31,588 ($10,000 setup + $21,588) | $50,988 ($15,000 setup + $35,988) |
| Billed monthly | $36,988 ($10,000 + 12 × $2,249) | $59,988 ($15,000 + 12 × $3,749) |
The 20%, in dollars. Paying the year up front is one payment instead of twelve — and $5,400 less per term on Standard, $9,000 less on Premium. Running the Compliance Pack? Add $6,000/year, billed monthly.
These are starting figures for a typical two-system pair. What can move them ↓
the numbers above become a fixed quote.
Book a scoping callAdd-on: Compliance Pack — +$500/month, flat
PH statutory file generation from your synced data: BIR, SSS, PhilHealth, Pag-IBIG. Available on either tier, for pairs whose local side runs Philippine payroll. Add it whenever filings start to hurt — it's built against data you're already syncing — and drop it at term end. The annual discount doesn't apply — add-ons stay at the monthly rate.
How the Pack works →Adding integrations¶
Second and subsequent pairs: 30% off setup — from $7,000 as a Standard pair, from $10,500 as Premium — because discovery and infrastructure are already done. The discount applies whether the pair joins your first engagement or arrives a year later. The monthly fee stays full per pair, at its tier's rate, because every pair gets its own monitoring, its own SLA measurement, and its own support — and its own 12-month term from its own go-live, with annual payment your choice per pair. A second pair is never a side project.
Find your pair on the Integrations page →Three ways to pay for this problem
A consultancy or your Workday SI. Day rates through the build, then roll-off — and changes after go-live re-open the meter.
An iPaaS plus your own people. The license is the line item you see; the real cost is the engineer who builds on it, tests it, watches it at every cutoff, and updates it when a vendor API changes — a role you staff, forever.
Keep re-keying. The only option with no invoice — paid instead in hours every cutoff, and in payroll-error risk.
Here, it's published starting prices, per pair: the build in the setup fee; the running, connector maintenance, and minor mapping changes in the monthly.
More on these in the FAQ →Published price vs. your quote — what can move the number¶
Published figures are starting prices for a typical two-system integration: one global HRIS, one local system, vendor-supported APIs on both sides. And "starting" applies to the setup fee — for vendor-API pairs, the monthly fee is the monthly fee; it doesn't move. Your quote is fixed, and if it's higher than this page, the quote says so up front, not in a change order later. The usual things that move it:
- A system with no usable API. Screen-based or direct-database connectivity is custom scope — priced in your quote, including its monthly, with a connection-specific SLA defined there. The published 99.5% commitment applies to vendor-API connections.
- A first-of-its-kind connector. A pair we haven't built before is scoped as exactly that.
How that answer gets decided → - Complex business logic. That's Premium, named in the quote.
After go-live, larger structural changes — a new data domain or a new entity — are scoped and quoted as they arise; what the monthly fee already covers draws the boundary. Need Premium's logic later? Upgrade any time: the logic build is quoted, and the monthly moves to the Premium rate from then on. Downgrades take effect at term end.
When you pay: the monthly fee — and your 12-month term — starts at go-live, not at signing. You don't pay a monthly fee for a sync that isn't running. Annual-payment pricing is billed once, at go-live, per 12-month term; add-ons are billed monthly at the flat rate.
After month 12: your price is locked for the paid term — the annual discount isn't a year-one teaser. The contract renews at the then-published price; if the published price changes, you hear it in writing 60 days before it reaches an invoice. Leave at term end with notice — no exit fee. Any service credits accrued in a prepaid year net against your renewal invoice, refunded in cash if you don't renew.
What stands behind a number this size
A price this size usually leans on a customer-logo wall. Ours leans on what's in writing:
- The parallel run decides go-live — and you hold the pen. Every implementation runs against a real payroll cycle; you compare the outputs before cutover. It ships when they match, not before.
How implementation works → - Miss the SLA and the fee pays you back. 99.5% sync success, measured monthly in your dashboard; below it, service credits of 10%, 25%, or 50% of that month's fee — and any failed sync re-runs the same business day.
Read the SLA → - Prepaying a year isn't an act of faith. Chronic SLA failure — the contract defines exactly how badly, for how long — gives you the right to terminate, with unused prepaid months refunded pro-rata.
- Leaving is designed to be boring. Your data stays in your systems, the mapping documentation goes with you, and offboarding is a clean handover.
What happens if we leave →
Pricing questions, answered the way procurement asks them¶
Is the published price what we'll pay?
It's the starting price for a typical two-system pair. The scoping call turns it into a fixed quote — what can move it is published above.
Is the setup fee one-time?
Yes — once per integration pair, at the starting prices in the table above.
What can add cost after go-live?
Structural changes, scoped and quoted in advance: a new data domain or a new entity. Complex multi-entity logic is Premium's custom-logic feature; the Compliance Pack is a listed add-on. Vendor connector updates and minor mapping changes never arrive as a change order — they're in the monthly fee.
Can we change tiers mid-term?
Upgrade any time — the custom-logic build is quoted, and the monthly moves to the Premium rate from then on. Downgrades take effect at term end.
What's the minimum commitment?
12 months per pair, from go-live. Annual payment changes the billing, not the term.
What happens at the end of the term?
It renews at the then-published price — your rate is locked for the paid term, and any price change reaches you in writing 60 days before it reaches an invoice. Leave at term end with notice; no exit fee. Details in the terms above.
What happens if you miss the SLA?
Service credits, in the contract, keyed to the same sync-success number you can read in your own dashboard.
Read the SLA →What happens to our data if we leave?
It never lived only with us — it stays in your systems, and the mapping documentation goes with you.
What happens if we leave →Taking this to finance? The one-screen version.
- Currency
- USD
- Priced per integration pair, not per employee
- Term
- 12-month minimum per pair, from go-live
- Billing
- monthly, or annually up front (20% off the monthly fee)
- Renewal
- then-published price, 60-day written notice, no exit fee
- Compliance Pack
- +$500/mo flat, billed monthly, PH-payroll pairs only
- Second pair
- 30% off setup, full monthly
- SLA
- 99.5% sync success, service credits 10/25/50% · SLA & Support
- Data processing
- PH Data Privacy Act–compliant, GDPR-ready DPA · Security
- Hosting
- AWS Singapore (ap-southeast-1) · Security
- On exit
- your data stays in your systems · FAQ
OmniSync HR · Pricing · as of 2026-07-11
You've seen the starting price. The call makes it exact for your stack.
A scoping call isn't a sales pitch — the prices on this page are the structure we quote against. We map your systems and your payroll calendar, and you get a fixed quote within a week, whether or not you buy.
Book a scoping call