Enterprise use case · ADP Workforce Now + Workday + OpenAI + ServiceNow
Timesheet anomaly review before payroll
Inconsistent time entries reach payroll without a clear distinction between a genuine error, an approved exception and an unfamiliar work pattern. Payroll reviewers see unusual time entries with source context and a reason to investigate before making corrections.
Systems involved
What each system contributes
13 actions
- Time3
- Work Assignment7
66 actions
- Time Tracking10
- Employee12
- Payroll15
25 actions
- Chat Completions8
The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
Architecture
One governed run
How it starts: A time period is released for review before the organization's payroll cutoff.
Step by step
How the process runs
- 01
Assemble the time context
Read the permitted ADP Workforce Now time entries and Workday worker, assignment and period context.
- 02
Check explicit policies
Rules identify missing values, overlaps and breaches of the configured time-entry requirements.
- 03
Assess unusual patterns
The selected model compares the approved history and current entries, explaining atypical patterns without inferring intent or misconduct.
- 04
Open a review item
Create a restricted ServiceNow case with the affected entries, policy flags and model explanation for the appropriate payroll owner.
- 05
Apply approved corrections
After review, a separate ADP or Workday action updates only the authorized values through the available interface.
Control
Human decision and exception path
Human decision
The named payroll owner checks the source record and relevant employee or manager explanation before approving a correction. No flag automatically reduces pay, rejects hours or becomes a disciplinary finding.
Exception path
- Missing history or a changed assignment limits the comparison and is shown to the reviewer.
- Approved overtime, shift changes and other legitimate exceptions can dismiss a flag without altering the entry.
- Unresolved entries remain in the agreed payroll exception process rather than being silently changed or omitted.
Evidence
What gets audited
- Time-entry references, review period and permitted context.
- Policy-rule version and model comparison basis.
- Flag explanation, reviewer disposition and any correction approval.
- ADP or Workday update request and response where applicable.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- ADP Workforce Now-Workday integration
Integration pattern · Approved Workday employment changes reach the ADP payroll process with reliable employee matching.
- ADP Workforce Now connector
13 pre-built actions
- Workday connector
66 pre-built actions
- OpenAI connector
25 pre-built actions
- ServiceNow connector
55 pre-built actions
- Human-in-the-loop
Where approval belongs in a running workflow.
- Order to cash across CRM, ERP and billing
Another enterprise use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- A time period is released for review before the organization's payroll cutoff.
- What if a step is not covered by a pre-built action?
- The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
- Does an anomaly mean someone entered time incorrectly?
- No; a flag is an investigation prompt, and a legitimate assignment or scheduling change may explain it.
- Does the workflow stop an employee's pay automatically?
- No; payroll treatment remains with the authorized payroll process, including its handling of unresolved exceptions.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.