Skip to main content
Gruv.ai logo
Affiliate networks

Move approved commissions into a payout batch you can reconcile.

Bring the affiliate, approved amount, currency, commission reference, and program context into one reviewed batch. Keep item outcomes ready for support and finance.

Commission referenceItem-level reviewFinance export
Operating model

What stays connected from commission file to finance close

01
Reference
Approved commission
Partner, program, period, and source stay attached.
02
Import
Payable batch
Beneficiary, amount, and currency are explicit.
03
Review
Item-level status
Reason details guide exception follow-up.
04
Export
Result for finance close
Structured rows carry payout outcomes and references.
Capabilities

Keep approved commissions connected to the payout result

Keep the payable inputs, affiliate references, item states, and export result connected without pretending the payout batch calculates commissions for you.

Approved commission input

Start from the partner amount and program result your commission process has already approved.

Program context

Keep the program, earning period, and source references in batch or item metadata.

Known beneficiary

Connect the affiliate record to the beneficiary used for the payout instruction.

Item-level review

Use payout state, reason codes, and explanations to investigate the row that needs attention.

Stable references

Retain external and provider references for support and reconciliation.

Finance export

Export partner IDs, commission references, payout states, and provider references for close.

How it works

From approved commission to traceable payout result

The payout workflow begins after your program has approved the commission amount. From there, five steps carry the payable rows through review and close.

  1. 1

    Prepare approved commissions

    Start from the commission result your program has already approved. Keep the affiliate, amount, currency, period, and source reference together.

  2. 2

    Import one payable batch

    Upload CSV rows or send structured items with a beneficiary, amount, currency, external reference, and optional program metadata.

  3. 3

    Review every item

    Check the imported rows before processing. Held or failed items keep their status explanation and reason codes visible for follow-up.

  4. 4

    Process the ready batch

    Move the reviewed batch into the enabled payout workflow while retaining the idempotency key and item references that prevent duplicate instructions.

  5. 5

    Close with the result

    Export the batch rows with payout states and references so finance can reconcile the result in its own accounting process.

Choose your pattern

Choose the commission pattern your program needs to support

Your commission system owns the earning calculation. Gruv begins with its approved payable result.

Performance network

Pay publishers from approved performance commissions

Use this pattern after your tracking or commission system has approved each publisher amount and its source references.

  • Retain publisher, program, and period references
  • Carry one approved amount into the payout row
  • Export the payout outcome for reconciliation

SaaS partner program

Pay channel partners from referrals and MRR share

Use this pattern after the partner system has finalized referral, recurring-revenue, expansion, adjustment, and threshold rules.

  • Keep the referral or revenue-period reference
  • Preserve the approved amount and currency
  • Match payout results to partner earnings

Retail affiliate

Pay affiliates from order commissions with returns and holds

Use this pattern after the commerce and commission systems have applied returns, promotions, adjustments, and program holds.

  • Retain order or commission references
  • Review affected affiliate rows by item
  • Export status and provider references

Finance affiliate

Pay introducers from approved leads and funded accounts

Use this pattern only after the owning system has confirmed eligibility, approved the commission, and recorded the relevant application or account event.

  • Carry the approved source-event reference
  • Keep program review ownership explicit
  • Match payout result to the commission record

Four decisions to make before the first affiliate batch

Which system approves the commission?

Name the source of truth and the stable affiliate, program, period, and commission references that should reach each payout row.

Which rules run before import?

Document thresholds, carry-forwards, adjustments, clawbacks, and review holds in the commission process that produces the payable file.

What makes an affiliate payable?

Confirm beneficiary setup, payout method, required program checks, and the owner who resolves an incomplete row.

What does finance need back?

Agree on the source reference, payout state, provider reference, reason detail, and export columns needed for reconciliation.

Frequently Asked Questions

Does Gruv calculate affiliate commissions?+
Your tracking or commission system remains the source of truth for attribution, eligibility, rates, thresholds, adjustments, clawbacks, and the approved amount. Gruv starts from that payable result.
Can we start with an approved commission CSV?+
The current batch workflow accepts CSV text or structured items. Each row needs a beneficiary, amount, and currency; external references, memos, and metadata can retain commission context.
Where should thresholds and clawbacks be applied?+
Apply commission rules in the system that owns the affiliate program, then pass the approved payable amount and source references into the batch. Do not rely on the payout batch to recalculate commissions.
Can finance trace a payout back to the original commission?+
Use the affiliate or beneficiary ID, external source reference, commission period metadata, approved amount, payout state, and provider reference to match the two records.
What do we validate before expanding to more networks or countries?+
Source mappings, threshold rules, hold policies, payee readiness, payout methods, launch markets, support ownership, and ERP export fields.

Pay your affiliates. Close your books.

Start with one approved commission file. Map its partner references, item-review path, and finance result before expanding.

Bring one approved commission file and the finance columns you need back.