Tutorial — Recording Revenue Events
Tutorial — Recording Revenue Events
What This Tool Is For
How to enter revenue at the right granularity — attached to the service that earned it — and why that one habit unlocks every margin report.
Step-by-Step Walkthrough
Step 1 — One event per earning: when revenue is earned (service delivered), record an event with amount, date, project, and — crucially — the service that earned it.
Step 2 — Resist the lazy default of booking everything to the project or the company. Project-level revenue can hide a money-losing service inside a profitable product; only service-level attribution exposes it.
Step 3 — For advance payments (a year paid up front), record the cash receipt but recognize revenue month by month as the service is delivered — the platform separates "cash received" from "revenue earned" so neither story corrupts the other.
Step 4 — Verify in the margin view: once costs and revenue both carry service links, each service's profitability appears side by side. That table is the payoff for the discipline.
Real-World Example
Scenario: The streaming product books $80,000 in June — healthy at first glance. Because every event carries its service: Video CDN $60,000 (70% margin), Live Transcoding $15,000 (10%), Archival Storage $5,000 (negative 44% — it loses money on every sale). The repricing meeting happens that same week. With project-level booking, the loss-maker would have hidden for another year.
Tips & Common Mistakes
- The service link at entry time costs three seconds; reconstructing it months later costs days.
- Keep one-time revenue (setup fees, consulting) clearly separated from recurring revenue — your growth metrics depend on the distinction.
- Cash received is not revenue earned; let the platform hold the advance until the months it belongs to.
Everything described in this tutorial is a working feature of TupicFinance, the financial management platform of the Tupic ecosystem. The screens, workflows, and guardrails above behave exactly as written there — this guide doubles as the platform's user manual for this tool.