What counts as a voucher for a payout? The documentation rule most companies get wrong

Every expense in your books needs a voucher: the supporting document that proves the booked line is real. Accountants have a word for it in every language (bilag, Beleg, justificatif), and auditors have one question about it: show me.

For classic purchases this is easy, because the supplier sends an invoice. For payouts it gets murky fast: what's the voucher when you pay a freelancer who never invoices? A creator whose earnings you calculated? Forty contractors in one batch? Companies either over-engineer this or quietly hope nobody asks. The rules are simpler than both reactions suggest.

What a voucher must do

Jurisdictions phrase it differently, but a valid voucher consistently needs to:

• identify who paid whom,
• state the amount, currency, and date,
• say what the payment was for,
• be linked to the booked line (a reference the booking carries), and
• be retrievable for the statutory retention period, commonly 5 to 10 years.

The right document depends on who you paid

• A business supplier → an invoice. Either the supplier's own, or a self-billing invoice you issue on their behalf under a self-billing agreement, with reverse-charge VAT wording when it crosses borders.
• An individual who doesn't invoice (freelancer, creator, affiliate) → a payment statement the payer produces: both parties' identities, amount, date, and description. This is a long-established, legitimate document type, not a workaround.
• The payout fee → the provider's fee receipt, with its VAT treatment stated.

One payment, one document. A bank confirmation alone is not enough (it proves money moved, not what for), and a blockchain transaction hash alone isn't either; the voucher is the business document about the transfer.

The myth: "it has to be attached inside our accounting system"

It doesn't, in most jurisdictions. The legal requirement is that the booking references the voucher and that the voucher is retrievable for the retention period, not that a PDF is physically stapled to every ledger line. Think of bank statements: nobody attaches the bank's internal records to each booked line; the booking references the statement, and the bank archives it. Attaching documents in-system is preferred practice (audits go faster), but reference + retrievable archive is the actual rule.

What auditors do care about, intensely, is numbering. Vouchers should carry sequential references from a gap-free series. A gap suggests a document (and possibly a payment) that vanished, and every gap is a question you'll answer years later.

How this works in Kiip

Kiip's payout tool treats documentation as part of the payment, not an afterthought:

• The moment a payout completes, the correct document for that recipient type exists: payment statement, self-billing invoice, or the supplier's own uploaded invoice.
• Every document carries a sequential, gap-free reference (KP-2026-000041) that also appears on the corresponding line of your monthly accounting import, which makes the booking-to-voucher link mechanical.
• Documents are durably archived and retrievable at any time; recipients see their own copies too.
• Prefer attachments in-system? The monthly ZIP contains the period's documents with filenames matching the import references, so you can bulk-attach in minutes instead of per payout.

You remain the payer and the keeper of your own books; the tool guarantees that for every booked line, the show me answer already exists.

This article is general information, not accounting advice. Retention periods and formal requirements vary by country, so confirm specifics with your advisor.

Want the whole monthly routine? Read How to pay people and companies anywhere in the world, or your accountant can start with the accountant's guide.