Exam Bundle

Validate aging cutoff dates and calendars at each period close. That safeguard is aimed at a different risk: Collection agents cannot distinguish recent from seriously overdue balances because the aging definition has incorrect period buckets. It does not most directly prevent recurrence of: Credit exposure can include transaction states other than posted AR invoices depending on configured rules.

Audit hold overrides and repeat-risk customers each month. That safeguard is aimed at a different risk: A sales order is held for credit review, but a junior user releases the order without documenting why. It does not most directly prevent recurrence of: Credit exposure can include transaction states other than posted AR invoices depending on configured rules.

Track promised-payment due dates and overdue follow-up assignments. That safeguard is aimed at a different risk: The collection team records debtor conversations outside Dynamics, so nobody knows whether a payment promise was made. It does not most directly prevent recurrence of: Credit exposure can include transaction states other than posted AR invoices depending on configured rules.

Review recognition batch history and posted schedules before any repeat processing. This fits a DIFFERENT issue within Configure and manage subscription billing: A subscription deferral journal posts twice because the month-end recognition batch is rerun without checking prior completion. It does not address the current problem, whose mechanism is: Deferral defaults determine which source transactions receive schedule treatment at line level.

Configure and apply a revenue deferral template and recognition schedule matching the service period. This fits a DIFFERENT issue within Configure and manage subscription billing: A prepaid annual license is invoiced today, but accounting books all recognized revenue immediately. It does not address the current problem, whose mechanism is: Deferral defaults determine which source transactions receive schedule treatment at line level.

Apply a supported billing schedule hold for the authorized pause period. This fits a DIFFERENT issue within Configure and manage subscription billing: A service contract is paused for maintenance, but the monthly billing schedule continues issuing invoices. It does not address the current problem, whose mechanism is: Deferral defaults determine which source transactions receive schedule treatment at line level.

The setup charge follows approved recognition timing while recurring service revenue is deferred over service periods. That would verify a different case: 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 verify the required corrective action: Configure deferral defaults by supported relevant items or categories, not an unqualified global vendor setting.

Future invoice lines use the new agreed rate while already-posted periods retain history. That would verify a different case: A subscription customer receives a new contracted unit price midterm, but the billing schedule keeps the old amount. It does not verify the required corrective action: Configure deferral defaults by supported relevant items or categories, not an unqualified global vendor setting.

Invoices generate when intended milestone conditions are satisfied, not simply every calendar month. That would verify a different case: A three-phase implementation contract requires billing milestones, but invoices are generated on a flat monthly frequency. It does not verify the required corrective action: Configure deferral defaults by supported relevant items or categories, not an unqualified global vendor setting.

Subscription billing schedules drive recurring contract invoices through period definitions and item grouping. That explains a separate case: A customer buys a 12-month support subscription, but the sales team manually invoices all twelve months and misses renewal price rules. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Different components of a contract may require distinct recognition schedules. That explains a separate case: The finance team adds a one-time setup charge to a subscription but the charge is recognized evenly over 12 months against policy. 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.

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: Deferral defaults determine which source transactions receive schedule treatment at line level.

Run overlap detection before subscription renewals and upgrades. That safeguard is aimed at a different risk: A customer upgrades from a monthly to an annual plan, but its old schedule continues billing and overlaps the new contract. It does not most directly prevent recurrence of: Deferral defaults determine which source transactions receive schedule treatment at line level.

Reconcile deferral schedules to invoicing and general ledger balances. That safeguard is aimed at a different risk: A prepaid annual license is invoiced today, but accounting books all recognized revenue immediately. It does not most directly prevent recurrence of: Deferral defaults determine which source transactions receive schedule treatment at line level.

Run the approved vendor foreign currency revaluation for eligible open vendor balances. This fits a DIFFERENT issue within Implement and manage accounts payable: A month-end AP foreign-currency revaluation is skipped and open vendor liabilities are understated. It does not address the current problem, whose mechanism is: Supplier invoice numbers and identity should be checked regardless of source document filename.

Use the authorized vendor prepayment process with correct liability/asset treatment and subsequent settlement. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. It does not address the current problem, whose mechanism is: Supplier invoice numbers and identity should be checked regardless of source document filename.

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: Supplier invoice numbers and identity should be checked regardless of source document filename.

The advance remains visible and is applied against the final vendor invoice as permitted. That would verify a different case: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. It does not verify the required corrective action: Enable or apply duplicate vendor invoice controls using supplier identity and invoice number.

A valid non-PO expense invoice is processed with the correct controls while PO invoices retain matching. That would verify a different case: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not verify the required corrective action: Enable or apply duplicate vendor invoice controls using supplier identity and invoice number.

The generated payment file uses the approved bank and currency while the other bank remains excluded. That would verify a different case: A batch vendor payment run selects a bank account not authorized for that currency. It does not verify the required corrective action: Enable or apply duplicate vendor invoice controls using supplier identity and invoice number.

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.

Vendor advances need distinct posting and settlement rather than being treated as final goods receipt. That explains a separate case: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Invoice charges add line/header costs outside the base purchase price and need explicit mapping. That explains a separate case: A vendor charges an agreed freight fee, but the AP invoice amount differs from the purchase order because the charge code is missing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile foreign-currency invoice values and rates at approval. That safeguard is aimed at a different risk: A vendor invoice is received in EUR but its liability is initially valued in USD at the wrong exchange rate. It does not most directly prevent recurrence of: Supplier invoice numbers and identity should be checked regardless of source document filename.

Reconcile due-to and due-from accounts after centralized payment batches. That safeguard is aimed at a different risk: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not most directly prevent recurrence of: Supplier invoice numbers and identity should be checked regardless of source document filename.

Use duplicate-payment detection and generated-file reconciliation on batch retries. That safeguard is aimed at a different risk: A vendor payment batch is approved, but the payment file generation fails and the team plans to resubmit the journal without inspecting status. It does not most directly prevent recurrence of: Supplier invoice numbers and identity should be checked regardless of source document filename.

Configure payment method and personal-versus-corporate transaction handling on expense reports. This fits a DIFFERENT issue within Configure expense management: An employee pays a reimbursable expense with a corporate card, yet the system also schedules the employee for direct cash reimbursement. It does not address the current problem, whose mechanism is: Expense report workflow identity rules determine who may authorize employee costs.

Configure the appropriate expense category and associated main account, tax and policy mapping. This fits a DIFFERENT issue within Configure expense management: Employees submit taxi costs under a client entertainment expense category, creating incorrect tax and ledger treatment. It does not address the current problem, whose mechanism is: Expense report workflow identity rules determine who may authorize employee costs.

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: Expense report workflow identity rules determine who may authorize employee costs.

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: Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately.

The reimbursed amount and local accounting amount match the approved rate calculation. That would verify a different case: An employee attaches a receipt but submits a currency conversion with an incorrect reimbursement currency and exchange rate. It does not verify the required corrective action: Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately.

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: Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately.