aldro.

Portland

Portland Food-Cart Records: Units, Pods, Events and Settlements

Connect a Portland food cart’s unit, site and event dates with operating documents, supporting services, organizer statements and unresolved balances.

Prepared by Aldro Accounting · Published · 6 min read

Latest source check

The quick answer

Give each food cart a unit identifier, then connect its actual sites and operating dates to the right license, supporting-service agreements and financial packet. Keep the cart operator, pod operator and event organizer distinct. An itinerary and event statement explain facts a bank deposit cannot, while ordinary POS, tip and payroll reconciliations remain separate parts of the close.

Start with the unit and the operator

A cart can trade under one public name while its license, trailer purchase and bank account use different descriptions. Create a unit register showing the internal unit ID, legal operator, cart name, license reference and identifying information from the actual documents. Keep the owner or lessor distinguishable from the person operating the business.

Use that ID on the pod agreement, service bills, equipment records and event file. If the business operates two carts, retain a separate operating record for each, even when one company owns both. A pod name or payment-terminal nickname should not be the only way to identify which unit incurred a cost.

Multnomah County’s cart guidance treats operating approval, ownership changes and supporting facilities as specific matters. Preserve the documents for the actual operator and approved arrangement when buying, leasing or changing a cart; a previous operator’s paperwork should not quietly become the new business’s record.

Connect the itinerary to each event packet

ORS 624.320 requires the operator to keep specific mobile-unit itineraries on file and available to the authority. It also requires prior notice when the unit moves to another delegate county. Maintain a schedule with unit ID, site address, county, operating dates and the document reference for any required notification or review.

Multnomah County asks operators to report location or menu changes. Keep the change request and relevant response with the affected period. Record an expected booking separately from the dates actually worked, and explain a cancellation or replacement site rather than overwriting the original itinerary.

For an event, add the organizer, agreement, sales arrangement and actual service setup. Is the business serving from its approved unit, adding off-unit activity or operating a separate booth? OHA’s guide describes circumstances where off-unit operations require a single-event temporary restaurant license. Multnomah County publishes a separate temporary-event process. Have the relevant authority confirm the route for the actual setup and retain that confirmation.

This schedule preserves operating facts. A health notification, event booking or itinerary entry does not decide a tax allocation or establish approval for a different state.

Separate the cart’s file from the pod’s responsibilities

Multnomah County distinguishes the pod owner or lessee from an individual cart operator. Its pod guidance assigns shared-site responsibilities such as wastewater, waste handling and power utilities to the pod operator. A cart tenant does not automatically become the pod-license applicant. Identify the actual parties before assigning a bill or an unresolved operating question.

Keep the signed space agreement and a short service schedule: what the payment covers, who provides it, which unit or site uses it and the period charged. Separate ordinary rent, extra services, refundable amounts and agreed credits. A single transfer to the pod operator may not explain all of those components.

Record the approved supporting-facility arrangement too. OHA allows self-sufficient units to operate without a commissary when the required operations can be accommodated onboard. Confirm the actual approved model and retain relevant commissary, warehouse, restroom and wastewater documents. Do not infer approval from having one piece of equipment or assume every cart follows the same commissary arrangement.

Keep service records beside the correct unit or site cost

Multnomah County identifies other agencies that may need to approve a cart, including planning, building and fire authorities. Give each relevant document its own holder, unit or site reference and follow-up owner. A food-health license and a service invoice do not answer every operating question.

Portland Fire & Rescue says the service report for an installed fixed fire-suppression system must remain on-site. Keep a retrievable report reference beside the related unit’s service bill. Portland Environmental Services separately describes cart-pod sewer connections and ongoing wastewater requirements. Preserve the approved arrangement, responsible party and service evidence rather than using a utility payment as the complete explanation.

When equipment, food stock or supplies move between units or locations, keep a practical transfer note. Give shared costs and significant equipment purchases to the reviewer with their actual use and payment facts; the unit register does not decide their tax treatment.

Attach the event money to the same unit and dates

Assume a fictional cart leaves its regular Portland pod for a two-day Oregon event. The agreement says the organizer collects and settles the stated sales. Its statement shows US$2,000 collected, US$100 refunded, a US$250 contractual participation charge, US$50 processing cost and US$150 still held as a refundable amount. The cash settlement is US$1,450.

Attach that statement and bank reference to the same unit ID and event dates in the itinerary. Keep the US$150 open for follow-up until its return, application or other explanation is documented. The US$250 is a fictional contract charge, not a government license fee. A later return of held money should link to this event rather than appear as another customer order.

This limited example excludes tips, taxes, earlier balances, other units and food, labor or fuel costs. It explains the event packet and cash movement, not profit or taxable income. Use the restaurant reconciliation guide for the ordinary POS and tip close.

Close with a unit-and-site exceptions list

Review service days missing from the itinerary, costs assigned to the wrong unit, changed locations or menus, unconfirmed support arrangements and event balances still held. Match a recurring charge to the agreement and period before treating an unexplained difference as another expense. Give each exception a responsible person and next action.

Hand over the unit register, site-period schedule, event packets, supporting agreements, service records and unresolved items alongside the reconciled company accounts. Keep employee time and payroll detail in the separate payroll process. Work across the Oregon–Washington line needs the existing cross-state review.

When requesting bookkeeping help, identify the units, systems, periods and event arrangements involved. Confirm which cleanup, payroll and tax work the engagement covers, and who handles operating-approval questions. The record packet makes those responsibilities visible without assuming every task belongs to the accounting provider.

Common questions

Does the pod’s license replace the cart’s operating record?

Keep the roles separate. Multnomah County has distinct cart and pod processes, and says an individual cart operator does not automatically apply for the pod license. Retain the documents for the actual operator and site arrangement.

Does every event appearance require the same temporary license?

Confirm the actual arrangement. OHA distinguishes licensed-unit operation from some off-unit activities that require a single-event temporary restaurant license. Keep the setup details and authority’s response in the event file.

Should a refundable amount held by an organizer become a vendor fee?

Keep it separately identified while the agreement, release or application is checked. A held amount and an actual charge need different evidence; the tracking schedule alone does not determine tax treatment.

Sources & scope

This guide explains records and general filing questions. Requirements depend on the entity, activity, location and tax year. Confirm the current rules and your written engagement before relying on a filing assumption. Workflow examples are illustrative.

Put your records in order.

Start with the bookkeeping handover checklist, then tell us which periods, entities and jurisdictions you need help with. We’ll confirm the scope before work begins.

For service details, explore monthly bookkeeping, catch-up bookkeeping and business tax filing.

Get started

Keep reading

Portland Restaurant and Café Bookkeeping: Reconcile POS Sales to CashPortland–Vancouver Business Records: A Checklist for Work Across Oregon and WashingtonHiring Your First Oregon Employee: Records and Payroll Handoff Checklist