Frequently Asked Questions

Kelvaro is contractor operations software for businesses that run on rotating crews. It connects contractor onboarding and readiness with job/work records, payout approval, funding controls, contractor transfers, reconciliation, and year-to-date reporting.

The initial pilot is designed for U.S. businesses such as event and wedding operators, production agencies, tour or destination-management operators, and other teams that assemble changing contractor crews across jobs or projects.

No. Kelvaro is not a W-2 payroll provider. It is an operations and contractor-payment control system for independent-contractor workflows.

Kelvaro's contractor workflows are designed to be mobile-friendly and use secure links for onboarding and operational actions rather than requiring a traditional desktop workflow. Follow the instructions in the invitation your organization sends you.

Setup time depends on the organization and contractor readiness. During the controlled pilot, Kelvaro personally walks each customer through organization setup, the first contractor, tax-document readiness, Stripe payout onboarding, and the first payment workflow.

A payout obligation is created and explicitly approved first. Approval does not itself move money. The customer then funds the approved obligation. Kelvaro waits until that funding is SETTLED before the contractor transfer can be initiated. Stripe events and Kelvaro reconciliation then verify the resulting transfer state.

The settlement gate prevents Kelvaro from treating an unsettled customer funding attempt as available money for a contractor transfer. It is a deliberate money-safety control, not just a user-interface status.

Contractors complete Stripe-hosted payout onboarding. Kelvaro only marks the required payout setup ready when the current Stripe recipient capability needed for transfers is active.

Receipt timing varies with funding settlement, Stripe eligibility, the contractor's payout destination, banking schedules, the payout rail, and any provider review. A Kelvaro approval is not a promise that money will arrive by a fixed clock time.

Do not create a replacement payment blindly. Kelvaro's support process reconciles the payout, funding record, Stripe identifiers, transfer state, and audit history first. Duplicate-payment concerns are treated as money-safety incidents.

International payout coverage is not part of the current controlled pilot. Pilot money movement is limited to the supported U.S. configuration that has been tested and approved for launch.

The workflow tracks the contractor record, required tax-document readiness, and Stripe-hosted payout onboarding. Organizations should not treat a contractor as payout-ready until the required readiness checks are complete.

Stripe-hosted payout onboarding is used for contractor payout-destination setup. Kelvaro should not be used as a place to copy full bank-account credentials into notes, support tickets, or audit records.

The contractor should return to the Stripe-hosted onboarding flow and complete the requested information. Kelvaro fails closed rather than marking the contractor payout-ready while the required transfer capability is inactive or restricted.

No. The controlled pilot does not bypass payout-destination verification, required tax-document controls, approval, funding settlement, tenant checks, webhook verification, or reconciliation to force a payout through.

Not currently. Kelvaro supports W-9 and W-8 workflows, year-to-date contractor records, threshold monitoring, 1099 readiness, and exports for an accountant or filing provider. Native 1099 e-filing remains post-pilot work.

No. Worker classification is the customer's responsibility. Kelvaro does not make legal classification determinations and is not a substitute for an employment attorney, CPA, or tax adviser.

No. Kelvaro provides workflow and recordkeeping tools. Tax treatment, filing obligations, backup withholding, classification, and jurisdiction-specific requirements should be reviewed with the customer's qualified advisers.

Use Kelvaro's readiness and year-to-date records to identify missing documentation and prepare an export for your accountant or filing provider. The customer remains responsible for reviewing the filing population and completing required filings.

Not in the current controlled pilot. Use the available reporting/export and accountant-handoff workflows. Native synchronization should not be assumed until a specific integration is released and acceptance-tested.

Kelvaro includes reporting/export workflows for operational and year-end handoff. The exact available exports depend on the product surface and organization permissions.

Kelvaro minimizes sensitive-data exposure and uses third-party providers such as Stripe for payment onboarding. See the Privacy Policy and Security page for current disclosures.

Yes. Follow the process described in the Privacy Policy. Retention can be affected by legal, security, dispute, financial-record, and provider requirements; Kelvaro does not promise an unsupported fixed deletion period.

Kelvaro is currently onboarding a small number of controlled pilot customers. Pilot commercial terms are confirmed during onboarding while the direct-operator general-availability pricing model is finalized and tested end to end.

Kelvaro previously had multiple inconsistent pricing concepts across product surfaces. Rather than publish a price that does not match billing configuration, the pilot uses controlled terms until one canonical direct-operator model passes Stripe billing acceptance.

No assumption should be made that they are the same. A firm managing many client organizations and an operator paying its own rotating crews are different buyer models and are being treated separately.

Email support@getkelvaro.com. The address routes into the monitored Kelvaro support inbox. For suspected duplicate/wrong payments, unauthorized money movement, or material data-integrity issues, stop affected money movement and escalate immediately.

Suspected duplicate payment, wrong recipient, unexplained Stripe/Kelvaro discrepancy, unauthorized money movement, material data-integrity issue, or critical tenant-isolation concern should be escalated immediately and affected money movement should stop until reconciled.

Kelvaro treats a blocked production payout or critical workflow as a high-priority operational incident, restores the service or dependency, and reconciles affected records before closing the incident.