What the accounting actually looks like
A food truck discovery and event-booking platform earns through booking fees, premium truck listings, and event-organizer subscriptions. Revenue lands across Stripe and possibly Square, with deposits, balances, and refunds split across event lifecycles. Expenses include hosting, mapping APIs, marketing, and contractor support for content and sales. The 1099 footprint is moderate, weighted toward marketing and content contractors rather than the trucks themselves. A monthly close with event-level reconciliation works.
How ATCS handles it for flavorfleets.com
-
Multi-account reconciliation
Booking deposits and balances arrive at different points; reconciling across processors keeps event-level revenue accurate.
-
Department/location coding
Coding by event or region shows which markets and event types pay back the booking effort.
-
AI-assisted categorization
Mapping API fees, ad spend, and processor charges each train into stable categories.
-
Per-transaction document attachments
Event contracts and organizer agreements attach to the booking they reference.
Bookkeeping reality for Local services & marketplaces
Two-sided marketplaces and event platforms live on the gross-versus-net revenue question. Whether the books recognize platform fees only or full transaction value, then remit to providers, has to be settled in policy and reflected consistently. Provider payouts produce large 1099-NEC populations — most local-service providers are sole props or single-member LLCs — making tokenized W-9 capture and encrypted TIN storage table stakes. Refunds, weather cancellations, and partial-job adjustments are recurring journal volume. Sales tax marketplace-facilitator rules apply in some states.