What reports do nonprofits need for payment reconciliation?

Most nonprofits need a transaction-detail report, a payout or transfer report, bank activity, donation-system records, refund and dispute records, and an exception log for payment reconciliation. The exact report names vary by provider. The practical goal is to connect each donation or other payment to its status, any later adjustment, the amount transferred to the bank, and the entry recorded by the organization.

No single report always explains the entire flow. A donation platform may organize gifts by campaign or donor, while a payment provider organizes activity by transaction, balance event, or payout. A bank statement shows the final transfer but usually does not contain every underlying payment. Reconciliation brings those views together without forcing unlike totals to match.

Start with the core report set

Transaction detail

Use an itemized activity report that shows each completed payment and its non-sensitive reference, date, amount, currency, status, and channel. This is the starting point for matching gifts, event payments, membership payments, and other receipts to the nonprofit's own records.

Payout or transfer detail

Use the provider's payout, disbursement, or reconciliation report to identify which payment activity contributed to each bank transfer. Current Stripe and PayPal documentation both distinguish transaction-level activity from reports designed to connect activity with payouts or balance movement.

Bank activity

Use the bank's posted activity to confirm that the expected transfer reached the correct organizational account. Match by transfer reference, date, currency, and amount where available, while documenting timing differences rather than assuming every transfer posts on the activity date.

Add nonprofit records that explain donor intent

Payment-provider reports establish what happened in the payment system, but the nonprofit's donation records explain why the payment was received. Preserve a gift or order identifier, campaign or appeal, fund designation when used, donor-facing receipt status, and the staff-approved accounting category. Keep those fields connected through a stable internal reference instead of relying on a donor name or payment amount alone.

Event registrations, memberships, merchandise, sponsorships, and ordinary donations may share one payment service while requiring different internal treatment. Reconcile each channel separately before combining organizational totals. The nonprofits, donations, and fundraising FAQ hub provides related payment-workflow guidance, and the nonprofit, religious, and membership industry page helps frame broader operating needs.

Keep adjustments visible as separate events

Refunds, reversals, disputes, corrections, and other balance adjustments should remain visible instead of being silently netted against the original gift. Stripe documents refunds as separate balance transactions, and PayPal's current reporting overview lists sales, refunds, disputes, fees, withdrawals, and other activity within reconciliation-oriented reports. The provider's terminology and available fields may differ, so use its current report definitions.

Create an exception log for anything that does not match during the first review. A useful entry identifies the period, source reports, payment or payout reference, expected result, observed difference, owner, next action, and resolution date. Never re-run a payment merely because it is absent from one report. Confirm the account, status, date basis, time zone, and report filters first.

Use a repeatable reconciliation sequence

Define the period. Use the same time zone and documented start and end points across the donation system, payment provider, and accounting workflow.
Confirm source activity. Total completed payments by channel and keep unsuccessful or pending attempts outside completed receipts.
Trace adjustments. Link each refund, reversal, or dispute record to the original transaction without overwriting either event.
Match transfers. Use payout-level detail to connect activity to the amounts posted by the bank. Preserve timing differences and transfers that combine more than one operating day.
Resolve exceptions. Assign each difference to a person, retain the supporting reference, and document the approved correction rather than forcing a balancing entry.
Record review. Save who prepared and reviewed the reconciliation and when the period was closed under the nonprofit's established accounting process.

For a wider explanation of these report boundaries, review the statements, reporting, and reconciliation guide. The merchant statement help center offers additional context for understanding processing records.

Protect donor and payment information

Reconciliation files can contain donor contact details, transaction references, staff activity, and organizational account information. Store exports only in an approved access-controlled location, limit access by job responsibility, and share the minimum information needed for review or provider support.

Do not copy complete card numbers, security codes, bank credentials, passwords, payment tokens, secret API keys, or unredacted account statements into spreadsheets, email, chat, or a general inquiry form. Use masked payment references and the provider's secure support channel. Retention and accounting requirements depend on the organization's circumstances, so the nonprofit should follow its approved policies and obtain qualified professional guidance when needed.

Questions to ask each reporting provider

Which itemized report contains completed payments and their stable transaction references?
Which report connects transactions and adjustments to each payout or bank transfer?
Which date and time zone control each report?
How are refunds, reversals, disputes, and corrections represented?
Can reports be filtered by account, campaign, channel, location, or currency where relevant?
Which export format preserves references without exposing unnecessary sensitive information?
How long are reports available, and how are corrected or regenerated reports identified?

Document the provider's answers beside the exact report name and review date. That prevents one platform's labels from being applied to another and makes later reconciliation easier to repeat.

Build the nonprofit's report map

List every payment and donation channel, name the transaction and payout reports for each one, identify the related bank account and internal donation record, and assign an owner for exceptions. Test the map with a normal gift, a refund, a delayed transfer, and an unmatched record before relying on it for a full close.

Payments Max can help organize payment-reporting questions for a provider discussion without replacing the nonprofit's accountant or professional advisers. Discuss a nonprofit payment workflow

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.