Your org changed.Your payroll
probably didn't.
Drop in your HR file and your payroll file. Get back a list of every person the two systems disagree about.
Terminations still on payroll. Transfers running in two countries. Promotions that never reached commissions. Ninety seconds, in your browser.
See your drift first. Pay only if it’s worth it.
Findings, severity and dollars are free$10 opens the detailNo subscriptionYour files never leave the tab
Built for the payroll and sales-comp analysts who catch this by hand today. No session recording on any page that touches your data.
Employee transferred London to New York. UK payroll still shows active. Duplicate pay is grouped into a finding the analyst can review and export.
Reported to us by a payroll lead running ADP, UKG and Workday. Exactly the kind of miss a cross-system check exists to catch.
Beta member · reported, not caught by us
What the same person spends checking those systems against each other. The work this replaces is already on somebody’s calendar.
Beta member · Payroll lead
The reconciliation tool our founder built inside a Fortune 500 comp team, years before OrgDrift existed.
Ken Lannon · Founder
Companies withheld. Roles, stacks and figures are as reported by the people who ran the work. We label what we found ourselves and what we did not.
Walk through a full reportThe formulas all came back clean.
One employee was on two payrolls.
Same three files. Left: an analyst tabbing between HR_HRIS · ADP_UK · ADP_US one column at a time — with no way to see what spans all three simultaneously. Right: OrgDrift reading every cross-system edge at once.
| EMP ID | LOCATION | STATUS | PAY |
|---|---|---|---|
| 1440 | US | ACTIVE | $9,100 |
| 1441 | UK | TERM | #N/A |
| 1442 | US | ACTIVE | $11,000 |
| 1407 | UK | TERM | #N/A |
| 1389 | US | LOA | $9,800 |
| 1443 | UK | ACTIVE | £7,200 |
| 1463 | UK | ACTIVE | £8,100 |
| 1444 | UK | ACTIVE | £6,800 |
VLOOKUPs can only check what you point them at. Cross-system drift — like one employee running on two payrolls — is invisible until OrgDrift reads all three files at once.
Scan my dataSeen enough? The scan takes ninety seconds.
Your own files, in your own browser. Findings, severity and dollars are free. $10 opens the detail.
“I was the one signing the control.
I knew what was missing.”
I spent two decades inside the comp and payroll systems every enterprise runs on, and I watched the same failure over and over. Something changes in one system. It syncs to most of the others. A few never catch up. By the time anyone notices, the wrong dollar has been paid, in the wrong country, against a status that no longer exists.
I served as reviewer on eleven commission controls in a Fortune 500 risk and control matrix. The evidence we attached was a PDF of a spreadsheet of a query. No auditor was ever really comfortable with that, including me.
So I built my own reconciliation tool inside that comp team, and it cut one recurring check by 98%. That proved the checking could be automated. It could not prove the check ran, because I built it, I ran it, and an auditor discounts anything you attest to yourself.
OrgDrift is the independent version I always wanted to cite. Now I'm building it.
Your team may call it a failed sync, stale record, reconciliation break, or source-of-truth issue.
We call it drift.
If you’ve ever closed a termination only to watch the benefits deduction keep firing, written a clawback memo, signed a restated quarter, or had your name on a control that “passed” before the auditor pulled samples — you know the pattern.
A relocation in March.
$132,000 in duplicate payroll by September.
An employee relocates from London to New York. HR updates the record the same day: new office, new manager, new cost center. US payroll activates her correctly. UK payroll keeps paying her. A transfer isn't a termination, so no off-boarding signal ever fires. Every local control passes its local check. Six months later: full wages paid in two countries, employer taxes in both, and a clawback conversation nobody wanted to have.A composite of the global-mobility pattern, walked step by step. Names and dates are illustrative; the failure path and the controls it slips past are not.
A payroll manager walked us through exactly how drift gets past her.
Caroline's team reconciles employee records every payroll cycle, across HR, ADP, and benefits. That is over 20 manual touchpoints a month. Pull the headcount report. Compare it to ADP, field by field. Flag what doesn't match. By hand, every time.
It trickles down to somebody getting termed off their benefits by mistake.
In a product validation session, Caroline mapped what one wrong record does on its way downstream. This isn't hypothetical. It is the failure she works to prevent every payroll run.
Everything lives in NetSuite — you have to carry it through from your HRIS to payroll, to commissions, to expenses, to your Fidelity feeds. When something's off at the source, it propagates all the way down until someone loses their benefits.
I never would have thought to look for something like this — but once you see it, you realize how many places it applies.It solves problems I didn't even know I had a way to solve.
Every control is watching its own domain.
No one is watching the seams.
HR checks HR. Payroll checks payroll. Commissions checks commissions. Finance checks finance. Every domain passes its own check. The drift hides in the spaces between them, where no single reviewer has the complete picture.
Five quiet failure modes. Four are honest error. The fifth is the one no one wants to sign their name to.
Drift isn't one thing. It shows up everywhere two systems are supposed to agree. Below are the patterns we keep running into. Each one costs real money. Each one has an audit consequence. And each one walks straight past the controls built to catch it.
International double-pay
Someone transfers between countries. HR updates cleanly. The new country’s payroll starts paying. The old country’s payroll never stops, because a transfer is not a termination, so no off-boarding trigger ever fires.
- · Country-siloed payroll reviews
- · Bank disbursement approvals
- · Payroll-to-GL reconciliation (totals balance)
Promotion pay-rate drift
The promotion takes effect on the 15th. Payroll cuts on the 10th in one country and the 20th in another. Each one reads that date boundary its own way. Some pay the raise twice. Others skip a period entirely.
- · Monthly payroll review (totals balance)
- · Effective-date policy documentation
- · HRIS change-approval workflow
Terminated rep, CRM opportunities still crediting
A rep leaves. Their CRM login is disabled the same day. But 23 open deals stay assigned to them. Those deals close, flow into the comp engine, and accrue commission to someone who no longer works here. The monthly recon does catch it, usually at quarter end, after the accruals have already posted.
- · CRM user deactivation (opps don’t auto-reassign)
- · Payroll roster review (doesn’t see CRM)
- · First-pass commission calculation
+−Two more drift patterns we've catalogedHide additional patterns
Cost-center reorg → GL drift per employee
A reorg moves 80 people from one cost center to another. HR updates. Payroll totals still tie to the general ledger, so the close looks clean. But 7 of those people land in the wrong cost center, and their wages post to the wrong department. That department’s numbers are wrong. Nobody notices until someone asks why headcount cost looks off.
- · Corporate controller reconciliation (totals balance)
- · Payroll review (roster is correct)
- · Departmental P&L (uses payroll as source)
Ghost employees & terminated-but-still-paid
Someone is terminated in HR. Off-boarding completes: the manager signs, the badge is revoked, the login is killed. Payroll was the last to know, or never knew. Direct deposit fires next cycle. Benefits deductions keep posting. The retirement match keeps accruing. It could be a process gap. It could be someone keeping a friend on the books. No local control can tell you which, and the fraud-risk walkthrough your auditor runs has to rule out both.
- · HRIS off-boarding workflow (completes cleanly)
- · Payroll roster review (employee “looks active”)
- · Bank disbursement approval (totals reconcile)
Schema Drift Detection
An export template changes quietly. A column gets renamed, dropped, or added. The automation keeps running against the old shape, so the check still comes back clean while the file underneath stopped saying what it used to say.
- · Scheduled exports
- · Column-based automations
- · Downstream formulas that still execute
Exposure figures are modeled, not measured: per-event bands derived from published correction-cost and wage research, sized against the drift types we see. The full derivation and its sources are on the pricing page.
Three checks. Every critical change. Every system.
See every critical change, across every system you run.
One read-only layer watches HR, CRM, commissions, payroll, and benefits at once. The moment a pay rate, role, location, plan, status, or enrollment changes in one place, you see whether it reached everywhere else it should have. You set the rules and the time window. The same inputs always produce the same finding, and every run traces back to source.
Confirm it arrived. Or catch the drift before payroll runs.
When the far system matches what HR intended, the check logs clean. When it does not, you see the exact field that differs, how many people and dollars it touches, and what the whole group adds up to. All before payroll runs. One number, the integrity score, tells you what share of everything checked still agrees across systems. Sorted by severity and sent to you, not buried in another inbox.
Produce audit-ready evidence. Signed, sealed, linked.
Every check you run leaves a record, whether it passed or failed. We call it a Control Execution Record. Each one is stamped with the time, linked back to your source data, and locked to the record before it, so no one can quietly edit history. Your auditor can accept it as independent evidence and map it straight to the SOX controls you already have.
Continuous Controls Verification. The layer that closes the loop.
DevOps gave software a layer that never stops checking. RevOps gave sales one. Continuous Controls Verification does it for your controls. It watches every system, checks every change, and leaves audit-grade evidence behind as a byproduct. OrgDrift is the first product built for it.
Already running Continuous Controls Monitoring? This is the seam it cannot see. Monitoring watches inside one system. Verification compares two, from outside, and proves they agreed.
Your existing stack has pieces of this. Integration platforms move the data. Reconciliation tools compare the numbers. GRC files the paperwork. Your auditors sample it once a year. None of them close the loop.
Not another alert.
The workpaper you actually wanted.
A Control Execution Record is what your SOX manager, your internal auditor, and your external auditor all actually want: a signed record of whether the control ran, and what it found.
- Locked to the record before it. Each record is sealed to the one before it, so nobody can quietly edit history after the fact.
- Your auditor can sample it. They pull any record, re-verify it against your own source data, and close testing faster.
- It fits the matrix you already have. It attaches to your existing risk and control matrix, the sheet your auditor tests against. No re-documentation, no second framework to keep current.
An employee shall be active in exactly one country payroll system per pay period. When the HRIS work-location attribute changes, the prior country's payroll system shall deactivate the employee on or before the next pay cycle.
Meet VERA. The rules-based engine finds the drift. VERA narrates it. You sign.
VERA doesn't find the drift. The rules engine does that. VERA is OrgDrift's Verify Engine and Remediation Assistant, and its job starts the moment a finding lands. It names the change that caused it. It sizes the dollars. Then it drafts what happens next: the Slack message, the ServiceNow ticket, the Control Execution Record, each one with the evidence already attached. Your team reads it and signs.
- Root cause, one click away. The upstream change that triggered each finding — surfaced for you across every system in scope.
- Exposure sized before you act. Dollars at risk, records affected, cohort breakdown — on your desk before the first message goes out.
- Remediation drafts waiting for your sign-off. Slack notifications, ServiceNow tickets, owner routing — evidence pre-attached. You approve, VERA sends.
- Your Control Execution Record, written. Ready for your signature. Attest in minutes, not hours.
Different roles. Same source of truth about the truth.
RevOps & Sales Comp Managers
You're the last gate before commission accruals lock, and the first person called when a clawback hits a rep. Run the check across HR, CRM, and the comp engine continuously, so plan assignments, deal ownership, and quota mismatches surface before they turn into rep disputes or month-end rework. Sign a workpaper your auditor can re-verify from source.
People Ops & HR Analytics
Every HR change ripples out to payroll, benefits, commissions, and access. Catch the ones that never arrived. The termination that didn't off-board. The transfer that never updated the tax state. The status change the benefits feed missed. Catch them before someone loses their coverage.
AR & Finance Ops
Your CRM and your ERP are both right, and they still disagree. Closed-Won deals with no invoice. Invoices with no matching deal. Amounts that moved after the fact. Run the comparison yourself, without touching finance's systems, before the auditor does.
SOX & Internal Audit Directors
When the practitioner hands them a signed Control Execution Record, already mapped to the risk and control matrix they test against, they sample it, re-verify it from source, and close faster. The list of drift auditors need for fraud-risk testing is the same list the practitioner already produced. Finally, a workpaper attachment that isn't a PDF of a spreadsheet of a query.
Studio Unlimited, free for 3 months. $1,500 value. Given to 40 beta operators. Not sold.
Common questions.
What is OrgDrift?+
OrgDrift checks whether your systems agree about your people.
You upload one export from your HR system and one from payroll, commissions, or benefits. OrgDrift reads them side by side and lists every person the two systems describe differently. A termination payroll never got. A raise commissions never saw. A transfer that left someone on two payrolls. It runs in your browser, and your files never leave your computer.
When you need to prove the check ran, each one seals into a Control Execution Record. It is timestamped, tamper-evident, and your auditor can re-verify it from your own source data.
What is cross-system drift?+
Drift is when one change lands in one system and not in the others. Someone is terminated, promoted, moved to a new territory, or put on a new plan. HR records it correctly. Payroll, commissions, or benefits never catch up.
The integration usually looks fine. The pipe ran. The far end rejected the change, remapped it, or quietly ignored it. And because every reconciliation looks inside one system, nobody sees it until it shows up as a payroll error, a commission dispute, or an audit finding.
Is this the same as Continuous Controls Monitoring (CCM)?+
Close, and the difference matters. Continuous Controls Monitoring grew up around the ERP. Tools like Pathlock and SafePaaS watch transactions and access inside a financial system and flag what breaks a rule. That is real work, and we do not replace it.
Verification asks a different question. Do two systems still agree about the same person and the same dollar? A tool sitting inside your ERP cannot answer that, because it only sees one side. OrgDrift reads both, from outside, and seals what it found as evidence.
If you already run CCM, OrgDrift covers the seam it cannot see. HR to payroll. CRM to commissions. One country payroll to another.
What is Continuous Controls Verification (CCV)?+
Most teams check each system on its own. HR checks HR. Payroll checks payroll. Nobody checks whether the two agree.
Continuous Controls Verification is the habit of running that cross-system check all the time, not once a quarter, and keeping proof that you ran it. It is what DevOps did for software and RevOps did for sales, applied to the checks your auditor asks about. OrgDrift is the first product built for it.
What does the free scan actually show me?+
Findings, severity, and dollar exposure, on your own files, before you pay anything. You see how many people your systems disagree about, how bad each mismatch is, and what it adds up to.
The $10 opens the row-level detail and the exports. If your scan comes back clean, there is nothing to buy and you have paid nothing. See your drift first. Pay only if it is worth it.
What does OrgDrift do with our data?+
Today the scan runs entirely inside your browser tab. There is no upload endpoint to send your file to. Field values are hashed for comparison, and raw employee data never reaches us. We keep the verification evidence and its signatures, nothing else.
Session replay and web analytics are blocked on every route that can render your data, and you can check that by viewing source. Private Mode goes one step further and turns off the last outbound call, so you can disconnect your network and watch a scan finish anyway. Live read-only integrations are on the roadmap.
Who uses OrgDrift?+
Four kinds of people, for four reasons. Payroll and controllership teams check that terminations and rate changes reached payroll. RevOps and sales-comp managers catch plan, territory, and ownership mismatches before a clawback hits a rep. SOX and internal audit directors need evidence they did not produce themselves. CFOs and controllers would rather know now than at quarter close.
We already reconcile manually every month and quarter. Why do we need OrgDrift?+
Manual reconciliation is good work. It is just not complete. Your checks run on a cadence, inside one domain, and often inside one country. Drift that crosses those lines slips past all of them, because no reviewer holds every system view at once.
OrgDrift runs continuously, across domains and across countries. It does not replace your team's judgment. It hands them the one view they currently assemble by hand.
And even when reconciliation works, it produces a findings list, not evidence. At audit time your team still pulls 45 samples and builds workpapers. OrgDrift turns the same work into evidence as a byproduct, so your auditor pulls the samples themselves.
Doesn't our existing iPaaS (Workato, MuleSoft, Boomi) already handle this?+
An integration platform moves data. OrgDrift verifies it arrived correctly. The failure mode is not that the pipe broke. It is that the pipe ran fine, the far system rejected or remapped the change, and nobody was watching for that. OrgDrift is the independent observer above the pipes.
We already have Optro, Workiva, or Diligent. Isn’t that this?+
GRC platforms manage the framework around controls: the documentation, the workflow, the sign-off. They do not read from your operational systems, and they do not produce independent proof that two systems agreed. OrgDrift sits underneath and feeds Control Execution Records into your GRC platform. They are complementary, not competitive.
How is this different from SafeBooks or other reconciliation AI tools?+
Independence. A tool that lives inside your finance stack, or one whose AI decides what looks wrong, is checking its own work, and an auditor will treat its output that way. OrgDrift is a referee: read-only, outside every system it checks, running fixed rules. The same inputs always produce the same finding, and any auditor can re-verify a result from source. The evidence is the product, not a dashboard summary of it.
Couldn't our IT team just build this?+
They could build the checks. Many teams have. What IT cannot build is independence. A control built and run by the same organization that operates the systems is self-attestation, and auditors discount it. OrgDrift's value is not the comparison logic. It is the independent, tamper-evident Control Execution Record proving the check ran, on what data, with what result. Your auditor can sample it without having to trust your scripts.
Is OrgDrift an AI product? What does VERA actually do?+
Pasting an HR export into a chat assistant gives you an opinion that changes between runs, cannot be signed, and will not survive auditor review. Detection has to be repeatable to count as evidence.
OrgDrift's detection engine runs fixed rules. When a change in one system should have reached another and did not, we surface it. No probability, no guessing. That part is auditable.
VERA is the AI layer on top. It speeds up the work around a finding: naming the root cause, sizing the exposure, drafting the remediation messages and tickets, drafting the Control Execution Record. VERA never publishes evidence on its own. Every record needs a human signature first, and VERA's drafts and inputs are logged too, so your auditor can see exactly what was AI-assisted and what was human-reviewed. This follows the NIST AI Risk Management Framework and ISO/IEC 42001 principles.
Why does OrgDrift matter more as we adopt AI and automation?+
AI and automation speed up the work inside your systems. They also speed up the rate at which those systems drift apart. Schemas change, vendors rename fields, models retrain on slightly different data, and an automation that ran cleanly last quarter starts producing the wrong output. Nobody notices until a payroll run, a commission cycle, or an audit surfaces it.
OrgDrift sits above the automation and checks its work against the systems of record. Continuously, on fixed rules, with signed evidence. The automation keeps its speed. The outcomes stay correct.
Will auditors accept a Control Execution Record as evidence?+
Control Execution Records are built to be cited as independent evidence attached to management's assertion in ICFR testing, the annual review of your financial-reporting controls. A Big 4 workpaper template, so records drop into existing audit procedures without re-documentation, is on the roadmap. The goal is simple: let external auditors pull samples directly instead of waiting on workpapers, which turns weeks into hours.
How long from first visit to first real drift finding?+
The scan on the homepage runs on your own files in about ninety seconds. There is no signup and no integration. A full pass across one pair of systems is under a day end to end. Your first Control Execution Record lands inside the first week.
Who is OrgDrift not for?+
If you run one system of record, with no cross-system payroll, comp, benefits, or CRM flows, you do not need a referee yet. That single system's own controls are enough. OrgDrift earns its keep the moment two systems are supposed to agree about the same person or the same dollar and no single reviewer sees both.
We’re mid-M&A integration. Is it too early for us?+
Mid-integration is exactly when drift is most likely and most expensive. OrgDrift is useful the moment two systems are supposed to agree with each other, which is usually day one.
Field notes on cross-system drift.
You Built AI Automation for SOX. Who's Testing the AI?
AI is reshaping SOX compliance and that's a good thing. But every major framework published in the last year (COSO, PCAOB, SEC) puts the same requirement at the center: independent oversight of what the AI does. Here's why building it yourself doesn't close that gap.
Terminated Employees Keep Getting Paid. It's Not Fraud. It's Drift.
When a terminated employee keeps getting paid, everyone looks for fraud. That's usually the wrong call. Here's what's actually happening inside your systems, and why it keeps costing companies money even when every team does their job correctly.
Detect. Verify. Prevent. Why Order Matters in Revenue System Integrity
Detect → Verify → Prevent is not a tagline. It's the only order in which revenue system integrity actually works. Skip detection and your verification is guesswork. Skip verification and your prevention is theater. This is the operating logic behind the Organizational Drift Index.
Is your pay data clean?
Find out now.
Ninety seconds. Your browser only. No integrations, no sales call, no account required.
Runs on your own files, inside your browser. No integrations, no IT ticket, nothing uploaded.
Self-serve stays open to everyone · no sales call · Ken replies within one business day