Affiliate accounting: turning confirmed conversions into invoices you can pay

Paying affiliates is where an otherwise tidy program gets messy. The tracking can be perfect, the attribution airtight, and still, at the end of the month, someone is in a spreadsheet cross-referencing conversion exports against payout rates, worrying about which sales were confirmed, whether a refund needs clawing back, and whether an affiliate cleared their minimum. Affiliate accounting is the discipline of turning confirmed conversions into invoices you can actually pay — accurately, repeatably, and with a paper trail. This guide explains how it works, and why the details that seem fussy (thresholds, currencies, clawbacks) are exactly the ones that keep partners trusting you.

Self-billing: you write the invoice

Most affiliate programs run on a self-billing model, and it is worth being clear about what that means, because it surprises people new to the space. In a normal supplier relationship, the supplier sends you an invoice. In affiliate marketing it is the reverse: the program generates the invoice for the affiliate — "we owe you X for these conversions in this period." The affiliate doesn't have to produce a document; you produce it on their behalf and it becomes the record of the debt.

One thing self-billing does not do is move money. The invoice is a document and a status tracker, not a payment rail. You still pay through your own bank transfer, PayPal, or accounting software; the accounting layer records that the payment happened and against which invoice. Keeping the money movement outside the platform is deliberate — it means the program never holds funds, and your finances stay in the tools your finance team already trusts.

What an invoice is built from

An affiliate invoice sums the payout owed on every conversion that meets three conditions, and each condition exists to prevent a specific kind of error.

First, the conversion must be confirmed. Pending, cancelled, rejected, test, and duplicate conversions are never billed. This is why a disciplined conversion review process matters so much: the review queue is what turns raw pixel fires into the confirmed set that accounting draws from. Bill from unreviewed data and you pay for fraud and duplicates; bill from confirmed data and you pay for real business.

Second, the conversion must fall inside the billing period — usually a calendar month, though a custom window works too. Third, it must be in one currency. An invoice covers a single currency, so if an affiliate earned in both euros and dollars in the same period, they get one invoice per currency and amounts are never silently converted. That restraint protects everyone from exchange-rate disputes.

The payout figure on each line is the resolved amount — the number after revenue-share percentages, campaign and sub-ID overrides, and caps have all been applied. It is the same figure the affiliate sees in their own reports, which is what keeps the invoice from ever contradicting what a partner already believes they earned. The mechanics behind that resolved number are covered in the contracts and payouts guide.

Drafts: recompute until you're ready

An invoice starts life as a draft, and a draft is fully recomputable. You can regenerate it as often as you like and it always reflects the latest confirmed conversions — so if three more sales get confirmed the day after you generated it, regenerating picks them up. Nothing is frozen until you decide to freeze it. For programs with many partners, generating drafts in bulk across every affiliate with confirmed conversions in a period turns month-end from a day of work into a single action, with a report of which generated cleanly and which need a second look.

Adjustments, thresholds, and VAT

Real payouts are rarely just "sum of conversions." Three mechanisms handle the exceptions, and all of them apply while the invoice is still a draft.

Adjustments let you add a manual line: a bonus for a partner who hit a target, or a clawback — a negative line — for a conversion that later refunded. Each adjustment records who added it, so the history is auditable. Clawbacks are the honest way to handle refunds after an invoice from a prior period is already closed: rather than reopening old records, you net the correction onto the next invoice.

Payment thresholds solve a small but real problem: it isn't worth paying (or a partner receiving) tiny amounts. Set a minimum, and any invoice below it is held — its total shows as zero and the balance carries forward, automatically rolling into the next period until it finally clears the threshold. The affiliate accumulates until they're worth paying, and nobody chases a two-dollar transfer.

VAT, where it applies, is added on top at your program's configured rate. Notably, VAT never applies to a held, below-threshold invoice — because nothing is actually being paid yet. These small correctnesses are what keep your accounting defensible when someone audits it.

The lifecycle: draft, issue, pay

Once a draft is right, you issue it. Issuing freezes the invoice: it receives a permanent, sequential invoice number and its amounts lock. This is the moment the number becomes a promise. After issuing, a later change to a conversion's status never silently moves the invoice — if something needs correcting, you do it explicitly with a clawback on the next one. That immutability is what makes issued invoices trustworthy as financial records.

From there the states are straightforward. Mark paid records that you have paid it, with an optional payment reference for reconciliation. Void cancels a draft or an issued invoice — but never a paid one, because you can't un-pay money you've sent. And issued invoices can be emailed to the affiliate as their statement, which they can also see in their own portal.

Who sees what

Visibility follows role, and the boundaries matter. Administrators see every invoice. A staff member scoped as an account manager sees and acts on invoices only for the affiliates they manage — the same book-of-business boundary that governs managing affiliates generally. Affiliates see only their own issued and paid statements in their portal: never drafts, and never your revenue or margin. A partner should be able to verify what they were paid without ever seeing what you kept.

Currencies, periods, and the discipline they enforce

The constraints that feel restrictive at first — one currency per invoice, a fixed billing period, confirmed conversions only — are each doing quiet work to keep your books defensible. One currency per invoice means you never bury an exchange-rate assumption inside a total a partner might later dispute; if they earned in two currencies, they get two clean documents and settle each in its own money. A fixed billing period means every invoice covers a knowable window, so a partner can reconcile it against their own records line by line rather than trusting a rolling, ambiguous total. And billing from confirmed conversions only means the invoice reflects money you've actually decided to honor, not raw pixel fires that might turn out to be duplicates or fraud.

None of this is glamorous, but it's the difference between an accounting layer a finance team trusts and a spreadsheet a finance team dreads. The resolved payout figures flow from the same contracts and payouts logic that governs every conversion, so there's a single, traceable path from "a sale happened" to "here's the invoice line for it" — and when someone asks why a number is what it is, you can answer without archaeology.

Why the fussy details are the point

It is tempting to treat affiliate accounting as a spreadsheet job — export conversions, multiply by rate, pay. But the spreadsheet has no concept of "confirmed only," no carry-forward for sub-threshold balances, no clawback trail, no per-currency discipline, and no immutable issued record. Those are exactly the things that cause disputes, overpayment, and the slow erosion of partner trust when a number changes after the fact.

An accounting layer built into the platform draws directly from the same confirmed, resolved figures your partners already see, which means the invoice and the affiliate's own view can never disagree. That single fact removes most of the friction from paying partners. If you want to see invoices generated from live confirmed conversions — thresholds, clawbacks, and all — the reporting feature overview shows the numbers accounting draws from, and a demo will run a full billing cycle on your own data with you.