← Back to full.link
Request a demo

Configuration checks and reconciliation for Workday

Your system foots, reconciles and is always on.

To keep your system consistent, on, and always working, OnRecon ensures worktags are always built with your current configuration in mind.

Our configuration checks look at your setup, not your money.

Nightly configuration review

Sample

20 of 20 reports checked

  • FDM structure

    Matches approved workbook

    Pass
  • Custom validations

    1 rule changed since approval

    Review
  • Worktag usage

    Consistent with workbook

    Pass
  • Required-worktag rules

    1 new cost center not covered

    Review
  • Tenant setup

    Matches approved workbook

    Pass

A validation rule was edited after the workbook was approved. It no longer covers the new cost center, so journals using it may be rejected.

Recommended fix drafted. Your team approves and applies it.

The problem

Configuration drifts quietly.

Go-live is the most consistent your setup will ever be, unless someone keeps checking it. Small changes pile up, and each one can look harmless on its own.

Worktags get added one at a time

Each request looks simple. Its effect on validations, hierarchies and reporting usually isn't.

The workbook stops matching the tenant

Quick fixes and new requirements move the live setup away from what was approved.

Problems surface at the worst time

Rejected journals and reports that don't tie out often show up during close, long after the change that caused them.

Products

Four separate products. Choose what you need.

Each product stands on its own and states exactly what kind of data it uses.

Metadata only

Finance Configuration Check

Confirms your finance setup is consistent, logical and matches your approved workbook.

  • FDM structure
  • Custom validations
  • Worktag usage
  • Tenant setup

Metadata and/or data

Security Configuration Check

Reviews how security is set up. Run it on metadata alone, or add data if your review calls for it.

  • Security groups
  • Domain security policies
  • Business process security
  • Consistency with your approved design

Metadata only

HCM Configuration Check

Confirms your HCM setup is consistent, logical and matches your approved design.

  • Organizations and hierarchies
  • Business processes
  • Custom validations
  • Tenant setup

Financial data

Basic Financial Reconciliation

Confirms the basics foot and reconcile, using your financial data.

  • Balances that foot
  • Reconciliation against your source reports
  • Differences called out clearly
  • Summaries written for controllers

Inside the Finance Configuration Check

Two jobs, done every time.

Nightly configuration review

About 20 configuration reports, checked every night.

  • Confirms your FDM is consistent and logical
  • Tests custom validations against the approved design
  • Reviews worktag usage across your setup
  • Compares tenant setup to your approved workbook
  • Explains each finding in plain language

Worktag requests and impact analysis

Know what a new worktag touches before it's built.

  • One clear path for requesting new worktags
  • Checks how each request affects your current configuration
  • Checks how your current configuration affects the request
  • Spells out what needs to change, and where

Impact analysis

Sample

New cost center: CC20583 - Field Operations

  • Company restrictionRestrict to CO20

    90% of cost centers are restricted to a single company. Based on the CC number, this one should be restricted to company CO20 - Global Services Inc.

  • IntegrationsDecision needed: INT1024

    Banking integration INT1024 is specifically for CO20 - Global Services Inc and specifies the cost centers to include. Do you need to include this cost center in the integration?

  • Validations1 rule to update

  • HierarchiesNeeds a parent assigned

  • DefaultsNo change

  • Required-worktag rulesNo change

  • Reporting2 reports to check

How it works

Rules decide. AI explains. You approve.

  1. 01

    Connect

    Start with a read-only integration user limited to configuration reports, or choose another setup below.

  2. 02

    Check

    Every night, your configuration is tested against defined rules and your approved workbook. The same setup gets the same result, every run.

  3. 03

    Explain

    Anything off comes with what changed, why it matters and what to do next. AI drafts these explanations and flags patterns that look wrong but break no rule.

  4. 04

    Approve

    OnRecon recommends and drafts. Your team approves and applies every change.

AI never decides pass or fail, and it never changes your tenant.

What you get

Confidence in the setup behind your numbers.

Catch drift sooner

Checks run every night, so issues can surface before they reach a close.

Build worktags right the first time

Every request is reviewed against your current configuration before it's built.

Keep the workbook meaningful

Your approved workbook stays the standard the live setup is measured against.

Get results you can repeat

Pass and fail come from defined rules, not judgment calls that shift from run to run.

Read findings without translation

Summaries are written for controllers, not only for system administrators.

Know what's in scope

Every product states what data it uses, so your security team knows before anything starts.

Stay in control

Nothing changes in your tenant unless your team decides to change it.

Work with a CPA

OnRecon comes from a firm led by a CPA who understands what your setup has to support.

Deployment

Set up to fit your risk profile.

Choose how OnRecon connects based on what your security team is comfortable with.

Recommended start

Configuration only

A read-only integration user, limited to configuration reports.

How it works
You set up the integration user, and OnRecon pulls the configuration reports it needs each night.
What we see
Configuration reports only.
Best for
Teams that want the simplest setup and a fast start.

You control delivery

Your extracts

You schedule report delivery to an SFTP site you own, and OnRecon gets read access.

How it works
Your team schedules the reports, and OnRecon reads them from your SFTP site.
What we see
Only the reports you choose to deliver.
Best for
Teams that want to control what's delivered and when, without an outside integration user.

Most separation

Your environment

The review runs on your infrastructure. Only the findings report comes to full.link.

How it works
The review is installed and run on your side, using access you manage.
What we see
The findings report only. full.link doesn't hold your tenant credentials.
Best for
Teams with the strictest security requirements.

Questions

Common questions.

Does OnRecon look at our financial data?
Only if you choose a product that needs it. The Finance and HCM Configuration Checks use metadata only. The Security Configuration Check can use metadata, data or both. Basic Financial Reconciliation uses financial data.
Can OnRecon change anything in our tenant?
No. It recommends and drafts changes, and your team approves and applies them.
Where does AI fit in?
AI explains findings, flags patterns that look wrong but break no rule, and writes summaries. Pass or fail always comes from defined rules, so results stay consistent from run to run.
What do we need to get started?
Your approved configuration workbook and a conversation with your security team about which setup fits. A free FDM health check is the easiest first step.

See OnRecon on your setup.

Request a demo, or start with a free FDM health check to see what OnRecon would flag in your configuration. There's no commitment to continue.