Aggregating micro-earmarks: why the batch matters.
MAY 2026 · IMPACTTen thousand $8 line items per month would swamp reconciliation and, at partnership activation, wire fees. One monthly batch into the pooled fund is cleaner. Here's the math and the timing.
Every LADLE subscription earmarks $8 for the meal fund — the pool that grows toward the $50,000/year partnership threshold. If we naively treated each $8 as its own micro-transfer (either as a per-subscription line item to the partner we select today, or as an individual wire when the partnership activates), three things would happen: (1) we'd burn a huge fraction in transfer fees post-threshold, (2) the partner's finance operations would drown in tiny incoming transactions once we're a partner, (3) the monthly reporting would be per-transaction chaos rather than per-month clarity.
So we batch. Every month, on the last day, we post one aggregated total to the pooled meal fund and publish it in the month's fund report. Post-threshold, the same aggregate ships as a single donation via the partner we select. This post is the specific reasoning about the batch, since it comes up occasionally.
**The transfer-cost math (applies once we cross the $50,000/year threshold).**
International wire transfers have fixed costs — typically $15-50 per transaction depending on the corridor and bank. Even if we used a low-cost cross-border rail (Wise, or similar) fees are meaningful on small transactions.
At $8 individual transfers, a $10 fee is 125% of the amount being consumed by overhead. At a $500 aggregated transfer, the same $10 fee is 2%. At a $10,000 aggregated transfer, it's 0.1%. Batching is not optional at scale.
**The operational math.**
Our future hunger-relief partner aren't designed to receive thousands of individual transfers per corporate donor per month — which is one of the reasons their corporate-partnership framework exists in the first place, and one of the reasons it has a threshold. When we aggregate, a partner sees one incoming transfer per month with a summary line item, cross-references it to our monthly report, issues one receipt, and moves on to distribution planning.
Individual per-subscription transfers would create reconciliation overhead that would consume the partner's staff time — which is the opposite of what we want. Their staff time should go to logistics, not to paperwork about our micro-earmarks.
**The timing.**
Charge clears (say, on the 3rd of the month) → $8 earmarked immediately in the LADLE ledger to "pending accrual for month X" → at end of month, sum all accruals for the month, subtract any refunds that occurred in the 7-day window, post the net total to the pooled meal fund → fund report published within 5 business days.
This means: your July 3rd subscription's $8 earmark is part of the July batch, posted at end of July, reported in early August. Post-threshold, the same batch ships as a real partner donation and the partner reference number appears on that month's report.
**What about refunds mid-month?**
Refunds within the 7-day window unwind the meal accrual before the batch is posted. Refunds after the batch has been posted don't get reversed — the $8 stays in the pooled fund earmarked for meals — and LADLE absorbs the ops-side impact. This has happened rarely enough that the operational cleanliness (never asking the fund to unwind a posted batch) is worth the small absorbed cost.
**Why not weekly batches?**
We considered. Monthly matches how our future hunger-relief partner think about incoming aggregated donor flows once you're a corporate partner. Weekly would create 4x the accounting artifacts for negligible speed improvement. The meals aren't served the day a wire clears anyway — the partner's distribution runs on its own schedule.
**The escape hatch.**
If the monthly batch doesn't post for any reason (our error, an ops issue), we say so in the changelog with the reason. The accrual doesn't disappear — it rolls to the next month with a note explaining the delay. Never happened to date. Documented in advance because it might, and we want to be ready.
**Bottom line.**
Batching is boring plumbing. It's also the operational move that makes the whole model work at scale — both today (as we pool toward the $50,000/year threshold) and later (when the partnership activates and each month's batch ships as a real partner donation). Without batching, either the future wire fees would eat 15%+ of every earmark, or our future partner would be drowning in reconciliation work — either way, fewer meals for the same money. Batching is boring, batching is honest, batching is how the numbers stay big.