PSAK 201: Revenue from Contracts with Customers
If you are an accountant or auditor in Pakistan dealing with PSAK 201, you already know the basic framework. It mirrors IFRS 15 almost exactly. The five-step model is carved into every finance textbook now. But the real world does not always fit neatly into the five steps, and that is where things get complicated. The standard was adopted in Pakistan several years ago, but the updates and interpretive guidance have continued to accumulate. Most of the significant changes come from the IFRS Interpretations Committee and amendments issued by the ICPAK. Here is what actually matters in practice. PSAK 201 applies to all contracts with customers to provide goods or services, except for leases, insurance contracts, financial instruments, and a few other narrow categories. The five steps are: identify the contract, identify the performance obligations, determine the transaction price, allocate the transaction price, and recognize revenue when or as obligations are satisfied.
Most companies handle steps one through three without major issues. Step four is where the spreadsheet work begins, and step five is where disagreements between auditors and management tend to surface.
Key Recent Developments
One of the more consequential updates involves guidance around license arrangements. The IFRSIC clarified that whether a license grants a right to use or a right to access matters significantly for timing of revenue recognition. If it is a right to use, revenue is recognized at a point in time. If it is a right to access, revenue is recognized over time. This distinction has forced many software and media companies in Pakistan to revisit how they structure and report licensing deals. Another area of activity centers on principal versus agent considerations. The standard has always required judgment here, but recent enforcement observations have made it clear that simply calling yourself an agent in a contract clause is not enough. You need to demonstrate that you do not control the good or service before it transfers to the customer. I have seen multiple engagements where management had to reclassify revenue from gross to net based on actual facts, not just contractual language. The concept of contract costs has also received more scrutiny. Capitalizing incremental costs of obtaining a contract requires that you expect to recover those costs. If the contract is unlikely to be profitable or is likely to be terminated early, the capitalization should not happen. Companies with high churn rates in subscription businesses sometimes struggle with this.
Get the Full Details
A Practical Problem I Encountered
Last year, I worked with a construction company that had entered into a contract to build a facility. The contract included a penalty clause for delays and a bonus clause for early completion. Under PSAK 201, variable consideration needs to be estimated. The straightforward approach would be to use the most likely amount. But in this case, the penalty and bonus created a range of outcomes that made the most likely amount method problematic. The contract also had a significant milestone structure. Revenue was supposed to be recognized over time using an input method based on costs incurred. However, the actual progress on site did not always match the cost input. Materials were delivered early but not yet installed. Labor hours were logged but some work had to be redone due to specification changes. The workaround was to use a hybrid approach. We kept the cost-to-cost method for the core construction work but adjusted the input measure by overlaying physical completion data from site engineers. This gave a more accurate picture of progress than either method alone. The auditors accepted this because it was grounded in observable data rather than management estimates. I would recommend documenting the rationale for any deviation from the pure cost-to-cost method, because that is what auditors will ask for.
Common Pitfalls
One of the most frequent mistakes I see is treating every contract modification as a separate contract. The standard requires you to assess whether a modification adds distinct goods or services at their standalone selling price. If it does, it is accounted for separately. If not, you adjust the existing contract. Companies often skip this assessment and just book the modification as a new contract, which can materially overstate revenue in a period. Another pitfall involves performance obligations that are not distinct. Bundling multiple deliverables into one performance obligation when they should be separated inflates the transaction price allocation complexity and can lead to misstatement. I have seen this particularly with IT service contracts that include software licenses, implementation, and support. Each of these may need to be a separate obligation depending on whether the customer can benefit from them on their own or with readily available resources.
What the Standard Does Not Handle Well
PSAK 201 is not a perfect fit for every business model. Subscription services with free trials are particularly awkward. The standard does not give explicit guidance on how to handle zero-price periods upfront. Some companies recognize no revenue during the trial and then start recognizing when the paid period begins. Others allocate the transaction price across the entire commitment period including the trial. Both approaches can be defensible, but they produce different results, and auditors do not always agree on which is correct. Build-operate-transfer arrangements also fall into a gray area. While the standard mentions them, the practical application requires significant judgment about when control transfers. In Pakistan, infrastructure projects with BOT structures are common, and the revenue recognition timeline can span decades. The standard provides a framework, but the specifics are often worked out on a case-by-case basis.
Implementation Checklist
If you are reviewing your company's compliance with PSAK 201, start by mapping every revenue stream to the five-step model. Do not rely on old policies. The way revenue was recognized before PSAK 201 may not be valid anymore. Document the standalone selling price for each good and service. This is often the weakest area in company records because the standard requires reasonable estimation methods like adjusted market assessment, expected cost plus margin, or residual approach. Review your contract modification process. Set up a formal procedure for evaluating whether each change to a contract is a separate contract or an adjustment to an existing one. Train your sales team to document key terms that affect revenue recognition. Disputes often arise because the commercial terms were not clearly captured in writing. For companies in regulated industries, check whether the standard's exceptions apply. Telecommunications, banking, and insurance sectors have specific interactions with PSAK 201 that require careful review.
Where to Find the Standard
PSAK 201 is published by the Institute of Chartered Accountants of Pakistan. It is available through the ICPAK website or through the professional library subscriptions that most firms already maintain. The interpretive guidance from the IFRS Interpretations Committee is also relevant and can be accessed through the IFRS Foundation website. Staying current on these updates matters because the standard is not static.
