RemoFirst Deadlines and Sync Cadence

Overview

Build a timing plan from the documented business cutoffs and supported connector behavior. No reviewed public source publishes a general RemoFirst API quota, so this skill must not manufacture request-per-minute limits, retry headers, endpoints, or backoff rules.

Prerequisites

• Workflow, population, period, country, owners, and timezone.
• The live RemoFirst calendar or connector status available to an authorized user.
• A support owner for ambiguities or missed deadlines.

Current Contract

• Monthly payroll has documented revision, review, approval, and funding stages; live dates and worker-specific schedules remain authoritative.
• Contractor timesheet approval locks a submitted timesheet; rejection returns it for correction.
• Workday sync is manually initiated and imports only supported approved records.
• ADP setup uses a short-lived account ID during connector authorization.
• No public first-party general API quota or SDK retry contract was found.

Instructions

1. Classify the timing domain: payroll, contractor timesheet, invoice funding, Workday sync, ADP activation, or a provider-issued private integration.
2. Record every time in one canonical timezone plus the operator's local time. Include source URL, retrieval date, owner, and whether it is a guide or live date.
3. For payroll, confirm revision, approval, funding, and pay-date milestones from the live period. Do not silently reuse dates from a prior month.
4. For timesheets, leave review time before approval because approval locks the record. Reject incorrect entries early enough for contractor correction.
5. For Workday, schedule a human-triggered sync, review imported records, and reconcile unsupported or edited data manually.
6. For ADP, generate the account ID only when the connector owner is ready to use it; if it expires, repeat the documented setup instead of reusing it.
7. If a private interface is involved, use only its customer-specific written quota and retry contract. Otherwise escalate rather than guessing.

Tool Discipline

Use Read, Glob, and Grep on approved schedules and redacted reconciliation artifacts. Use Write/Edit only for timing plans and evidence summaries. Do not run sync, approve time/payroll, generate credentials, or fund invoices.

Approval Boundaries

Payroll approval, timesheet approval/rejection, connector sync, account-ID generation, invoice payment, and any retry against a private interface require the designated human operator or explicit authority.

Output

Return workflow, timezone-normalized milestones, source and retrieval date, owners, safety margin, lock or expiry behavior, reconciliation step, blockers, and escalation path. State explicitly when no public API quota applies.

Error Handling

• Missing live date: block the plan and ask the payroll or provider owner.
• Missed cutoff: document impact and obtain a revised provider-confirmed date.
• Sync mismatch: stop repeat syncs until mapping and record state are reconciled.
• Unknown quota: do not probe; request the private contract from RemoFirst.

Examples

• A payroll plan labels published day ranges as guidance and records live dates.
• An expired ADP account ID is regenerated by its authorized connector owner.
• "Use exponential backoff" is rejected without a private API contract.

Validation

• Every milestone has timezone, owner, evidence, and current-period confirmation.
• Locking, expiration, and manual-sync behavior are represented accurately.
• No invented request limit, endpoint, retry code, or API credential appears.

Resources

See references/official-docs.md for the reviewed payroll, timesheet, Workday, ADP, invoice, and support sources.