Finance on Workday

Month-end close checklist on Workday

Runs the close as a shared checklist per entity and day, with each task's status read from the ledger and every sign-off recorded.

SCREENSDATA HANDLERSWORKDAY · READ IN PLACES01 My tasksS02 Task detailS03 Entity sign-offS04 Cost center reviewS05 Close boardS06 Calendar setupdh_journal_lineJournal lineFinancial_Management: Get_Journalsdh_supplier_invoiceSupplier invoiceResource_Management:Get_Supplier_Invoicesdh_capital_requestCapital requestFinancial_Management: Get_Projects(capital) · Get_Assetsdh_cost_centerCost centerFinancial_Management: Get_Cost_Centers ·Get_OrganizationsWRITE BACK TO WORKDAYJournal line → Submit_Accounting_Journalrows stay in Workday · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Workday object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
4
objects read in place from Workday
catalogue
6
screens on those rows
catalogue
7 days
to production-grade
estimate
1
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Workday objects behind each handler

Workers, organisations, positions, time off and expense reports are read in place through Workday's SOAP and REST web services and through Reports-as-a-Service for lists. The rows stay in Workday.

ObjectRead fromFields the app usesFreshness
Journal lineFinancial_Management: Get_JournalsJournal.Journal_Number (document) · Journal_Line.Ledger_Account (account) · Journal_Line.Ledger_Debit_Amount − Credit (amount) · Journal_Line.Cost_Center (cost center)live through the API
Supplier invoiceResource_Management: Get_Supplier_InvoicesSupplier_Invoice.Invoice_Number (number) · Supplier_Invoice.Supplier (vendor) · Supplier_Invoice.Total_Amount (amount) · Supplier_Invoice.Purchase_Order (po)live through the API
Capital requestFinancial_Management: Get_Projects (capital) · Get_AssetsProject.ID (request) · Project.Name (desc) · Project.Budget (amount) · Project.Fiscal_Year (year)live through the API
Cost centerFinancial_Management: Get_Cost_Centers · Get_OrganizationsCost_Center.ID (id) · Cost_Center.Name (name) · Organization.Manager (owner) · Company.ID (company)live through the API
The trigger

The start criterion in Workday's own fields

In plain words: The close calendar starts on the last working day of each month for every entity, or when the accounting manager opens it early.

This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.

Start

The close calendar starts on the last working day of each month for every entity, or when the accounting manager opens it early. The instance then reads its rows from Workday through the handlers above.

What the app writes back

Through released interfaces

Writes go through the released web-service operations (for example Submit_Expense_Report, Request_Time_Off, Hire_Employee) under an integration system user with the security groups the operation needs. Each call returns the Workday ID, and the app records it beside the decision.

ObjectWhat changesInterface
Journal lineaccrual, reclassification and correction journals posted from a task through the released journal interface; the document number stored on the taskSubmit_Accounting_Journal
Acknowledged and logged

Each write stores the identifier Workday returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

Security groups are mapped to Lima access policies once. A manager sees their own team in the app, exactly as in Workday.

  • An integration system user with domain security for the objects the app reads and writes
  • A Reports-as-a-Service report for each list the app needs at scale
  • Tenant URL and allowed IP set up
  • Business-process definitions in Workday agreed so approvals raised from the app land in the right step
Register the handlers4 objects from the catalog; each shows its rows at once.
Nearby

This app on other systems, and other apps on Workday

Month-end close checklist on

Other apps on Workday

Terms on this page

Working dayA counted day of the close calendar, starting at 1 on the first working day after period end.
Ledger checkA criterion on live ledger data that decides whether a task is complete, for example 0 supplier invoices left to post.
Read in placeThe rows stay in Workday; the handler sends the filter and the columns and Workday returns the matching rows.
Questions

Does this app copy data out of Workday?

The screens read through handlers that leave the rows in Workday. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does Workday need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on another system as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, and the app's other system pages show them.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.