The processing fee is categorized as an income account in your integration, which violates GAAP for nonprofits. It must map to an expense account.

Fee Accounting

Processing fees must always be recorded as an expense — never as negative income — regardless of who pays them.

Why this matters:

The governing principle is gross vs. net presentation under GAAP. Revenues and expenses are separate elements of the financial statements (FASB Concepts Statement No. 6, paragraphs 78–89). Netting an expense against revenue — which is what Givebutter is doing — violates this principle because it understates both gross revenue and gross expenses. The fact that the donor covered the fee doesn't change the nature of the fee: it's a cost nonprofit orgs incur to collect donations, full stop.

Contribution Accounting

Similarly, Givebutter must acknowledge the full contribution amount to donors. The full contribution amount for tax purposes is the contribution amount + the Processing Fee the donor has covered. If a donor contributes $100 and then also contributes $4.30 to cover the fees, the donor's total contribution is $104.30.

Mapping

For my nonprofit, we would want the mapping to provide a separate revenue option for the Contribution (contribution and donor-covered processing fee) and separate expense option for the Processing Fee (cost to org to collect contribution). Seems like each transaction would require TWO QBO transactions...a sales receipt and an expense.

We definitely need all types of payments mapped. Just add fourth option to select at donation for donation type ie Auction, Donation, Ticket and then a separate mapping for fees

All types of transactions should be different mappings. We started the trial thinking this integration would be seamless. It's quite a cost bump.

Donations

Fees

Ticket Sales

Auction Item Sales

Modifying every transaction is so tedious. At this point, a csv upload would be quicker and this does not require a premium account. Please!!!!!!!

Agree with this - the ability to create separate mapping rules for fees would be incredibly helpful!

Oh no. We are two days from flipping the switch from our old CRM to GB, and I just discovered this problem today in testing, and that there is this known problem, dialog, and no solution. I don't think the rest of my conversion team will allow the conversion to stop just because I will have this extra work to do. If this bug gets out to others wanting to convert to GB, it will be a significant deterrent for larger not-for-profits to switch.

Separate tracking of fees is critical; also donor amount should include fees for tax records!

I agree this is very important. The reason we upgraded to GiveButter premium was to have less manual work, but I still need to go in and change all the fees separately.

We have to go in and modify every single sales receipt so we map fees separately from donations and ticket sales. This is laborious and frustrating.