A donation tracking app is a ledger first and a giving screen second.

A gift is a row with more fields than an amount

Start with the row, not the screen. A gift record that survives an audit holds the donor, the amount, the date the gift was received, the method it arrived by (cash, card, bank transfer, cheque, stock, goods), the fund or appeal it was given to, whether it is a payment against a pledge, whether the donor received anything in return and your estimate of what that was worth, and the date the acknowledgment went out. Nine fields, and six of them are the ones a spreadsheet quietly loses.

Two of them cause most of the trouble later. The date received is not the date you banked it and not the date the deposit cleared, so keep those as separate fields if your bookkeeping needs to reconcile. And a non-cash gift gets a description rather than a number from you: the donor values their own property, you describe what arrived and when.

Designation is the field people add last and regret. A gift to the roof fund is not income for general operations, and a donor who sees their restricted gift reported as unrestricted will say so. Anything with named funds and weekly repeat giving, a church giving app being the obvious case, wants the fund on the gift row itself rather than in a free text note that nobody can total.

What you owe the donor in writing, and when

Two dollar thresholds shape the paperwork, and they belong to different parties. A donor claiming a deduction of $250 or more has to obtain and keep a contemporaneous written acknowledgment. Contemporaneous means the donor holds it no later than the date they file the return for the year of the gift, so a statement in January is safe and one in June may already be late for an early filer.

The acknowledgment has to state the name of the organisation, the amount of a cash contribution, a description but not the value of a non-cash contribution, and whether you provided any goods or services in consideration for the gift. If you did, it needs a good faith estimate of the value of those goods or services. Where what the donor received was entirely intangible religious benefits, the acknowledgment says that instead.

The second threshold is your job rather than the donor's. If a donor makes a quid pro quo contribution in excess of $75, meaning they paid you and received goods or services back, you have to provide a written disclosure statement. It tells the donor that the deductible amount is limited to what they paid above the value of what they received, and gives a good faith estimate of that value. Gala tickets, auction lots and the tote bag all land here.

Both rules are about specific sentences on a document, which is exactly why they belong in software rather than in a volunteer's memory. The app already knows the amount, the date and whether anything went back, so it can produce the right wording every time.

IRS, substantiating charitable contributions

What Apple lets a donation app collect

This is the rule that decides your architecture, so read it before you design the giving screen. Apple does not treat charitable donations as in-app purchases. Guideline 3.2.1(vi) says approved nonprofits may fundraise directly within their own apps or third-party apps, provided those campaigns adhere to all the App Review Guidelines and offer Apple Pay support. Those apps must disclose how the funds will be used, abide by local and federal law, and ensure appropriate tax receipts are available to donors. If your app lists other charities as well, every nonprofit in it has to have gone through the approval process too.

The other half is guideline 3.2.2(iv). Unless you are an approved nonprofit, or otherwise permitted under 3.2.1(vi), collecting funds within the app for charities and fundraisers is not allowed: apps that seek to raise money for such causes must be free on the App Store and may only collect funds outside of the app, such as via Safari or SMS. So a charity giving app put together by a volunteer for a group that has not been through Apple's nonprofit approval has one legal route, which is a free app and a checkout on the web.

Read plainly, that leaves three shapes. Approved nonprofit: Apple Pay inside the app, with receipts available to donors. Not approved: collect on the web, and let the app do the recording, the receipts and the totals. Or build only the staff-side ledger, which is the part most groups are actually missing. The mechanics of moving money inside an app go further than one page can, and approval is Apple's to give, not something any app builder can hand you.

App Store Review Guidelines, 3.2.1(vi) and 3.2.2(iv)

Tracking gifts is half of donor management

A gift table answers what came in. A donor management app answers who is still with you, which needs history rather than totals: the same donor across five years, the appeal each gift answered, the ask that got no reply, the month a standing gift stopped.

The cheap version of that is three views over one table. Gifts this year by fund. Donors who gave last year and not this one. Recurring gifts that failed. Those three lists drive most of the decisions a small development office makes, and none of them stays trustworthy in a spreadsheet once two people are editing it.

Relationships that run for decades want the history attached to the person instead of the gift, which is the whole design of an alumni engagement app: a gift is one event among many, next to the reunion they came to and the student they mentored. If your donors are also your community, build the person record first and hang gifts off it.