Workday captures and stores transaction data but doesn't perform reconciliation on its own. Matching transactions against bank statements, investigating discrepancies, and documenting decisions typically happens outside the ERP, usually in spreadsheets. Nominal closes that gap by executing reconciliation work directly on top of that data.
For most accounting teams, Workday account reconciliation still ends the same way it always has: in a spreadsheet. Month-end arrives, someone pulls a transaction export, and the matching begins by hand, line by line, against the general ledger.
None of this feels unusual if you run close on the ERP. It's the explanation every new hire gets: the software holds the data, and the spreadsheet is where the real work happens. The gap is so familiar it barely reads as a problem anymore.
But it is an issue , and it isn't a sign of bad data or a weak team. It comes down to architecture: the platform was never built to execute reconciliation on its own. Seeing exactly where that gap lives is the first step toward closing it.
What Is Workday Account Reconciliation?
Workday account reconciliation is the process of matching transactions recorded ERP against external records, such as bank statements, to confirm the general ledger is accurate. The platform captures and stores the transaction data, but the matching, investigation, and documentation involved in reconciliation typically happen outside it.
That distinction, between recording data and acting on it, is where most of the manual work in accounting operations comes from.
What Workday Handles Well
It's a recording system, meaning that it captures every transaction, enforces accounting rules, and keeps the general ledger accurate at scale. For thousands of organizations, it's the operational backbone of finance.
The platform knows what happened, when it happened, and how the numbers roll up. For a controller managing a complex entity structure, that reliability is worth a lot.
Where things get harder is the moment someone needs to act on those records, not just store them.
Where the Reconciliation Work Actually Happens
Its reconciliation coverage stops well short of what accounting teams actually need. It captures the inputs and stores the outputs, but matching, investigating, documenting, and resolving exceptions still fall to the team. Four handoffs create most of the friction.
1. Manual Transaction Matching
Bank transactions rarely map cleanly to general ledger entries. A single payment might correspond to several invoice lines. Several deposits might summarize into one GL entry. Fees, FX adjustments, and timing differences often post separately from the transactions they relate to.
The underlying data is accurate and complete. But matching a bank line that reads "AMZN MKTP US" to a GL entry recorded as "Amazon Marketplace, Invoice #4471" takes contextual judgment that static rules can't provide. Multiply that across thousands of transactions and multiple entities, and the scale becomes clear: this is hours of mechanical work, usually done by senior accountants during the most pressured week of the month.
Related post: Bank Reconciliation: From Month-End Bottleneck to Continuous Automation
2. Timing Variance Investigation
Cash clears the bank on one date and gets recorded on another, sometimes reclassified later. These timing differences are normal, but proving that a variance is timing rather than an actual error still takes investigation: pulling transaction details, comparing posting dates, and tracing activity across systems.
Under deadline pressure, it's tempting to flag items as timing differences and move on. Small discrepancies add up. Bank fees that should be posted immediately sit in workpapers instead, and duplicate payments go unnoticed until audit. Because nothing in the workflow surfaces these things on its own, that investigation work lands on a person, under pressure, without enough time to do it properly.
Accounting teams describe a similar pattern across industries: days lost each close cycle chasing accruals and comparing entries across systems just to confirm whether a variance is timing or a real error. The information exists somewhere. Finding and connecting it doesn't happen by itself.
Explore more on this topic: Smarter Variance Analysis: Automate Insights, Skip the Spreadsheets
3. Scattered Documentation
When reconciliation happens outside the system of record, audit support fragments by default. Screenshots end up in Slack, PDFs sit in shared drives, notes live in email threads, and commentary gets buried in spreadsheet cells.
When an auditor asks why a specific item was cleared, someone has to reconstruct a trail that was never centralized in the first place. The workflow breaks down here, not the platform. Documentation fragments because reconciliation happens somewhere else.
4. Linear Scaling as Entities Grow
Every new bank account, entity, or payment processor adds manual work. Reconciliation hours scale in direct proportion to volume, so every stage of growth triggers a proportional increase in accounting labor. For companies expanding through acquisition or geographic reach, that's the constraint that turns accounting into a bottleneck.
Some organizations end up with six or seven figures in unresolved discrepancies, not because the numbers are missing from Workday, but because nobody executes the work of tracking, matching, and resolving them. The data is there. No system is executing on it.
Why the Gap Exists
No ERP was designed to execute reconciliation work on its own. Workday was built to solve a data organization problem, giving companies a single system of record where all financial activity lives under consistent rules. That problem got solved, and solved well.
Reconciliation execution is a different problem. It calls for matching logic that handles one-to-many relationships, investigation that traces timing differences across systems, documentation that captures decisions as they happen, and scaling that doesn't grow linearly with transaction volume. Those capabilities sit outside the ERP. They're accounting operations built on top of its data.
Its responsibility ends at exactly the point reconciliation begins. That's by design, not a shortfall. The accounting team takes over from there, and for most teams, what happens next is Excel.
What the Gap Looks Like Across Accounting Teams
Some accounting teams manage a P&L complex enough that native formatting can't support it, and end up rebuilding financial statements in Excel just to get something reviewable. The underlying data is accurate, and the system of record is sound, but shaping, reconciling, and presenting that data falls outside what the platform can execute. So the work moves into spreadsheets that carry version control risk, rework, and close delays.
This is the pattern accounting teams recognize immediately, regardless of company size: a sophisticated ERP, clean data, and a reconciliation process still run by hand. The tools improve. The handoff doesn't change.
Nominal: The Execution Layer for Workday Reconciliation
Nominal sits alongside Workday as the execution layer, handling the reconciliation work the ERP records but doesn't perform.
The ERP stays the system of record, the authoritative source for the general ledger, financial statements, and reporting. Agents connect to that data and execute the operational accounting work that has always lived in spreadsheets, with no migration, no disruption to existing workflows, and no change to how it operates.
Continuous Matching, Not Period-End Sprints
Instead of compressing all reconciliation work into the final days of closure, Nominal's agents work continuously. Transactions match as they move through bank accounts, and exceptions surface in real time instead of piling up for month-end investigation.
The platform executes over 90% of matches without manual input by recognizing transaction patterns: one-to-many and many-to-one relationships, vendor name variations, and expected timing differences.
High-confidence matches resolve on their own. Uncertain items route to the right reviewer with full context and a clear explanation of why the system flagged them.
Transparent Reasoning for Every Decision
Every match Nominal executes comes with an explanation: amount, date proximity, vendor pattern, historical precedent. Controllers can see exactly why two transactions were paired, which keeps trust high and keeps human review focused on genuine exceptions instead of re-checking work the system already got right.
Intelligent Adjustment Suggestions
When transactions don't match on their own, agents suggest journal entries based on context and historical patterns. Common scenarios, like unrecorded bank fees, interest payments, and timing adjustments, get recognized and addressed with proposed entries that include account codes learned from past activity. Once approved, adjustments post directly back to Workday, closing the loop without manual data entry.
Documentation That Lives Where the Decision Was Made
Reconciliation decisions, match logic, and exception resolutions get captured the moment they happen, attached to the relevant item, and ready for audit. When an auditor asks why a specific item was cleared, the answer is already there. Nothing needs to be reconstructed.
What Changes When the Handoff Executes Itself
The shift is specific and measurable, not just a change in tone.
By the time close arrives, reconciliation work is largely finished. Transactions have matched continuously throughout the month, and exceptions have already been resolved in context instead of under deadline pressure. Close becomes a review and approval step, not a scramble to do operational work that should have happened weeks earlier.
Senior accountants spend their time on genuine exceptions: the items that actually call for judgment, investigation, and a decision. Mechanical matching that a well-designed system can execute and complete without anyone touching it stops eating their week.
For the CFO, the shift is strategic. Reconciliation capacity stops scaling in lockstep with transaction volume, so adding entities, bank accounts, or payment processors no longer means a proportional hiring plan. Accounting supports growth instead of limiting it.
For the organization, audit readiness becomes the default state instead of a close-cycle scramble, since every decision carries its documentation from the moment it happens.
Workday Account Reconciliation, Executed End to End
Workday and Nominal work as a complete system: one records what happened, the other executes what comes next. The handoff that has always required a spreadsheet, a senior accountant, and a deadline can finally run on its own.
Ready to see it in your environment? Book a demo to see how Nominal executes Workday account reconciliation: continuously, accurately, and with a full audit trail.
About the writer
