Exam Bundle

Billing generation produces the correct monthly documents with intended dates and rates. That would verify a different case: A customer buys a 12-month support subscription, but the sales team manually invoices all twelve months and misses renewal price rules. It does not verify the required corrective action: Configure contract billing milestone definitions and schedule group appropriate to approved project milestones.

The initial invoice records deferred revenue and monthly recognition reduces the liability over the term. That would verify a different case: A prepaid annual license is invoiced today, but accounting books all recognized revenue immediately. It does not verify the required corrective action: Configure contract billing milestone definitions and schedule group appropriate to approved project milestones.

Eligible item lines create recognition schedules while unrelated charges post immediately. That would verify a different case: A finance admin marks every expense of one vendor as deferred, even though only certain item classes require deferral. It does not verify the required corrective action: Configure contract billing milestone definitions and schedule group appropriate to approved project milestones.

Expense deferral allocates incurred prepaid costs over their benefit period. That explains a separate case: An annual maintenance expense is prepaid, but the expense hits one month instead of spreading over coverage. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Billing schedule hold status can suspend future invoice generation without deleting historical charges. That explains a separate case: A service contract is paused for maintenance, but the monthly billing schedule continues issuing invoices. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Multiple active schedules for the same service period can double bill a customer. That explains a separate case: A customer upgrades from a monthly to an annual plan, but its old schedule continues billing and overlaps the new contract. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile active contracts to billing schedules and generated invoices. That safeguard is aimed at a different risk: A customer buys a 12-month support subscription, but the sales team manually invoices all twelve months and misses renewal price rules. It does not most directly prevent recurrence of: Milestone contract billing differs from ordinary time-based subscription billing.

Require idempotent period-completion checks in recognition batch operations. That safeguard is aimed at a different risk: A subscription deferral journal posts twice because the month-end recognition batch is rerun without checking prior completion. It does not most directly prevent recurrence of: Milestone contract billing differs from ordinary time-based subscription billing.

Review contract line types and performance obligation treatment. That safeguard is aimed at a different risk: The finance team adds a one-time setup charge to a subscription but the charge is recognized evenly over 12 months against policy. It does not most directly prevent recurrence of: Milestone contract billing differs from ordinary time-based subscription billing.

Apply controlled vendor bank account verification and approval before selecting the new beneficiary. This fits a DIFFERENT issue within Implement and manage accounts payable: A new vendor bank account is accepted from an unverified email and inserted directly into the next payment run. It does not address the current problem, whose mechanism is: Vendor invoice conversion depends on company ledger currency and applicable transaction rate.

Use the supported intercompany invoice linkage and verify legal-entity transaction references. This fits a DIFFERENT issue within Implement and manage accounts payable: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. It does not address the current problem, whose mechanism is: Vendor invoice conversion depends on company ledger currency and applicable transaction rate.

Apply the correct approved accounts payable charges code with the required posting/tax treatment. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor charges an agreed freight fee, but the AP invoice amount differs from the purchase order because the charge code is missing. It does not address the current problem, whose mechanism is: Vendor invoice conversion depends on company ledger currency and applicable transaction rate.

A test payment settles subsidiary vendor invoices and creates reconciling intercompany entries. That would verify a different case: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not verify the required corrective action: Validate the AP transaction currency, exchange-rate type and effective rate before posting.

Unapproved bank details cannot generate a payment file until validated. That would verify a different case: A new vendor bank account is accepted from an unverified email and inserted directly into the next payment run. It does not verify the required corrective action: Validate the AP transaction currency, exchange-rate type and effective rate before posting.

The mismatched invoice is held or flagged, while a valid quantity/price invoice passes. That would verify a different case: A purchased item invoice is received for 130 units while the purchase order receipt shows only 100, but the invoice posts without a warning. It does not verify the required corrective action: Validate the AP transaction currency, exchange-rate type and effective rate before posting.

Payment proposals use configured invoice eligibility and due-date selection criteria. That explains a separate case: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Vendor posting profiles map operational vendor liabilities to general ledger accounts. That explains a separate case: A new vendor invoice is booked to the wrong accounts payable control account because the vendor group has an incorrect posting profile. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Invoice validation policies may vary by document and procurement scenario. That explains a separate case: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Include discount opportunities and liquidity constraints in payment-run review. That safeguard is aimed at a different risk: A supplier offers a cash discount if paid within ten days, but AP payment proposal ignores discount dates and pays full amount on day eight. It does not most directly prevent recurrence of: Vendor invoice conversion depends on company ledger currency and applicable transaction rate.

Check legal-entity field scope before bulk vendor updates. That safeguard is aimed at a different risk: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. It does not most directly prevent recurrence of: Vendor invoice conversion depends on company ledger currency and applicable transaction rate.

Require source invoice and reason codes on vendor credit notes. That safeguard is aimed at a different risk: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. It does not most directly prevent recurrence of: Vendor invoice conversion depends on company ledger currency and applicable transaction rate.

Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately. This fits a DIFFERENT issue within Configure expense management: Expense reports stay in Submitted status because workflow approval roles were changed and no approver is assigned. It does not address the current problem, whose mechanism is: Corporate card and personal out-of-pocket expenses have different settlement counterparties.

Configure expense management per diem rules with applicable trip duration and meal reductions. This fits a DIFFERENT issue within Configure expense management: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. It does not address the current problem, whose mechanism is: Corporate card and personal out-of-pocket expenses have different settlement counterparties.

Check expense transaction currency, reimbursement currency, company setup and rate for the transaction date. This fits a DIFFERENT issue within Configure expense management: An employee attaches a receipt but submits a currency conversion with an incorrect reimbursement currency and exchange rate. It does not address the current problem, whose mechanism is: Corporate card and personal out-of-pocket expenses have different settlement counterparties.

An over-limit test expense is flagged or blocked while an allowed amount proceeds. That would verify a different case: A receipt reimbursement exceeds the department's maximum hospitality allowance, but the expense report has no policy warning. It does not verify the required corrective action: Configure payment method and personal-versus-corporate transaction handling on expense reports.

An eligible half-day trip calculates only the permitted per diem amount. That would verify a different case: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. It does not verify the required corrective action: Configure payment method and personal-versus-corporate transaction handling on expense reports.

An example trip calculates reimbursement from the current rate and distance. That would verify a different case: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. It does not verify the required corrective action: Configure payment method and personal-versus-corporate transaction handling on expense reports.

Per diem calculations depend on duration, destination and policy-specific allowances. That explains a separate case: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Intercompany expenses need explicit source and destination company accounting rules. That explains a separate case: A project consultant travels for a subsidiary company, but their expense report charges headquarters because intercompany expense configuration is missing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Mileage policies apply an eligible distance and rate rather than a manual expense amount. That explains a separate case: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review rates and effective dates during annual travel policy updates. That safeguard is aimed at a different risk: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. It does not most directly prevent recurrence of: Corporate card and personal out-of-pocket expenses have different settlement counterparties.

Review expense legal entity when projects cross subsidiary boundaries. That safeguard is aimed at a different risk: A project consultant travels for a subsidiary company, but their expense report charges headquarters because intercompany expense configuration is missing. It does not most directly prevent recurrence of: Corporate card and personal out-of-pocket expenses have different settlement counterparties.

Test expense threshold exceptions and approver authority. That safeguard is aimed at a different risk: A receipt reimbursement exceeds the department's maximum hospitality allowance, but the expense report has no policy warning. It does not most directly prevent recurrence of: Corporate card and personal out-of-pocket expenses have different settlement counterparties.