Skip to content

Payment Settings

The Payment Settings screen controls how PartnerPortal handles revenue, commissions, approvals, exports, and whether the payments tools are visible across the portal.

Open it from Portal Setup → Payment Settings.

This section applies across your whole commission workflow, whether commissions are created manually or on a schedule.

Set the portal currency here before your portal starts collecting commission or revenue data.

Once your portal already has money data or connected payment or accounting integrations, currency changes may be locked.

PartnerPortal supports two status models:

  • Modern: Needs Approval, Approved, Do Not Pay, and Paid
  • Legacy: older statuses such as Pending, Scheduled, Processing, and Complete

Modern statuses are usually the better fit for export-based finance workflows.

When this setting is enabled, new commissions start in Needs Approval so your team can review them before payout.

This setting matters most when:

  • your portal uses the modern status model
  • your payout workflow happens outside PartnerPortal
  • finance or ops wants an approval step before export or payment

This section stores the accounting fields that should travel with exported commissions.

Examples include:

  • Expense Account
  • Tax Code
  • Class
  • Location
  • Department
  • Tracking Category names and values

If your team exports commissions into systems like QuickBooks, Ramp, or BILL, setting these defaults once here reduces cleanup later.

Use this section when your portal wants PartnerPortal to store revenue from Stripe or QuickBooks inside the app.

When capture is enabled:

  • Stripe charges and refunds or QuickBooks payments appear on the Revenue page
  • your team can review and correct that revenue inside PartnerPortal
  • the in-app revenue ledger becomes available as a commission source

Revenue capture handles new incoming records. Older history usually needs a manual import or backfill.

If your team started capturing revenue after activity already existed in Stripe or QuickBooks, use the import tools from the Revenue page.

If your team needs to clear the in-app revenue ledger for the portal, this section also exposes the destructive delete action for captured revenue.

That action removes captured revenue records, but it does not automatically disconnect the integration or turn capture off.

Older docs may call this the Commission Scheduler. In the current app, this section is named Commission Generation.

This is where PartnerPortal turns eligible revenue into commission records on a schedule.

Turn this on when you want PartnerPortal to create commissions for you automatically.

If it is off, your team can still create commissions manually from the Commissions page.

This setting decides which revenue source powers scheduled commission generation.

  • Legacy reads directly from Stripe or QuickBooks when the scheduler runs
  • In-App Revenue generates commissions from the revenue already stored on PartnerPortal’s Revenue page

For many portals, In-App Revenue is the clearer workflow because your team can review the revenue before commissions are created.

This part controls the timing rules:

  • frequency: monthly, quarterly, or in some older portals yearly
  • start date: when the cycle starts for yearly schedules
  • payout delay: how long PartnerPortal waits before revenue becomes eligible for payout
  • lead expiry time: how long won leads can stay inactive before expiring while the schedule is active
  • payment type: manual or an enabled payments integration such as PayPal

The Commission Generation section in Payment Settings.

Use the run-now button when you need a one-time generation pass for the most recently completed commission period.

This is useful after fixing revenue, updating mappings, changing settings, or connecting an integration after the normal run should have happened.

Use this only if your portal does not run on partner commissions.

Disabling the payments interface hides Revenue, Commissions, and other payment-related sections across the portal, and stops scheduled commission generation.

Before you can disable payments, your portal must have:

  • Partner Tiers disabled
  • Commission Generation disabled
  • no Accounting integration enabled
  • no Payments integration enabled

Once those prerequisites are satisfied, you can turn off the payments interface from the same Payment Settings screen.

The Disable Payments Interface section in Payment Settings.

If you want the operational steps that go with these settings, see How to Track Revenue, How to Manage Commissions, and How to Pay Commissions.