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.
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.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Journal line | Financial_Management: Get_Journals | Journal.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 invoice | Resource_Management: Get_Supplier_Invoices | Supplier_Invoice.Invoice_Number (number) · Supplier_Invoice.Supplier (vendor) · Supplier_Invoice.Total_Amount (amount) · Supplier_Invoice.Purchase_Order (po) | live through the API |
| Capital request | Financial_Management: Get_Projects (capital) · Get_Assets | Project.ID (request) · Project.Name (desc) · Project.Budget (amount) · Project.Fiscal_Year (year) | live through the API |
| Cost center | Financial_Management: Get_Cost_Centers · Get_Organizations | Cost_Center.ID (id) · Cost_Center.Name (name) · Organization.Manager (owner) · Company.ID (company) | live through the API |
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.
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.
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.
| Object | What changes | Interface |
|---|---|---|
| Journal line | accrual, reclassification and correction journals posted from a task through the released journal interface; the document number stored on the task | Submit_Accounting_Journal |
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.
Security groups are mapped to Lima access policies once. A manager sees their own team in the app, exactly as in 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.
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.
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.
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.