Funding in Dapple is where you plan, award, schedule and record grant money for successful submissions — from an optional organisation-wide budget down to each individual payment. It replaces the spreadsheet most teams use to track who's been awarded what and what's been paid. Dapple never moves or holds money: payments still go out from your own bank, and Dapple keeps the record. Turn Funding on, create a fund for a project, award it to successful submissions, schedule the payments, then approve them and mark them as paid. Everyone on the team sees the same numbers.
How do budgets, funds, awards and payments fit together in Dapple?
Funding in Dapple uses four building blocks. Each one sits inside the one above it: a budget holds funds, a fund is split into awards, and each award is paid in one or more payments.
Building block | What it is | Example |
Budget (optional) | An organisation-wide pot of money for a date range. Funds draw from it. | Grants budget 2026/27 — £500,000 |
Fund | The money set aside for one project. Each fund has one currency. | Community Arts Fund 2026 — £120,000 |
Award | The amount one successful submission receives from a fund. | £12,000 to one applicant |
Payment | One instalment of an award, with an amount, a due date and a payment method. | Initial payment — £3,000, due 2 Oct 2026 |
Does Dapple send or hold grant money?
No. Dapple never moves, holds or sends money. Payments go out from your own bank, exactly as they do now. Dapple is where you plan, approve and record them.
No payment provider to set up.
No regulatory risk from Dapple handling funds.
Every payment you record carries a date, method and reference, so your finance team can match it against the bank statement.
Where does Funding live in Dapple?
Budgets belong to the organisation. Funds, awards and payments belong to a team's project. Shared lists, such as payment methods, are set once for the whole organisation.
Item | Belongs to | Where you find it |
Budgets | The organisation | Funding → Budgets — the same view whichever team you're in |
Funds, awards and payments | A team's project | The Funding area in the team sidebar |
Payment methods and schedule templates | The organisation | Organisation settings — shared by every team |
One submission's award and schedule | The submission | The submission's Award tab |
What's the difference between Funding → Payments and Entry fees?
Funding → Payments lists grant payments you make to applicants. Entry fees lists money applicants pay you through Stripe on your submission forms. The team sidebar item previously called Payments is now called Entry fees.
| Funding → Payments | Entry fees |
Direction | You pay applicants | Applicants pay you |
Money moves through | Your own bank | Stripe |
What Dapple does | Records the schedule, approval and payment | Takes the payment at checkout |
What does a typical Funding workflow look like?
Turn Funding on and check your payment methods.
Create a fund for the project. Optionally, draw it from an organisation budget.
Award the fund to successful submissions — usually in bulk from the Stages board or submissions list.
Schedule each award's payments from a template, adding release conditions where needed.
Approve payments as they fall due.
Record each payment as paid, with a date, method and reference.
Best practice
Create one fund per project round so totals stay clean.
Add a budget only if you report against an overall pot — it's optional.
Keep two-person sign-off switched on for any fund that pays out real money.
Agree a payment reference format with your finance team before your first payment run.