Skip to main content
Gruv.ai logo
Merchant of Record for business

Clear each contractor invoice before you collect payment

Keep the contractor, contract, client, required checks, approval status, and payment updates with the invoice. Finance can see what needs attention before sharing a payment link.

Invoice and contractRequired checksApproval or holdPayment status
The legal seller, markets, currencies, providers, payout methods, and accounting connection are confirmed for each business program.

Give finance the full picture behind each contractor invoice

Put the people, contract, requirements, decision, and payment status in one place instead of chasing the context across email and spreadsheets.

Everything behind the invoice

Keep the contractor, contract, engagement, client, countries, currency, and tax context with the invoice.

Checks before collection

See whether the contractor, client, tax, screening, contract, payout, and corridor details are ready.

A clear approval or hold

Approve the invoice when it is ready, or keep it on hold with a reason finance can act on.

Payment updates for finance

Follow the payment status and keep the available invoice, payment, and ledger references together.

From invoice to payment link

When these checks are part of your program, Gruv keeps the payment link on hold until the required information is ready and any approval is complete.

  1. 1

    Prepare the invoice

    Add the contractor, contract, client, countries, currency, line items, and tax context.

  2. 2

    Check what is required

    Review the contractor, client, tax, screening, contract, payout, and corridor details that apply to the program.

  3. 3

    Approve or explain the hold

    Move a ready invoice forward, or keep the reason and next action visible while a requirement is still open.

  4. 4

    Share the payment link

    After the required checks and approvals are complete, issue the payment link and follow the provider payment updates.

Set the program up before you bill

Merchant of Record programs can differ by market, provider, transaction, and accounting setup. Agree on these details before the first client invoice goes out.

See the full Merchant of Record workflow
  • The legal seller, invoice issuer, and contracted entity
  • Countries, currencies, providers, payment methods, and payout routes
  • Required contractor, client, tax, screening, and contract checks
  • Approval rules, hold reasons, finance exports, and accounting connections

Frequently Asked Questions

What does the business Merchant of Record workflow connect?+
Gruv can keep the invoice connected to the contractor, contract, engagement, client, required checks, approval or hold, and payment status. The exact payment and payout steps depend on the program set up for your business.
What can stop an invoice from moving forward?+
A missing contractor detail, tax decision, payout setup, client verification, screening result, contract, corridor check, or approval can keep the payment link on hold. Finance can see the reason before taking the next step.
Who is the legal seller and invoice issuer?+
Those roles are confirmed in the agreement for each program. They should not be assumed from this page alone because the contracting entity, transaction type, market, and provider setup can differ.
What can finance see on the invoice?+
Finance can see the contractor and client context, the current checks, approval or hold status, payment status, and available finance references without rebuilding the story from separate systems.
Which countries, currencies, and payout methods are available?+
Availability depends on the business program, country and currency rules, provider, and payment corridor. Confirm the markets and methods you need before launch.

Start with one contractor invoice

Bring the client, contractor, contract, required checks, payment method, and finance steps you use today. We'll map what needs to happen before the payment link is ready.

Talk through your billing flow