Source status and current version
Know where each time input came from and which version is current.
Completev3 current
For Finance & Payroll
Bring governedworkforce timeinto the payroll handoff.
Give payroll and finance teams a clearer starting point: workforce-time records with source context, approved decisions, exceptions and linked evidence—ready for authorized downstream use.
Workforce-time governance, not payroll calculation or employee surveillance.
The handoff problem
Time reaches
payroll. Context
often does not.
Time inputs can arrive through schedules, spreadsheets, manual adjustments and separate approval messages. When source quality, policy decisions and revisions are hard to trace, finance teams must ask the same questions again.
Missing source
Start time — from where?
Approval in email
“Looks fine, approve.”
Manual adjustment
Spreadsheet cell edited
Revised after export
Which version did payroll get?
What TEMVERIS contributes
Evidence-backed time.
Clearer decisions.
Controlled handoff.
TEMVERIS brings approved time and attendance context together with the policy and review history that explains it.
Decision and evidence
See the authorized decision and the evidence that explains it.
Approved 09:31Attendance v3
Eligible vs sent vs acknowledged
Keep handoff milestones separate so "sent" never reads as "paid".
EligibleAck unknown
Product boundary.Your payroll application remains responsible for pay calculation, deductions, taxes and payment.
One record, responsible access
A shared record does
not mean shared
access to everything.
Operations, HR, Finance & Payroll, Legal & Compliance, and IT & Security depend on the same governed record. Each function sees only the details permitted for its role and purpose.
GOVERNED RECORD · SYNTHETIC
TV-10482
Decision · Govern
Approved
Policy
Attendance v3
“Approved” refers to its Govern decision — not to payment.
Finance & Payroll view / TV-10482
DecisionApproved (Govern)
PolicyAttendance v3
EligibilityEligible for handoff
Deliveryv3 sent · acknowledged
Reviewer notesNot in this view
HR case detailsNot in this view
Role-scoped access. Only permitted information is shown in this view.
Product preview · synthetic
Know which time
records are ready for a
downstream handoff.
Review period scope, current approval decision, source completeness and any outstanding exception before the authorized transmission step.
Finance & Payroll / Record readiness
Pay period: Sep 21–Oct 4, 2026Scope: Site North · authorized
As of Sep 25, 2026, 07:00 PTEligible
2
Needs review
1
Awaiting decision
1
Ack unknown
1
| Record | Period | Decision | Source | Exception | Eligibility | Delivery | Action |
|---|---|---|---|---|---|---|---|
| TV-10482 | Sep 23 · Morning | Approved | Complete | None | Eligible | Acknowledged | Open |
| TV-10484 | Sep 23 · Day | Approved | Partial | Source gap | Needs review | Not sent | Open |
| TV-10485 | Sep 24 · Evening | Approved | Complete | None | Eligible | Sent · ack unknown | Open |
| TV-10487 | Sep 24 · Morning | Awaiting decision | Complete | Pending review | Not eligible yet | Not sent | Open |
Five stages, five authorities
From work event to
evidence-backed
downstream input.
Capture receives approved work inputs. Plan provides expected context. Govern records authorized decisions. Evidence retains history. Integrate controls delivery; the payroll engine processes pay.
Authority: Capture
Captured
Approved work inputs are received with their source.
For finance & payroll
Each stage has its own owner and state; none implies payment.
Pre-handoff confidence
A missing input is not
a zero-hour record.
Before approved time is used downstream, confirm that its source, period, policy and decision context meet the configured handoff requirements. Missing, late or disputed inputs need review, not guesswork.
Complete
Source received
As of 08:42 PT
Partial
End time missing
As of 16:05 PT
Missing
No input yet
Not zero hours
Late
Arrived after cutoff
Received Oct 5
Disputed
Correction open
Owner: Operations
Eligibility check / TV-10484 · proposed rule
SourcePartial — end time missing
PeriodSep 21–Oct 4 · in range
PolicyAttendance v3 · effective
DecisionApproved
ResultNeeds review — not eligible yet
The eligibility business rule is a proposal and must be confirmed with your payroll owner. No completeness “grades”.
Missing ≠ 0 h
Governed approvals
See who authorized
the record—and
under which policy.
A payroll-ready input retains the actor or authorized role, effective policy version, time of decision and any superseding review. Finance sees no “Approve” button without permission.
AUTHORITY
Approved by Operations Manager
Acting roleApprover · Site North
Decided atSep 23, 2026, 09:31 PT
ReasonLate handover confirmed
Superseded byDC-8820 (after correction)
POLICY VERSION
Attendance review · v3
EffectiveSep 1, 2026 →
RuleStart-time difference review
EvaluationReview required
Source of authorityConfigured approval path
Controlled exceptions
Resolve the gap without
rewriting the source.
Finance sees what is missing, who owns the next action and whether the downstream handoff is blocked. Corrective action routes to the owning team — no worker fault or wage withholding implied.
Exceptions affecting handoff / Sep 21–Oct 4
SYNTHETIC DEMO DATARevisions that stay explainable
A correction should not erase
what was previously sent.
When a time record is revised after approval or transfer, the new version needs its own decision, trace and downstream follow-up. “Payroll cutoff” is a customer-policy concept, not a TEMVERIS default.
Version 2 · sent Sep 25 · superseded
08:00–16:00
Historical — not current
Correction
after export
Version 3 · current
08:00–16:30
New decision required
| Field | Version 2 | Version 3 |
|---|---|---|
| Recorded interval | 08:00–16:00 | 08:00–16:30 |
| Correction reason class | — | Handover overrun confirmed |
| Decision | DC-8812 | DC-8820 (re-approved) |
| Downstream | Export EX-02 · acknowledged | Corrective transmission EX-05 · queued |
Recorded interval
Version 2
08:00–16:00
Version 3
08:00–16:30
Correction reason class
Version 2
—
Version 3
Handover overrun confirmed
Decision
Version 2
DC-8812
Version 3
DC-8820 (re-approved)
Downstream
Version 2
Export EX-02 · acknowledged
Version 3
Corrective transmission EX-05 · queued
The finance principle
Approved. Eligible. Sent.
Acknowledged. Different answers.
A superseded copy must not appear current simply because it was once exported.
Photo: Kimon Maritz / Unsplash
Trace what matters
The record behind the number is part of the answer.
Source provenance, configured policy, decision authority and revision history help payroll reviewers explain where an authorized time input came from and why it is in its current state.
Evidence preview / TV-10482
08:12Capture
Source provenance
SE-55120 · approved channel
09:17Govern
Policy evaluated
Attendance v3 · review required
09:31Govern
Decision authority
Operations Manager · DC-8812
Sep 25Evidence
Revision
v2 → v3 · reason recorded
Sep 25Govern
Re-approved
DC-8820
Where the input came from
Which policy version applied
Who decided, and when
What changed after export
Evidence owns storage, retention and access. Synthetic event IDs; no certification badges.
The delivery truth
Approved. Eligible.
Sent. Acknowledged.
Different answers.
A governed decision can make a record eligible for handoff. Integrate records whether it was transmitted, and the receiving application determines whether it processed it.
Approved→
Eligible→
Sent→
Ack unknown
01 · Govern
Approved
Sep 23, 09:31 PT
02 · Govern
Eligible
After checks
03 · Integrate
Sent
Sep 25, 11:02 PT
04 · Recipient
Acknowledged
Unknown
05 · Payroll application
Processed
Outside TEMVERIS
What “Approved” means
A governed decision was recorded by an authorized person.
What it does not mean
That the record was sent or paid.
Downstream data fit
Use the fields your
downstream workflow
is authorized to receive.
Field scope, identifier mapping, time basis, versioning and destination expectations are set in an integration discussion. Pay codes and calculations remain governed by the receiving application.
Example field mapping / proposal
SYNTHETIC DEMO DATA| TEMVERIS field | Destination field | Sensitivity | Nullable | Type | |
|---|---|---|---|---|---|
record_id | → | external_reference | Low | No | string |
decision_version | → | source_approval_ref | Low | No | string |
interval_start_utc | → | work_start | Personal | No | ISO 8601 |
interval_end_utc | → | work_end | Personal | Yes (partial) | ISO 8601 |
record_version | → | revision | Low | No | integer |
Right tool, right authority
TEMVERIS governs the input.
Your payroll and finance
systems own the result.
Payroll providers calculate pay, deductions and statutory amounts; finance systems post their own accounting entries and reconcile results.
TEMVERIS governs
Approved time
Decision
Evidence
Eligibility
Transport state
Your systems own
Pay calculation
Deductions
Tax
Settlement
GL posting
Decision-ready visibility
Understand the quality
of the handoff, not a
fabricated ROI figure.
Every summary discloses its scope, freshness and inclusion rules. No gross payroll cost, overtime savings or statutory figures.
Eligible records
412
of 436 identified · Site North
Approved + checks passed · as of Oct 5, 06:00
PT
Needs review
17
reasons: source 9 · timing 6 · revision 2
Open review items blocking eligibility
Acknowledged by recipient
398
of 412 sent · 14 unknown
Recipient-reported acknowledgment only
Small unit · East
—
Suppressed
Cohort below privacy threshold
Representative synthetic counts. Time zone America/Los_Angeles.
Enterprise integrations
Connect governed records to
the systems you already use.
Integration scope is confirmed during technical evaluation. Integrate owns authentication, mapping and transport. No third-party logos.
API access
Read governed records and their state.
Webhooks
State notifications when a record changes.
Structured exports
Approved-data exports with version references.
Approved connectors
Available for your contracted deployment.
From evaluation to fit
Start with the
requirements that
determine a safe handoff.
No employee names, wage files or personal payroll data are needed to start.
Work-data sources
Where approved time and attendance come from
Decision owners
Who approves, returns or escalates records
Pay periods
Boundaries, cutoffs and time zones
Expected fields
What the destination is authorized to receive
Transfer formats
API, webhook, export or connector
Security roles
Who in finance can view what
Required acknowledgement
What receipt the destination provides
Destination support
Which systems are contracted
Bring this checklist to your evaluation.
Request an implementation review
8 questions· no personal data