Exam Bundle

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: Collection letters depend on configured sequence and elapsed-time conditions.

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: Collection letters depend on configured sequence and elapsed-time conditions.

Review pools and worklist ownership when collections staffing changes. That safeguard is aimed at a different risk: A customer is repeatedly delinquent but its assigned collection agent changes weekly and activities become orphaned. It does not most directly prevent recurrence of: Collection letters depend on configured sequence and elapsed-time conditions.

Process an approved billing schedule price update effective on the contract's amendment date. This fits a DIFFERENT issue within Configure and manage subscription billing: A subscription customer receives a new contracted unit price midterm, but the billing schedule keeps the old amount. It does not address the current problem, whose mechanism is: Billing schedule hold status can suspend future invoice generation without deleting historical charges.

Use the supported termination process with approved effective date and final billing adjustment. This fits a DIFFERENT issue within Configure and manage subscription billing: A customer terminates a subscription early, yet finance deletes the entire billing schedule and loses historical audit evidence. It does not address the current problem, whose mechanism is: Billing schedule hold status can suspend future invoice generation without deleting historical charges.

Create a supported subscription billing schedule with customer, period and applicable pricing rules. This fits a DIFFERENT issue within Configure and manage subscription billing: 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 address the current problem, whose mechanism is: Billing schedule hold status can suspend future invoice generation without deleting historical charges.

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: Apply a supported billing schedule hold for the authorized pause period.

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: Apply a supported billing schedule hold for the authorized pause period.

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: Apply a supported billing schedule hold for the authorized pause period.

Subscription termination changes future eligibility and may require prorated adjustments, not historical deletion. That explains a separate case: A customer terminates a subscription early, yet finance deletes the entire billing schedule and loses historical audit evidence. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Price updates to billing schedules need effective dates and historical invoice preservation. That explains a separate case: A subscription customer receives a new contracted unit price midterm, but the billing schedule keeps the old amount. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Milestone contract billing differs from ordinary time-based subscription billing. That explains a separate case: A three-phase implementation contract requires billing milestones, but invoices are generated on a flat monthly frequency. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile prepaid schedules at each month-end. That safeguard is aimed at a different risk: An annual maintenance expense is prepaid, but the expense hits one month instead of spreading over coverage. It does not most directly prevent recurrence of: Billing schedule hold status can suspend future invoice generation without deleting historical charges.

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: Billing schedule hold status can suspend future invoice generation without deleting historical charges.

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: Billing schedule hold status can suspend future invoice generation without deleting historical charges.

Set appropriate payment proposal due-date criteria and review selected vendors and invoices before generation. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not address the current problem, whose mechanism is: Non-PO invoices still require account assignment and policy controls independent of purchase order matching.

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: Non-PO invoices still require account assignment and policy controls independent of purchase order matching.

Configure supported centralized vendor payment and intercompany posting relationships among the companies. This fits a DIFFERENT issue within Implement and manage accounts payable: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not address the current problem, whose mechanism is: Non-PO invoices still require account assignment and policy controls independent of purchase order matching.

Only invoices due in the authorized payment window appear in the proposal. That would verify a different case: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not verify the required corrective action: Use the supported vendor invoice journal or invoice process with appropriate invoice validation policies and workflow setup.

The posted invoice includes the freight fee and reconciles to the expected expense account and tax. That would verify a different case: 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 verify the required corrective action: Use the supported vendor invoice journal or invoice process with appropriate invoice validation policies and workflow setup.

An approved early payment realizes the correct contractual cash discount and records its accounting entries. That would verify a different case: 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 verify the required corrective action: Use the supported vendor invoice journal or invoice process with appropriate invoice validation policies and workflow setup.

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.

Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances. That explains a separate 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. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Paired intercompany AR and AP documents need source references and company-specific posting accuracy. That explains a separate case: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Test over-receipt and over-price invoice cases before enabling automated posting. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Non-PO invoices still require account assignment and policy controls independent of purchase order matching.

Enforce independent bank change validation and callback evidence. That safeguard is aimed at a different risk: A new vendor bank account is accepted from an unverified email and inserted directly into the next payment run. It does not most directly prevent recurrence of: Non-PO invoices still require account assignment and policy controls independent of purchase order matching.

Review policy scope after adding new AP invoice types. That safeguard is aimed at a different risk: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not most directly prevent recurrence of: Non-PO invoices still require account assignment and policy controls independent of purchase order matching.

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: Mileage policies apply an eligible distance and rate rather than a manual expense amount.

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: Mileage policies apply an eligible distance and rate rather than a manual expense amount.

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: Mileage policies apply an eligible distance and rate rather than a manual expense amount.

The transaction posts to the beneficiary entity with correct due-to/due-from entries. That would verify a different case: A project consultant travels for a subsidiary company, but their expense report charges headquarters because intercompany expense configuration is missing. It does not verify the required corrective action: Update the authorized mileage expense rate and effective date in expense management.

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: Update the authorized mileage expense rate and effective date in expense management.

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: Update the authorized mileage expense rate and effective date in expense management.