Study guide
12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods
Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MB-310 Exam Overview & Financial Architecture
1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework
2 Chapter 2: Chart of Accounts & Main Accounts
2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions
3 Chapter 3: Financial Dimensions & Account Structures
3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates
4 Chapter 4: Ledgers, Calendars & Currencies
4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles
5 Chapter 5: General Ledger Journals & Allocations
5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals
6 Chapter 6: Intercompany Accounting & Settlements
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing
7 Chapter 7: Cash and Bank Management
7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting
8 Chapter 8: Periodic Closing & Financial Consolidations
8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules
9 Chapter 9: Sales Tax & Withholding Tax
9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting
10 Chapter 10: Accounts Receivable Setup & Invoicing
10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts
11 Chapter 11: Credit Management & Collections
11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals
12 Chapter 12: Subscription Billing & Revenue Deferrals
12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)
13 Chapter 13: Accounts Payable & Invoice Processing
13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation
14 Chapter 14: Vendor Payments & Expense Management
14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses
15 Chapter 15: Budgeting & Budget Control
15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries
16 Chapter 16: Fixed Assets Configuration & Transactions
16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)
12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods
Key Takeaways Explain This Topic AI
Under ASC 606 and IFRS 15, revenue is recognised as performance obligations are satisfied, not when the customer is invoiced.
A deferral default on the released product sets the deferral account, recognition method, and number of periods used when that item is invoiced.
Items marked deferred by default create a deferral schedule automatically at invoicing, with no user intervention.
Recognition methods include monthly straight line by period, daily straight line by exact days, and event-based recognition triggered manually.
Last updated: August 2026
12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods
Quick Summary: Under international and US accounting standards ( ASC 606 and IFRS 15 ), revenue cannot be recognized upon billing unless the corresponding performance obligation has been fully satisfied. When customers are invoiced upfront for annual subscriptions, warranties, or maintenance contracts, the billed amount must be recorded as an Unearned Revenue liability on the Balance Sheet and recognized into Profit & Loss (P&L) revenue progressively over time. The Revenue and expense deferrals (RED) sub-module ( Subscription billing > Revenue and expense deferrals ) automates deferral schedule creation, calculates monthly amortization, and posts recognition journal entries seamlessly.
1. Accounting Principles: ASC 606 & IFRS 15 Deferral Fundamentals
The five-step revenue model under ASC 606 / IFRS 15 mandates that revenue is recognized as (over time) or when (point in time) performance obligations are fulfilled: +---------------------------------------------------------------------------------------------------------+
- | Balance Sheet to P&L Deferral Flow |
- +---------------------------------------------------------------------------------------------------------+
- | 1. INVOICING EVENT (Day 1 - Annual Contract $12,000 Billed Upfront) |
- | |
- | Accounts Receivable (120100) Unearned Revenue Liability (250100) |
- | ---------------------------- ----------------------------------- |
- | Dr. $12,000 | Cr. $12,000 (Balance Sheet Liability) |
- | |
- | 2. PERIODIC RECOGNITION (Monthly Amortization: $1,000 / month across 12 Periods) |
- | |
- | Unearned Revenue Liability (250100) Subscription Revenue (400100) |
- | ----------------------------------- ----------------------------- |
- | Dr. $1,000 | Cr. $1,000 (Profit & Loss Revenue) |
- | |
- | 3. EXPENSE DEFERRAL EQUIVALENT (Prepaid Vendor Expense e.g. 1-Year Cloud Hosting $6,000) |
- | |
- | Prepaid Expense Asset (140100) Accounts Payable (210100) |
- | ------------------------------ ------------------------- |
- | Dr. $6,000 | Cr. $6,000 |
- | |
- | Monthly Amortization: Dr. Cloud Hosting Expense (600100) $500 / Cr. Prepaid Expense (140100) $500 |
- +---------------------------------------------------------------------------------------------------------+
- Dual Capability: Revenue and Expense Deferrals
Revenue Deferrals: Defers customer billing to balance sheet liability account 250100 (Unearned Revenue) and amortizes to P&L revenue 400100 .
Expense Deferrals: Defers vendor expenditures (e.g., upfront annual software licenses, insurance policies, or sales commissions) to balance sheet asset account 140100 (Prepaid Expenses) and amortizes to P&L expense 600100 .
2. Deferral Defaults Configuration Hierarchy
Deferral defaults ( Subscription billing > Revenue and expense deferrals > Setup > Deferral defaults ) establish the rules by which Dynamics 365 Finance automatically generates deferral schedules when transaction lines are entered. +---------------------------------------------------------------------------------------------------+
- | Deferral Defaults Configuration Resolution Hierarchy |
- +---------------------------------------------------------------------------------------------------+
- | Priority Level | Configuration Level | Use Case / Specificity |
- | :-------------- | :------------------ | :------------------------------------------------------- |
- | **1 (Highest)** | **Item** | Specific high-value software SKU with unique terms. |
- | **2** | **Item Group** | Standard SaaS products group sharing common deferral GL. |
- | **3** | **Customer/Vendor** | Strategic partner with specialized recognition rules. |
- | **4 (Lowest)** | **Main Account** | Fallback rule triggered whenever a specific GL is hit. |
- +---------------------------------------------------------------------------------------------------+
- Core Configuration Parameters in Deferral Defaults
Deferral Schedule Template: Links the default recognition calculation method (Daily, Monthly, Event).
Deferral Account: The Balance Sheet liability/asset holding account (e.g., 250100 Unearned Revenue ).
Recognition Account: The P&L account where revenue or expense is recognized upon amortization (e.g., 400100 Subscription Revenue ).
Short-Term Deferral Account (Optional): Supports GAAP balance sheet reclassification, automatically separating the portion recognized within 12 months from long-term unearned revenue.
3. Deferral Schedule Calculation Methods
Dynamics 365 Finance provides three distinct recognition calculation conventions: +---------------------------------------------------------------------------------------------------------+
- | Deferral Calculation Methods Comparison |
- +---------------------------------------------------------------------------------------------------------+
- | Method | Mathematical Mechanics | Practical Business Scenario |
- | :---------------------- | :--------------------------------------------- | :---------------------------- |
- | **Straight-line by day**| `Daily Rate = Total Amount / Total Days` | Precise daily service contracts|
- | (Daily) | Month recognition = Daily Rate × Days in Month | (Feb gets 28 days, Mar 31 days)|
- | ----------------------- | ---------------------------------------------- | ----------------------------- |
- | **Monthly** | `Monthly Rate = Total Amount / Total Months` | Standard SaaS subscriptions |
- | (Equal per period) | Equal recognition across all full calendar mos.| ($1,000.00 every month). |
- | ----------------------- | ---------------------------------------------- | ----------------------------- |
- | **Event-based /** | Amount recognized upon triggering discrete | Milestone service deliverables|
- | **Milestone** | events, milestones, or manual percentages. | or training completions. |
- +---------------------------------------------------------------------------------------------------------+
- 4. The Deferral Defaults Hierarchy in Practice
Deferral behaviour is resolved at invoicing time from the most specific configuration available:
- Precedence Where it is set Typical use
- 1 (most specific) Deferral entered manually on the invoice line One-off contract with negotiated terms
- 2 Released product > Deferral defaults An item that always defers, such as a 12-month SaaS SKU
- 3 Deferral default on the item group / procurement or sales category A whole family of maintenance items
4 (fallback) Subscription billing / Revenue recognition parameters Organisation-wide default account and method
An item flagged as deferred by default builds its deferral schedule automatically the moment the invoice posts — the user never opens a deferral form. This is what makes high-volume subscription invoicing viable, and it is also the reason a mis-set default silently defers revenue that should have been recognised immediately.
5. Recognition Methods Compared
Method How the periodic amount is derived Best fit
Monthly straight line (by period) Contract value ÷ number of periods; every period is equal Clean calendar-month subscriptions
Daily straight line (by exact days) Contract value × (days in period ÷ total contract days) Contracts that start mid-month, where each month's share differs
Straight line with a stub period First and last partial periods are pro-rated, whole months in between are equal Annual contracts starting on, say, the 17th
Event-based / manual Nothing recognises until a user or process releases the period Milestone deliverables and acceptance-based revenue
A $24,000 annual subscription starting 1 January recognises $2,000 per month under monthly straight line. The same contract starting 17 January under daily straight line recognises 15/365 × $24,000 ≈ $986 in January, a full month's proportional share thereafter, and a stub in the following January. Reading which method the case study specifies before you compute is the difference between the right answer and a plausible wrong one.
Exam trap: The deferral account and the recognition method come from different levels of the hierarchy in some designs. A released product can supply the number of periods while the parameters page supplies the deferral account. Do not assume one source populates every field.
Deferral Schedules Are Created at Invoicing, Not at Order Entry
No deferral schedule exists while the sales order is open. The schedule is generated when the invoice posts , which is why cancelling an unposted order has no deferral consequences, and why a posted invoice must be credited (not merely cancelled) to unwind a schedule that should never have been created.