Easy Affiliate (from Caseproof, the MemberPress team) tracks affiliates, transactions, payouts and clicks in its own tables (eafl_affiliates, eafl_transactions, eafl_payouts, eafl_visits and related). The built-in reports cover the basics well: a transactions list, an affiliates list, a payout history and a few per-affiliate summary stats. What they don't do is let you combine those into a single editable cohort with partner, status, amount and payout date filterable together in one pass.

SleekView reads the Easy Affiliate tables and joins transactions with affiliates and payouts so each row pulls from the right columns. A transactions view shows transaction_id, affiliate name, type, amount, status and created_at in one row, sortable by any column and filterable in combinations the default reports don't surface. A payout queue view filters to unpaid transactions, sums the amount column for the next cycle and lets a payout admin bulk-flip them to paid after the actual transfer.

Inline status edits route through Easy Affiliate's CRUD layer where supported, so payment hooks keep firing for downstream MemberPress integrations and accounting workflows. Bulk status flips across a saved filtered view run through the same audit and automation triggers as a per-row edit.

Easy Affiliate already collects everything a program needs: who referred whom, which transactions paid, who got the commission and which ones got rejected. The built-in reports cover each piece well on its own screen, which is fine for spot checks and unhelpful for the cross-cutting questions that actually drive program decisions. A table that joins transactions with affiliates and payouts turns separate reports into one workspace, where filters combine status, partner and date in a single click and bulk-mark-paid happens in one pass instead of one transaction at a time.

Same Easy Affiliate tables, same status flags, completely different operational posture. The table renders the data the plugin already maintains as a queryable, editable surface, which is the difference between three good reports and one program workspace.