Revenue Recognition Protocols

How does Netflix… How does Netflix accounts for a Yearly Subscription Paid in Advance (Ind AS & IFRS Perspective) Let’s look at a clean accounting example using Netflix’s annual subscription model. Assume a customer pays ₹7,800 upfront for a 12-month Netflix subscription. From an accounting standpoint, cash receipt and revenue recognition are separate events under both Ind AS and IFRS. 👉 At the time of receipt of payment (Day 1) Although cash is received, the service will be delivered over the next 12 months. So revenue is not recognised immediately. As per Ind AS 115 / IFRS 15 – Revenue from Contracts with Customers, Netflix has an unsatisfied performance obligation at this point. ✅ Journal entry: Cash / Bank     Dr ₹7,800 Contract Liability (Unearned Revenue) Cr ₹7,800 This contract liability represents the obligation to provide access to the service in future periods. 👉 Revenue recognition over time Netflix satisfies its performance obligation over time, as the customer consumes the service evenly throughout the subscription period. Monthly revenue recognised: ₹7,800 ÷ 12 = ₹650 per month ✅ Monthly journal entry: Contract Liability Dr ₹650 Revenue      Cr ₹650 This entry is passed each month as the service is delivered. 👉 Position over the subscription period After 6 months: • 50% of the revenue is recognised in the Statement of Profit and Loss • 50% remains as a contract liability in the Balance Sheet After 12 months: • The full ₹7,800 is recognised as revenue • The contract liability balance becomes nil. Relevant Accounting Guidance 📘 ‼️ Ind AS 115 / IFRS 15 requires revenue to be recognised when or as performance obligations are satisfied ‼️ Advance receipts for services create a contract liability, not immediate revenue ‼️ Revenue is matched with the period in which control of the service is transferred to the customer This is a straightforward illustration of revenue recognition over time under Ind AS and IFRS for subscription-based business models.

Studying IFRS 15 📚 taught me: money isn’t earned when you think it is. Revenue from Contracts with Customers Honestly? This standard is one of those that affects everyone, from Netflix lovers to my Balogun Aunty who sells aso-ebi. At its heart, IFRS 15 is asking one simple question: 👉 “When exactly should revenue be recognized?” Not when cash hits your account. Not when you feel like it. But when value is truly delivered. It gives us a 5 step roadmap: 1️⃣ Identify the contract – Is there an agreement? 2️⃣ Identify performance obligations – What’s being promised? 3️⃣ Determine the transaction price – How much is to be paid? 4️⃣ Allocate the price – Share the price across promises. 5️⃣ Recognize revenue – As and when value is delivered. Example? Aunty Balogun sells you cloth for ₦50k and gele tying lessons for ₦5k. She can’t call it ₦55k “cloth money.” She must split it and only recognize each part when delivered. 🚧 Construction contracts This is where IFRS 15 really flexes. Imagine a company building a bridge for Lagos State, it takes 3 years. Should they wait until 2028 to recognize all the revenue? No way. IFRS 15 says: 👉 Recognize revenue over time as the work is done (if the client controls the asset as it’s built or benefits as it progresses). So, if 40% of the bridge is complete this year, 40% of the revenue shows this year. Simple. 📖 In the books: 👉 Initial recognition (when cash is received, but no delivery yet): Dr. Cash (₦200k) Cr. Contract Liability / Unearned Revenue (₦200k) 👉 Subsequent recognition (when Obligation is satisfied): Dr. Contract Liability (₦200k) Cr. Revenue (₦200k) Costs are matched too, so it’s not just vibes it’s aligned with reality. That’s why IFRS 15 is powerful: it keeps financials honest, balanced, and reflective of the real story. Revenue is not about money collected, it’s about promises kept. So, whether you’re Netflix spreading subscriptions, Aunty Balogun delivering gele lessons, or a contractor building Third Mainland Bridge part 2, IFRS 15 ensures your revenue speaks the truth. I’d love to hear from you too, how do you explain IFRS 15 in simple terms? #Accounting #Finance #ICAN #LearningJourney

𝐋𝐞𝐭’𝐬 𝐓𝐚𝐥𝐤 𝐀𝐛𝐨𝐮𝐭 𝐈𝐅𝐑𝐒 𝟏𝟓: 𝐑𝐞𝐯𝐞𝐧𝐮𝐞 𝐟𝐫𝐨𝐦 𝐂𝐨𝐧𝐭𝐫𝐚𝐜𝐭𝐬 𝐰𝐢𝐭𝐡 𝐂𝐮𝐬𝐭𝐨𝐦𝐞𝐫𝐬 Let’s be honest, 𝐫𝐞𝐯𝐞𝐧𝐮𝐞 𝐢𝐬 𝐭𝐡𝐞 𝐥𝐢𝐟𝐞𝐥𝐢𝐧𝐞 𝐨𝐟 𝐚𝐧𝐲 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬 and how it is recognised directly impacts reported profits, performance metrics, and even investor perception. 𝐈𝐅𝐑𝐒 𝟏𝟓 is one of the most practical but challenging standards for many accountants. It does not just replace 𝐈𝐀𝐒 𝟏𝟖 and 𝐈𝐀𝐒 𝟏𝟏; it introduces a 𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞𝐝 𝟓-𝐬𝐭𝐞𝐩 𝐦𝐨𝐝𝐞𝐥 to ensure revenue recognition reflects the transfer of goods or services to customers, not just the flow of cash. 𝐓𝐡𝐞 𝟓-𝐒𝐭𝐞𝐩 𝐌𝐨𝐝𝐞𝐥 𝐮𝐧𝐝𝐞𝐫 𝐈𝐅𝐑𝐒 𝟏𝟓 1. Identify the contract with a customer 2. Identify the performance obligations in the contract 3. Determine the transaction price 4. Allocate the transaction price to the performance obligations 5. Recognise revenue as or when the performance obligations are satisfied Practical Example A manufacturing company signs a contract to supply a machine to a customer for 𝐆𝐇𝐒 𝟏𝟎𝟎,𝟎𝟎𝟎, with an additional two-year maintenance service included. At first glance, recognising the full GHS 100,000 as revenue when the machine is delivered might seem simple. But 𝐈𝐅𝐑𝐒 𝟏𝟓 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐬 𝐚 𝐝𝐞𝐞𝐩𝐞𝐫 𝐥𝐨𝐨𝐤. 𝐒𝐭𝐞𝐩 𝟏: Identify the Contract with the Customer The contract is enforceable, approved, and payment terms are clear, it qualifies. 𝐒𝐭𝐞𝐩 𝟐: Identify the Performance Obligations The machine and maintenance services are distinct, so they are separate performance obligations. 𝐒𝐭𝐞𝐩 𝟑: Determine the Transaction Price The price = GHS 100,000 (no variable consideration or financing component). 𝐒𝐭𝐞𝐩 𝟒: Allocate the Transaction Price Machine normal price = GHS 90,000 Service normal price = GHS 20,000 Total = GHS 110,000 Allocation: Machine = (90,000 ÷ 110,000) × 100,000 = GHS 81,818 Service = (20,000 ÷ 110,000) × 100,000 = GHS 18,182 𝐒𝐭𝐞𝐩 𝟓: Recognise Revenue Machine (81,818) → recognised at delivery. Service (18,182) → recognised over 2 years (likely straight-line). #Financial Statement Treatment On delivery: Dr Trade Receivable / Cash 100,000 Cr Revenue (Machine) 81,818 Cr Deferred Revenue 18,182 Over 2 years: Dr Deferred Revenue 9,091 Cr Revenue (Service) 9,091 (each year). 𝐖𝐡𝐲 𝐈𝐭 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 IFRS 15 brings consistency across industries. Without it, businesses could accelerate or defer revenue to manipulate results. By linking revenue to the actual transfer of goods and services, it strengthens transparency and comparability. For accountants, auditors, and finance professionals, mastering IFRS 15 is not optional, it’s essential. #IFRS15 #ICAG #CIMA #ACCA #FinancialReporting #Auditing #Finance Dr. Sigmund E. Yevugah Paul Aninakwah ACMA,CGMA, ESG Osman Musah Erastus Etsibah Kwame Ampim-Darko Kwame Aidoo Stephen Boateng Coby Kyei Simons,CIA,CA Samuel Reuben Ofori, CIA, FCCA, CA (Ghana), CRMA Emmanuel Obeng Ansong

Revenue recognition isn't about when you get paid Most founders mess this up. They see $12,000 hit their bank account and think they just made $12,000 in revenue. Wrong. You made $1,000 in revenue...if it's an annual contract. What is Revenue Recognition? Revenue is earned income from delivering goods or services. Recognition is when it's reported on your income statement. These happen at different times. You collect $12,000 upfront for an annual subscription. But you only earned $1,000 of that in month one. The other $11,000? That's deferred revenue sitting on your balance sheet. The Journal Entries: When the sale happens: Debit Cash $12,000 Credit Deferred Revenue $12,000 Each month as you deliver service: Debit Deferred Revenue $1,000 Credit Revenue $1,000 This moves money from your balance sheet to your P&L as you actually earn it. Daily vs Monthly Methods You can recognize revenue daily or monthly. Daily method: $12,000 ÷ 365 days = $33 per day Monthly method: $12,000 ÷ 12 months = $1,000 per month Both get you to $12,000 over the year. Daily gives more precision but monthly is simpler. The Base Formula Every deferred revenue balance follows this pattern: Beginning Balance + Additions - Subtractions = Ending Balance Additions = new cash collections Subtractions = revenue recognized Track this for every contract and you'll know exactly where you stand. The Manual Nightmare Most founders start tracking this in spreadsheets. Works fine for 10 contracts Gets messy at 50. Completely breaks at 100+. Picture this...you've got 50 active contracts. Each one has different start dates, different terms, different recognition schedules. You're tracking everything in Excel. Every month you need to: Update deferred revenue balances for each contract. Calculate how much revenue to recognize. Create journal entries for each one. Make sure everything ties to your GL. I've seen many people spending 3 full days every month just on revenue recognition. And you know what happened? They'd still find errors weeks later. Daily Method Makes it Worse. Think monthly is bad? Try daily recognition with multiple contracts. $12,000 annual contract = $32.88 per day $24,000 contract = $65.75 per day $6,000 contract = $16.44 per day Now multiply that by 50+ contracts...each starting on different dates. You're calculating different daily amounts for hundreds of line items. Automation Saves Your Sanity Maxio completely eliminates this pain. Set up your revenue recognition rules once. The system automatically applies them across every contract. Daily, monthly, whatever method you choose...it just works. 30 minutes to run reports and review everything. That's it. No more manual calculations, no more formula errors, no more audit trail headaches. Everything's automatically GAAP compliant and audit-ready. === How do you currently track your revenue recognition? #MaxioPartner

What’s Revenue Recognition and why can it make or break your funding round? Imagine you run a toy shop. A customer pays you ₹1,000 today for a toy that you’ll deliver next month. Do you count that ₹1,000 as today’s revenue? No. Because you haven’t delivered the toy yet. That’s revenue recognition. You only record sales when you’ve actually delivered what you promised. Here’s where it gets tricky in real businesses: SaaS startups: Collect a year’s subscription upfront. If they count all of it today, their P&L looks inflated until an investor digs deeper. Exporters: Ship goods in March, but payment clears in April. Which financial year does it belong to? D2C brands: Marketplace shows “sales booked” but half are returns. If you book it all as revenue, your numbers are not real. At FAB MAVEN, we’ve seen this repeat often: Startups showing “hockey-stick growth” but without factoring return rates. SaaS firms losing credibility when MRR ≠ reported revenue. Exporters paying tax on money not yet received. Revenue recognition isn’t just an accounting rule but it creates a legit difference between appearing fundable and actually being fundable.  Have you ever caught a revenue number in your business that looked too good to be true?

Closed the deal? Great. But did you earn the revenue yet? This is where most founders get tripped up. They land a big contract and immediately count the whole thing as revenue. It feels good. It looks great on a dashboard. But it’s not accurate. Because cash ≠ revenue. Revenue recognition is one of the most misunderstood concepts in SMB finance. And it’s one of the easiest ways to mislead yourself and your team. Here’s what I mean: If you sign a $120K contract in January, but deliver the service over 12 months, your recognized revenue is $10K/month. Not $120K up front. Same goes for prepayments, deposits, and multi-month projects. If you haven't delivered the value, you haven’t earned the revenue. That’s not just an accounting rule. It’s an operational reality. When you don’t get this right, you: • Overspend based on inflated “monthly” revenue • Overhire thinking you’re more profitable than you are • Burn too fast because you don’t see the actual timing of revenue and delivery Here’s a simple rule of thumb: Ask yourself, if we had to refund this client tomorrow, how much would we keep? That number is usually much closer to your true earned revenue. Don’t just track cash. Don’t just celebrate closed deals. Build a financial system that tells you what’s real. That’s how you make decisions you don’t regret 6 months from now.

We've been talking to finance folks at SaaS & expecially AI companies and learning tremendously. Turns out Finance teams wants to "evenly recognizing revenue". It means that, even in the event of a company paying you money upfront for the entire year, you need to break it down to atleast MRR revenue. This might sound weird to most early stage startups, but that's how revenues are realised and growth is projected. Reason? Here it is: 1. It distorts your MRR/ARR growth Revenue recognition is blind to real product usage. Let’s say: You sell $120K in January. Customer uses 80% of credits in Q1, barely touches it after that. The Ratable rev rec will show flat $10K/month. But in reality, your product was mostly "delivered" in Q1. This makes it look like you’re growing steadily, when you’re not. You might think you have 12 months of runway on that deal, but you don’t. 2. It breaks your unit economics and cohort analysis Finance teams and boards care about things like: Revenue per user (ARPU) CAC payback Retention by usage. If you recognize revenue evenly, but usage is front-loaded or lumpy, you get a skewed picture. You might think a customer is high-value when in reality… they churn after 3 months of heavy use. 3. It’s not ASC 606 / IFRS 15 compliant for usage-based delivery Accounting standards say: Recognize revenue when the performance obligation is met. If the customer hasn’t used the product yet, you technically haven’t delivered value—so you shouldn’t recognize the revenue yet. You can get away with ratable rev if usage is reasonably predictable—but as soon as it’s not, you're taking a compliance risk. 4. Audits & Due Diligence During a funding round Investors or auditors will want to know: "Did you earn this revenue?" "What if the customer doesn’t use what they paid for?" If your rev rec isn’t tied to usage, you're exposed. You may need to restate revenue or explain gaps—never a fun conversation. At Stykite we intend to give finance teams automated, audit-ready revenue recognition tied directly to usage—no duct tape, no spreadsheets, no dev hand-holding. If that’s a challenge your team’s facing, I’d love to chat. #RevenueRecognition #UsageBasedPricing #RevOps #SaaS

Day 27/30 The 5 Steps of Revenue Recognition (IFRS 15) You run a software #company. A client signs a contract to buy: a license for your app, installation services, and two years of ongoing support. How do you recognize the #revenue? All at once? Or spread out? #IFRS15 – Revenue from Contracts with Customers gives us a 5-step model to ensure revenue is recognized faithfully and consistently. 1⃣Identify the contract Ask: Do we have an enforceable agreement? It could be written, verbal, or implied but there must be rights and obligations. 📍Example: Signed contract for license + support = valid contract. 2⃣Identify performance obligations Break down what you promised. Each distinct good or service equals a separate performance obligation. 📍 Example: License = one obligation Installation = another obligation Support = another obligation 3⃣Determine the transaction price How much consideration are you entitled to? Fixed? Variable? Discounts? 📍Example: Customer pays ₦10,000. 4⃣Allocate the price Split the total price across performance obligations, based on stand-alone selling prices. 📍Example: License normally sells for ₦6,000 Installation = ₦2,000 Support = ₦4,000 ₦10,000 is allocated accordingly to have: License = ₦5,000 Installation =₦1,667 Support = ₦3,333 5⃣Recognize revenue Recognize revenue when (or as) you satisfy each obligation. 📍Example: License = upfront (delivered once) Installation = when service is completed Support = over 2 years (time-based recognition) IFRS 15 is about giving investors and stakeholders a true picture of when value is really delivered, not when cash simply changes hands. Next time you see a bundled deal or a long-term service contract, think IFRS 15’s 5 steps. This is how you avoid misstatements and keep revenue recognition transparent. Good evening. #GloriaA.

IFRS 15: The 5-Steps Revenue Recognition Framework A standard that reshaped how companies recognize revenue — aligning accounting with economic substance and transfer of control. But how do finance leaders apply it in complex, real-world scenarios? Here’s a breakdown of the model many still find tricky, with some advanced layers worth noting 👇 1️⃣ Identify the Contract with a Customer Not every agreement is a contract under IFRS 15. ✔️ Must be enforceable. ✔️ Bundle contracts if they form one economic deal. ✔️ Adjust for modifications — they may create a new contract or change the existing one. 2️⃣ Identify Performance Obligations - Each distinct good or service = a separate obligation. - Even implicit promises (like free training or warranties) must be captured. - The key? If it provides standalone value, it should be separated. 3️⃣ Determine the Transaction Price - This is where variability creeps in: - Discounts, bonuses, penalties - Financing components (cash today vs. delivery later) - Revenue constraints (only recognize what won’t reverse) 4️⃣ Allocate the Price - Now, spread the price across obligations. - You use standalone selling prices, observable or estimated. - Bundle discounts? Spread them logically — not equally. 5️⃣ Recognize Revenue Revenue is earned when control transfers — either: - Over time (e.g., customized assets, ongoing services) - At a point in time (e.g., product delivery) - Choose the right progress measure (input vs. output), and reassess regularly. Want more? I’ve built a short FAQ & case-based summary for real use cases. Just comment "IFRS 15 FAQs" or ask for "IFRS 15 Arabic" and I’ll send you the full version. #ifrs15 #ifrs #accountingstandards #financialreporting #cma