Your Workday Billing Implementation: Why It Might Not Be Done

Your Workday Billing implementation went live. The implementation team rolled off, the steering committee saw its closing slide, and invoices are going out. Then you notice that someone in Finance still builds a spreadsheet every month to fix what the system doesn't do.

That spreadsheet is the sign. Manually created invoices are a major red flag. A Workday Billing implementation is only finished when the scope you cut, the requirements you misread, and the pricing you have since changed are all accounted for. Most teams never schedule that work. This post is about finding it.

What went overboard to hit the date

Every implementation trades scope for schedule and resources, and the trade is usually reasonable at first. However, when several scope cuts are made, the end result rarely resembles what was demoed during the sales cycle. Worse yet: the dropped items are rarely recorded as debts with owners. They become "phase two," and phase two has no budget. The usual casualties:

• Mid-term contract changes. Go-live covered the clean contract and regular event that were on people's minds. Infrequent Upgrades, co-terms, and credits are handled by hand.
• Billing exceptions. Rules for holds, disputes, and rebills were deferred, so someone still reviews every invoice run offline.
• Conversion history. Legacy invoices were cut back to the last year, so nobody can compare a renewal price to the prior term.
• Reporting. Last on the list, and the first thing dropped when UAT ran late.
• Revenue recognition edge cases. Schedules were signed off for the standard deal only.

Write each item down with a monthly cost: hours of manual work and who does them. That number is your case for finishing.

A common version of this: the team defers invoice exception handling to hit go-live, and six months later a senior accountant spends two days each cycle checking a run that a rule could have screened. Nobody decided that was acceptable. It accumulated.

What only production can teach you

Test data is tidy. Production is not. The first real billing cycle surfaces customers who need invoices grouped differently, contracts with three billing contacts, credit memos that arrive after period close, and a run that takes overnight instead of minutes.

Some of what surfaces is a misunderstood requirement. Nobody lied. "We bill monthly" turned out to mean monthly in arrears for usage and annually in advance for the platform fee. The person who describes a process in a workshop and the person who runs it every month often give you two different processes. The AR clerk has the second one.

Two or three months of live billing produce the most accurate requirements list you will ever get. Schedule it as a planned release, not as a queue of defects.

When the pricing model changed and the configuration didn't

Commercial models move faster than configuration. A flat subscription becomes usage plus a minimum commit. Fixed-fee projects shift to time and materials with a cap. A new bundle needs one price split across several lines.

Take the usage example. The contract needs a monthly minimum plus overage, but the configuration only knows a fixed installment. So someone bills the minimum through the schedule and keys the overage as a separate invoice, and the two never appear together on the customer's statement.

Each change is a sound business decision. Each lands on a billing setup built for the previous model. You see it as manual credit and rebill invoices, contract lines with workaround descriptions, and revenue handled offline for "special" deals.

Here is the test. If Sales can sign a deal type that your billing configuration cannot express, the implementation is behind the business. Build for change: billing schedule templates and a clean contract line structure, so a new model means a new template instead of a workaround.

Reporting that answers the profitability question

Go-live reports tell you invoices went out. Leadership asks something else: which customers and contracts are profitable, how billed compares to recognized, where write-offs concentrate, and how long it takes to go from work performed to invoice.

Those answers depend on decisions made at setup. Service line, product, and project need to be captured consistently on the contract line, and billing needs to connect to project cost. If those attributes were skipped at go-live, retrofitting them across live contracts is slow and painful.

Start with a short list of measures you define once and report monthly:

• Time to invoice. Days from work completed or milestone met to invoice issued.
• Billing accuracy. Credits and rebills per hundred invoices.
• Unbilled aging. Work performed that has not been invoiced, by age.
• Margin by service line and customer. Billed revenue against delivery cost.

Four measures, reported consistently, will tell you more than a dashboard with forty.

A 90-minute review you can run this quarter

Get Finance, your Workday admin, and one AR analyst in a room. Bring four lists: the items deferred at go-live, the ten manual workarounds people do every month, the deal types the configuration cannot express, and the questions leadership asks that Workday cannot answer today. Rank everything by monthly cost.

The top of that ranking is your real phase two, with a budget attached and an owner named.

Working through what your implementation left behind? Let's talk.