One gift, entered once, flows from the giving through the receipt, the acknowledgement, the ledger and the report — the donor-facing surface as capable as the tools that do nothing else.
A supporter raises on the charity's behalf through their own page under the campaign — their network gives through them, every gift still landing in the charity's account and carrying the charity's compliant receipt.
A timed appeal that runs to a target within a window, and a standing fund that simply accumulates with no end date, either branded to the cause.
Attendance sold for a gala, a dinner or an auction, with the deductible part of each ticket worked out under the fundraising-event rules rather than guessed.
An ongoing monthly commitment by card or, better, by direct debit, which fails less and costs less, so the charity keeps a dependable base of income.
Supporters commit an amount they choose and are charged only when the campaign reaches its goal, so demand is proved before a cent is collected.
A donor commits a fixed total paid in instalments the platform collects on a schedule, each receipted as it is taken and tracked against the total with reminders.
The progress display can be a plain total, or a staged ascent in which the published target lifts as each threshold is reached, every threshold carrying a short description of what it unlocks.
The charity chooses plain or staged for each campaign and writes the levels itself, with no code.
The same thermometer runs on a hosted page or embedded on the charity's own site, updating in real time as gifts arrive.
Where a charity holds several gift funds, the donor can direct the gift to the fund they choose and it lands in that fund's own account.
Each suggested amount is paired with the concrete thing it funds, so the donor is choosing an outcome rather than a number.
The gifts made can be listed, each donor appearing by name or anonymously — off unless the charity switches it on.
No account and lowest friction, the receipt by email as a matter of course; an account is offered only to the donor who wants their receipts and recurring gifts in one place.
Whether and how much of the gift is tax-deductible is shown at the point of giving, and where a payment carries a benefit the deductible part is shown too.
A gift made in memory or in honour of a named person, with an optional card the platform sends to someone the donor names.
Manage or pause recurring gifts, keep every receipt with the consolidated end-of-financial-year summary, and read the charity's updates on what the giving did — on the web and in the app.
The receipt is the rigid compliance artifact and the acknowledgement is a card the charity designs in its own voice, the two generated separately and combined only at delivery, so the design can never disturb the correctness of the receipt.
The card fills with personalisation as it sends — the donor's name, the amount, the campaign, and the concrete thing that amount funds — so it reads as written for them.
The charity holds several cards and the platform picks among them by rule: a different one for a first gift than a later one, a fuller one by the size of the gift, and a different one per campaign.
Preview a card filled with sample data and send a test before a campaign opens, and render the card as a document to post by hand for a major gift.
Every receipt carries exactly what the ATO requires, built from the entity's verified registration data, so every ATO-required field is filled before a receipt is issued; a non-endorsed entity is issued an ordinary receipt that claims no deductibility, and the NSW two-dollar rule is observed where it applies.
A free gift is distinguished from a payment that returns something of value — an event ticket, a membership with a benefit, an auction lot — and each is receipted correctly.
For an eligible event the platform applies the whole test: a contribution over $150, the benefit no more than the lesser of $150 and 20%, the deductible amount the contribution less the benefit, tracking the two-contributions and fewer-than-fifteen-events limits and warning as one nears.
Where a charity is registered for GST the platform computes the tax on the parts of its takings that are sales rather than gifts and presents the figures for the activity statement — preparing them and never lodging.
Each fund is a separate ledger, only true gifts and their income credited and commercial money kept out, the classification enforced at entry and reconciled, so the separation the law demands is native rather than improvised.
Each outward distribution is checked against the recipient's DGR status and blocked if ineligible, and tracked against the minimum the fund must distribute — 4% public, 5% private, with the announced 6% reform held as pending.
Each DGR category a client uses is handled by its governing distinction, and the registered-charity layer is kept distinct from the DGR-endorsement layer, so the common error of treating one as the other is designed out.
Each entity's ABN, charity registration and DGR endorsement are checked against the public registers before the entity goes live, and the bank account is verified through the payment provider, so a status that is not real is caught before any artifact flows from it.
The inputs to the ACNC Annual Information Statement, the figures the ATO needs, the donor year-end summaries and the reconciliation against the provider's settlements are produced through the year as standing output.
The whole encoding is versioned and maintained against a reforming regime, each receipt and report recording which version of the rules governed it, and state fundraising law tracked passively and never used to gate a donor by where they live.
One body holds several legally distinct entities, each with its own legal name, ABN, charity status, DGR category, bank account, receipt template and ring-fenced fund; a gift lands only in its entity's account and carries only its entity's receipt while the body sees them all in one view — a single-fund charity being simply the easy instance of it.
The board authorises entities and accounts, an administration role runs the day-to-day, and an oversight or advisory role observes and recommends without the power to transact.
Campaigns are composed from blocks with no code, and a repeating appeal is built once and copied each time with only its target, dates and impact lines changed.
A refund is recorded as a fresh cancelling receipt rather than an alteration, and a chargeback reconciled against the provider's record.
The whole administrator console, the hosted donor pages and the donor portal — built first, so a demonstration needs no company to exist.
A donation form, the threshold-marked progress display and a giving button placed on the charity's own website by a script or a plugin, styled to the site and live, with a hosted link page for the charity that has no site.
The whole donor experience and the whole administrator console on the phone, at parity with the web rather than a cut-down companion.
An overseas supporter gives in dollars and their own bank converts. The payment provider holds the card data and the platform holds none, the money settling to the charity's own account rather than the platform's.
Data held in an Australian region, the donor's consents theirs to set and withdraw, data accessible and erasable on request with the records the law requires kept regardless.
Two-factor sign-in required of every account that can move money or read donor data, and every compliance-bearing action written to a record no role can alter.
Card-testing and fraud defences, every uploaded image screened, a breach-notification process set down in advance, accessibility to a recognised standard, and an independent penetration test before launch.
The donor data belongs to the charity and the donor, never mined or sold, and exportable in full at any time, so adopting the platform never means being held to it.
Explore a live demonstration campaign and the administering-body console, all on worked-example data.