Responses

1. Refund Transaction Entries: OPEN
2. Miscellaneous: DONE

1. Refund transaction entries

<aside> ✏️

The current transaction CSV export does not clearly define how refunded transactions are represented, which makes it difficult (and risky) to use as a source of truth for accounting, reconciliation, and audit purposes.

There are no documented field definitions explaining how refunds are represented or how totals should be interpreted.

This isn’t a generally accepted U.S. accounting practice where original transactions and refunded amounts are combined into a single line in reporting without showing the refund separately as its own financial event.

</aside>

Current Behavior

A $100 transaction on 1/1 later refunded on 2/1 still shows $100 in the Amount column with status “Refunded”

Ref #	Amount	Transaction Date	Payment Captured	Refunded Date	Status Friendly
AAAAAA	$100	1/1	1/1	2/1	Refunded
BBBBBB	$320	1/2			Succeeded
CCCCC	$80	1/2			Succeeded
TOTAL	**$500

Monthly Report** Jan revenue: $??? Feb revenue: $??? (How is the sales be reported?) | | | | | |

In the exported CSV:

Refunds are indicated via a status field (e.g., “Refunded”) and a Refunded Date
The Amount column remains positive
Refunds are not represented as separate transaction rows
Field definitions are not documented

Problems This Creates

Ambiguity about whether refunded transactions are included or excluded in totals
No explicit refund amount (assumes full refund)
Refunds are represented as state changes, not financial events
This issue affects users who rely on CSV exports for manual accounting, third-party systems, internal reporting, or audit support — not just users who import directly into QuickBooks.
Not audit-friendly and increases risk of revenue misstatement, especially for nonprofits

As a result, accountants and CPAs cannot rely on this export without manual interpretation or external reconciliation.

Ambiguity

Does January revenue include the $100?
Is the refund booked in January or February?
Was the money already deposited before refund?

Who This Impacts: This affects users across both nonprofit and for-profit organizations, including:

Bookkeepers and accountants preparing monthly closes
Controllers and CFOs reviewing revenue and refunds
Finance committees and board members
Auditors and compliance reviewers
Fundraising and marketing teams relying on net totals

Accounting common and standard practices

Improvement Request (changes in blue)

Ref #	Amount	Transaction Date	Payment Captured	Status Friendly	Transaction Type
AAAAAA	$100	1/1	1/1	Succeeded	Donation
BBBBBB	$320	1/2		Succeeded	Donation
CCCCC	$80	1/2		Succeeded	Donation
AAAAAA-R1	($100)	2/1	2/1	Refunded (or Refund_Succeeded, etc)	Refund
TOTAL	**$400

Export refunds as separate rows with:

Transaction type (Payment / Refund)
Refund amount as a negative value
Link to original transaction ID
Clear event dates

Responses

1. Refund transaction entries

Current Behavior

Accounting common and standard practices

Why This Matters