A vendor at a Saturday farmers market can ring up forty transactions before 9 a.m. — a $6 cash sale for a bunch of kale, a $22 SNAP/EBT purchase split across three tokens, a $14 card tap for a jar of honey, and a scale ticket for 2.3 pounds of heirloom tomatoes priced by weight. By the time the tent comes down, that vendor is holding a cigar box of cash, a stack of wooden tokens, a phone full of card-reader notifications, and zero idea of what the day actually earned. Multiply that by 30 market Saturdays a season and you get why farmers market bookkeeping quietly becomes one of the hardest reconciliation problems in small business — not because the dollar amounts are large, but because the payment types don't talk to each other.
Most vendors don't fail at farmers markets because their product doesn't sell. They fail because they can't tell, six months later, whether they actually made money — and by tax season, "I think I did okay" isn't a defensible number to the IRS.
Why Farmers Market Income Is Harder to Track Than It Looks
A typical retail business has one or two payment rails: cash and card. A farmers market vendor routinely juggles four or five, often on the same folding table:
- Cash — still the most common payment method at farmers markets, and the easiest to lose track of if it isn't logged the same day it's collected.
- Card/mobile payments — usually through Square, which is the most widely used payment app at farmers markets because of its free plan, no-cost card reader, and offline mode for spotty market Wi-Fi.
- SNAP/EBT — either the vendor is individually authorized to run EBT cards directly, or the market itself holds the authorization and reimburses vendors for SNAP tokens they collect.
- Nutrition-incentive matches (Double Up Food Bucks and similar programs) — a second layer of tokens, usually restricted to fresh produce, that the market reimburses separately from raw SNAP dollars.
- Weight-based sales — anything priced per pound needs its own paper trail back to a certified scale reading, which state weights-and-measures law treats as a legal record, not a convenience.
None of these rails reconcile against each other automatically. If you don't build a habit of logging each one the same day, by October you're reconstructing a season of Saturdays from memory and a shoebox.
Rule One: Log Every Payment Type the Same Day, Every Market
The single most common bookkeeping failure among market vendors is simple: cash goes uncounted, or gets counted three markets later. If you do not log cash sales, you are underreporting your income — and underreporting doesn't just create an IRS exposure, it also hides whether a given market or product line is actually profitable.
The fix doesn't need to be sophisticated. A dedicated notebook works: tape or staple receipts to the pages, and at the end of each market day write down cash total, card total, and token/EBT total separately, plus what didn't sell. A phone-based spreadsheet works just as well — the point is that the log happens at the market, not from memory afterward. At minimum, each market day's entry should capture:
- Cash collected (counted at close, not estimated)
- Card/mobile payment total (pulled from the reader's daily summary)
- SNAP/EBT tokens or vouchers collected, by type
- Unsold inventory, so cost-of-goods and waste are visible over a season
- Market fees or stall rent paid that day
SNAP/EBT: Two Very Different Reimbursement Models
How EBT money reaches a vendor's bank account depends entirely on which authorization model the market uses, and mixing them up is a common source of "where did that money go" confusion.
Market-wide authorization: the market itself holds the SNAP retailer authorization. Customers swipe their EBT card at a central booth, receive tokens, spend the tokens at any vendor stall, and the market reimburses each vendor afterward — typically weekly, based on tokens turned in. Under this model, a vendor's own books should treat token redemptions as accounts receivable the moment they're collected at the tent, not as revenue the day cash actually lands from the market. If you record the token as income only when the reimbursement check clears, your day-of-market sales total will never match your deposit total, and you'll spend hours every month chasing a phantom discrepancy that's really just timing.
Individual vendor authorization: each vendor carries their own SNAP retailer number and swipes EBT cards directly through their own POS device, same as a card payment. This is simpler to reconcile — the transaction settles on a normal payment schedule — but it means the vendor, not the market, is on the hook for SNAP compliance recordkeeping.
Either way, a wireless POS device generates a per-market-day transaction record that should become the source of truth for reconciling scrip distributed against scrip redeemed — because the number of tokens redeemed on a given day and the total scrip a customer walked off with are never identical. Some tokens leave the market in a customer's pocket to be spent next Saturday; some vendors hold tokens to turn in later rather than every week. That gap is normal, not an error, as long as it's tracked as outstanding scrip rather than written off.
Nutrition-Incentive Matches Are a Second Ledger, Not a Bonus
Programs like Double Up Food Bucks double a SNAP customer's purchasing power dollar-for-dollar, but the matched dollars usually come with a restriction — typically limited to fresh produce — and are reimbursed by a different funder (often a nonprofit, not the USDA directly) on a different schedule than raw SNAP dollars. A vendor who lumps "SNAP tokens" and "Double Up tokens" into one bucket loses the ability to answer a very practical question: which reimbursement is late, the state's or the nonprofit's?
The cleanest fix mirrors what markets themselves are advised to do: markets benefit from maintaining a separate bank account for SNAP and nutrition-incentive funds, and the same logic scales down to a vendor's own books — track raw SNAP and matched-incentive tokens as two distinct receivables, even if they get counted into a single "tokens" pile at the table. It's a five-second habit at data-entry time that saves an afternoon of detective work when a reimbursement doesn't match expectations.
Scale-Ticket Recordkeeping Is a Legal Requirement, Not Just Bookkeeping Hygiene
Anything priced by weight — produce, meat, cheese — has a compliance layer most vendors don't realize applies to them until an inspector shows up. A scale used for retail weighing must be NTEP-certified and inspected and sealed by a state Weights and Measures official before its first sale, then re-inspected annually, and every transaction must run on net weight using the tare function to zero out the container, with the reading displayed to both vendor and customer simultaneously. A scale that fails inspection doesn't get a warning — it gets an immediate stop-use order, meaning no more sales by weight until a compliant unit is back in place.
For bookkeeping purposes, that means the scale ticket (or the printed/digital receipt a certified scale produces) is your cost-of-goods and revenue record for weight-priced items, and it should be retained the same way you'd keep any other source document — not just because a bookkeeper wants it, but because your state's weights-and-measures office can ask for it. Building "photograph or save the scale ticket" into the same end-of-day routine as counting cash closes a gap most vendors don't think about until it becomes a problem.
Schedule F or Schedule C? It Depends on What's in the Bag
Come tax time, farmers market income doesn't automatically go on one form. The dividing line is whether you're selling something you raised or grew yourself, unprocessed, or something you made from it:
- Schedule F (Profit or Loss From Farming) covers cash from the sale of agricultural commodities raised or cultivated on the farm — raw produce, eggs, milk, market livestock.
- Schedule C (Profit or Loss from Business) covers products that are processed in any way — jams, cheeses, baked goods, cider, value-added items — even if the raw ingredients came from your own farm.
A vendor selling both a bushel of raw tomatoes and a jar of tomato jam at the same table is, technically, running two different tax activities that both need clean books. Net profit from either flows to Schedule SE for self-employment tax once net earnings clear $400, so the Schedule F/C split isn't just a filing preference — it changes which expenses are deductible against which income stream. Keeping raw-product and processed-product sales in separate columns from day one (not reconstructed in March) is what makes that split painless instead of a guessing game.
A Season-Long System That Actually Holds Up
Putting it together, a workable weekly routine looks like this:
- At the market: log cash, card, SNAP, and incentive-match totals separately as the day closes; save every scale ticket or POS export.
- Within 48 hours: enter the day's totals into your books, recording SNAP/incentive tokens as receivables if you're on the market-reimbursement model, not as same-day cash.
- Monthly: reconcile actual reimbursement deposits against the receivables you logged, and flag anything outstanding past the market's normal payment cycle.
- At tax time: split raw and processed product sales by the Schedule F/Schedule C line, and confirm your season totals tie back to 30-plus individual market-day entries instead of one guessed number.
Keep Your Season's Records Honest From the First Saturday
Every one of these problems — cash going uncounted, SNAP reimbursements booked on the wrong day, scale tickets that vanish before tax season — comes down to the same root cause: records that live in someone's memory instead of a system. Beancount.io offers plain-text accounting that keeps every market day, every token reconciliation, and every scale ticket in a transparent, version-controlled ledger you actually own — no proprietary format, no vendor lock-in. Get started for free and turn a shoebox of receipts into books you can trust by October.