How to Actually Work Through the Assignment Without Getting Lost in the Steps
IFRS 15 and IFRS 16 together cover some of the most judgment-heavy territory in financial reporting. The five-step revenue model looks clean on paper — until you hit contract combinations, principal vs agent calls, or a telecom bundle where nothing has an obvious standalone price. Add IFRS 16 sub-lease classification on top, and you have a lot of moving parts. This guide tells you how to approach each one without spinning in circles.
📊 Need expert help with your IFRS 15 or IFRS 16 assignment?
Get Expert Help →What This Assignment Is Actually Testing — and Why Students Struggle With It
IFRS 15 and IFRS 16 assignments are not knowledge-recall exercises. They are judgment exercises. The standards give you a framework — five steps for revenue, a classification test for leases — but they will not tell you the answer to your specific fact pattern. Your job is to take the facts, apply the criteria, reach a conclusion, and explain your reasoning. Students who just define terms and recite standard paragraphs without connecting them to the given scenario score well below those who work through each criterion methodically and state a supported conclusion.
The scenario you are working with is a telecom context — specifically one that involves a device management and leasing contract (DLM) bundled with a mobile phone contract, plus an external service provider arrangement and a device sub-lease to an end customer. That combination is not an accident. It is designed to surface the hardest judgment calls in both standards at the same time: contract combination, distinct performance obligations, principal versus agent, standalone selling price estimation, and sub-lease classification.
The best approach? Work through each step in order. Don’t skip ahead to revenue recognition before you have pinned down what the performance obligations actually are. Don’t jump to lease income recognition before you have classified the sub-lease. The steps build on each other, and an error at Step 2 will carry through every subsequent step.
Assumptions Must Be Stated — Not Hidden
Your scenario will have gaps. Real-world fact patterns always do. Where the facts do not determine an answer, you have to make an assumption, state it clearly, and then apply the standard consistently with that assumption. Markers do not penalise reasonable assumptions. They do penalise analysis that proceeds without acknowledging the uncertainty, or that contradicts itself because assumptions shifted midway through.
The Five-Step Model — Get the Structure Right Before Anything Else
IFRS 15’s five-step model is the skeleton of your revenue analysis. Every assignment question about revenue recognition — regardless of industry, product type, or complexity — maps back to these five steps. Before you write a single sentence of analysis, sketch the five steps and list the key issues your fact pattern raises at each stage. That map will stop you from answering Step 5 before you have resolved Step 2.
The IFRS 15 Five-Step Revenue Recognition Model
Each step has defined criteria. Work through them in order — skipping ahead creates analysis that looks confident but rests on unresolved foundations.
Identify the Contract
- Legally enforceable?
- Rights and payment terms identifiable?
- Commercial substance?
- Collection probable?
- Contract combination needed?
Identify Performance Obligations
- Distinct goods or services?
- Customer benefit test
- Separately identifiable test
- Principal vs agent
- Series of distinct goods
Determine Transaction Price
- Variable consideration
- Significant financing component
- Non-cash consideration
- Payable to customer
- Constraint on estimates
Allocate Transaction Price
- Standalone selling prices
- Estimation methods
- Discount allocation rules
- Variable consideration allocation
Recognise Revenue
- Over time vs point in time
- Control transfer criteria
- Progress measurement
- Output vs input methods
Each step in the model is a separate analytical task. The temptation — especially when you are short on time — is to blend them together. Describe what the company does, call it a performance obligation, assume it is recognised over time, and move on. That approach misses the analytical precision the assignment demands. Step 2 is not the same question as Step 5. Distinct performance obligation and revenue recognition timing are different criteria with different rules.
Use the Step Headings as Your Analytical Scaffolding
In your written answer, label each section clearly by step number. This is not just organisational hygiene — it signals to the marker that you understand the structure of the model and are applying it deliberately. An answer that discusses “whether revenue should be recognised” without establishing which performance obligation it relates to, or without having first confirmed the contract exists, lacks the analytical sequencing that characterises a high-scoring response.
Identifying the Contract — Including When You Have Two That Should Be One
Most Step 1 analyses in assignment scenarios are designed to be straightforward on the basic contract identification criteria — the entity has a signed agreement, rights are identifiable, payment terms are clear, commercial substance exists, collection is probable. Tick those boxes, state your conclusion, and move on. The real work in Step 1 for a bundled telecom scenario is the contract combination question.
The Five Criteria for Contract Existence
IFRS 15 requires all five of the following to be met before a contract can be accounted for under the standard. Work through each one for your fact pattern rather than just asserting the contract exists.
| Criterion | What You Are Looking For | How to Apply It |
|---|---|---|
| Approval and commitment | Both parties have approved the contract in a form that creates enforceable rights and obligations | Usually satisfied by a signed written contract. Note if there is evidence of both parties’ commitment — formal signature, service activation, or conduct that demonstrates acceptance. |
| Identifiable rights | Entity can identify each party’s rights regarding goods or services to be transferred | For a telecom bundle, map out who gets what: customer gets mobile communications services and managed services; entity provides each. If rights are ambiguous across services, flag this. |
| Payment terms | Entity can identify the payment terms for goods or services to be transferred | Monthly billing, upfront payments, bundled pricing — identify the payment structure from the fact pattern and confirm terms are determinable. |
| Commercial substance | The contract has commercial substance — i.e., the risk, timing, or amount of entity’s future cash flows is expected to change | Almost always satisfied for commercial contracts. Only a concern if the arrangement appears to be a non-commercial exchange. |
| Probable collection | It is probable that the entity will collect the consideration it will be entitled to in exchange for goods or services transferred | Assess credit risk at contract inception. For a corporate customer, state your assumption about creditworthiness. This criterion is about the customer’s ability and intention to pay — not whether payment is guaranteed. |
Contract Combination — The Step 1 Issue That Matters Most in Telecom Scenarios
Here is where your analysis needs to do real work. The scenario presents two contracts: a device and leasing management (DLM) contract and a mobile phone contract. Taken separately, they look like independent arrangements. But there is a 10% discount on the mobile phone contract that is directly conditional on the customer also entering into the DLM contract. That pricing dependency is the trigger for contract combination under IFRS 15.
IFRS 15 requires contracts to be combined and accounted for as a single contract if any of these criteria are met: the contracts are negotiated with a single commercial objective, the amount of consideration in one contract depends on the price or performance of the other, or the goods and services promised are a single performance obligation. The 10% discount satisfies the second criterion directly — the price of the mobile contract is dependent on entering the DLM contract.
State the Impact of Your Step 1 Conclusion
Do not just conclude that the contracts should be combined and then proceed to Step 2. State the consequence. If the contracts are not combined, the 10% discount disappears from the allocation — that means managed services revenue gets overstated and mobile communications revenue gets understated. Markers want to see that you understand the financial reporting implications of your technical conclusion, not just the technical conclusion itself.
Identifying Performance Obligations — The Distinct Test Has Two Parts, and You Need Both
Step 2 is where many answers fall apart. Students identify what the entity does — provides managed services, provides mobile communications, activates devices — and call each one a performance obligation. But IFRS 15 does not say every promised good or service is automatically a separate performance obligation. It must be distinct. And distinct has a specific two-part test.
Part one: the customer can benefit from the good or service either on its own or together with other readily available resources. Part two: the entity’s promise to transfer the good or service is separately identifiable from other promises in the contract. Both parts must be satisfied. Miss either one and it is not a distinct performance obligation.
Managed Services (Repair, Help Desk, Administration)
Customers can obtain these services independently from third-party providers — so the standalone benefit test is met. These services are not so integrated with the device or the mobile contract that they lose their individual identity — so the separately identifiable test is met. Conclusion: distinct performance obligation. Recognised over the service period.
Mobile Communications Services (Calls, Data, SMS)
Mobile communications services are routinely sold and used independently — customers buy SIM-only plans constantly. The benefit is clear and standalone. The promise to provide communications is not integrated with managed services in a way that eliminates individual identity. Conclusion: distinct performance obligation. Recognised over the contract term.
Upfront Services — Activation / Shipping
Activation and shipping are preparatory steps. The customer cannot benefit from activation independently — the value comes entirely from the ongoing service it enables. These are not separately identifiable from the primary service promise. Conclusion: not a distinct performance obligation. They are inputs to the delivery of the core service, not separate promises.
The critical thing to show in your analysis is that you applied both parts of the distinct test to each promised good or service. A single-sentence conclusion with no working is not analysis. Walk through the criteria. Show your reasoning. Then conclude.
Activation Is a Classic Trap — Don’t Fall Into It
A lot of students see “activation” in a telecom scenario and treat it as a separate performance obligation because it happens at a specific point in time. That instinct is wrong. The question is not when it happens — the question is whether the customer can benefit from it independently and whether it is separately identifiable. Activation exists to enable the ongoing service. Without the service, activation has no value to the customer. That makes it a preparatory activity, not a distinct performance obligation.
Principal vs Agent — This Changes Gross vs Net Revenue, Which Changes Everything Downstream
Once you have identified what the performance obligations are, Step 2 requires one more analytical layer for arrangements involving third parties: is the entity acting as principal or as agent? This matters enormously for revenue reporting — a principal recognises gross revenue (the full amount charged to the customer), while an agent recognises only the net fee or commission retained.
The core test under IFRS 15 is control. An entity is a principal if it controls the specified good or service before it is transferred to the customer. Three indicators help determine control: whether the entity is primarily responsible for fulfilling the promise, whether it holds inventory risk, and whether it has discretion in setting the price.
| Service | Primary Responsibility | Inventory Risk | Pricing Discretion | Conclusion |
|---|---|---|---|---|
| Managed Services (Repair, Help Desk, Admin) | External service provider performs the service. Entity is facilitating, not fulfilling. | No inventory risk — services are provided by the external provider. Assumes no minimum purchase commitment. | Entity sets price as part of bundle (assumed). | Agent — recognise net revenue only |
| Mobile Communications Services | Entity is primarily responsible for providing network access, calls, data, and SMS to the customer. | Not applicable — service-based, no inventory. | Entity sets price (assumed). | Principal — recognise gross revenue |
The impact of getting this wrong is significant. If the entity incorrectly treats managed services as a principal arrangement, it recognises gross revenue instead of net. That overstates both revenue and costs with no effect on gross margin — but it inflates EBITDA if the costs sit below that line, and it misrepresents the economic substance of the arrangement.
State the SOX Control Implication If Your Assignment Asks for It
In a Vodafone-style scenario, any principal vs agent misclassification is a material financial reporting risk. If your assignment is framed around a business context where internal controls are relevant, note that appropriate controls are needed to prevent principal treatment where agent treatment applies. An overstated revenue figure from a gross vs net error will flow through to EBITDA, operating profit, and potentially to management performance targets — which creates the incentive for misclassification that SOX controls are designed to prevent.
Transaction Price and Allocation — Where to Use the Estimation Methods and How to Handle the Discount
Step 3 asks what the entity expects to receive in exchange for transferring the promised goods and services. In a standard bundled telecom contract with fixed monthly fees, the transaction price is relatively straightforward — it is the total contracted amount over the term. Where Step 3 gets complicated is when variable consideration, significant financing components, or consideration payable to the customer is involved. Check your fact pattern for each of these before concluding the transaction price is simply the stated contract amount.
Step 4 is where allocation happens. You take the total transaction price established in Step 3 and split it across the performance obligations identified in Step 2, based on their relative standalone selling prices. That sounds simple. It is not, because many bundled goods and services do not have observable standalone prices.
Standalone Selling Price — What to Do When You Cannot Observe It
IFRS 15 requires the standalone selling price to be determined at contract inception. The best evidence is an observable price — what the entity charges when it sells that good or service separately. If an observable price does not exist or is not available, estimation is required. Three approaches are permissible.
Adjusted Market Assessment Approach
Estimate the price a customer in the market would pay for that good or service. Look at competitor prices for similar goods or services, adjusted for the entity’s cost structure and margins. Use when market reference points exist but your entity does not sell the item separately.
Cost Plus Margin Approach
Forecast the expected cost of satisfying the performance obligation and add an appropriate margin. Useful when internal cost data is reliable and margins are observable for similar services. Be clear about what margin rate you are using and why it is appropriate for the specific good or service.
Residual Approach
Subtract the observable standalone selling prices of all other performance obligations from the total transaction price. What remains is allocated to the performance obligation with no observable price. Only permissible when the standalone selling price is highly variable or uncertain. Not a default — it is a last resort.
Allocating the Discount — Default Rule vs Exception
This is one of the more nuanced allocation issues in a telecom bundle. The default rule under IFRS 15 is that a discount in a contract is allocated proportionately to all performance obligations based on their relative standalone selling prices. You spread the discount across everything.
The exception is that a discount can be allocated entirely to one or more — but not all — performance obligations if three specific conditions are all met: the entity regularly sells each of the performance obligations on a standalone basis; the entity also regularly sells some (but not all) of those goods or services bundled together at a discount; and the discount in the current contract is consistent with those prior bundled discounts, making it observable that the discount relates to specific performance obligations rather than the bundle as a whole.
In the Vodafone-style scenario, the 10% discount on the mobile contract applies when the customer also signs the DLM contract. Whether the exception applies depends entirely on whether those three conditions are satisfied. If they are not — and your fact pattern may indicate they are not — default proportionate allocation applies. That means the discount is spread across managed services and mobile communications in proportion to their respective standalone selling prices. Show this calculation. Do not just state a conclusion; show the maths.
Show the Allocation Table Even If the Numbers Are Assumed
Markers want to see the mechanics. Even if you are working with assumed standalone selling prices (which is common in case study assignments), lay out a table: performance obligation, standalone selling price, relative percentage, allocated transaction price. It shows you understand the allocation process. An answer that just says “revenue is allocated based on relative standalone selling prices” without demonstrating how that works in numbers is leaving marks on the table.
Recognising Revenue — Over Time or at a Point in Time, and Why the Answer Matters
By the time you reach Step 5, you should know exactly which performance obligations you are recognising revenue for and how much revenue is allocated to each. Now the question is timing. IFRS 15 says revenue is recognised when — or as — a performance obligation is satisfied. The primary distinction is between recognition over time and recognition at a point in time.
A performance obligation is satisfied over time if any one of three criteria is met: the customer simultaneously receives and consumes the benefits as the entity performs; the entity’s performance creates or enhances an asset that the customer controls as it is created; or the entity’s performance does not create an asset with an alternative use, and the entity has an enforceable right to payment for performance completed to date.
Both performance obligations in this scenario are recognised over time. That is not always the case — if a product is transferred at a single point (say, a handset sale), revenue is recognised at the point the customer obtains control. In your analysis, always start with the over-time criteria. Only if none of the three criteria are satisfied does the entity recognise at a point in time.
IFRS 16 Lease Classification — The Criteria, the Accounting Entries, and the P&L Impact
IFRS 16 changed lessee accounting fundamentally. Before the standard, operating leases stayed off balance sheet entirely. Under IFRS 16, most leases come on balance sheet for lessees: a right-of-use (ROU) asset and a corresponding lease liability. The classification question — finance lease vs operating lease — now primarily affects lessor accounting, not lessee accounting.
For lessees, the first question is whether a contract contains a lease at all. A lease exists when a contract conveys the right to control the use of an identified asset for a period of time in exchange for consideration. Two elements of control must both be present: the right to obtain substantially all the economic benefits from the asset’s use, and the right to direct the use of that asset throughout the period.
Identifying a Lease in a Telecom Device Scenario
Work through the asset identification and control tests in order. Both must be satisfied before the IFRS 16 lessee model applies.
Identified Asset
- Is there a specific asset? Yes — a specific mobile phone identified by IMEI or serial number.
- Does the supplier have a substantive substitution right? If they can swap out the device at any time for their own benefit, there is no identified asset. In this scenario, there are no substantive substitution rights — so the identified asset test is met.
Right to Obtain Economic Benefits
- Does the customer have exclusive use of the device for the full term?
- Can the customer use the device for all purposes — calls, data, apps, photos, sub-lease?
- In the scenario: the lessee has exclusive physical possession for the full 24-month term. Test met.
Right to Direct the Use
- Who decides how and for what purpose the asset is used?
- In the scenario: the lessee controls configuration, applications, connectivity, and usage purpose — business or personal.
- The lessee also has the right to sub-lease the asset. Right to direct use is met.
Head Lease Accounting — The Lessee Journal Entries
Once you establish a lease exists, the lessee (in this case, the entity leasing the device from an external provider) recognises an ROU asset and a lease liability at commencement. The entries that follow:
Know the P&L Impact — EBITDA vs Below EBITDA
This is a key discussion point in any IFRS 16 question. Under IFRS 16, the lessee replaces a single operating lease expense (which sat above EBITDA) with depreciation and interest. Depreciation is typically included in EBITDA calculations; interest is below EBITDA. The practical effect is that IFRS 16 front-loads total expense in the early periods (higher interest when the liability is largest) and improves EBITDA relative to the old operating lease model. For any assignment that asks about business impact or comparability, this P&L shift is central to your answer.
Sub-Lease Accounting — Finance or Operating, and What the Intermediate Lessor Records
The sub-lease layer is where IFRS 16 gets genuinely difficult. The entity (now acting as an intermediate lessor) takes the device it has leased from the head lessor and leases it out to an end customer. IFRS 16 requires the intermediate lessor to classify the sub-lease as either a finance lease or an operating lease — but using a reference point that catches many students off guard: the classification is made by reference to the right-of-use asset from the head lease, not by reference to the underlying physical asset.
This matters because the ROU asset has a fixed remaining life tied to the head lease term. If the sub-lease term covers substantially all of the remaining life of the ROU asset, it will typically qualify as a finance lease — even if the physical device has a much longer economic life.
The Classification Test — Applying the Finance Lease Indicators
| Finance Lease Indicator | Application to the Sub-Lease Scenario | Conclusion |
|---|---|---|
| Lease term covers major part of economic life | Sub-lease term (24–36 months) equals 100% of the economic life of the ROU asset from the head lease. The head lease and sub-lease terms are co-extensive. | Indicator met |
| Present value of payments is substantially all of fair value | If the present value of sub-lease payments approximates the carrying value of the ROU asset at commencement of the sub-lease, this indicator is met. The assumption in the scenario is that this is satisfied. | Indicator met (on assumption) |
| Transfer of ownership at end of term | There is no purchase option for the end customer. Ownership does not transfer. | Indicator not met |
| Bargain purchase option | Not present in the scenario. | Indicator not met |
| Specialised asset with no alternative use | A standard mobile handset can be re-leased to another customer — not a specialised asset. | Indicator not met |
The first two indicators are enough to support a finance lease conclusion in this scenario. The sub-lease term covers the entire economic life of the ROU asset, and the present value of sub-lease payments is substantially all of the ROU asset’s fair value. Conclusion: finance lease.
Accounting Entries for Finance Sub-Lease (Intermediate Lessor)
If the sub-lease is instead classified as an operating lease — which would apply if the sub-lease term covers significantly less than the head lease term — the accounting is different. The intermediate lessor retains the ROU asset, continues to recognise depreciation and interest on the head lease, and recognises sub-lease income on a straight-line basis over the sub-lease term.
Practical Rule of Thumb for Sub-Lease Classification
In practice, if the sub-lease term is more than approximately 75% of the remaining head lease term, finance lease classification is typically the result. The exact threshold depends on the present value calculation, but this heuristic helps you flag early in your analysis which classification direction you are heading. State this explicitly in your answer, then work through the formal indicators to support it. Do not rely on the rule of thumb alone — it is a navigation tool, not a substitute for the technical analysis.
Verified External Source: IASB — IFRS 16 Lessor Accounting Implementation Guidance
The International Accounting Standards Board (IASB) publishes detailed implementation guidance for IFRS 16, including illustrative examples covering sub-lease classification by intermediate lessors. Example 22 in the IFRS 16 Illustrative Examples specifically addresses sub-lease classification and the accounting entries for a finance sub-lease. These examples are authoritative guidance, freely accessible at ifrs.org. They are not a substitute for the standard itself, but they show exactly how the IASB intended the classification criteria to apply in practice. For citation purposes, reference the IASB directly: International Accounting Standards Board. (2016). IFRS 16 Leases: Illustrative Examples. IFRS Foundation. https://www.ifrs.org/issued-standards/list-of-standards/ifrs-16-leases/
Common Errors That Cost Marks — and the Fix for Each
| # | The Error | Why It Costs Marks | The Fix |
|---|---|---|---|
| 1 | Treating every promised good or service as a distinct performance obligation without applying the two-part test | IFRS 15 does not say every promised item is automatically a separate obligation. The distinct test has two parts, and both must be satisfied. Skipping the test and listing performance obligations as if the conclusion is obvious shows you do not understand the standard’s analytical requirements. | For every promised good or service, explicitly work through both criteria: customer benefit test and separately identifiable test. Reach a conclusion on each, then state whether it qualifies as a distinct performance obligation. This is more work per item — but that is what the question requires. |
| 2 | Missing the contract combination analysis in Step 1 | If two contracts should be combined and you treat them separately, you will misallocate the discount entirely. That error will compound through Step 4 and produce revenue figures that do not reflect the commercial reality of the arrangement. | When the fact pattern involves multiple contracts with the same customer entered at or near the same time, always ask whether the combination criteria are triggered. A pricing dependency between contracts is the clearest trigger. State it, apply the criteria, conclude. |
| 3 | Confusing principal vs agent with the distinct performance obligation analysis | These are two different questions. Distinct tells you whether a performance obligation exists. Principal vs agent tells you how to measure the revenue from that obligation. Students often blur them — concluding that because managed services are contracted with an external provider, they are not a performance obligation. That is wrong. Whether the entity is principal or agent does not determine whether a performance obligation exists. | Keep the questions separate. First confirm whether a distinct performance obligation exists (Step 2 — distinct test). Then, for any obligation involving a third party, apply the principal vs agent analysis (also Step 2, but a separate section of the analysis). |
| 4 | Applying the residual approach for standalone selling price estimation as a default | IFRS 15 only permits the residual approach when the standalone selling price is highly variable or uncertain. It is not an alternative to the adjusted market assessment or cost plus margin approaches. Using residual as your default method — because it is easier — is technically wrong and markers will penalise it. | For each performance obligation, first determine whether an observable standalone selling price exists. If not, consider the adjusted market assessment approach. Cost plus margin is the second option. Residual is the last resort when prices are genuinely variable or uncertain. State which method you are using and why it applies. |
| 5 | Classifying the sub-lease by reference to the underlying physical asset instead of the ROU asset | IFRS 16 explicitly states that a sub-lease is classified by reference to the right-of-use asset, not the underlying asset. This distinction is one of the most commonly tested points in IFRS 16 questions, precisely because it is counterintuitive. A device with a 5-year economic life can generate a finance sub-lease over 24 months if the ROU asset’s remaining life is also 24 months. | State clearly in your analysis that you are classifying the sub-lease by reference to the ROU asset from the head lease, per IFRS 16 paragraph 55. Then apply the finance/operating lease indicators with reference to the ROU asset’s remaining term and carrying value. |
| 6 | Ignoring the P&L and EBITDA implications of accounting choices | Technical accounting answers that do not address business impact are incomplete in most assignment contexts. Whether managed services are principal or agent affects EBITDA. Whether the sub-lease is finance or operating affects when income is recognised and what sits above versus below EBITDA. These are not incidental observations — they are part of the answer. | After each technical conclusion, add one or two sentences on the financial reporting impact. What changes in the income statement? What changes in EBITDA? What balance sheet line items are affected? This does not need to be elaborate, but it should be present. |
| 7 | Writing conclusions without stated assumptions where the fact pattern is ambiguous | Every assignment scenario has gaps. If you proceed without acknowledging them, you look like you missed them. If you make assumptions but do not state them, the marker cannot follow your reasoning. Unstated assumptions are invisible scaffolding — they might be holding up your answer, but nobody can see them. | When the fact pattern does not determine an answer, write: “Assuming that [X], then [Y] applies, and the conclusion is [Z].” Then proceed consistently with that assumption. Make the assumption reasonable — use commercial logic — and keep it consistent throughout your answer. |
Pre-Submission Checklist — IFRS 15 and IFRS 16 Assignment
- Step 1: All five contract existence criteria addressed, not just stated as met
- Step 1: Contract combination analysis included where multiple contracts exist
- Step 1: Financial reporting impact of the combination conclusion stated
- Step 2: Two-part distinct test applied to every promised good or service individually
- Step 2: Conclusion on each item — distinct PO, combined PO, or not a separate PO
- Step 2: Principal vs agent analysis completed for any third-party arrangement
- Step 2: Gross vs net revenue implication of principal/agent conclusion stated
- Step 3/4: Standalone selling price approach identified and named, with justification
- Step 4: Discount allocation — default proportionate rule or exception applied with conditions checked
- Step 4: Allocation shown in tabular form, even with assumed figures
- Step 5: Over-time vs point-in-time conclusion reached with specific criterion cited
- IFRS 16 — Head Lease: Identified asset and control tests both addressed
- IFRS 16 — Head Lease: Initial and subsequent journal entries shown
- IFRS 16 — Head Lease: EBITDA impact explained
- IFRS 16 — Sub-lease: Classified by reference to ROU asset, not underlying asset
- IFRS 16 — Sub-lease: Finance lease indicators applied; conclusion reached
- IFRS 16 — Sub-lease: Journal entries shown for finance sub-lease treatment
- All assumptions stated clearly at the point where they are made
- Financial reporting impact addressed for each major conclusion
FAQs: IFRS 15 and IFRS 16 Assignments
What the Best Answers on This Assignment Do That Average Ones Don’t
The highest-scoring answers on IFRS 15 and IFRS 16 assignments have one thing in common: they do not just describe the standards. They apply them. Every paragraph moves from criterion to fact to conclusion. The student is never just telling you what IFRS 15 says about performance obligations in the abstract — they are saying: here is what the standard requires, here is what the fact pattern shows, and here is why that leads to this conclusion.
They also do not hide behind the complexity. Where judgment calls exist — principal vs agent, discount allocation, sub-lease classification — they acknowledge the ambiguity, lay out the competing considerations, and reach a clear conclusion with a stated rationale. That is what professional accounting judgment looks like. That is what the question is training you to do.
The mechanics matter too. Journal entries need to balance. Allocation tables need to add up. Classification conclusions need to reference the specific IFRS criterion, not just the general idea. Small technical errors in entries or calculations suggest the concepts are not fully embedded, even when the surrounding written analysis is strong.
If you need support working through the analysis, structuring your answer, or reviewing your technical conclusions against the standard — the team at Smart Academic Writing covers IFRS assignments, financial reporting case studies, and accounting papers at undergraduate and postgraduate level. You can visit our accounting homework help service, our research paper writing service, our editing and proofreading service, or contact us directly with your assignment details and deadline.