Financial Audit Agent and Revenue Contract Agent are separate Workday-built finance agents. Audit packages sample evidence for procure-to-pay. Revenue Contract Agent turns an uploaded customer-contract PDF into a draft customer contract and lets you ask about that document. Neither agent is a general finance close copilot, and neither one reads HCM data.
Both require Agent System of Record, UMSA for Workday-built agents in non-Production and Production, and the Flex Credits and Platform Entitlement Policy before you can register and use them in Production. You can register only agents included in products your organization can access. Runtime checks both Available To on the skill and the user’s access to the APIs the tools call. Use View Security for Agent Skill to line those up.
What each agent is for
| Financial Audit Agent | Revenue Contract Agent | |
|---|---|---|
| Published job | Financial Audit AgentHigh-volume audit sample requests in procure-to-pay | Revenue Contract AgentCreate customer contracts from uploaded documents and provide contract insights |
| Skill Workday names | Financial Audit AgentGenerate Compilation Package | Revenue Contract AgentRevenue Contract Creation |
| Product gate | Financial Audit AgentAudit domains and expense, invoice, and payment domains below | Revenue Contract AgentWorkday Contract Intelligence, plus Set Up: Revenue Contract Agent in Customer Contracts |
| User entry | Financial Audit AgentCreate Audit Request | Revenue Contract AgentCreate Customer Contract with Create from Document, or Update with Revenue Contract Agent on a draft |
| Output | Financial Audit AgentA compiled PDF package of supporting documents | Revenue Contract AgentA draft customer contract routed on Customer Contract Event |
| Non-Production data | Financial Audit AgentLast 45 days only. Older data returns no results. | Revenue Contract AgentNot given a 45-day rule on the pages fetched here |
Financial Audit Agent
The skill retrieves expense reports, supplier invoices, and payments, plus supporting documents, and compiles them for an audit request. Scope is accounts payable and procure-to-pay, including supplier invoices and related documents. The agent has no HCM access.
Security for users:
- View and modify on Audit: Audit Requests in Common Financial Management.
- Expense reports: Manage: Expense Report.
- Supplier invoices, at least one of: Process: Supplier Invoice - Reporting, Reports: Financial Compliance, or Reports: Supplier Accounts.
- Supplier payments, one of: Process: Settlement or Reports: Supplier Payment.
The agent runs on behalf of the initiator. It retrieves objects the initiator can access. It retrieves requested supporting documents without evaluating the initiator’s security, but the initiator’s security still controls whether those documents are visible in the results. Access to the financial dataset is read-only. Users can see all audit requests from all users; which results display still follows security. Setup also calls out the Agent Management Hub domain in Agent System of Record and Reports: AI Agent Security in System.
Non-Production returns only the most recent 45 days. If that window is empty, refresh the tenant to restore those 45 days. Workday says to use Production when the sample is older than 45 days. A Sandbox rehearsal of last year’s audit selections will look like a broken agent.
Workday’s compilation example (page dated 2023-06-23) says the package includes invoice attachments only in PDF, CSV, JPEG, PNG, TXT, XLS, and XLSX. The worked path is Create Audit Request, a natural-language request that names the supplier invoice, then confirm the Document Types the agent selected. The example text names Supplier Invoice and Receipt among those types and tells you to add or remove types before Complete Review and Complete Request. The result is a PDF package you send to the auditor. View access to at least one returned document is required.
Register from Unregistered Workday Agent, enable Generate Compilation Package, set Available To, and activate. Deactivate from Agent Management Hub when the audit cycle is over; you can reactivate later.
Revenue Contract Agent
You need Workday Contract Intelligence.
- Existing Contract Intelligence customers: follow the setup topic, submit the Revenue Contract Agent intake form, and add users in the existing User Provisioning Workspace.
- New customers without a full deployment: submit the intake form. Workday says tenant setup can take up to 5 days. Set up the User Provisioning Workspace while you wait.
- New customers with full deployment services: wait until the services team finishes tenant setup, then follow the same register steps.
Then:
- Open Agent Management Hub and register Revenue Contract Agent.
- Configure Agent and enable Revenue Contract Creation.
- Set Available To.
- Run Set Up Revenue Contract Agent Configuration and enable or disable header and line fields the skill is allowed to extract.
After that, Workday shows Create from Document on Create Customer Contract, Update with Revenue Contract Agent on draft contracts, and Workday Chat on Edit Customer Contract for questions about the documents used to create the draft.
To create a contract: open Create Customer Contract, complete required contract information, choose Create from Document, and upload a customer-contract PDF. When processing finishes, review on Edit Customer Contract and Revenue Hub. Workday also sends a notification that opens the generated contract and the uploaded document side by side. The contract then follows the Customer Contract Event business process. Configure that business process and its security in Customer Contracts and Project Billing before you expect approvals to move.
Failure modes
- Testing audit samples in Sandbox from a prior fiscal year. Non-Production will not return documents older than 45 days. That is a documented limit, not a security bug.
- Expecting payroll or worker documents in the audit package. The agent does not read HCM.
- Treating a revenue-contract draft as approved. Creation fills a draft and routes Customer Contract Event. Someone still approves.
- Skipping the intake form. Registration steps assume Contract Intelligence tenant setup, which can take days for a new customer without full deployment services.
- Extracting fields you turned off. Header and line extraction follows Set Up Revenue Contract Agent Configuration. If a commercial term is disabled there, chat insight on Edit Customer Contract is not a substitute for that field being extracted.
- Sharing one security group across both agents. The domains are different. An audit requester is not automatically a contract creator.
Frequently asked questions
Can one agent do both audit evidence and contract creation?
No. They are separate rows in the Workday-Built Agents reference, with separate skills and setup topics.
Does the audit agent decide which samples the auditor wants?
The example starts from a request you type, including the invoice number and the documents you want. It compiles support. It does not document a statistical sampling engine.
Which file do we upload for a customer contract?
The create-from-document steps say a customer contract PDF. The audit package’s attachment types are a different list and apply to invoice attachments inside a compilation, not to contract upload.
Sources checked
Financial Audit Agent about, setup, and compilation example; Revenue Contract Agent setup and create-from-document; Workday-Built Agents reference. Fetched 2026-11-16.