How to Reconcile Revenue Across Multiple Payment Providers

1. Define Which Revenue Question You Are Answering

Choose whether you are reviewing customer payments, money arriving in the bank, or marketing credit. Those are related records, but they are not interchangeable. A payment can happen this week, be refunded later, and settle to the bank in another batch after fees. Adding the payment and its payout counts the same money twice.

For this workflow, the starting measure is completed payment value less the included refunds. Record the website or store, period, timezone, currency, tax treatment and export time beside it. Keep a separate provider-to-bank reconciliation for settlement, fees, disputes, reserves and other adjustments.

Stripe’s payout reconciliation documentation shows why a bank deposit needs its own review: an automatic payout settles a batch of transactions, with itemized payment, refund, fee and other balance entries. Its payout reconciliation report is intended for automatic payouts; Stripe directs manual-payout users to the balance report. A website’s net-revenue chart is not a substitute for either process.

Start with a short, closed period you can inspect. Keep the original exports. An unavailable report is a coverage gap, not a measured zero. If a provider connection failed halfway through an import, a smaller total does not establish that the business made fewer sales.

2. Inventory Each Provider and Its Available History

In Attriboo, choose the website, open Setup and expand Connect your payment provider. You can connect more than one supported provider to the same website. An owner or admin should follow the account’s actual connection instructions and check the result in that workspace; the public example’s connected state does not authorize or verify your account.

Make a coverage inventory before comparing totals. The current connections do not all start at the same date, and a successful connection is not proof of unlimited backfill. Use the provider guide for the exact supported checkout route and check the recent import result.

Stripe’s import checks up to 1,000 Checkout Sessions and 1,000 paid invoices per run. It does not import historical refunds, and standalone PaymentIntents outside Checkout or Billing are not covered. Polar’s current import is bounded to 1,000 orders; Lemon Squeezy’s is bounded to 1,000 orders and 1,000 renewal invoices. Treat those as limits to verify, not a promise that every account’s last 90 days is complete.

If you switched billing services, write down the migration date and which provider still handles existing subscriptions or late refunds. A new provider’s connection does not automatically replace the old provider’s history. Keep the operational handoff explicit instead of treating a change in provider as a marketing result.

3. Check One Payment and Refund From Each Provider

Compare a small set of known records before relying on the aggregate. Use authorized exports or a provider-supported test environment where appropriate; there is no need to charge a real customer just to follow this guide. Keep keys, customer emails and other private information out of public screenshots and this worksheet.

1. Locate a completed payment and confirm its provider, account, reference, currency, amount and relevant date.
2. Compare the same record in Attriboo’s recorded payments. Check that it belongs to the intended website.
3. Locate an existing refund and inspect whether the connector represents it as an individual event or an updated cumulative refund row.
4. Compare included taxes and refund treatment before choosing the amount you will use in a cross-provider review.
5. Retain the export time and any unresolved exception. Do not change the source ledger just to force two totals to agree.

Amount definitions can differ even when both rows say USD. Attriboo’s Polar and Lemon Squeezy connectors record before-tax order amounts. Stripe’s supported payment paths use the paid Checkout or invoice amounts. Check how tax is included in those provider records before treating their combined value as a reconciled before-tax total.

Lemon Squeezy’s order reference documents separate total, tax, currency and refunded amounts. Polar’s order response likewise distinguishes net, tax, total and refunded amounts. Use the actual fields and the connector’s treatment rather than choosing whichever provider dashboard number is easiest to copy.

Refund history deserves a separate check. Some Attriboo connectors maintain a cumulative refund row for an order or charge, so a later partial refund can update an existing amount. An import may also expose the latest refund state rather than every historical refund event. Keep an as-of export for a period close and investigate changed historical totals; do not assume every connector supplies an immutable event-by-event refund ledger.

Keep original currencies separate. Attriboo does not automatically normalize mixed payment currencies into a reconciled reporting currency. A website currency label is not evidence that foreign-currency records were converted. Review currency fields in the underlying payment records before reading a combined dashboard amount, and use a separate finance workflow if you need a documented exchange-rate conversion.

4. Review Migrations and Possible Duplicate Business Orders

Distinguish repeated delivery of one provider event from the same business order appearing through two systems. A webhook retry should not become a second sale. A storefront order and its processor payment can also describe one purchase, but their different references do not prove that automatically.

Attriboo stores a transaction using its website, provider and external reference. Re-delivery of that same supported record can update the existing transaction. That protection does not automatically merge a Shopify order with a Stripe payment, or a sale copied into a different provider during migration. Cross-provider business-order overlap needs its own review.

For example, if an order is represented by both a store connector and a processor connector, compare the business-order reference and payment evidence before adding the amounts. Two equal payments on the same date might still be genuine separate purchases. Equal amounts alone are not a safe deduplication rule.

Keep the provider and account beside every reference. A customer moving from Stripe to Polar can receive a new customer or subscription ID. That does not establish a newly acquired customer or a new marketing touch. Reconcile the migration against the business records and distinguish initial charges, renewals, prorations and refunds.

When you find overlap, record which system is authoritative for the affected order and how the exception will be resolved. Do not issue a customer refund, delete a genuine payment or disconnect a working integration just to make an analytics percentage look cleaner.

5. Review Website Revenue Before Comparing Source Credit

Once you understand the compatible payment scope, open Dashboard and confirm the website, dates, timezone and Credit setting. Under the summary cards, open Payment Match to inspect linked and unlinked payments and the connected provider statuses. A payment can count in recorded revenue without a matching visit; that gap matters when you discuss marketing credit.

Open Money → Follow the money and keep All traffic selected for the website-wide comparison. Read Sales, Refunds and Net together. The chart’s Channel and Source controls describe marketing activity; they are not payment-provider filters. Selecting Google Ads does not select Stripe, and selecting AI search does not select Polar.

Then inspect recorded source credit for a defined marketing question. Keep the Credit rule and look-back fixed for the initial comparison. Changing the attribution rule redistributes eligible credit; it does not repair missing payment history, convert currencies or remove a duplicate business order.

Importing old payments does not recreate old website visits. A later valid match can improve attribution when the required recorded history exists, but it cannot reconstruct every earlier source or device. Keep payment reconciliation separate from visit coverage and attribution confidence.

6. Keep Currency Totals and Exceptions Visible in the Worksheet

Use this small worksheet to review supplied records after aligning their amount basis. Keep the tab-separated header and enter one row per payment or refund event, with a distinct event reference. It retains the provider, account and reference, groups compatible currencies, and flags repeated keys without silently deleting rows.

In the example, Stripe contributes USD 100 of payments and USD 20 of refunds, for USD 80. Polar adds USD 80, bringing the entered USD net to USD 160. Lemon Squeezy contributes EUR 50 less EUR 5 of refunds, for EUR 45. Keep USD 160 and EUR 45 separate; adding them as 205 would discard their units.

The worksheet supports USD, EUR and GBP with up to two decimal places, and JPY with no fractional units. Other currencies need their own ledger. Paste amounts in major currency units, not raw API integers. Stripe’s currency documentation explains that API amounts use currency-specific minor units, so a value copied straight from an API response can be misread by a spreadsheet or manual form.

A repeated provider/account/reference key keeps the review unverified; all entered rows remain visible. The tool cannot determine whether records from different providers describe the same business order. Mark suspected overlap when appropriate and resolve it against authorized records. It does not connect accounts, certify completeness, convert exchange rates or reconcile bank settlements.

7. Close the Review With an Owner and a Next Check

Save the scoped provider exports and write an exception list: missing history, incomplete import, currency mismatch, tax-basis difference, repeated reference, possible cross-provider overlap or unmatched visit. Put an owner and review date beside each unresolved item. A total with an explained gap is more useful than a forced match.

On the next review, use the same definitions and compare the new as-of export with the retained one. Investigate new refunds and migration-related changes before presenting a trend as a marketing outcome. If the question is recurring performance, separate renewal payments and subscription status from the initial-purchase view.

Use Attriboo to inspect recorded website revenue and its marketing credit after these scope checks. Use provider and accounting records for settlement, fees and financial close. A repeatable marketing report should carry the payment coverage and known exceptions beside its recommendation.

Common questions