Aid Requests and Volunteer Expenses, End to End

Two things that used to happen in a notebook, a group chat and a spreadsheet now happen in Muin: giving money out to the people you serve, and giving it back to the volunteers who spent their own.

Both were already possible in pieces. What shipped over the last three months is the connecting tissue: the screens, the rules and the records that turn a pile of parts into something a two-person organization can run.

Giving money out: one screen, one motion

A family asks for help with rent. The question is never just “can we afford it”. It is also: what have they had before, does our own fairness rule allow it, is the fund the right one, and who is allowed to say yes.

The review cockpit puts all of that on one screen. Open an assistance request and you see the household, the amount asked for, prior aid, the fund, and the request type, with links through to the full person record if you need them. Then you decide.

Approve & disburse does the decision and the payout together. One dialog takes the payout method, the approved amount, a gift-card reference if that is what you are handing over, which grant to charge, and a notification to the family on whichever channel actually reaches them: WhatsApp, email or SMS. If you would rather decide now and pay later, Record decision only does that instead.

The other outcomes are first-class, not afterthoughts. More info asks the applicant a question and holds the request. Waitlist says yes in principle and defers for funds, which is the honest answer more often than anyone would like. Deny records the decision with a reason.

Fairness as a rule, not a memory

Deciding each request on its merits gets harder the more requests you take. By the fifteenth family, consistency is a feat of memory.

Fairness policies make it a rule. One policy per assistance class: a period of a week, month, quarter or year; a cap on the amount, the number of requests, or both; applied per household or per person. Muin enforces it at intake and at approval, so a request that would exceed a cap is caught before anybody promises anything.

There is also a Typical amount field that does no enforcing at all. It grounds the AI reviewer, so its recommendations look like what you actually give rather than a generic average.

Paying out, and undoing it

Every payout (cash, check, ACH, gift card, in-kind, Stripe transfer) lands in one list you can filter by method and status.

Mistakes get voided rather than edited. Voiding restores the fund, reverses the ledger entry, returns in-kind stock, and reopens the request so it can be paid correctly. The dialog spells out all four before you confirm, and a written reason is required. That reason is the audit trail, and it is the thing an auditor asks for.

Gift cards have their own lifecycle: issued, activated, redeemed, with void available until redemption. Muin tracks which card went to whom and what happened to it. It does not buy the cards for you, and it does not pretend to.

Giving money back: a photo of the receipt

Somebody bought pizza for the youth night out of their own pocket. The old answer was a group chat message and a treasurer’s memory.

Volunteers and parents now file their own claims in the member portal, and they never need a staff account to do it. Open Money back, tap New request, photograph the receipt, and Muin reads the merchant, total and date off the photo. You check what it read, correct anything wrong, and send it. Starting from the event you signed up for links the claim to that event automatically. Mileage needs no receipt, only the miles.

Staff with a Muin login, such as a teacher who bought classroom supplies or a coordinator who bought gas, file the same way, from My expenses on the web or the Muin Go mobile app, against a class, program or event. Same queue, same approvers, same payment.

Payout preferences is how the treasurer knows where to send it: Zelle, Venmo, a mailed check or cash, with one marked as the default. Muin does not move the money. Your treasurer pays by the method you chose and records it, the claim shows Paid with that method, and the ledger entry posts.

Approvals that fit a two-person organization

The hardest part of all of this is not the money. It is the approval.

Plenty of software assumes a finance department. A small organization of an owner and one coordinator does not have a second approver to route things to, and being forced to invent one means the rule gets ignored rather than followed.

So the approval question is configurable, and the same settings govern every kind of request rather than each flow inventing its own: who approves, whether an owner or admin may approve something they sent themselves, and the amount above which a second signature is required.

A small organization can choose to run with one person. Nothing is queued for a second approver, and the owner approves their own claim by writing down why, in a note that stays on the audit record permanently. Larger organizations can set an amount below which claims with a receipt are approved automatically and recorded, one approver above it, and two above a second amount. Until the questions are answered, nothing is approved automatically and nobody approves their own request.

When a rule stops you, Muin opens a dialog that names the rule and links to the exact setting that governs it, rather than flashing a message you might miss.

The compliance side, for the programs that need it

Organizations running federal food programs have paperwork that is not optional.

Eligibility screening runs a household against a profile and the federal poverty guidelines, and returns eligible, ineligible, needs review, or overridden. If you are going to help a household the rule says does not qualify (and sometimes you are), the override is recorded with your name and your reason, permanently, with the original determination kept alongside it. An undocumented exception is the one that gets asked about.

The attestation statement people agree to at certification is yours to write, in English, Spanish, Arabic, Urdu or Pashto, with a version label recorded on every certification so a signature stays attributable to the text that was actually shown. Muin ships starter copy for TEFAP, CSFP and a general program, and marks it Draft on purpose, with a banner that will not go away until your counsel has reviewed it.

The food-pantry report set covers intake against outflow, the TEFAP monthly report with its demographic breakdowns, a signature audit that counts tampered signatures as a number you can see, and non-fulfillment: the visits where somebody did not get what they came for.

Cash, counted by two people

Physical cash is the hardest money to account for honestly, so Muin makes it a process rather than a form.

At least two people count it, and Muin will not create a session with one counter. From there the session moves through approval, deposit and reconciliation, and it is only at reconciliation, once a matching bank deposit has been linked, that a contribution is recorded for each envelope. A counted, approved, deposited session is a record of cash, not income.

When the counted total does not match the deposit slip, that is exactly the case this exists for. Return it for a recount if you doubt the count, or flag the discrepancy if the money is genuinely missing. Flagging cancels the session and records nothing as a contribution, with a required reason. What you cannot do is reconcile a total you do not believe.

Where to start

If you run assistance programs, start with the fairness policy for the class you give most often. The rule is worth more than the screen.

If you have volunteers spending their own money, turn reimbursements on and answer the approval questions. Money back becomes a top-level door in the member portal the moment you do, which is the difference between a feature and a thing people use.