Qavren
← All products
Product/Fintech · Payouts

RemitHQ

Cross-border contractor payouts for U.S. businesses. The operations console for actually getting people paid.

A small U.S. company hires three engineers in Brazil, a designer in Portugal, and a copywriter in the Philippines. Now somebody has to actually pay them every month, in their currency, on time, with the right paperwork. RemitHQ is that somebody.

What it is

RemitHQ is an operations console for cross-border contractor payouts, built for U.S. businesses paying international contractors. It manages the contractor roster, invoice intake, approval workflow, payout execution, compliance documentation, and the ledger reconciliation behind it. It is not a payment processor; it's the workflow layer on top of one.

The repo ships a Next.js 16 + React 19 frontend for the operations console plus a .NET 10 backend scaffold that's actively building toward production.

What it does well

One console for the whole flow. Contractors, invoices, approvals, payouts, review queue, compliance, ledger, exports — separate screens, single coherent model. Nobody has to live in a spreadsheet and three vendor portals at once.

Approvals that make sense. Invoice arrives → routes by amount, contractor, or category → approver clicks through with full context → released to the payout queue. Multi-level approval where the company needs it; single-click where it doesn't.

Compliance documentation that's actually attached. W-8BEN, W-8BEN-E, country-of-residence proofs, contractor agreements — all linked to the contractor record, surfaced at every payout that needs them.

Provider-agnostic. The payout adapter is an interface, not a hardcoding. Wise, Payoneer, ACH, bank wires — whichever one fits the contractor, the company, and the corridor.

Real ledger, not a list. Every payout creates the corresponding ledger entries — gross, fees, FX rate locked, net to contractor — so reconciliation isn't a Friday-afternoon Excel job.

Who it's for

U.S. SMBs and startups with international contractor teams who've outgrown PayPal and don't want to graduate straight to Deel or Remote.com.

Agencies running global creative teams who need predictable, auditable monthly payouts.

Finance teams at growth-stage companies that need the ledger and compliance hygiene without staffing a full AP function.

Anyone whose contractor-payment process currently involves the founder, a personal Wise account, and a recurring sticky note.

What it looks like in practice

A 15-person agency runs a single monthly payout cycle through RemitHQ. The five contractors submit invoices into the queue. The CFO reviews everything in one screen, approves in bulk, and releases. Payouts execute through the appropriate adapter for each contractor's country. The ledger updates atomically. Exports for the bookkeeper are ready by Tuesday.

What it's not

It's not employer-of-record. RemitHQ pays contractors, not employees. EOR is a separate business.

It's not a payment processor. It sits on top of real rails. Wise, Payoneer, the banks — those move the money. RemitHQ orchestrates.

It's not a tax filing service. It records the documents and produces the reports; your CPA still files the 1099-NECs (and the 1042-S where it applies).

Status

Operations-console UI shipping. Backend Milestone 0/1 scaffold in place (identity, organizations, health, session). Provider adapters, webhook processing, and production deploy pipeline are the active build.

Have a use case for RemitHQ?

Talk to the people who built it.