RemoFirst Payment and Workflow Error Triage

Overview

Classify a RemoFirst operational failure before suggesting a correction while keeping payment state, bank settlement, invoice reconciliation, timesheet approval, and account visibility separate. A dashboard status such as Paid is evidence of platform state, not proof that funds reached the receiving account.

Prerequisites

• A redacted issue summary, expected outcome, event time, and affected period.
• The authorized payment or workflow owner and escalation contact.
• Access to approved evidence without copying bank or identity data.

Current Contract

• Delayed funds may require Proof of Payment, ISO/MX evidence, or an MT103 trace coordinated through RemoFirst; do not invent a transfer status.
• A wrong or missing Payment Request ID can prevent automatic reconciliation.
• Issued invoice changes require RemoFirst; approved credits apply later, while overpayments are refunded rather than credited to a future invoice.
• Unsigned agreements, incomplete onboarding gates, unapproved timesheets, or non-compliant invoices can block contractor payment.

Instructions

1. Classify the issue as access, onboarding gate, timesheet, invoice, PRID, client funding, in-transit delay, returned payment, amount mismatch, or other.
2. Build a redacted timeline: expected amount/currency, invoice period, submitted and approved dates, payment status changes, and first observed failure.
3. For access or missing objects, verify tenant and group scope before requesting broader permissions. Never treat missing visibility as a deleted record.
4. For timesheet/invoice blocks, reconcile agreement, onboarding gates, approved hours, invoice, PRID, and client payment in sequence.
5. For delayed funds, request provider-approved trace evidence. Do not tell the contractor to retry, change bank details, or accept direct payment by default.
6. For correction, recall, refund, or urgent reprocessing, obtain finance and RemoFirst approval and record the duplicate-payment risk.
7. Close only on verified resolution or a provider ticket with owner, promised next update, and a privacy-safe evidence index.

Tool Discipline

Use Read, Glob, and Grep to inspect redacted reconciliation records. Use Write or Edit only for approved timelines, decision logs, and support drafts. Do not query live accounts, execute payments, or store bank and identity fields.

Approval Boundaries

Require approval before invoice correction, refund, recall, reprocessing, direct payment, bank-detail change, timesheet decision, or privilege change. Never infer legal, tax, sanctions, or banking conclusions from a symptom.

Output

Return classification, redacted timeline, expected versus observed state, checked gates, evidence available/missing, safest next a…

RemoFirst EOR Employee Onboarding Control

Overview

Turn an approved global hire into a reviewable onboarding packet before a human uses RemoFirst's People > Add employee flow. Country options, employment type, contract type, payment frequency, leave, benefits, and local documents vary; never infer them from another country or treat this skill as legal advice.

Prerequisites

• Approved hire, employing country/region, target start date, and budget owner.
• Named People operator and authorized signatory.
• RemoFirst/local-team confirmation for country-specific requirements.

Current Contract

The documented flow captures team and location, personal/contact/address data, visa needs, job details, employment and contract type, compensation and payment frequency, additional compensation, leave policy, and optional RemoHealth, RemoTech, or RemoCheck services. Submission starts RemoFirst review; it does not make the worker active. The worker later supplies documents and signs an agreement.

Instructions

1. Create a redacted control record with country/region, role, employment type, proposed contract type, target start date, manager, and accountable approver.
2. Separate worker-supplied personal data from client decisions. Minimize fields in the working packet and keep identity documents out of repository artifacts.
3. Confirm country-dependent options with RemoFirst before setting compensation, frequency, leave, benefits, visa, background-check, or equipment choices.
4. Reconcile salary, currency, frequency, allowances, bonus, leave, and optional services against the approved offer and budget. Record unresolved differences.
5. Run a two-person review of job description, location, dates, manager, and all money-bearing fields before a human selects Continue.
6. After approved submission, record only the RemoFirst status and next owner. Do not copy documents or sensitive screens into the repository.
7. Treat Active as dependent on required documents and agreement signatures; escalate rejected documents through the documented operator flow.

Tool Discipline

Use Read, Glob, and Grep for approved offer, policy, and checklist artifacts. Use Write/Edit only for redacted control records and templates. These tools do not authorize entering or submitting worker data in RemoFirst.

Approval Boundaries

Require explicit approval before entering personal data, selecting employment or contract type, committing compensation/benefits, ordering checks/equipment, or submitting the hire. Never manufacture local-law, tax, leave, or visa guidance.

Output

Return the redacted hire key, country, target date, field-completeness matrix, country confirmations, financial reconciliation, document/signature states, approvers, current status, blockers, and next operator action.

Error Hand…

RemoFirst Contractor Onboarding and First Payout

Overview

Prepare a contractor engagement and first-payment control record while treating contractor and EOR engagements as different classification, benefit, control, and compliance decisions. RemoFirst's documented contractor path is dashboard-operated and requires agreement, tax, identity, bank, invoice, and payment checkpoints.

Prerequisites

• Approved engagement model, country, work scope, term, rate, and currency.
• Authorized signatory, line manager, and payment owner.
• A classification review and approved personal-data handling path.

Current Contract

• Rate types include monthly, daily, hourly, and milestone; available currencies and payment frequency belong to the live engagement context.
• The client may generate an agreement in RemoFirst or upload a pre-signed one.
• Contract signing enables timesheet submission; first payout also depends on tax forms, identity verification, bank details, and compliant invoicing.
• Approved hours link to an invoice, and payments are processed only after the client funds the required payment. A status is not a bank-settlement guarantee.

Instructions

1. Record why contractor—not EOR—is approved, plus country, scope, term, rate type, amount, currency, frequency, manager, signatory, and payment owner.
2. Choose generated or pre-signed agreement handling. Record that RemoFirst does not accept legal responsibility for a client-uploaded pre-signed agreement.
3. Reconcile contractor, job, compensation, IP, confidentiality, and signatory fields before sending an invitation. Require two-person review for money.
4. Track agreement signature, tax form, identity verification, bank details, and invoice readiness as separate gates. Do not mark payout-ready from one gate.
5. For hourly work, review or reject the submitted timesheet. Approval locks the entry for payment; rejection must carry a clear correction reason.
6. Match the approved period and hours to the invoice and correct Payment Request ID. Confirm client funding without recording bank data in the artifact.
7. Close only when the contractor can see the expected status and the payment owner has a documented exception/escalation path.

Tool Discipline

Use Read, Glob, and Grep for approved scope, classification, and payment records. Use Write/Edit only for redacted checklists and reconciliation artifacts. This skill does not invite, sign, approve, reject, fund, or deactivate live records.

Approval Boundaries

Require approval for engagement classification, agreement path, invitation, rate/currency/frequency, timesheet decision, invoice payment, refund, direct payment, conversion to employee, and offboarding. Do not make legal conclusions.

Output

Return engagement decision, commercial terms…

RemoFirst Privacy-Safe Support Bundle

Overview

Produce the smallest support packet that lets RemoFirst investigate without copying credentials, worker documents, bank details, full payrolls, or unrelated personal data. The bundle describes observed behavior and approved record keys; it does not reverse-engineer a private API or scrape a browser session.

Prerequisites

• Incident owner, affected workflow, first/last observed time, and severity.
• A redaction standard and approved support channel.
• Consent to include each screenshot or exported field.

Current Contract

RemoFirst accepts support by email, in-platform chat/live agent, and Help Center ticket. The Workday guide asks for company name, affected team member, relevant Workday record or event, and a clear issue description. Payment investigations may require provider-issued trace evidence; sensitive values should travel only through the approved support path.

Instructions

1. Assign a bundle ID, owner, severity, workflow, environment, tenant/company, affected period, first seen, last seen, and business impact.
2. Write expected and observed behavior in neutral terms. Separate facts from hypotheses and label every timestamp with timezone.
3. Include only redacted provider-visible identifiers needed to locate the case. Use placeholders for worker, bank, payment, and authentication values.
4. List reproduction steps that stop before any irreversible approval, payment, connector reset, offboarding, or personal-data exposure.
5. Create an evidence manifest with filename, source, capture time, owner, redaction reviewer, sensitivity, and retention deadline.
6. Scan the bundle for passwords, codes, cookies, tokens, bank details, identity documents, health data, and unrelated workers. Remove or quarantine findings.
7. Draft the support message with bundle ID, urgency, requested decision, and next contact time. A human reviews and sends it through the approved channel.

Tool Discipline

Use Read, Glob, and Grep to inventory and scan approved local evidence. Use Write or Edit for the redacted manifest and draft. Do not capture new live data, send a message, upload an attachment, reset a connector, or alter a record.

Approval Boundaries

Require approval before including any personal/payment evidence, uploading the bundle, naming a worker, initiating a trace, or reproducing against production. Never include authenticator, recovery, session, or bank-secret material.

Output

Return bundle ID, severity, redacted timeline, expected/observed behavior, reproduction boundary, evidence manifest, redaction result, requested provider action, owner, next-update time, retention deadline, and send approval state.

Error Handling

• Evidence cannot be redacted safely: omit it and describe what support may req…

RemoFirst First-Session Readiness Check

Overview

Verify that a new client operator can reach the right company and the minimum navigation required for their job. This is a metadata-only orientation; it does not list employees, download reports, approve payroll, or call an undocumented API, and its outcome is a redacted readiness receipt and a list of access gaps.

Prerequisites

• Completed remofirst-install-auth access review.
• The intended company, team, role, and first workflow.
• A safe evidence destination that excludes personal and payroll data.

Current Contract

RemoFirst's client resource hub organizes work into account setup, hiring and onboarding, payroll/payments/invoices, team management, benefits/compliance, and offboarding. Access groups can hide or expose portions of those areas. A missing menu item is therefore an access signal, not proof that a product feature is gone.

Instructions

1. Write a preflight card with operator, company, expected groups, expected team, intended workflow, approver, and evidence-retention period.
2. Ask the operator to sign in using their own credentials and 2FA. Do not collect the password, authenticator code, recovery code, or session cookie.
3. Confirm the displayed company and non-sensitive profile metadata. Stop if the tenant is unexpected or if multiple companies are ambiguous.
4. Check only the navigation labels needed for the intended duty, such as People, Payroll, Invoices, Timesheets, or Company settings. Do not open a worker row.
5. Confirm the operator can reach the Help Center or in-platform support option.
6. Produce a PASS, LIMITED, or BLOCKED receipt with missing navigation and the narrow remediation owner. End the session without changing live data.

Tool Discipline

Use Read, Glob, and Grep for local policy and readiness templates. Use Write or Edit only for an approved redacted receipt. This skill does not drive the browser, perform login, inspect worker data, or mutate RemoFirst configuration.

Approval Boundaries

Require approval before opening People, Payroll, Invoices, documents, reports, or any individual record. Visibility checks do not authorize exports, approvals, invites, payment changes, or connector activation.

Output

Return company identity, operator role, expected versus visible navigation, support-path availability, receipt status, access gaps, owner, next review date, and a list of prohibited or pending live actions.

Error Handling

• Wrong tenant: sign out and escalate; do not browse for the intended company.
• Missing menu: compare the access matrix before requesting broader privileges.
• Login loop or rejected 2FA: follow the access-recovery runbook and support path.
• Personal data appears: stop capture and remove it from the r…

RemoFirst Secure Access Readiness

Overview

Prepare a human-operated RemoFirst account without fabricating an API key, base URL, SDK, or machine credential; the reviewed public contract covers client account activation, password login, optional 2FA, manager groups, and named Workday or ADP connector setup. Treat any custom API access as unavailable until RemoFirst supplies a customer-specific written contract.

Prerequisites

• A RemoFirst welcome invitation for the intended person.
• The company, team, billing contact, and required operator duties.
• An approved password manager and 2FA recovery-code storage location.

Current Contract

• Client activation starts from the welcome email and requires a password, acceptance of terms, company review, and at least one billing contact.
• Client 2FA uses an authenticator application and a one-time recovery code.
• Manager groups separate PTO, expense, payroll, finance, people, and team-admin duties. Selecting no group defaults the user to Superuser.
• Public first-party sources do not publish a general RemoFirst API or SDK contract. Do not reuse a generic API-key example.

Instructions

1. Record the person, company, team, business duty, approver, and requested duration. Reject a shared login or generic mailbox as the account owner.
2. Activate only from the expected welcome email. Confirm the company record, terms, privacy notice, and billing contact before completing setup.
3. Map duties to the narrowest documented groups. Never leave a user with the implicit Superuser default merely because the group selection was skipped.
4. Enable 2FA from Account preferences > Security. Store the recovery code in the approved vault; do not place it in a repository, ticket, chat, or output.
5. Have a second operator verify visible teams and permitted areas without opening worker documents or exporting personal data.
6. Record owner, groups, 2FA state, review date, and removal trigger. Keep secret values and screenshots containing personal data out of the evidence file.

Tool Discipline

Use Read, Glob, and Grep to inspect local access policy and configuration. Use Write or Edit only for an approved redacted access matrix or runbook. These tools do not authorize account creation, login, group changes, or secret capture.

Approval Boundaries

Require explicit approval before activating an account, assigning Team Admin or another privileged group, changing a billing contact, disabling 2FA, or using a live worker record. Never ask the user to paste a password or recovery code.

Output

Return the account owner, company/team scope, requested and granted groups, 2FA and recovery-code custody status, billing-contact status, review/removal date, redacted verification evidence, and every live action still awaiting app…

RemoFirst Offline Workflow Rehearsal

Overview

Validate mappings and controls with synthetic data against RemoFirst's documented dashboard reports, two-column contractor-timesheet CSV upload, and named Workday/ADP connectors, which do not include a general public sandbox API. A local loop must therefore model documented inputs and decisions without claiming provider execution parity.

Prerequisites

• The workflow and current first-party source that defines its fields.
• A fixture directory containing synthetic—not anonymized production—records.
• Expected counts, invariants, failure cases, and approval owner.

Current Contract

• Contractor monthly timesheet CSV requires exactly Email and Total Monthly Hours; emails must match active accounts and hours allow up to two decimals.
• Downloadable reports include employee and contractor data and are sensitive.
• Workday mapping and sync semantics are documented separately; local fixtures are a model and cannot prove live connector behavior.

Instructions

1. Name the workflow, source article, fixture schema, assumptions, and the provider behavior that the rehearsal explicitly cannot prove.
2. Generate synthetic identities, countries, amounts, dates, and record keys. Reject copied or merely masked production rows.
3. Encode field names, types, required/optional rules, uniqueness, rounding, and allowed state transitions from the reviewed source.
4. Add positive fixtures plus missing header, duplicate, invalid decimal, unknown identity, wrong period, stale mapping, and unsafe-field cases.
5. Run deterministic parsing and reconciliation: input, accepted, rejected, duplicate, and output totals must balance.
6. Produce a preview and rollback/checkpoint design. Do not create a live import file until a human approves both mapping and data source.
7. Mark PASS only for local controls. Record live validation as PENDING and assign an approved operator for the later dashboard step.

Tool Discipline

Use Read, Glob, and Grep to inspect schemas and fixtures. Use Write/Edit only for approved synthetic fixtures, mappings, tests, and reports. Do not log in, download live reports, upload CSV, or access a private interface.

Approval Boundaries

Require approval before using any export, generating a live upload, opening a worker record, or running the documented dashboard/connector operation. Local PASS does not authorize production use.

Output

Return workflow/source, synthetic-fixture manifest, mapping version, invariants, test matrix, reconciliation counts, assumptions, unproven provider behavior, rollback design, live-validation owner, and approval state.

Error Handling

• Production-like data detected: quarantine and replace with synthetic fixtures.
…

RemoFirst Payroll and Invoice Production Gate

Overview

Create a two-person control gate before payroll approval and invoice payment that tracks RemoFirst's documented early-month revisions, provider review, client final approval, invoice generation, and prompt payment. Dates may vary by calendar or worker schedule, so confirm the live period rather than turning examples into universal guarantees.

Prerequisites

• Payroll period, countries/teams, employee population, and payroll owner.
• Approved source records for salary, time, leave, expenses, and adjustments.
• Finance approver and verified payment method.

Current Contract

• The general guide places expense approvals and revisions by the third working day, provider review on days one through seven, and client approval around days eight through ten with two business days before default approval.
• Approval generates an invoice; delayed approval or payment can delay salaries.
• Additional payments require type, currency, amount, reason, and notes.
• Hourly-worker cutoffs can be schedule-specific; late submission or approval may move payment to the next cycle.

Instructions

1. Freeze the live payroll calendar: period, cutoffs, expected approval window, invoice due date, funding lead time, pay date, holidays, and timezone.
2. Reconcile population against prior period: starters, leavers, country/team, pay frequency, and status. Investigate every unexplained change.
3. Reconcile base compensation, approved time, time off, expenses, bonuses, commissions, deductions, benefits, currency, and reason notes.
4. Separate data preparer, payroll approver, and payment approver. Record any exception to separation of duties with owner and compensating review.
5. Review each changed employee and aggregate totals. Request changes rather than approving a payroll whose source or calculation is unresolved.
6. Before approval, capture redacted counts/totals and an evidence hash; never copy worker-level payroll into a repository.
7. After human approval, reconcile generated invoice, currency, total, payment method, due date, and accounting visibility. Escalate discrepancies promptly.

Tool Discipline

Use Read, Glob, and Grep on approved redacted control artifacts. Use Write/Edit only for checklists and reconciliation summaries. Do not approve payroll, change payments, download worker reports, or fund an invoice.

Approval Boundaries

Final payroll approval, Request changes, additional payment, bank setup, invoice payment, auto-payment change, or default-approval reliance requires explicit human authority. Never treat silence as safe approval in this workflow.

Output

Return calendar, population and financial reconciliation, exception list, preparer/approvers, evidence hash, payroll decision state, ge…

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…

RemoFirst Supported Integration Boundary

Overview

Choose the narrowest documented exchange mechanism. The public first-party contract covers named Workday and ADP connectors plus controlled platform reports and CSV workflows; it does not establish a general RemoFirst SDK or API.

Prerequisites

• Source system, business object, direction, cadence, owner, and lawful purpose.
• Data classification and approved minimum field set.
• Authorized RemoFirst and source-system administrators for connector changes.

Current Contract

• Workday is a one-way inbound connector using a Workday integration system user and OAuth credentials; the RemoFirst operator starts sync manually.
• Supported Workday data is mapped before sync. Approved time-off and time-entry states matter; edits after sync may require reconciliation.
• Workday offboarding can be prefilled but requires human confirmation.
• ADP Workforce Now uses the RemoFirst connector and ADP SSO authorization.
• Reports and documented CSV templates are operator-controlled exports/imports.
• No public general SDK, endpoint, authentication, or versioning contract was found.

Instructions

1. Classify the request as Workday inbound, ADP connection, report export, documented CSV workflow, manual platform operation, or private integration.
2. Reject a generic SDK design unless RemoFirst has issued a written contract to this customer. Record its owner and version without copying secrets.
3. Build a field-level map with source, destination, direction, required status, transformation, sensitivity, and accountable data owner.
4. For Workday, establish the least-privileged integration system user and OAuth client through Workday's approved administration path. Never store secrets here.
5. Test a minimal synthetic population, trigger the documented manual sync, and reconcile counts, fields, time rounding, approvals, and unsupported records.
6. For ADP, coordinate the connector and SSO flow while its temporary account ID is valid; verify the intended company before authorization.
7. For reports or CSV, preserve the documented schema, minimize sensitive rows, transfer through an approved channel, and reconcile import/export totals.
8. Define rollback as pausing the connector and returning to the prior controlled process; never assume a sync can reverse prior writes.

Tool Discipline

Use Read, Glob, and Grep for schemas, mappings, and redacted samples. Use Write/Edit for design and reconciliation artifacts. Do not authenticate, sync, export production data, upload CSV, or modify either system.

Approval Boundaries

Credential creation, connector authorization, production sync, worker export, CSV upload, mapping change, and offboarding confirmation require accountable human approval. Legal and priva…

RemoFirst Security and Privacy Baseline

Overview

Produce an evidence-based access and data-handling review for RemoFirst client operations. Focus on interactive account security, explicit group assignment, least data, controlled exports, connector credentials, and escalation.

Prerequisites

• Named operator or service integration, business duty, countries, and teams.
• Current group membership and workflow inventory from an authorized source.
• Privacy, security, and business owners for exceptions.

Current Contract

• Client users can enable authenticator-based two-factor authentication and receive a one-time recovery code that is replaced after use.
• A manager without an assigned group receives Superuser access by default.
• Groups constrain access by responsibility and team; direct-manager assignment is a separate workforce relationship.
• Reports may contain payroll, invoice, time-off, and worker information.
• Workday connector credentials originate in Workday; they are secrets.
• The reviewed public sources describe GDPR/DPA handling but not a general API key.

Instructions

1. Inventory each identity, accountable owner, duty, group, team scope, last review, two-factor state, and termination/change trigger.
2. Treat no-group assignment as high risk because the documented default is Superuser. Assign the narrowest group through an authorized administrator.
3. Require two-factor authentication for client operators. Confirm recovery-code custody without collecting the code or any authenticator seed.
4. Separate workforce reporting lines from application permission groups; verify both independently when a manager changes role or team.
5. Inventory reports, CSV files, support attachments, and reconciliation artifacts. Minimize fields, redact identifiers, encrypt approved transfers, and define retention/deletion.
6. Keep Workday OAuth material and any provider-issued private credential only in an approved secret manager. Record owner and rotation evidence, not values.
7. Verify the applicable DPA and lawful purpose with privacy owners before adding a new data flow, country, integration, or support attachment.
8. Capture exceptions with risk owner, compensating control, expiry, and review date.

Tool Discipline

Use Read, Glob, and Grep on approved redacted inventories and policies. Use Write/Edit for the review artifact. Do not reveal secrets, recovery codes, bank details, identity files, tax documents, payroll rows, or production exports.

Approval Boundaries

Group changes, Superuser access, two-factor reset/disable, credential issuance, report download, worker-data disclosure, DPA acceptance, and exception approval require the appropriate human authority.

Output

Return identity/group matrix, two-factor status, …

RemoFirst Controlled Workflow Cutover

Overview

Plan a reversible change from a manual/export process to a documented RemoFirst connector or from one supported boundary to another. This is a business-data cutover, not an API-version migration; no public general API version contract was found in the reviewed first-party documentation.

Prerequisites

• Current and target process owners, systems, populations, countries, and dates.
• Baseline counts/totals and an approved minimum field map.
• Change approver, privacy/security review, rollback owner, and support path.

Current Contract

• Workday provides one-way inbound data to RemoFirst through mapped fields and a manually initiated sync.
• Approved time-off/time-entry state affects eligible Workday data; edits may not automatically resync, and time is subject to documented conversion/rounding.
• Workday offboarding data is prefilled but still needs human confirmation.
• ADP authorization uses its named connector, SSO flow, and temporary account ID.
• Reports and CSV workflows remain controlled alternatives for supported tasks.

Instructions

1. Document the current process, target boundary, business objective, exclusions, accountable owners, freeze window, and success/abort criteria.
2. Inventory and classify fields. Map only documented target fields, record direction and transformations, and exclude unsupported or unnecessary data.
3. Establish least-privileged connector identities and approvals without copying credentials into the plan, repository, ticket, or support bundle.
4. Test with synthetic records, then a small approved cohort. Reconcile source and destination counts, values, status, time conversion, and ownership.
5. Run a time-boxed parallel period against the current controlled process. Keep one authoritative writer per field and prevent duplicate payroll actions.
6. At the change gate, obtain explicit business, system, security/privacy, and payroll approval. Start the production sync or authorization only then.
7. Reconcile immediately after cutover and again at the first payroll/invoice boundary. Human-confirm every offboarding or other irreversible action.
8. If an abort threshold is crossed, pause the connector, retain evidence, revert to the documented prior process, notify owners, and engage RemoFirst support.

Tool Discipline

Use Read, Glob, and Grep on approved redacted maps, baselines, and results. Use Write/Edit for plans and reconciliation records. Do not authorize connectors, sync production data, upload worker files, approve payroll, or execute rollback.

Approval Boundaries

Production credential creation, connector activation, sync, export/import, offboarding confirmation, payroll impact, rollback, and decommissioning require named human owners. New data purpose…