Business
New
$13.00Pricing Strategy
Choose packages, value metrics, price points, margin guardrails, and a measurable test without turning assumptions into validated demand.
pricing strategypackaging
Q
quorin
Updated Jul 23, 2026
Reconcile attendance, leave, overtime, and corrections before payroll. Produces controlled employee-day records, an exception register, period totals, and a release decision.
Attendance data can balance and still be wrong. One export stops before page two. A fallback-hour shift loses sixty minutes. A manager edits a punch without approval. Duplicate events inflate time. Held-out overtime quietly slips back into payroll.
Attendance Payroll Handoff turns source attendance, roster, schedule, leave, correction, and approval evidence into a controlled payroll input. It freezes the period and population, records source coverage and time zones, preserves raw events, reconstructs employee-days, and applies only the supplied policy revision. Missing rules stay missing; the workflow does not invent rounding, overtime, leave, pay, tax, or labor-law decisions.
The output separates payroll-ready regular time, approved leave, approved overtime, and unresolved held time. Every correction and exception keeps its source references, owner, required evidence, and resolution state. Bidirectional controls reconcile roster to attendance, leave to approvals, corrections to authorizations, employee-days to period totals, and period totals to payroll rows.
Release states are deliberately strict. Held-out time prevents an unsupported payment, but it does not resolve the exception. A period remains blocked when time-affecting corrections, overtime, policy conflicts, source gaps, or mapping issues are open. Ready for approval means the final reviewer's signature is the only remaining gate.
The package includes the core workflow, an attendance reconciliation contract, exception codes, source and employee-day field definitions, payroll handoff fields, release gates, and Codex interface metadata. It can review exports from Lark, spreadsheets, time clocks, or HR systems. It does not authenticate to those systems, change punches, approve leave or overtime, interpret labor law, calculate statutory amounts without supplied rules, or write payroll without separate authority.
Version 1.0.0 was evaluated on 30 July 2026 through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. Across three blinded cases, the candidate scored 97.92, compared with 70.83 for the same agent without the skill and 77.92 for the exact free Lark attendance upstream. It passed every case and led the aggregate comparison by 27.08 and 20 points. The cases covered incomplete Lark pagination and a daylight-saving shift, corrections and capped overtime, and recovery from an ambiguous payroll import. This evaluation measures the supplied cases; it does not prove a real payroll run was changed or approved.
The reviewed package SHA-256 is 6f9757e57789b5945a8651e5f516023462be0f8a94e8281dc19f64053ed8612c. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Roster: 120 employees. Lark returned page 1 of 2 for 61 employees. E044 worked 00:30 EDT to 08:30 EST with a 30-minute break. Policy pays 480 regular minutes and overtime above that. Can this period go to payroll?
Output
A not-controlled source verdict, nine-hour elapsed-time trace, 480 regular and 30 overtime minutes for E044 as diagnostic evidence, population and pagination exceptions, and a blocked period-level handoff.
Input
Three employees. One correction lacks approval, one employee has approved full-day leave, and one has 80 overtime minutes with approval for 60. A conflicting manager memo has no owner or effective date.
Provide the payroll entity and period, stable employee roster, attendance export or records, schedules, holidays, approved leave, time zones, grace and rounding rules, break and overtime policy, correction and approval evidence, payroll input fields, materiality rule, and authority boundary. Ask for a monthly close review, employee-day reconstruction, exception register, period bridge, payroll handoff, release decision, or ambiguous-import recovery plan.
Entity, pay group, period, cut-off, intended payroll run, stable employee population, expected output fields, and materiality or release rule.
Immutable or identifiable attendance exports and source metadata, including filters, row and page coverage, event IDs, timestamps, time zones, extraction time, and source owner.
Approved schedules, holidays, workday definition, breaks, grace, rounding, overtime, leave, correction, approval, privacy, and retention rules with revisions and effective dates.
Separate authority for inspection, calculation, correction approval, export, payroll write, notification, and final release, plus the target payroll field contract.
SKILL.md; attendance reconciliation contract with source, employee-day, exception, payroll handoff, and release fields; Codex interface metadata
No reviews yet.
Output
Employee-day calculations, a policy-conflict register, separate correction and overtime exceptions, 20 overtime minutes held out, bidirectional controls, period totals, and a blocked release until the resolution package is complete.
Input
An 80-row import timed out. Seventy-seven rows match, one has wrong overtime, one appears twice, and one is absent from page 1 of 2. Support proposes replaying all rows and deleting a duplicate.
Output
Per-target effect classifications, no full replay, a page-two evidence request, target-specific repair rows with new operation IDs and exact payloads, independent read-back controls, and a blocked handoff.
Creator
Kkorven8