01
Normalize
Commission sources
Network reports map to one ledger.
Affiliate networks
Impact, CJ, and ShareASale reports in. Clean payouts out.
Your affiliate network pays out in 60 countries, but your ops team still reconciles commissions in a spreadsheet. Gruv normalizes every network report, applies thresholds and holds, validates payees, and ships ERP-ready proof.
Commission recordThreshold rulesERP proof
Operating model
What stays connected from Impact report to NetSuite close
02
Rules
Thresholds and holds
Per-program logic enforced before release.
03
Validate
Payee readiness first
Tax, identity, and method checked early.
04
Export
Proof for finance close
ERP-ready rows with provider references.
Capabilities
What affiliate payout teams keep connected
Six capability areas that keep commission data, threshold rules, payee readiness, and finance proof connected.
Commission ingest
Impact, CJ, ShareASale, Partnerize, and direct affiliate earnings via files, APIs, or connectors.
Threshold rules
Minimum payout, adjustments, clawbacks, and manual holds applied before release.
Payee validation
Incomplete profiles, invalid payout details, and blocked states surfaced before the run.
Reversal & clawback
Reversals tied to the original commission with reason and owner attached.
Affiliate portal
Partner-facing earnings statement with line items, holds, and payout history.
Reporting export
Partner IDs, references, payout statuses, and ERP-ready rows for finance close.
How it works
From commission file to paid partner
Commission reports from Impact, CJ, or Awin become a closed payout batch in five steps: connect, threshold, validate, release, and export.
gruv.app › affiliates › source
affiliatessourcesadd
ValidatingConnect commission source
ProviderImpact
Accountacct_94f1
API tokenimp_live_xxx
Webhook secretwhsec_a82
MarketsUS · CA · GB · AU
Sync cadenceDaily 02:00 UTC
Source checks
Auth · OAuth handshake
Currency normalization rules
Commission event mapping
First sync · 14 days backfill
Where it works
Affiliate program models running on Gruv
Same payout backbone across performance networks, SaaS partner programs, and direct affiliates.
Performance network
Pay publishers from Impact and CJ commission reports
A performance network pays 2,000 publishers from CPA, CPL, and revenue-share commissions. Reports arrive from Impact, CJ, and three direct advertisers.
- Network reports normalized per publisher
- Threshold and clawback rules applied per program
- Per-publisher statement portal kept current
Affiliate operations scenario
Affiliate program founder
We normalized commission reports from four networks in a spreadsheet every month. Now Gruv ingests them, applies thresholds, and exports the close to NetSuite.
Scenario: Founder - Performance affiliate network
Frequently Asked Questions
We already use Tipalti for affiliate payouts. Why add Gruv?+
Tipalti executes transfers. You still build commission normalization across Impact, CJ, and direct networks, plus threshold rules, payee readiness, hold management, and the NetSuite export. Gruv owns that operating layer.
Can we start with commission CSVs and wire up APIs later?+
Yes. Most affiliate teams start with network report files, prove the threshold and validation record, then add APIs and connectors once the first batch runs clean.
How do thresholds, clawbacks, and fraud holds work?+
Threshold rules, clawbacks, review queues, and holds apply before release. Batches include only records ready to move. Held commissions keep their reason, owner, and next action.
Can finance trace a payout back to the original commission?+
Yes. Partner IDs, source references, commission periods, adjustments, payout statuses, and provider references tie what the partner earned to what was paid. Finance exports it all to NetSuite in one close.
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.
Commissions from Impact, CJ, and direct programs normalized, validated, and exported in one workflow.
Many teams start with a narrow launch in weeks.