Step 23 · Build & grow
Public chapterAccounting and operations
Position
SwiftBite will launch with a processor-backed order subledger, automated settlement instructions, and summarized postings to QuickBooks Online. The founder owns treasury and exceptions; a contracted marketplace bookkeeper owns reconciliation and month-end close. Launch remains blocked until processor approval, local courier-pay requirements, tax treatment, and funded payout timing are documented.
Financial-control setup
System ownership and controls
| Component | SwiftBite configuration | Accountable role |
|---|---|---|
| Payments | Stripe Connect, subject to marketplace underwriting; connected-account verification required before merchant or courier activation | Founder |
| Order subledger | White-label vendor’s managed ledger integration; immutable order, charge, refund, transfer, and payout identifiers | Vendor integration lead |
| General ledger | QuickBooks Online; separate merchant payable, courier payable, tips payable, tax payable, processor clearing, and operating-cash accounts | Marketplace bookkeeper |
| Banking | Dedicated LLC collections and operating accounts; customer and merchant obligations excluded from spendable cash | Founder |
| Monitoring | Managed webhook monitoring, processor-fee comparison, settlement-aging alerts, and vendor status checks | Vendor integration lead |
| Access | Named accounts, multifactor authentication, restricted API keys, and bookkeeper approval of bank-detail changes | Founder |
The vendor statement of work must include webhook replay, idempotent posting, payout-status tracking, complete ledger exports, and migration assistance. Reject any license requiring the founder to maintain custom payment code. The contract must identify integration-support ownership and prohibit unapproved changes to payout logic.
Order-level posting specification
| Event | Required ledger action and control |
|---|---|
| Checkout | Display food subtotal, applicable tax, delivery fee, and optional tip separately. Record the merchant commission basis as the food subtotal after merchant-funded discounts, excluding tax and tips. |
| Capture | Debit processor clearing for captured funds; credit merchant payable for food proceeds net of commission, platform revenue for commission and delivery fee, and the appropriate tax and tip liabilities. |
| Delivery completion | Debit courier delivery expense and credit courier payable at the published rate, including any wage-floor supplement. Allocate the entire courier tip to courier payable without reducing delivery pay. |
| Processor assessment | Debit processing expense and credit processor clearing using the actual balance transaction, not the checkout estimate. |
| Transfer and payout | Move amounts through connected-account clearing; close the relevant payable only when the processor confirms the corresponding obligation is discharged. Track bank payout failures separately. |
| Refund or dispute | Post a linked reversal or adjustment against the original order. Never edit the original transaction or net unrelated merchant balances. |
The merchant agreement specifies the advertised commission cap, payout calendar, refund allocation, dispute evidence process, and consent requirements for recovery of merchant-attributable losses. SwiftBite bears its own service failures. Refunds reverse the corresponding commission; processor fees remain SwiftBite expenses unless separately lawful, disclosed, and accepted.
The courier agreement publishes delivery compensation before acceptance, preserves tips, and requires time records sufficient to calculate the local minimum-wage equivalent. Counsel must approve the compensable-time definition and contractor classification. Required supplements accrue before payout; tips never satisfy the floor.
Automation and exception routing
| Trigger or schedule | Automated action | Escalation |
|---|---|---|
| Each payment event | Verify webhook signature; deduplicate; post balanced entries; compare allocations with captured funds | Unbalanced orders enter a payout hold queue |
| Each bank-detail change | Suspend outgoing payment to the changed destination pending independent confirmation through the existing contact channel | Founder and bookkeeper approval |
| Daily reconciliation | Match orders, processor balance transactions, connected-account balances, and bank deposits | Bookkeeper investigates every unexplained difference |
| Merchant payout target: second business day after funds become available (estimate) | Release eligible proceeds under the processor-approved calendar | Notify merchant of failed or delayed payout |
| Courier payout target: next business day after funds become available (estimate) | Release earned compensation and supplements; observe any earlier statutory deadline | Founder funds obligations from operating cash when required |
| Fee variance above $0.05 per order (estimate), or missing webhook acknowledgement after five minutes (estimate) | Alert founder and vendor; compare contracted rates and service status | Suspend affected payout batches, not verified unrelated balances |
Checkout stops accepting payment when capture status cannot be established reliably. Fulfilled orders retain their payment obligations during outages. Routine reconciliation and payouts run unattended; exceptions require documented approval and an audit trail.
The numbers
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file |
| Personal cash requirement | $67,200 (estimate) | Grounded monthly burn of $4,800 multiplied by grounded runway of 14 months |
| Capital remaining before venture expenditure | $17,800 (estimate) | Starting capital less personal cash requirement; not an approved operating budget |
| Merchant commission / consumer delivery fee | 12% cap / $3.99 | Grounding file |
| Illustrative food subtotal | $25.00 (estimate) | Planning basket; excludes tax and tips |
| Platform revenue per illustrated order | $6.99 (estimate) | Commission plus delivery fee |
| Processing assumption | 2.9% + $0.30 (estimate) | Budget placeholder, not a processor quote |
| Processing expense | $1.14 (estimate) | Applied to illustrated $28.99 charge (estimate); tax and tips increase actual expense |
| Published base courier-pay proposal | $4.75 per delivery (estimate) | Subject to local wage-floor validation and supplements |
| Variable software and payout allowance | $0.25 per order (estimate) | Vendor quote pending |
| Refund and dispute allowance | $0.25 per order (estimate) | Replace with observed loss rate |
| Illustrated contribution | $0.60 per order (estimate) | Before fixed costs and wage-floor supplements |
| Maximum courier cost before illustrated contribution reaches zero | $5.35 (estimate) | Other illustrated variable costs held constant |
Decisions and trade-offs
| Decision | Binding trade-off |
|---|---|
| Use licensed financial integration | Reject cheaper software without exportable order-level accounting |
| Keep merchant proceeds segregated in accounting and treasury controls | Merchant balances cannot finance payroll, founder drawings, or growth |
| Protect courier floor and commission cap | Pause uneconomic routes or launch hours rather than underpay couriers or increase merchant commission |
| Retain exception review | No promise of flawless or immediate bank settlement |
| Hold expansion approval | Positive contribution must include actual supplements, payment costs, refunds, and incentives |
Do this next
| Action | By when | What proves it worked |
|---|---|---|
| Obtain processor and white-label integration approval | Before license signature | Written funds-flow approval, fee schedule, support responsibilities |
| Retain marketplace bookkeeper and local counsel | Before merchant contracting | Approved chart of accounts, tax responsibilities, courier terms |
| Fund a payout and dispute reserve | Before accepting orders | Bookkeeper-approved cash stress test and restricted reserve balance |
| Test capture, split, refund, duplicate webhook, dispute, and failed payout | Before launch | Balanced ledger exports and successful replay without duplicate payment |
| Validate contribution by route and operating period | Before expansion | Actual positive contribution after all variable obligations |
Risks in your situation
The unspecified jurisdiction prevents final approval of contractor status, wage-floor calculations, marketplace tax collection, and payment timing. Processor reserves or delayed availability could exhaust the modest capital remaining after personal needs. Written settlement approval and a funded stress test are mandatory; merchant float is not a contingency.
Evidence gate
- ☐ Processor approves the complete merchant and courier funds flow.
- ☐ Signed contracts preserve the commission cap, transparent checkout, and courier floor.
- ☐ Test transactions reconcile across subledger, processor, bank, and general ledger.
- ☐ Failed payouts and duplicate events cannot create duplicate payments.
- ☐ Reserve funding covers documented settlement-delay exposure.
- ☐ Actual contribution supports launch without unpaid obligations.