Perpetual Software License + Post-Contract Support (PCS) — Point in Time + Ratable
Recognizing revenue on the sale of a perpetual software license bundled with annual post-contract support (maintenance/upgrades) — allocating the transaction price and recognizing license revenue immediately and support ratably.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Accounts Receivable (License Fee + First Year PCS) | Asset (+) | 120,000.00 | - |
| Software License Revenue (Right-to-Use — Functional IP — Point in Time) | Revenue (+) | - | 96,000.00 |
| Deferred Revenue — PCS / Post-Contract Support (12 Months Ratable) | Liability (+) | - | 24,000.00 |
💡 Accountant's Note
Oracle, SAP, and traditional enterprise software companies sell perpetual licenses with an annual PCS fee (typically 18–22% of license fee). Under ASC 606: the perpetual license is a FUNCTIONAL IP license — the customer gets the right to USE the software as it exists at the time of delivery (they can run the software indefinitely without updates). Revenue is recognized at the POINT IN TIME the license key is delivered (or software is made available). PCS (post-contract support = technical support + unspecified future software updates) is a DISTINCT performance obligation recognized RATABLY over the support period (typically 12 months). The transaction price ($120,000) is allocated: License SSP ($96,000) → recognized at delivery; PCS SSP ($24,000) → recognized $2,000/month. On renewal of PCS in year 2: only the PCS renewal fee ($24,000) is collected and recognized ratably. The shift from perpetual license + PCS to SaaS subscription changes this model completely — SaaS subscriptions are ratable over the subscription term (no point-in-time component).
Practitioner & Systems Framework
💻 ERP Architecture
Legacy enterprise software companies (Oracle, SAP, IBM) have massive perpetual license installed bases with annual PCS renewal streams. The license revenue is front-loaded (large license sale in year 1); PCS revenue is highly predictable annuity income. Revenue recognition systems must track: license delivery date (recognition trigger), PCS start and end dates, monthly PCS amortization, and PCS renewal timing. The PCS renewal rate (what percentage of customers renew annual support) is a key metric — high renewal rates indicate customer dependency on ongoing support.
⚠️ Audit Flags
Auditors test that license revenue is only recognized when the software is actually delivered (license key issued, software made available for download). Revenue cannot be recognized at contract signing if the license is not yet deliverable. The SSP for perpetual license vs. PCS must reflect the standalone selling prices — companies with observable standalone transactions (customers buying license only, or PCS-only renewals) have strong SSP evidence. For heavily bundled arrangements, the adjusted market assessment approach must be documented.
📄 Required Documentation
License delivery confirmation (license key issuance, software download record, or activation log), PCS term dates, SSP documentation (observable standalone prices or adjusted market assessment), transaction price allocation calculation, deferred revenue rollforward (PCS), PCS renewal history and renewal rate, and functional IP license classification analysis.
Professional Excel Template
Get the automated version of this entry. Includes built-in IFRS checks, VAT calculators, and SAP-ready upload formats.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.
Related Journal Entries
Technology (Hardware, Software & Platforms)
Hardware + Embedded Software Bundle — Distinct vs. Not Distinct Performance Obligation Analysis
Technology (Hardware, Software & Platforms)
Hardware + Future Software Updates + Services Bundle (Apple iPhone Revenue Model)
Technology (Hardware, Software & Platforms)