Skip to main content
Gruv.ai logo
Compliance Checklist

Free Cross-Border Compliance Checklist

Generate a corridor-specific compliance checklist covering KYC, sanctions screening, tax documentation (W-8BEN, W-9, certificate of residence), and invoice language. Copy, print, or export before release.

Corridor-awarePrint + PDFKYC + tax

Payment details

Set the corridor and payment type to generate a checklist.

Informational only

Use this checklist as a starting point and verify requirements with local compliance experts.

Scope first

A checklist is only as good as its scope line

A checklist turns a judgment into a set of conditions that have to exist before money moves, which is what makes it useful to somebody who was not part of the original decision. Its scope is therefore part of the content. The corridor it was written for, the amount band, the kind of payment and the date it was assembled all change which items belong on it, and a list that carries none of that reads as universal. That is how a checklist built for one market ends up governing a payment to a country whose documentation requirements have nothing in common with it.

The same corridor produces different lists, and what moves an item is worth naming. Amount bands move the verification, because institutions and payer programs set thresholds where further identity evidence attaches, so one payee clears at $900 and stalls at $9,000 with nothing about them changed. Payment type moves the tax documentation, since a services fee, a royalty and a commission are three characterizations and the withholding question follows the characterization rather than the payee. Whether the payee is a person or a company moves both the identity evidence and the signature you need on file. A list that records none of those assumptions cannot be reused safely.

Providers run their own screening and onboarding, against their own obligations, which is where the assumption that compliance is handled comes from. What stays on your side of the line is the part that touches your counterparty: knowing who you are paying and keeping the evidence for it, collecting the tax documentation before the payment rather than after, putting the required content on the invoice, and holding the record for as long as your own jurisdiction requires. A provider decision is no defense for the entity that made the payment.

Assumptions and sources

How the checklist is assembled

Your five answers select from a set of checklist lines written for this page. The result is a starting list of things to confirm rather than a set of requirements.

What it assumes

  • The payer country, payee country, payment type, entity type and amount band together select the lines shown.
  • Four lines appear on every checklist: collect full legal identity details, validate the bank account, document the payment purpose, and review AML reporting thresholds for both jurisdictions.
  • The one country rule is a United States payer paying elsewhere, which adds the W-8 and treaty lines. Any other pair produces the same list.
  • Individual and business payees pull different identity lines.
  • Amount bands are broad ranges used to surface the heavier diligence lines.

What it leaves out

  • Country-specific reporting thresholds and the forms that go with them.
  • Licensing questions, which decide whether a payment flow is available to you before diligence begins.
  • Sector rules, sanctions screening and the enhanced diligence some counterparties require.
  • Any confirmation that a completed checklist is sufficient. It is a prompt list.

Where the numbers come from

The checklist lines
Our own assumptionWritten for this page from common cross-border payment diligence steps. No regulation is quoted, and none of the lines is a legal requirement as stated.
The country and amount band lists
Our own assumptionEight countries and four bands chosen to cover common cases. The bands add heavier diligence lines above $10,000 and above $50,000, and the countries change the list only when the payer sits in the United States.

Assumptions and sources checked 5 September 2026. Published figures move on their own schedule, so confirm anything you rely on against the authority that issues it.

Process

How it works

  1. 01

    Pick the corridor

    Sender country, recipient country, amount band.

  2. 02

    Flag the use case

    B2B services, royalties, payroll, affiliate commission.

  3. 03

    Get the checklist

    KYC items, sanctions touchpoints, tax docs, invoice language.

  4. 04

    Print / copy / export

    Share with ops and finance before release.

Frequently Asked Questions

Does this checklist cover every jurisdiction?+
It provides a baseline checklist for common cross-border payment corridors. Verify edge cases with local compliance advisors.
Can I export to PDF?+
Yes. Use the Print / PDF button to generate a PDF via your browser.
Does it include treaty benefits?+
The checklist flags treaty considerations but does not calculate rates. Use the Tax Treaty Checker for rate comparisons.
How should I use this checklist?+
Prepare a baseline review before payout release. Final obligations depend on corridor, recipient type, amount, and local rules.
Can I share the checklist?+
Use the copy checklist button to share internally.

Checklist built. Checklist enforced

Turn the checklist into a payout-release review for KYC, sanctions, tax documents, invoice language, and corridor-specific requirements.

Many teams start with a narrow launch in weeks.