Skip to main content
iVentureTeam
Odoo Implementation

ASC 606 in Odoo: Five-Step Model, Deferred Revenue and Audit Trail

How to run ASC 606 in Odoo: the five steps mapped to Odoo, deferred revenue entries, standalone selling price allocation and an auditor-ready trail.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 20, 202613 min read1 view
ASC 606 in Odoo: Five-Step Model, Deferred Revenue and Audit Trail cover

Most US finance teams that move to Odoo ask the same question in the first workshop: can it keep us on ASC 606? Our Odoo consulting services start by mapping each contract type to the five steps before anything is configured.

Related service: Odoo implementation services — fixed-scope implementations with a named senior team.

This guide is for controllers, CFOs and accountants at software, services and equipment firms that report under US GAAP. If you are new to how ledgers, journals and reports fit together, read how Odoo Accounting works first.

What is ASC 606 and what are the five steps?

ASC 606 is the US GAAP standard for revenue from contracts with customers, and it works through five steps. The FASB and IASB issued the converged guidance in May 2014, with IFRS 15 as the international twin.

The revenue recognition overview on Wikipedia lists the ASC 606 five steps in the same order your auditor will use:

  1. Identify the contract: committed parties, clear rights and payment terms, and commercial substance.
  2. Identify the performance obligations: each distinct good or service you promised.
  3. Determine the transaction price: the consideration you expect to receive.
  4. Allocate the transaction price: split it across obligations by standalone selling price.
  5. Recognize revenue: when or as the customer gains control of each good or service.

Delivery, not invoicing, drives revenue. An annual invoice paid in January is mostly a liability, called deferred revenue, until you deliver.

How does Odoo map to the ASC 606 five-step model?

ASC 606 in Odoo: Five steps, where each lives

Odoo covers steps 1, 3 and 5 with standard records, while steps 2 and 4 depend on how you design products, invoice lines and journal entries. The table shows where each step lives in Odoo revenue recognition.

ASC 606 stepWhat it asksWhere it lives in OdooNative or custom
1. ContractIs there an enforceable agreement?Signed quotation or sales order, Sign appNative
2. Performance obligationsWhich promises are distinct?One product or invoice line per obligationDesign choice
3. Transaction priceWhat will the customer pay?Sales order total, discounts, pricelistsNative
4. AllocationHow is the price split by standalone selling price?Allocated line prices or a reclass entryProcess or custom
5. RecognitionWhen is each obligation satisfied?Deferred dates on invoice lines, milestonesNative for time-based
EvidenceCan you prove it to an auditor?Hashed journals, lock dates, audit trail reportNative

The practical rule: give every performance obligation its own product and invoice line. Once each promise sits on its own line, Odoo can defer or recognize it on its own schedule.

How does Odoo deferred revenue work?

Odoo deferred revenue works per invoice line: you enter a start and end date, and Odoo posts entries that move the amount from a deferred revenue liability into income over that period. No separate contract module is needed for time-based revenue.

According to the Odoo deferred revenues documentation, you set three defaults under Accounting, Configuration, Settings:

  • Journal: where deferral entries are posted.
  • Deferred Revenue account: a current liability that holds revenue until it is recognized.
  • Generate Entries: on invoice validation, or Manually and Grouped.

You also choose how Odoo calculates the spread. Days divides the amount by the number of days in the period. Months gives each full month an equal share and prorates partial months. Full Months treats any started month as complete.

Two testing details: the server checks once a day whether an entry must be posted, so a deferral can take up to 24 hours to post. The Deferred Revenue report only includes invoices dated before its period end.

What journal entries does Odoo post for deferred revenue?

Odoo posts one entry that moves the invoice amount from income to deferred revenue, then one entry per period that moves a share back to income. Here is an illustrative example for a US$12,000 annual support contract invoiced on 1 January with Months as the basis.

DateEntryDebitCredit
1 JanCustomer invoiceAccounts receivable 12,000Support revenue 12,000
1 JanDeferral entrySupport revenue 12,000Deferred revenue 12,000
31 JanMonthly recognitionDeferred revenue 1,000Support revenue 1,000
28 FebMonthly recognitionDeferred revenue 1,000Support revenue 1,000
31 AugBalance check8,000 recognized4,000 still deferred
31 DecFinal monthDeferred revenue 1,000Support revenue 1,000

The figures are illustrative, but the pattern matches Odoo's own example, where a January invoice deferred over 12 months has two thirds recognized by the end of August. Sales tax on the invoice is recognized at once and does not move with the deferral.

Start dates matter. With Months, a contract starting on the 15th recognizes half a month first and ends in a thirteenth month; Full Months avoids that. Write your rule into your revenue policy.

Should you generate deferral entries on validation or manually grouped?

Generate on validation when you have a modest number of deferred lines, and switch to Manually and Grouped when hundreds of deferred invoices would flood the journal. Both give the same balances; they differ in volume and review effort.

FactorOn invoice validationManually and Grouped
When entries appearAs soon as the invoice is postedWhen you click Generate Entries at month end
Entries createdOne deferral plus one per period, per invoiceOne grouped entry plus its reversal each month
Drill-downDeferred Entries button on each invoiceDeferred Revenue report by account
Review effortMany small entries to scanOne entry per month to review and approve
Best forLow to medium invoice volumeHigh-volume SaaS or service billing

Grouped mode posts an entry on the last day of the month and reverses it the next day, so each invoice is still recognized only once.

How do you handle multiple performance obligations in Odoo?

Split every bundle into one invoice line per performance obligation, allocate the price by standalone selling price, and give each line its own recognition rule. Odoo does not run the standalone selling price allocation for you, so the math happens in your process or a custom module.

Take an illustrative US$30,000 bundle: a software license, 12 months of support and onboarding training. Standalone selling prices are US$20,000, US$10,000 and US$5,000, so the total is US$35,000 and the bundle discount is spread across all three.

Performance obligationStandalone priceAllocated priceRecognition in Odoo
Software license20,00017,142.86At once, on delivery
12 months of support10,0008,571.43Deferred, 714.29 a month
Onboarding training5,0004,285.71Deferred to the delivery month
Total35,00030,000.00Ties to the contract price

A workable set-up in standard Odoo follows four steps:

  1. Products: create one product per obligation, each mapped to its own income account.
  2. Allocation: price the invoice lines at allocated amounts, or invoice at contract prices and post a reclass entry each month.
  3. Dates: set deferred start and end dates on the support line and the training line.
  4. Review: check the Deferred Revenue report against your allocation sheet before closing.

If allocated prices confuse customers, book the allocation as a journal entry instead. Our Odoo customization services can add standalone selling price fields and an allocation wizard when volume justifies it.

Which ASC 606 revenue patterns does Odoo not cover natively?

Odoo's deferral engine is time-based only, so revenue that depends on usage, progress, judgment or contract changes needs extra design. List these early so they land in scope, not in the first audit.

  • Uneven spreads: there is no percentage field for deferrals, so an 80% first month needs separate invoice lines, as an Odoo forum answer on deferred revenue explains.
  • Manual journal entries: the same answer notes deferrals do not work on manual journal entries, only on invoice lines.
  • Progress-based revenue: construction and long projects measured by cost or progress are covered in our guide to percentage of completion revenue recognition in Odoo.
  • Milestone billing: Odoo milestone invoicing controls when you bill, which is not always when control transfers.
  • Variable consideration: rebates, credits and usage fees need an estimate policy and adjusting entries.
  • Contract modifications: a mid-term change means a credit note and new invoice, or a manual adjustment, so test the flow in staging.

Recurring billing is a separate topic. For renewals, upsells and MRR, see our Odoo subscriptions guide; deferral then applies to each subscription invoice line as described above.

How do you build an Odoo audit trail your auditor will accept?

An auditor-ready Odoo audit trail combines hashed journals, lock dates, restricted deletion and a documented review of deferred balances. Each control answers a different auditor question.

The Odoo data inalterability documentation explains that Secure Posted Entries with Hash gives each secured entry a SHA-256 fingerprint chained to the previous one. Once a restricted journal has a posted entry, the setting cannot be turned off.

  • Hash chain: enable hashing on sales and miscellaneous journals, including your deferral journal.
  • Inalterability report: download the check report from Accounting settings to show every chain is intact.
  • Lock dates: the Odoo year-end and lock dates guide shows how a Lock Everything date blocks edits, while exceptions and reasons are logged on the company record.
  • No deletion: a forum thread on the restrictive audit trail confirms posted invoices can then no longer be deleted.
  • Audit trail report: the Odoo Accounting reports list includes Audit trail, Deferred revenue and General ledger.

Odoo 20 extends hashing to cash journals, as our Odoo 20 accounting release notes show. For approvals and segregation of duties, pair this with our Odoo internal controls guide.

How do you reconcile deferred revenue at month end?

Reconcile deferred revenue monthly by tying the Deferred Revenue report to the balance sheet account and explaining every movement. A clean rollforward is the document auditors ask for first.

  1. Post all invoices for the month, so new deferrals exist.
  2. Generate entries if you use Manually and Grouped mode.
  3. Run the Deferred Revenue report and compare its total with the deferred revenue account on the balance sheet.
  4. Build the rollforward: opening balance, plus new deferrals, less revenue recognized, less credit notes, equals closing balance.
  5. Review exceptions: lines with no end date, dates before the invoice date, or cancelled contracts.
  6. Set the lock date once the review is signed off.

Analytic tags make revenue reporting by product line or region easier; see our guide to Odoo analytic accounting. The full close sequence is in our Odoo month-end close checklist.

Which industries need ASC 606 setups in Odoo?

Any business that bills before it delivers, or sells bundles, needs a deliberate ASC 606 set-up in Odoo. The table shows the usual pressure points.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
SaaS and softwareAnnual prepaid licenses and supportDeferred dates per line, grouped modeConfigure deferrals, test start-date rules
Professional servicesRetainers and prepaid blocks of hoursDeferred revenue released as hours are deliveredDesign timesheet-based release entries
Equipment with installationHardware, install and warranty sold togetherOne line per obligation, allocated pricesBuild the allocation sheet or wizard
Training and educationCourses paid before they runDeferral to the course monthMap courses to products and dates
ContractorsRevenue over time on long projectsPercentage of completion with WIPLink to our dedicated contractor guide

Do you need revenue recognition software beside Odoo?

Most small and mid-size firms with time-based contracts do not need separate revenue recognition software; firms with heavy bundling, usage fees or frequent modifications often do, or need a custom module. Use these tests to decide.

  • Stay native if most revenue is prepaid service spread evenly over time.
  • Add custom logic if many deals bundle items at a discount and need standalone selling price allocation.
  • Consider a subledger if usage-based fees, rebates and mid-term changes affect a large share of revenue.
  • Check hosting: Odoo Online is incompatible with custom modules, so a custom allocation module needs Odoo.sh or on-premise.

To size the work, try the Odoo project estimate tool for an indicative cost and timeline.

How iVentureTeam helps with ASC 606 in Odoo

Planning ASC 606 work? Size it first

iVentureTeam turns your revenue policy into Odoo products, deferral rules and controls that hold up at audit time. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Contract mapping: each contract type walked through the five steps, with gaps listed before go-live.
  • Deferral set-up: accounts, journals, calculation basis and month-end routine, tested on your real invoices.
  • Bundle allocation: a standalone selling price sheet, or a custom wizard from our customization team.
  • Audit controls: hashing, lock dates, restricted deletion and a deferred revenue rollforward your auditor can follow.
  • Ongoing support: reviews after each close and help when Odoo upgrades change accounting screens, through our consulting team.

Odoo accounting customization case study: Fernando Tax Management

A Dutch tax practice moved to Odoo 18 and needed accounting data and compliance reports it could trust. The project shows the kind of accounting fixes and custom reports an ASC 606 set-up often needs.

Fernando Tax Management B.V. had outgrown a rigid legacy system. Manual entry across systems created duplicate and inconsistent records, and a hidden journal lines issue was obscuring accounting data.

We migrated the firm to Odoo 18 in a 10-week migration and customization project. We resolved the hidden journal lines issue, built a custom office cost tracking workflow in Sales and Purchase, and developed custom tax compliance reports for its Dutch and Curaçao contexts.

The firm now runs on one automated system, with reports it can hand to clients and regulators without a second pass. Read the Fernando Tax Odoo accounting automation case study.

The bottom line on ASC 606 in Odoo

Odoo is a solid base for ASC 606 when every performance obligation has its own invoice line and your controls are switched on from day one. Time-based deferrals are native; allocation and usage-based revenue need design.

Write your revenue policy first, then configure Odoo to follow it, and test a full year of contracts in staging before your first close.

Ready to map your contracts to ASC 606 in Odoo?

Book a revenue set-up review

Bring three real contracts and we will show you how each one flows through Odoo. Talk to an Odoo revenue recognition consultant, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

Is Odoo ASC 606 compliant?

+

Odoo provides the tools, not the compliance. Deferred revenue, hashed journals and lock dates support ASC 606, but your revenue policy, allocation method and reviews decide whether your statements comply.

How does Odoo handle deferred revenue?

+

You set start and end dates on an invoice line. Odoo moves the amount to a deferred revenue liability, then recognizes it in income by Days, Months or Full Months, either on invoice validation or in a grouped monthly entry.

Can Odoo allocate a bundle price by standalone selling price?

+

Not out of the box. Price each invoice line at its allocated amount, or invoice at contract prices and post a reclass entry. A custom module can add standalone selling price fields and an allocation wizard.

What are the five steps of ASC 606?

+

Identify the contract, identify the performance obligations, determine the transaction price, allocate the price to the obligations, and recognize revenue when or as each obligation is satisfied.

Does Odoo have an audit trail for accounting?

+

Yes. Odoo offers an Audit trail report, journal hashing with a SHA-256 chain, an inalterability check report and lock dates whose exceptions are logged. Restricting deletion stops posted invoices from being deleted.

Can I defer revenue unevenly in Odoo, such as 80% in month one?

+

Not on a single line, because deferrals have no percentage field. Split the amount across two or more invoice lines with different date ranges, or post a manual adjustment.

Is deferred revenue an asset or a liability?

+

Deferred revenue is a liability. It represents goods or services you still owe the customer, and it moves to revenue on the income statement as you deliver them.

Does Odoo support percentage of completion revenue?

+

Not as a native deferral rule. Contractors usually combine project costs, analytic accounts and period-end entries; our dedicated percentage of completion guide covers that set-up step by step.

Do I need Odoo Enterprise for deferred revenue?

+

The built-in deferral feature is part of Enterprise accounting. Community users have discussed OCA modules such as account_spread_cost_revenue as the closest equivalent, so test any module against your policy first.

Free Odoo support review

Want an honest audit of your Odoo?

We review your setup, customizations and data, score the risks and send a prioritised list of fixes with the effort for each.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.