Implement and Manage Accounts Payable and Expenses practice questions

Two-way matching policy with a 5% tolerance.

Why it fails: Two-way matching only compares the purchase order price with the invoice price. It does not account for the product receipt, meaning the system would not be able to verify that the goods were actually received. This is insufficient for companies that need to confirm inventory arrival before payment.

No matching policy.

Why it fails: Without a matching policy, the system performs no validation between the invoice and the purchase order. This would allow any invoice to be posted regardless of price or quantity discrepancies, which significantly increases the risk of overpayment, fraud, or processing incorrect supplier documentation.

Charge matching policy.

Why it fails: Charge matching is used specifically for verifying freight or miscellaneous charges on an invoice. It is not designed to handle the core price matching between the unit price on the purchase order and the vendor's invoice, and therefore cannot enforce the 5% tolerance requirement.

Manually create a payment journal for every line item.

Why it fails: The system automatically handles the reimbursement process through the payment proposal feature or the expense management posting process. Manually creating a journal for each line item is inefficient and redundant, as it bypasses the automated reconciliation and posting controls built into the expense management module.

Convert the expense report to a purchase order.

Why it fails: Expense reports and purchase orders are distinct document types in the system. Expenses are meant for employee reimbursement, while purchase orders are for vendor procurement of goods and services. Converting one to the other is not a standard business process and would disrupt accounting records.

Change the matching policy to 'No matching' to allow posting.

Why it fails: Disabling the matching policy removes the control mechanism entirely. This allows potentially erroneous or fraudulent invoices to be paid, which contradicts the goal of using the three-way matching process to ensure accuracy and compliance. This is a poor practice for maintaining financial accuracy in any ERP system.

Create a new purchase order to cover the variance.

Why it fails: Creating a new purchase order to cover a variance is improper accounting practice and creates duplicate liabilities. It obscures the original transaction and complicates auditing processes. Instead, the focus should be on reconciling the existing invoice against the original PO or amending the PO via a change order.

Ignore the error and post the invoice as an adjustment.

Why it fails: The system does not allow posting when a matching error exists because the invoice fails validation. Manually adjusting the ledger entries later is inefficient and prone to error. You must resolve the matching discrepancy directly in the invoice matching screen to keep the sub-ledger and ledger in sync.

Default Bank Account.

Why it fails: While recommended for automated payments, a default bank account is not mandatory to create a vendor record. Vendors can be paid via other methods or the account can be added later as part of the payment setup. The record creation process does not block the user.

Vendor primary contact email address.

Why it fails: Contact information like an email address is important for communication but is not a system-level requirement to save the vendor master record. The system allows the creation of a vendor without any contact details, as these are considered descriptive data rather than foundational accounting data.

Set the vendor's default payment terms.

Why it fails: Payment terms are set on the vendor master record or a specific invoice, not in the global Accounts payable parameters. Global parameters are for organizational-level rules, not for defining the specific financial terms of a business relationship with an individual vendor entity, which requires more flexibility.

Define the vendor's bank account.

Why it fails: The vendor's bank account details are specific to the vendor and must be entered on the vendor's master record. It would be impossible to maintain an accurate vendor bank file within the global parameters, as each vendor has a unique bank account for receiving their respective payments.

Set the default currency for the company.

Why it fails: The company's default currency is defined in the Ledger settings, not in the Accounts payable parameters. These global accounting settings govern the entire organization's books and are not meant to be modified in the AP module, which handles only the sub-ledger operations for vendor transactions.

Navigate to Accounts payable parameters, and on the Invoice tab, set the 'Check for invoice total' parameter to 'Approver' and define the threshold amount.

Why it fails: The check for invoice total parameter is utilized for matching validation discrepancies rather than applying a general processing hold based on high financial thresholds. Using it for threshold holds will yield unexpected matching workflow behaviors.

Navigate to Accounts payable parameters, and on the General tab, configure the 'Maximum invoice amount' to halt processing for high-value items.

Why it fails: The maximum invoice amount parameter is designed to prevent posting completely rather than placing the document on a manageable administrative hold. It rejects the transaction outright rather than routing it for review.

Navigate to Accounts payable parameters, and on the Workflow tab, set the activation threshold for automated approval routing.

Why it fails: Workflow parameters control routing rules and task assignments, but they do not execute a direct system-level invoice hold upon creation without a fully defined workflow template configured in the workspace.

Enable the Vendor invoice matching policy and set the tolerance percentage to 5% in the Accounts payable parameters.

Why it fails: Accounts payable parameters control global settings, but they do not house the specific tolerance percentage fields for invoice matching. Matching policies and their respective percentages are managed under the Invoice matching setup page, which provides granular control over vendor-specific or item-specific tolerance rules in the application.

Configure a matching policy on the Vendor record and set the total matching tolerance percentage to 5%.

Why it fails: While matching policies can be defined at the vendor level, the tolerance percentage itself is defined in the Matching policy setup, not directly on the vendor record. The vendor record only points to a policy definition, whereas the actual percentage thresholds are maintained in the central matching configuration.

Activate the Purchase order approval workflow and set a condition to validate the invoice total.

Why it fails: Workflows manage the approval routing of documents but are not designed to perform real-time mathematical matching between invoices and purchase orders. Invoice matching is a dedicated engine that functions independently of workflow, specifically designed to validate line-level and total-level discrepancies before the invoice reaches final approval.

Set up a new workflow for mileage approval.

Why it fails: While workflows are used for approval, they are not a prerequisite for the technical functionality of mileage calculations. Mileage logic operates independently of the document routing process, meaning the system can calculate reimbursements even without a specific mileage-dedicated workflow, as long as the underlying rates exist.

Assign a vendor account to every employee profile.

Why it fails: Employees are linked to their own internal entity, not necessarily a vendor record for expenses. Dynamics 365 Finance uses the worker/employee relationship for expense reimbursement, which is distinct from the vendor master. While vendors are used for external payables, internal reimbursements are handled via the expense management employee profile.

Enable the automatic tax calculation on mileage categories.

Why it fails: Automatic tax calculation is a global feature related to sales tax groups and item sales tax groups, not a requirement for enabling mileage expenses. Mileage reimbursements are typically processed as nontaxable or specific internal transfers, making this setting irrelevant to the core function of calculating distance-based travel reimbursements.

Initiate an electronic bank transfer directly to the vendor's API.

Why it fails: Payment proposals prepare the payment journals; they do not trigger external API calls to bank systems directly. Electronic payments are handled through the export of payment files or direct integration via bank communication apps, not by the proposal selection process itself, which is strictly an internal accounting function.

Change the vendor's bank account details permanently.

Why it fails: Payment proposals are intended for transaction selection and processing, not for modifying vendor master data. Permanent changes to bank account details must be performed on the vendor record itself to maintain data integrity and audit trails, keeping transactional activities separate from the master data management processes.

In the Vendor group configuration.

Why it fails: Vendor groups are primarily used for posting profiles and common settings across multiple vendors. They do not contain logic for invoice hold thresholds, as these controls are usually applied globally through the Accounts payable module's parameters or specifically through individual vendor account settings during high-value invoice processing.

In the Vendor posting profile.

Why it fails: Posting profiles are used to determine which General Ledger accounts are hit during financial transactions. They manage the accounting side of the invoice but have no functional capability to trigger invoice holds or validate invoice amounts against specific thresholds, as this is the role of the invoice matching engine.

In the Terms of payment setup.

Why it fails: Terms of payment define the due dates and cash discount terms for invoices. They are not designed to evaluate the invoice amount or manage approval status, as their sole purpose is to calculate the payment schedule based on the transaction date and predefined financial agreement terms with the vendor.

The vendor must have a credit rating of A or higher.

Why it fails: Credit ratings are used for risk assessment and do not affect the technical functionality of the invoice matching engine. The matching engine operates strictly on transactional data and rules, regardless of the vendor's financial standing, making credit ratings irrelevant to the mathematical process of verifying invoice document details.

The invoice date must be within 30 days of the PO date.

Why it fails: There is no default restriction that mandates an invoice date to be within 30 days of the PO date for matching purposes. While business rules might dictate such timing, the system's matching engine does not enforce this as a technical condition for successful invoice matching in Dynamics 365.

The Vendor aging report.

Why it fails: The aging report is an analytical tool for viewing overdue and outstanding balances. It is not an interactive interface for creating payment journals. While it provides visibility, it does not allow the user to select invoices for payment generation, as that must be done through the payment journal's proposal functionality.

The Vendor transaction inquiry.

Why it fails: Transaction inquiry is a read-only list of all historical entries for a vendor. It is designed for auditing and reporting purposes, not for processing payments. Attempting to manage payments here would be inefficient, as it lacks the settlement logic and journal creation capabilities found in the payment journal module.

The Global address book.

Why it fails: The Global address book manages party information such as names, addresses, and contacts. It contains no financial transaction data, invoice details, or payment processing logic. Therefore, it is impossible to use the Global address book to filter for invoices or prepare any kind of payment document in the system.

Vendor payment journals must include default offset accounts to handle automatically generated posting discrepancies during invoice matching.

Why it fails: Payment journals are utilized exclusively for disbursement processing and settlement tasks rather than controlling the evaluation parameters or validation rules enforced during initial vendor invoice matching and purchase order receipt verification procedures.

Accounts payable posting profiles must be updated to include separate clearing accounts for price tolerance variances.

Why it fails: Posting profiles control ledger account determinations for normal subledger transactions like invoices and payments, whereas invoice matching is a validation process that happens prior to final posting and does not directly depend on clearing accounts.

Vendor collaboration security roles must be assigned to procurement managers to ensure tolerance overrides are properly audited.

Why it fails: Vendor collaboration portals allow external vendors to view purchase orders and submit invoices, but internal security roles have no direct impact on configuring or executing internal invoice matching tolerance calculations.

Create a vendor group for the firm's manually paid vendors and clear the 'Payment proposal' checkbox on the vendor group's setup.

Why it fails: There is no 'Payment proposal' checkbox on the vendor group. Vendor groups control posting profiles, default terms, and settlement settings, but payment proposal inclusion is controlled at the vendor level via the Payment proposal exclusion field. Creating a group and toggling a nonexistent setting would not achieve the requirement, and it would incorrectly affect every other vendor assigned to that group.

Set the vendor's Default payment method to a method that is excluded from the payment proposal, such as a custom 'Manual check' method, so the vendor is skipped during proposal generation but can still be paid manually.

Why it fails: Excluding a payment method from the proposal only prevents the proposal from using that method; the vendor is still selected by the proposal if it has other eligible payment methods or if the method is not truly excluded. This does not reliably block the vendor, and it also blocks legitimate manual selection of the vendor during a proposal run when the firm might want to include it. The requirement is to prevent the vendor from appearing in the proposal at all, which this configuration does not guarantee.

Set the vendor's Hold status to 'All' on the vendor record so no transactions can be posted to the vendor until the hold is removed.

Why it fails: Setting a vendor hold to 'All' blocks posting of new invoices and payments to the vendor entirely, not just payment proposal inclusion. The firm would be unable to record the manual payment journal entry the scenario requires, because posting is blocked. A hold is a compliance control for stopping all transactional activity, not a targeted control for excluding a vendor from an automated proposal while still permitting manual payment.

The invoice posts successfully because the line quantity and price match exactly.

Why it fails: Exact line matching does not guarantee the whole invoice passes. The freight charge is an additional cost not present on the PO, and with zero tolerance the invoice total cannot exceed the matched amount. The system evaluates the invoice total against the PO, so the invoice is held despite the line-level match.

The invoice is automatically approved because freight is under the price tolerance.

Why it fails: The price tolerance applies to unit price variance, not to additional charges like freight. With a zero percent price tolerance, even a small unit price difference would fail; freight is a separate charge that is not covered by the price tolerance. The invoice will not be auto-approved under these settings.

The invoice posts successfully because freight is excluded from matching.

Why it fails: Freight charges are not automatically excluded from matching. If the matching policy does not include a charges tolerance and the freight is not on the PO, the invoice total exceeds the matched line total, causing a matching failure. The invoice will be placed on hold rather than posted successfully.

That the vendor posting profile includes a summary account for realized gains and losses.

Why it fails: The vendor posting profile controls the summary accounts for vendor balance transactions, not exchange difference accounts. Realized exchange gains and losses are posted to the ledger accounts configured for currency exchange differences in the Accounts payable parameters or currency setup, so the posting profile is not the right place to verify.

That the payment journal name is restricted to the vendor currency rather than the company currency.

Why it fails: Journal names do not carry a currency restriction that drives exchange difference posting. The currency on the journal line comes from the account and offset account setup, and restricting the journal name would not enable the automatic exchange difference calculation the treasurer expects.

That the vendor record has a payment fee configured for foreign currency transactions.

Why it fails: A payment fee is a charge the company pays or passes on for processing a payment; it is unrelated to exchange rate differences. Configuring a payment fee does not cause the system to post exchange differences when a foreign currency invoice is settled by a company-currency payment, so this check would not achieve the treasurer's goal.

Set the vendor's default payment method to 'Centralized' and assign a single bank account shared across all legal entities.

Why it fails: Payment method alone does not enable cross-entity payment selection, and bank accounts are legal-entity specific rather than shared. Centralized payments depend on intercompany configuration and the vendor's centralized payment flag in each entity, not on a shared bank account. This setup would not allow the proposal to reach the other entity's invoices.

Enable the 'Cross-company payment' parameter in the Accounts payable parameters and select the vendors to include.

Why it fails: There is no Accounts payable parameter named for cross-company payment that alone enables centralized payments. The capability is controlled through the vendor's centralized payment configuration and intercompany relationships. Relying on a parameter would leave the other legal entity's invoices invisible to the proposal.

Post a manual journal in the invoiced legal entity to transfer the vendor balance to the paying legal entity before running the proposal.

Why it fails: Manually moving vendor balances defeats the purpose of centralized payments and would create incorrect vendor balances in both entities. Centralized payments are designed to settle the original invoices directly, with intercompany entries generated automatically. A manual transfer journal is not required and would misstate the vendor subledger.

On the Accounts payable parameters page, set the 'Match invoice totals' option to Yes and define a tolerance percentage of 5%.

Why it fails: Setting 'Match invoice totals' to Yes enables invoice total matching against purchase order totals, but the tolerance for invoice totals is not defined as a simple percentage in the same way as price or quantity tolerances. Invoice total matching compares the invoice total to the sum of the purchase order lines, and the tolerance is configured separately under 'Invoice totals tolerance' in the Accounts payable parameters or on the item/vendor level. A blanket 5% on the parameters page is not how it works.

On the Accounts payable parameters page, enable 'Match invoice totals' and then on the Item model group, set the 'Invoice total tolerance' to 5%.

Why it fails: Invoice total tolerance is not configured on the Item model group. Item model groups control inventory costing and posting, not invoice matching tolerances. While invoice total matching can be enabled in Accounts payable parameters, the tolerance percentage is set on the 'Invoice totals tolerance' page or on the vendor record, not on the Item model group. This option incorrectly places the tolerance setting in a module unrelated to accounts payable.

On the Vendor master, set the 'Invoice matching' FastTab to 'Two-way matching' and specify a 5% tolerance.

Why it fails: Two-way matching compares invoice price and quantity to the purchase order, but it does not enforce a total invoice amount tolerance against the sum of PO lines. Two-way matching is about line-level price and quantity checks, not the overall invoice total. A 5% total tolerance would not be applied through this setting. Therefore, this configuration does not meet the requirement of checking that the invoice total does not exceed the PO total by more than 5%.

Payment schedule with multiple installments.

Why it fails: Payment schedules are used to split an invoice into multiple installments over time. They do not combine multiple invoices into one payment. Using a payment schedule would actually increase the number of payments, not reduce them.

Vendor payment journal with the 'One payment per invoice' setting.

Why it fails: The 'One payment per invoice' setting would create separate payments for each invoice, which is the opposite of what is needed. This setting is used when you want to track payments individually and is not suitable for combining invoices.

Vendor collaboration workspace to approve invoices for payment.

Why it fails: Vendor collaboration is used for vendors to submit invoices and for buyers to review them. It does not combine invoices into a single payment. The payment proposal is the correct tool for grouping invoices into one payment.

Configure the vendor's 'Payment method' to 'Check' and enable 'Consolidate payments'.

Why it fails: While some payment methods may have consolidation options, the standard 'Consolidate payments' setting is not on the vendor payment method. The primary control for combining invoices into one payment is the summarization setting within the payment proposal itself, not the payment method.

Set the 'Payment specification' to 'Invoice' in the Vendor payment journal.

Why it fails: Payment specification determines how payment lines are generated from the proposal, such as by invoice or by vendor, but it does not control summarization. Setting it to 'Invoice' would typically create separate lines per invoice, not combine them into one payment.

Enable 'Separate payment per invoice' in the Vendor payment terms.

Why it fails: Payment terms define due dates and discount calculations, not payment grouping. The 'Separate payment per invoice' option does not exist in standard payment terms; even if similar settings existed, they would force separate payments, which is the opposite of what the team needs.