How to pay freelancers and gig workers

Key takeaways

Start by identifying the arrangement and the party responsible for payment. In a direct freelance engagement, the client and contractor set the terms; in platform work, the platform may organise both the work and its remuneration. That distinction shapes the records, approval route and escalation path you need.
Do not let a contract label decide status. In the US, the actual relationship and degree of control matter; UK categories can also differ between tax and employment law. Review the applicable local rules before processing someone as an independent contractor.
Agree the payable work before it begins. Put the scope, rate or pricing basis, acceptance point, due date, cancellation handling and any rights terms in writing. A payment can settle an invoice without settling who owns the work.
Set up the recipient and documents before release. Match the correct contracting party, account details and any required tax information to an invoice or authorised self-bill. US contractor paperwork and UK VAT self-billing each have conditions of their own.
Choose a route by the funds the recipient can actually use. Ask for a current quote for the relevant countries and currencies, then check the exchange rate, all fees and deductions, the amount received, recipient eligibility and withdrawal access. No general payment method is best for every corridor.
Keep a traceable chain from agreed work through acceptance, the payable document, payment reference and reconciliation. When money is late, missing, short or reversed, check which step failed and preserve the contract, work evidence, communications and payment records before escalating.

Who is being paid, and who owes the payment?

Choose the payment route after you have mapped the work arrangement. A direct client engagement and work arranged through a digital platform can put different people or organisations in charge of the agreement, approval, payment and exception handling.

Decision tree: identify the work arrangement. Direct: identify parties and review local status and records. Platform: identify operator and worker roles and review national status rules. Choose the route after the applicable review. — Use the direct-engagement or platform-work branch to identify responsibility before selecting a route. Status rules are jurisdiction-specific; this is an editorial decision aid, not an automatic classification tool. IRS: Employee (common-law employee) · GOV.UK: Employment status: self-employed and contractor · European Commission: The future of work · IRS: Forms and associated taxes for independent contractors

Direct freelance engagements

In a direct engagement, begin with the agreement between the business commissioning the work and the party delivering it. The party named as the customer, the party that issues the invoice, and the account that receives the funds should all line up with that agreement. If finance sees a different payee or an account change, resolve the discrepancy before releasing the payment.

Put the payment responsibility into a small, usable record before work starts:

Contracting parties: name the business entity that orders the work and the contractor it engages.
Payable work: describe the service or deliverable, the agreed rate or pricing basis, and the amount or event that makes it payable.
Approval point: state who accepts the work and what happens when it needs revision or is disputed.
Payment terms: record the due date, invoice or self-billing process where applicable, and the person who owns a late-payment follow-up.

Written terms make the payment easier to approve and reconcile because the invoice can be matched to an agreed scope, amount and date. They also keep a payment from being treated as a substitute for a separate rights agreement: for UK commissioned copyright work, the creator is initially the owner unless the parties agree otherwise in writing.

The agreement label is only a starting point. Check the actual working relationship under the relevant local rules before processing the engagement as contractor work.

Platform-mediated gig work

Platform work has an extra operating layer. The European Commission describes it as work performed through a digital labour platform, which may organise the performance of work and its remuneration. That can make the person requesting a task, the platform operator and the worker distinct parts of the payment process.

Map those roles before you set a payout schedule or respond to a missing-payment report:

Work allocation: identify who offers or assigns the task and how completion is recorded.
Payment responsibility: identify the party and entity responsible for calculating and releasing the worker’s earnings.
Review route: record who can accept, reject or investigate a task, and where the worker can challenge that decision.
Payout route: record the recipient details, payout cadence, deductions or fees that may affect usable funds, and the reference that connects a payout to the task.

A rejected task calls for an acceptance decision. A completed payout that the worker cannot access calls for a route trace. Give each issue an owner and retain the task, decision and transaction records that let them investigate.

The platform’s presence does not settle the worker’s legal status. Review the arrangement under the applicable national rules before setting its routine payment workflow.

When the arrangement needs a status review

Run a status review when the label in the contract, the way work is organised and the payment workflow do not clearly point to the same arrangement. The review belongs before routine contractor processing, because a payment method cannot determine whether the worker is correctly classified.

The legal test depends on the jurisdiction. US federal guidance looks to control and independence in the working relationship, regardless of the contract label. In the UK, a contractor may be self-employed, a worker or an employee in an agency arrangement; tax status and employment-law status can differ. Platform work needs the same care: applicable national rules govern how the arrangement is assessed.

Make the review usable for operations by recording:

the parties, role and jurisdiction that the engagement concerns;
the agreement and the records that show how the work is actually organised;
the status decision, any conditions attached to it and the person responsible for keeping it current;
the documents and payment workflow that follow from that decision.

Revisit the record when the arrangement changes, such as a different contracting party, a material change in how work is directed or a new country in scope. Finance can then pause the workflow for a status review before approving the next payment.

Agree the work and payment terms before it starts

Put the work, the amount due and the path to approval in writing before anyone starts. Clear terms give the client a basis for authorising payment and give the freelancer or gig worker a record to use if the payment later needs to be traced or challenged.

Scope, rate and pricing basis

Define what the business is buying in terms that finance can match to a payment. UK Small Business Commissioner guidance treats the goods or services, quantity, conditions, duration and parties as core contract details; the same information makes an operating record usable across a payment workflow.

For each engagement, record:

The service or deliverable: what will be provided, including the quantity and any conditions that affect completion.
The agreed price: the rate or pricing basis, what it covers and the event or record that determines the amount due.
The parties: the business entity commissioning the work and the party that will invoice or otherwise receive payment.
The timeframe: when work starts, when it is expected to finish and how an extension or change is agreed.
The change path: who can approve a revised scope, rate or quantity before it creates a new payable amount.

An approver should be able to tell what was requested, what was accepted and how the amount was calculated without reconstructing the arrangement from chat. If the scope changes, update the agreement or its approved change record before the revised work enters the payment queue.

Deposits, milestones and final acceptance

Use deposits, milestone payments or a final payment only when the agreement says what each payment covers and what makes it due. The structure should fit the work: a payment against an early stage needs a record of that stage, while a final payment needs a clear acceptance route for the completed work.

For every payment trigger, agree:

the work, deliverable or period that the payment covers;
the amount or calculation method and any amount already paid;
the evidence the contractor or worker submits for review;
the person or process that accepts the work;
the route for a partial acceptance, revision request or dispute.

Do not leave final acceptance as an informal message that finance has to interpret later. Record the decision alongside the relevant work evidence, then match the approved amount to the invoice or authorised self-bill before release. If the work remains unresolved, keep the issue in the review route instead of treating the payment queue as the place to decide it.

The agreement should also make clear whether an advance or milestone payment changes the remaining amount due. The agreed terms should show how each deposit or milestone payment affects the balance.

Due dates, disputes and cancellations

Set a due date in the agreement rather than leaving payment timing to memory or a message thread. Tie it to a named event, such as receipt of a valid invoice after acceptance, and say who checks that the conditions have been met. For UK B2B transactions with no agreed date, the legal late-payment point is 30 days after invoice receipt or later service delivery; that local default does not replace a clear agreed term.

Second, don’t assume that your pay schedule will be the same for every client. My recommendation is that you ask before you begin.
— Tyra Seldon, writer, editor and small-business owner

Give a disagreement a route before it becomes overdue. The terms should identify the person who receives a query, the work or invoice records they will review, and whether the undisputed amount can proceed while the disputed part is resolved. Keep the decision with the work record so a payment approver can see why a release is paused, adjusted or cleared.

Cancellation needs the same precision. Record how either party notifies the other, what happens to work already completed, how outstanding expenses or approved milestones are handled where relevant, and whether any work must be returned or handed over. Do not infer the amount due from the cancellation alone; match it to the agreed scope, accepted work and the terms that apply to the engagement.

Rights, confidentiality and supporting records

Treat payment terms and rights terms as separate parts of the agreement. Paying an invoice does not, by itself, answer who owns a deliverable or what the client may do with it. For UK commissioned copyright work, the creator is initially the owner unless the parties agree otherwise in writing.

Set out the rights needed for the engagement before the work is delivered. That may include the intended ownership or permission to use the work, any handover materials, and the point at which those rights take effect. Where either party will share confidential information, describe what information is covered, who may access it and how it should be handled when the engagement ends.

Keep the documents that connect those terms to a specific payment:

the signed agreement and any approved scope, rate or rights changes;
the work evidence and acceptance decision for the relevant deliverable or period;
the invoice, or authorised self-bill where that method applies;
the payment reference and records of any dispute, adjustment or cancellation.

Operations and finance can use these records to resolve ownership, confidentiality or payment questions against the agreed terms.

Set up the recipient and documents

Set up the recipient record before the first payment is approved. The record should connect the contracting party, payment destination and documents that govern the payment, so an invoice and a transfer do not become disconnected from the engagement they relate to.

Identity, account and tax information

Collect the information needed to identify the recipient, route the funds and meet the rules that apply to the arrangement. The required documents vary by jurisdiction, worker status and payment channel, so do not use one generic tax checklist for every freelancer or platform worker.

You need to collect a lot of information and verify and validate that information even before you start to send payments
— Tim Nixon, founder and CEO of Trolley

For a US independent contractor, the IRS process places Form W-9 after the independent-contractor determination. Collect the form that fits the status decision; the form itself does not determine status.

At setup, match:

the recipient’s name and contracting role to the agreement;
the payment account or authorised payout route to that recipient record;
the tax information and documents required for the applicable jurisdiction and arrangement;
the person and process authorised to approve later changes to payment details.

Keep changes visible to finance and the engagement owner. A new account, a different invoicing party or an updated tax record can all require the payment record to be checked again before the next release.

Invoices, self-billing and work records

Use the invoice and work record together to show why a payment is due. An invoice identifies the payable item; the engagement records show the agreed scope and whether the relevant work was accepted. Keep both with the payment reference so a later question does not depend on someone’s memory of the engagement.

For a UK invoice, the required information includes a unique identification number, named supplier and customer details, a clear description of the goods or services, relevant dates and the amounts charged. Those fields give finance practical checks: does the invoice name the right parties, describe the work actually supplied and match the agreed amount?

Self-billing needs its own control. Under UK VAT rules, a buyer can issue self-billed invoices only when the supplier has agreed to that accounting method and a self-billing agreement is in place. Treat an authorised self-bill as a documented process, not as an informal substitute for an invoice.

For each payable item, retain:

the relevant agreement and any approved change to scope or price;
work evidence and the acceptance or review decision;
the invoice or authorised self-bill;
the payment reference and any adjustment, rejection or dispute record.

The exact documents change with the jurisdiction and arrangement. A reviewer should be able to trace the transfer back through the payable document to the accepted work and agreed terms.

US, UK and EU obligations that change the workflow

Build jurisdiction checks into the workflow at the point where they change an action: status review, recipient setup, invoice handling or reporting. A rule from one country should not be treated as a universal freelancer-payment requirement.

United States. Determine whether the payee is an independent contractor before using the IRS contractor process; Form W-9 follows that determination. Form 1099-NEC can apply to reportable nonemployee payments at the applicable threshold, with payment-channel and payee exceptions to check for the relevant tax year. The worker’s duty to report income is a separate issue from whether the business issues an information return.

United Kingdom. A person described as a contractor may be self-employed, a worker or an employee in an agency arrangement, and tax status can differ from employment-law status. Use that review alongside the UK invoice requirements and, where relevant, the formal agreement needed for VAT self-billing.

European Union platform work. The Platform Work Directive is specific to work performed through digital labour platforms. It requires member states to establish a rebuttable presumption of an employment relationship, so a platform operator should check the national rules that apply to its arrangement rather than extending one country’s result across the EU or to direct freelance work.

When a country-specific obligation affects the payment process, assign it to a named owner and retain the decision with the engagement record. That makes it possible to update the recipient documents or approval route when the arrangement, jurisdiction or applicable rule changes.

Choose a payment route by usable funds

Choose a payment route by what the recipient can access, not by the transfer label alone. For each real corridor, compare the amount sent with the amount the recipient can receive and use, then check the terms that determine when and how that happens.

Bank transfers and local electronic payments

Bank transfers and domestic electronic routes can be a practical starting point when the payer and recipient are eligible for the same route. In the US, ACH is a domestic electronic transfer option for business payments. Its availability says nothing about another country, bank or cross-border route.

Before selecting a bank or local electronic route, obtain the current terms for the actual payer, recipient, countries and currencies involved. Check:

the exchange rate, fees and taxes shown for the transaction;
any intermediary or recipient-bank deductions that can change the amount received;
recipient eligibility, account requirements and the way funds become available;
the expected payment timing, transaction reference and support route if the payment cannot be located.

US consumer remittance disclosures separate the exchange rate, fees and taxes, and the amount received. Those are useful questions for a business to ask about a B2B route, but they are not a business-price benchmark or a promise about a particular transfer.

Record the quote and selected route with the payment instruction. If a recipient changes accounts or the route terms change, review the usable-funds calculation again before treating an earlier choice as the default.

Cards, wallets and payment services

Cards, wallets and payment services are route categories, not interchangeable outcomes. A route can be available to the sender while the recipient faces different eligibility, withdrawal, currency-conversion or support conditions. Check the recipient’s access before making it the standard option for a contractor or worker group.

Use the same usable-funds review as for a bank route:

identify the sender’s total transaction cost and the amount the recipient is expected to receive;
ask which fees, deductions or conversion steps can occur before funds become usable;
confirm how the recipient accesses the funds and whether that access fits the country and account they will use;
record the payment reference, support contact and route for resolving a failed, reversed or unrecognised transaction.

Speed and cost depend on the payer, recipient, currency, country and product terms. Get a current quote for the specific corridor and retain it with the payment record.

Marketplaces, escrow and platform payout routes

When a marketplace, escrow arrangement or platform sits between the business and worker, map what that intermediary actually does before relying on its payout route. The work record, acceptance decision and payment instruction may sit in different places, so the route needs a clear owner for each step.

Confirm the terms for the specific arrangement:

who holds or controls funds before release, if anyone does;
what work or acceptance record triggers a payout;
which party can pause, reject, reverse or challenge a transaction;
what fees, deductions, recipient-access conditions and withdrawal steps affect usable funds;
where the task, payout and dispute records can be retrieved.

An escrow or platform route does not remove the need for agreed scope and evidence of completed work. If a task is rejected or a payout is missing, the business and worker need a record that identifies the task, decision, amount and route used. Keep the applicable agreement and payment reference with that record.

Before making the route a standard policy, test the actual recipient journey for the countries and currencies in scope. Use the current terms rather than assuming that a marketplace or platform follows the same payout process for every worker.

Compare total cost, timing and recipient access

Compare routes with a current quote for the actual payment, then read the result from both sides of the transaction. The sender needs a controllable total cost and a traceable release; the recipient needs to know what arrives, when it becomes usable and what restrictions apply.

Decision factor	Check for the sender	Confirm for the recipient
Total cost	Exchange rate, stated fees, taxes and any route-specific charges	Amount expected to arrive, possible intermediary or recipient-bank deductions, and any conversion before use
Timing	Release conditions, expected processing timing and the reference used to trace the transaction	When funds can be accessed or withdrawn under the route’s current terms
Access	Payer eligibility and the support route for a failed instruction	Country, account and withdrawal eligibility for the individual recipient
Exceptions	How a payment can be traced, corrected or disputed	Who the recipient contacts when the amount, status or access does not match the instruction

And optimal means best for both sides – the sender has cost and speed priorities, the recipient has their own preferences and restrictions.
— Ran Grushkowsky, Co-founder and CEO of MassPay

Use the table when requesting a quote and confirming recipient access. Keep the chosen route, quote and recipient confirmation with the payment policy; review them when the corridor or recipient conditions change.

Design a payout policy for gig platforms

A payout policy should make the earning schedule, calculation and exception route clear before it adds an optional faster-access feature. Predictable earnings and faster transfer access solve different problems, so measure and explain them separately.

In the Federal Reserve’s 2024 US survey, 41% of adults with gig activity in the prior month reported that their income varied at least occasionally month to month, compared with 26% of adults with no such activity. The comparison measures income variation, not payment delay or demand for faster payouts.

Bar chart of US adults reporting income that varied at least occasionally month to month in the October 2024 survey: 41% among adults with any gig activity in the prior month and 26% among adults with none. — US Federal Reserve survey, October 2024: 41% of adults with prior-month gig activity reported monthly income variation, compared with 26% with none. The comparison measures income variation, not payment delays or demand for faster payouts. Federal Reserve: Economic Well-Being of U.S. Households in 2024

Scheduled earnings and optional faster access

Start with a published payout cadence that tells workers when earnings are calculated, when a task or period closes, and what record they can use to check the amount. A clear schedule gives the platform a base process for approval, corrections and support, even where some workers later choose an optional faster-access route.

Make the policy explicit about:

the earning period, cutoff and normal release schedule;
the work or acceptance record used to calculate the payable amount;
fees, eligibility and deductions that apply to any optional faster-access route;
how a correction, rejected task or reversal affects an amount already scheduled or released;
the support and dispute route for a worker who cannot reconcile the payout with their task record.

An optional faster-access offer should be tested as a policy choice, not presented as a universal retention or welfare benefit. In a randomized US Uber pilot from 2016, offering Instant Pay increased daily driving minutes by 1.4% and daily net trip earnings by 1.5%. The study did not measure retention, welfare, direct freelance work or current cross-border outcomes.

Ask workers and operations teams about the schedule separately from the transfer route. Make the normal earnings schedule legible even if the platform offers immediate access. Faster access alone does not resolve variable income.

Fees, thresholds, reversals and worker support

Make every payout condition visible before a worker chooses a route or expects a release. In the Federal Reserve’s US survey, 61% of adults doing app- or website-mediated platform tasks said they wished pay was more consistent. The finding concerns consistency. It does not measure willingness to pay for faster access.

State the policy in terms workers and support teams can apply:

Fees: identify what the fee covers, who pays it and when it is charged.
Thresholds and eligibility: identify any minimum amount, route condition or review condition that affects whether a payout can be released.
Reversals and corrections: explain how a rejected task, adjustment or reversal changes an amount already shown as payable or released.
Support: provide a route for a worker to report a missing, short or inaccessible payment, with the task and payment reference needed to investigate it.

Do not borrow numbers from another platform or country to set these terms. Test fees, thresholds, delivery times and support against the actual route and recipient group. Retain the resulting terms and exception decisions with the relevant payout records.

When a reversal or correction occurs, keep the worker’s task record, acceptance decision, original payout reference and adjustment together. That lets support explain what changed and gives operations a way to distinguish a work dispute from a transfer problem.

Run each payment from approval to reconciliation

Run each payment as a linked record chain: agreed work, evidence of completion, acceptance, payable document, payment reference and reconciliation. The exact documents and legal requirements vary by jurisdiction, but the chain gives your team a practical way to stop an unresolved work issue from becoming an unexplained transfer.

Process: agree scope, rate and due date; retain work evidence; check acceptance. If unresolved, resolve the work issue. If accepted, match an invoice or authorized self-bill, release with a reference, and reconcile. — An editorial record chain based on UK contract, invoice and late-payment guidance. It separates an unresolved work issue from an accepted payable item; local law and the agreement determine the exact documents and escalation route. Office of the Small Business Commissioner: Contract Guide · GOV.UK: Invoices—what they must include · GOV.UK: Self-billing · GOV.UK: Late commercial payments

Match work, acceptance and the amount due

Release a payment only after the agreed work, the acceptance decision and the amount due point to the same payable item. Start with the terms, then match the invoice or authorised self-bill to the work record before the payment instruction is released.

Use four checks:

Agreed work: the service, deliverable or period matches the contract and any approved change.
Acceptance: the required reviewer has accepted the work, or any unresolved issue has been kept in the review route.
Payable document: the invoice or authorised self-bill identifies the right parties, work, dates and amount.
Amount due: the payment instruction reflects the approved amount after any documented advance, milestone payment, adjustment or dispute.

UK invoice guidance requires identifiers, supplier and customer details, a description of what is charged, dates and amounts. Those fields make the match more concrete, but local rules still determine the documents that apply to a particular engagement.

If one of the checks does not match, pause the release and identify the failed step. A missing acceptance record calls for a work decision; a wrong amount calls for a corrected payable document. Keeping those paths separate prevents finance from using the transfer itself to settle an unresolved work question.

Release, track and record the transaction

Once the payable item is approved, release the payment with a reference that connects the instruction to the engagement and payable document. The reference is the bridge between a completed approval and a later question about delivery, amount or access.

At release, retain the approved amount, recipient record, selected route, payment date and transaction reference. If the route exposes fees, deductions or exchange-rate information for that payment, retain those details too so the expected and received amounts can be compared without recreating the instruction.

Track the transaction through the point where it can be reconciled against the payable record. A practical reconciliation record should show:

the engagement and work or acceptance record that made the item payable;
the invoice or authorised self-bill and approved amount;
the payment route, recipient and transaction reference;
the release status and any known adjustment, reversal or unresolved exception;
the person responsible for investigating a mismatch.

Keep the record open until the payment can be reconciled. Where a recipient reports that funds are missing, short or inaccessible, use the reference to locate the failure point: the approval, instruction, route, intermediary or recipient-access step. Record the outcome and any correction alongside the original transaction rather than replacing the original trail.

When to replace a manual workflow

Replace a manual payment workflow when the team can no longer keep the engagement record, approval and payment trail connected without chasing information across files, inboxes and chat. A useful trigger is a routine exception that takes too long to locate because the work, decision and transaction live in separate places.

Look for operational signs that the workflow needs a shared system:

approvers cannot see the agreement, acceptance record and amount due in one review;
finance has to rebuild payment context from messages or spreadsheets;
account, status or scope changes reach different teams at different times;
a payment reference cannot be matched reliably to the work and document that made it payable;
access to contractor records needs to differ by company, country or team.

For organisations that need a central contractor record, 4dev.com states that its Contractor Platform keeps tasks, statuses, contracts, closing documents and engagement history in one register. Its workflows support configurable approvals, roles and access by company, country or team; its API can create tasks, sync records and reports, track workflow status and send webhook updates.

Choose a workflow that preserves the decisions your team must explain: who approved the work, which payable document matched it, which route was used and how an exception was resolved. Automation does not remove the need to review the underlying arrangement, recipient information or payment terms when they change.

Handle delayed, missing or disputed payments

Treat an exception as a traceable break in the payment record, then send it to the person who owns that step. A delay can begin with work acceptance, invoice handling, the payment instruction, the route or the recipient’s access to funds; a transfer confirmation alone does not identify which one.

Locate the failed step

Start with the task or engagement reference and work forward through the record chain. Ask what was agreed, whether the work was accepted, whether a payable document was issued, whether the payment instruction was released and whether the recipient could access the expected funds.

Reported issue	First record to check	Next action
Work was rejected or payment was not approved	Scope, work evidence and acceptance decision	Send the issue to the reviewer or dispute route for the work
Invoice is missing or the amount is wrong	Invoice or authorised self-bill, agreement and approved changes	Correct or replace the payable document before release
Payment is late or cannot be located	Payment instruction, transaction reference and route status	Trace the transaction through the applicable support route
Amount received is lower than expected	Quote, stated fees and payment reference	Check documented deductions, exchange-rate information and the route’s terms
Funds are inaccessible	Recipient record, route eligibility and account details	Confirm the recipient’s access conditions and investigate with the route owner

Keep the distinction between a work dispute and a payment-route problem. The ILO’s historical survey of workers on five microtask platforms found that work rejection or payment refusal was common in that particular sample; it is not a result for all gig work. Its practical lesson is that a worker needs access to the task and acceptance records before a payment dispute can be resolved.

For UK B2B transactions with no agreed payment date, the legal late-payment point is 30 days after invoice receipt or later service delivery. Use that as a UK-specific reference point, then follow the contract and applicable local process for the actual issue.

Preserve records and escalate

Preserve the record before an exception turns into an argument about what was agreed or sent. Collect the documents while the work, approval and payment references are still easy to locate, then use the appropriate contract, platform or route process to escalate the specific failure.

Gather and organize all relevant documents – any form of contract, relevant work materials, communication (texts, emails), unpaid invoices, and any other documentation
— Dylan Ward, Legal Program Director with the Freelancers Union

For a delayed, missing or disputed payment, retain:

the agreement, scope, rate, due date and any approved change;
work materials, timesheets or task records, plus the acceptance or rejection decision;
the invoice or authorised self-bill and any correction or adjustment;
communications about the issue and the payment instruction or transaction reference;
the route’s status, support case or dispute reference where one exists.

Escalate with a concise record of the failed step, the amount involved and the outcome requested. Send a work-acceptance dispute to the person or process that owns acceptance; send a transfer-tracing issue through the route’s support process; use the agreement and applicable local process for a late-payment or contractual dispute. Keep each response and decision with the original record so the next reviewer does not restart the investigation.

Do not promise an escalation result or timing that the agreement or route has not established. The immediate goal is to give the responsible party enough evidence to identify the issue and respond.

Resolve a short payment or reversal

Treat a short payment or reversal as an amount-and-route question first. Compare the approved amount, payment instruction, current quote and transaction reference before deciding whether the issue came from a work adjustment, a documented deduction, a route failure or recipient access.

Work through the record in order:

Confirm the payable amount against the agreement, accepted work, invoice or authorised self-bill, and any approved adjustment.
Compare that amount with the instruction and the recipient’s reported amount received.
Check the payment record for the exchange rate, fees, deductions, reversal reason and route status that applied to that transaction.
Send the issue to the responsible route: correct the payable record if the amount was wrong, trace the transaction if the instruction failed, or use the route’s support process when the recipient cannot access funds.

Recipient banks can deduct additional fees and foreign taxes in US consumer remittances. That is a reason to check deductions when a business payment arrives short, but it does not establish what a particular B2B route will deduct. Use the actual quote and route terms for the countries and currencies involved.

When you resolve the case, retain the original amount, reported issue, investigation result and any replacement or adjustment reference. A corrected payment should extend the record trail, so both the business and recipient can see what changed and why.

Frequently asked questions

How do gig workers and freelancers usually get paid?

Freelancers in a direct engagement are usually paid by the client after the agreed work, acceptance and payable document match. The route may be a bank transfer, local electronic payment, card or wallet route, or another agreed method; the business should confirm the recipient’s eligibility, expected amount received and access conditions for the actual corridor.

Gig workers using a platform may be paid through the platform’s payout process. In that case, identify who calculates earnings, what task or acceptance record triggers a payout, when the normal payout schedule applies and how the worker reports a missing or short payment.

For either arrangement, keep the agreement, work record, invoice or authorised self-bill where applicable, and transaction reference together. Those records make it possible to explain the amount and trace an exception without guessing which part of the workflow failed.

What is the best payment method for a freelancer?

The best payment method is the one that works for the actual payer, recipient, countries and currencies involved while giving both sides a clear record of the payment. Compare current terms for the actual transaction; the cheapest or fastest route can differ by corridor.

Compare current route terms before choosing. Check the exchange rate, stated fees and taxes, possible deductions, expected amount received, recipient eligibility, withdrawal access, expected timing and support process. A bank transfer, local electronic route, card, wallet or marketplace payout can produce different usable-funds outcomes for the same invoice.

Choose the route only after the freelancer confirms that they can receive and use the funds under those conditions. Keep the quote, recipient confirmation and transaction reference with the payment record, especially when the engagement involves a new country, currency or account.

Can a freelancer be paid before work is complete?

Yes, if the agreement defines the advance or milestone payment and what it covers. The terms should state the amount, the work or period it relates to, how it changes the remaining balance and what evidence or acceptance point applies before the next payment is due.

Do not treat an advance as a substitute for a record of the work. Keep the agreement, payment reference and any milestone evidence together, then match later invoices or authorised self-bills to the remaining approved amount. If the scope, schedule or acceptance decision changes, update the payable record before releasing the next amount.

There is no universal deposit percentage or milestone pattern. Use the structure both parties agreed, make any cancellation or adjustment path visible, and retain the records needed to explain how the final amount was calculated.

What tax forms does a business need before payment?

The forms depend on the payee’s status, jurisdiction and payment channel. For a US payee determined to be an independent contractor, the IRS contractor process calls for Form W-9 after that determination. A W-9 is part of the US workflow; it does not determine worker status by itself.

For US nonemployee payments, Form 1099-NEC can apply when the payment is reportable at the applicable threshold, subject to payment-channel and payee exceptions. Check the rules for the relevant tax year rather than relying on a fixed threshold from an old process. A worker’s own income-reporting duty is separate from whether the business issues an information return.

Outside that US context, obtain the identity, tax and invoice records required for the applicable arrangement and jurisdiction. If the payment setup involves UK VAT self-billing, the supplier’s agreement and a formal self-billing agreement are required before a buyer issues self-billed invoices. Retain the status decision and supporting documents with the recipient record before release.

How should a business pay a freelancer abroad?

Start with the arrangement, recipient record and documents required for the countries involved, then compare payment routes by usable funds. Ask for a current quote for the real payer, recipient, currency and route before you approve an international payment.

Check the exchange rate, stated fees and taxes, possible intermediary or recipient-bank deductions, expected amount received, recipient eligibility, withdrawal access, expected timing and support route. US consumer remittance disclosures distinguish the exchange rate, fees and taxes, and amount received; those are useful dimensions to check for a B2B payment, but they are not a price benchmark for contractor payments.

Confirm that the freelancer can receive and use the funds under the selected route’s current terms. Keep the agreement, invoice or authorised self-bill where applicable, quote, recipient confirmation and transaction reference together. If the amount arrives short or is inaccessible, those records let the business trace whether the issue lies in the payable amount, the payment instruction, the route or recipient access.

What should each party do when a payment does not arrive?

First, identify the failed step instead of assuming that the transfer failed. Check whether the work was accepted, whether the invoice or authorised self-bill is correct, whether the payment instruction was released and whether the recipient can access the selected route.

Party	First action
Business or client	Check the agreement, acceptance record, payable document, approved amount and transaction reference; send the issue to the owner of the failed step.
Freelancer or gig worker	Gather the agreement, work evidence, invoice where applicable, relevant communications and the payment reference; report the issue through the agreed contact or platform route.
Platform operator, where one is involved	Check the task decision, earnings calculation, payout status and recipient-access conditions; record the support case and its outcome with the task and transaction.

Keep a work dispute separate from a transfer-tracing problem. A rejected task needs an acceptance or dispute decision; a payment marked as sent but not received needs the route and transaction reference checked. For a short payment, compare the approved amount, current quote and any documented deductions before deciding what correction is needed.

Retain the original record and add every escalation, response and adjustment to it. That gives each party a shared trail for the next review and avoids replacing the evidence that explains how the issue began.

Conclusion

Reliable freelancer and gig-worker payments start before money moves. Identify the work arrangement and responsible parties, agree the scope and payable terms, collect the right recipient and document records, then choose a route by the funds the recipient can actually use.

Run each payment through the same record chain: agreed work, acceptance, payable document, approved amount, transaction reference and reconciliation. That chain gives finance a clear release decision and gives both parties a way to locate a delay, short payment or dispute without guessing.

Keep local status, tax and invoice requirements tied to the country and arrangement they govern. When the workflow grows beyond what a team can reconcile from separate files and messages, move the engagement, approval and payment records into a shared process that preserves the evidence behind every decision.

How to pay freelancers and gig workers: a business guide