Paddle Revenue sync

Sync Paddle Revenue into reviewed commission and royalty calculations

Allocora imports customer-owned Paddle Revenue data separately from Allocora billing, then turns paid transactions, completed transactions, and adjustment evidence into governed calculation inputs.

Start Free View Pricing

Revenue Sync Snapshot

Provider

Paddle

Revenue source

Transactions

Paid

Or completed

Adjustments

Tracked

Approved/reversed

Output

Evidence

Before payout

Direct Answers

What teams usually need to know first

What does the Paddle connector import?

Allocora pulls paid or completed Paddle transactions and approved or reversed adjustment evidence, then dedupes accepted provider events into immutable revenue records.

How are Paddle adjustments handled?

Adjustment pulls are status-polled and deduped because Paddle does not expose an updated-at filter for the adjustments list API.

Is this Allocora billing?

No. Paddle Revenue sync is for customer-owned revenue data. Allocora subscription billing remains a separate Paddle integration.

Workflow

From provider revenue to reviewed payout inputs

Allocora keeps payment-processor revenue separate from payout execution. The connector creates governed inputs for rules, calculations, statements, and exports.

01 Connect a customer-owned Paddle Revenue API key from the self-serve Integrations page.
02 Run a normal sync or full-history sync; queued jobs use source-level cursors and overlap protection.
03 Review skipped rows for zero amount or currency mismatch before calculations depend on them.
04 Map Paddle product identifiers to internal products and payee rules.
05 Run calculations, inspect adjustment impact, and export statements or rail-ready files after review.