Revenue Recognition in Workday Billing: A Plain-English Guide

Revenue Recognition is the most feared topic in all of accounting. The complexities and criticality of this function intimidate many professionals.

Workday has built a system that separates billing and revenue recognition by design, which helps clarify the distinction between what a customer owes and what the company has earned. Understanding this separation is crucial for accurate financial reporting and compliance with accounting standards and is the subject of this post.

Here is an example: You sell a perpetual license for $100,000 and twelve months of maintenance for $18,000. You invoice the full $118,000 on day one. At month end, finance reports $101,500 of revenue for the deal. Billing answers what the customer owes and when. Revenue answers what you have earned and when. Revenue recognition in Workday Financial Management keeps those two questions on separate tracks by design, and once you see why, most of the configuration stops looking arbitrary.

The classic case: a Subscription deal

Let's start simple: When a Software-as-a-Service company sells a 12 month subscription, the billing usually occurs upfront while the revenue recognition occurs over the service period. This mean the timeline when a company receives cash and when it reports revenue on their financial statements are different. The simple reason for it is that the company has not yet delivered the service and may potentially have to reimburse the customer. While this principle looks simple enough, things can quickly get more complicated if the deals contain multiple lines or stretch different offerings.

Take the example from the intro section: Two different things were sold. The license is delivered once and the customer keeps it, so revenue recognizes in a single installment on delivery. The maintenance subscription covers a year of service you have not performed yet, so the $18,000 goes to deferred revenue and releases across twelve installments on the daily method. First month: $100,000 of license plus $1,500 of maintenance.

Now change one commercial term. The customer negotiates quarterly maintenance billing instead of annual. The billing schedule becomes four installments at 25 percent each. The revenue schedule does not move. It is still twelve installments over the same twelve months, because the service you are delivering has not changed.

One contract line. Two schedules. Two different cadences, driven by two different questions.

ASC 606 and Multiple Element Arrangements, without the vocabulary

The reason to track billing and revenue separately is twofold: It gives a clearer picture of what the organization has "earned" for management reporting and it is a regulatory requirement for financial reporting. This is to prevent bloated income statements. The accounting standard governing revenue reporting for US companies is called ASC 606.

It has five steps, and only one of them is hard.

• Step 1: Identify the contract.
• Step 2: Identify what you promised, treating each distinct promise as its own performance obligation (license and maintenance are two promises, not one).
• Step 3: Determine the transaction price.
• Step 4: Allocate that price across the promises based on what each would sell for on its own, its standalone selling price.
• Step 5: Recognize each piece as you deliver it.

Step four creates the additional complexity beyond the timing difference of billing and recognition. Practitioners still call this a multiple element arrangement, or MEA, and still say carve-out, both inherited from the older standard and its VSOE tests. The mechanic survived the rewrite: the price printed on the order form is not necessarily the price you recognize.

Say two products are sold at $8,000 and $2,000 on a contract. If a customer had bought them alone, the pricing would have been $6,000 and $6,000 (according to a price list). The customer is invoiced $10,000. Revenue splits evenly. That $3,000 difference is the carve-out, and it exists because you discounted one product harder than the other to close the deal.

The Workday architecture: Two schedules on one contract line

To be able to reflect this relationship, every customer contract line in Workday carries a billing schedule and a revenue schedule, and they are independent objects. Different installment counts, different dates, different amounts.

In addition to the different schedules, each contract line has a Revenue Override Amount field that is separate from the Contract Line Amount. The contract line amount is what drives the billing, and the revenue amount is what feeds into the revenue schedule. Naturally, both need to add up to the same amount across the contract, but they are not required to be the same on each line. The system does not enforce that, so it is up to the contract administrator to make sure they tie out.

To reflect the Multiple Element Arrangements, the Revenue Override Amount can be used to represent the carve-out manually or you can let the system perform the allocation.

Where this breaks

In practice, several common mistakes can show up in the configuration and operation of revenue recognition in Workday Billing:

• Allocation done after the contract is executed. Fair value analysis belongs before data entry. Retrofitting it means amendments, adjustment entries, and an explanation for the auditor.
• Billing-only and revenue-only lines that do not foot. Total line revenue amount should equal total contract line amount. Nothing in the system stops you from entering $8,000 and $3,500 and closing the period on it.
• Revenue schedule method picked by habit. Even monthly installments and the daily method give different answers in a partial first month, and they diverge again in a leap year.
• Milestone-driven billing with no named milestone owner. Revenue sits waiting on an event nobody is watching, and it ages quietly in deferred.
• Sales items with no standalone selling price on file. Allocation has no input, so it gets calculated in a spreadsheet outside Workday and pasted back in.

Who owns it, and the reports they live in

Four roles touch this and they rarely sit together. The contract administrator creates the contract, the lines, and both schedules, and processes amendments. The revenue accountant owns fair value analysis, allocation, and the deferred balance. The billing specialist runs invoicing and confirms milestone events. The controller signs the number.

A few reports are critical for the revenue manager to monitor the operational health:

• The Deferred Revenue Waterfall per customer & contract shows the progress of the recognition at a detailed level as well as a timeline for future postings. It is the first place to look when a customer calls about a revenue dispute.
• Fair value determination report helps the revenue manager substantiate the Average Selling price or standalone price by sales item. This drives the automatic calculation of a Multi Element Arrangement.
• Contract Audit reports that identify common mistakes and misalignments between billing and revenue schedules. These reports are essential for ensuring that the revenue recognition process is accurate and compliant with accounting standards.

Understanding the architecture of Workday Financials to support Revenue Recognition is the first step to an effective and compliant approach. Stop treating the revenue schedule as a copy of the billing schedule with different dates. Consider the performance obligations and the contract structure, and the deferred balance will explain itself.