Comprehensive and Detailed 150 to 250 words of Explanation From Workday Record-to-Report/Course Guide/topics:

Workday can generate and display provisional accounting after the supplier invoice is submitted, even while the Supplier Invoice Event remains In Progress. The user can access the transaction's related accounting to review the ledger accounts, amounts, taxes, worktags, and balancing entries that the configured account posting rules derive. This early visibility supports review and approval before the invoice completes.

Waiting for final approval or Posted status is unnecessary for viewing the generated accounting. Those later states determine completion and ledger inclusion, not the first point at which derived accounting can be examined. Option C is overly broad because accounting is not necessarily available at every point; a document that has not been submitted may not yet have generated the operational journal representation. Once submitted, the accounting can be inspected and errors or unexpected derivations can be identified while the workflow is still active. If configuration changes or transaction revisions occur, Workday may regenerate the accounting before final posting. Accordingly, the correct timing is after submission, even if the invoice remains in progress. Posted status is the evidence that the operational journal has affected the ledger, whereas View Accounting during workflow is a diagnostic and approval aid.

Official Workday reference: Workday Education - Supplier Accounts ; topics: supplier invoice submission and View Accounting.

===============

Comprehensive and Detailed 150 to 250 words of Explanation From Workday Record-to-Report/Course Guide/topics:

The allocation source defines the ledger activity that forms the pool to be allocated. Because the requirement is limited to operating-expense activity carrying Cost Center Facilities and Location Chicago, both worktag criteria must be added to the Source section as source filter conditions. Workday will then include only journal activity satisfying the ledger-account criteria and the specified worktags.

Adding the worktags to the statistical definition would change the allocation basis rather than restrict the source pool. The basis determines how the selected amount is distributed, such as by square footage, headcount, ledger activity, or fixed percentage. The Target controls where allocated amounts are recorded, and the Offset determines how the source pool is relieved. Neither target nor offset filtering can correct an overinclusive source calculation. Source worktags of different types are evaluated together, so Facilities and Chicago form the required combined restriction. After updating the definition, the accountant should test the allocation and verify that the source total reconciles to the intended operating-expense lines before running it. Therefore, adding Cost Center and Location to the Source is the technically correct solution.

Official Workday reference: Workday Education - Allocations ; topics: allocation source filters and worktag conditions.

===============

Comprehensive and Detailed 150 to 250 words of Explanation From Workday Record-to-Report/Course Guide/topics:

Journal sequence generator IDs are applied when journals post, so the posted journals are the controlling dependency when a company needs to revise the sequence rule for the current ledger year. Because journals have already posted under the original rule, the company must first unpost every journal in that ledger year. This removes the posted-journal dependency and makes the affected sequence generators eligible for the controlled maintenance needed before the revised rule can be used.

After unposting, the company can remove unused generator IDs as applicable, update the journal sequence generator rule with the new condition, create the required generators again, and repost the journals so that numbering follows the revised configuration. The Mass Delete Journal Sequence Generator IDs task alone is not sufficient because it cannot delete identifiers that remain associated with posted journals. Closing the remaining periods also does not resolve the existing posted transactions or rebuild their sequence. Option C is therefore too absolute: the sequence can be changed for the current year, but only after the posted journals that depend on the original generator setup are unposted. Accordingly, D identifies the essential first action. This procedure preserves Workday's sequencing controls while allowing the updated condition to govern the journals when they are reposted.

Official Workday reference: Workday - Configure Journal Sequence Generator Rules ; topics: sequence generator lifespan, posted journals, and changes to journal sequencing.

===============

Comprehensive and Detailed 150 to 250 words of Explanation From Workday Record-to-Report/Course Guide/topics:

Before Company B creates an operating lease contract, administrators must establish the relationship among the company's enabled lease type, accounting method, and book code. The Maintain Lease Contract Book Code Configuration task provides this mapping. Workday uses it to determine which accounting basis applies when the lease contract is created and to route generated lease accounting into the correct book code.

Membership in a company hierarchy is not a prerequisite for entering a lease. A standalone legal entity can maintain its own lease configuration and accounting books. Approval of unrelated supplier contracts does not supply the required accounting mapping. Option C reverses the sequence: users should not manually choose an arbitrary lease type, method, and book code on the first contract before the governing configuration exists. Where multiple lease-accounting options are enabled, Workday specifically requires distinct lease contract book code configurations and prevents incompatible codes from being reused across standards. Once the configuration is complete, Company B can create the supplier contract using the appropriate lease contract type, and Workday can generate initial recognition, installments, expense recognition, and multibook accounting consistently. Therefore, Maintain Lease Contract Book Code Configuration is the required setup action.

Official Workday reference: Workday Education - Lease Accounting ; topics: lease contract book code configuration and operating lease setup.

===============

Comprehensive and Detailed 150 to 250 words of Explanation From Workday Record-to-Report/Course Guide/topics:

The Intercompany Work Area provides the operational workspace for reviewing and reconciling activity between affiliated companies. It presents intercompany transactions, settlement runs, in-progress accounting, unrecorded receipts, and outstanding due-to or due-from amounts, enabling the accountant to identify which items produce the balance difference between the two companies.

Customer Activity Summary and Supplier Activity Summary provide subledger views for external or supplier/customer relationships but do not deliver the consolidated intercompany workflow and counterparty matching needed here. A Bank Statement report supports cash reconciliation and cannot explain all intercompany receivable, payable, revenue, expense, or settlement differences. From the Intercompany Work Area, users can investigate transaction status and proceed to more detailed reports such as Intercompany Payables and Receivables Reconciliation or Intercompany Out of Balance. Typical issues include unmatched settlements, receipts not recorded, different posting periods, missing affiliate worktags, or currency differences. Correcting the source activity and rerunning the work area preserves the audit trail and supports elimination during consolidation. Therefore, the Intercompany Work Area report is the appropriate starting point.

Official Workday reference: Workday - Setup Considerations: Direct Intercompany Activities ; topics: Intercompany Work Area and balance reconciliation.

===============

Comprehensive and Detailed 150 to 250 words of Explanation From Workday Record-to-Report/Course Guide/topics:

The first configuration step is to establish the intercompany relationships through Edit Company Intercompany Profile. The profile determines which companies may transact with or settle each other and controls capabilities such as initiation, settle-only relationships, payment types, bank accounts, automatic intercompany receipts, and asset transfers. Without a valid profile, Workday cannot expose the affiliate as an eligible intercompany counterparty for many transaction types.

Historical journal conversion should occur only after the foundational company relationships, posting rules, affiliate worktags, and opening periods are correctly configured. Settlement terms and payment methods are components of the broader profile and settlement design; they do not replace creation of the relationship itself. Training users before configuration is complete would teach an incomplete process and cannot enable transactions. After profiles are established, administrators configure intercompany payables and receivables account posting rules, companies as customers or suppliers for direct intercompany activity, appropriate business processes, elimination rules, and reconciliation reporting. This sequence ensures that transactions create balanced due-to and due-from accounting and remain traceable through settlement and consolidation. Therefore, editing the intercompany profiles is the correct first step.

Official Workday reference: Workday - Define Intercompany Profiles ; topics: Edit Company Intercompany Profile and relationship setup.

===============