CCNA Implement and Manage Accounts Payable and Expenses Questions

The vendor payment proposal reads open vendor transactions, applies selection criteria such as due date and payment status, and writes the resulting payment lines into a payment journal. Invoices on payment hold are excluded from selection, so the clerk can generate the weekly run automatically and then post it after review.

Expense management workflows are the standard way to enforce the manager review requirement. By creating a workflow that includes an approval step assigned to the worker's manager, the system enforces the hierarchy before the document is finalized. This control is critical for preventing unauthorized spending and ensuring that all expenses comply with company policy prior to financial recognition in the ledger.

The payment proposal is driven by a query, and the two controls that shape its selection are the due-date range and vendor-level filters such as vendor group. Setting the from and to dates confines the proposal to the ten-day window, and filtering on the Domestic vendor group restricts it to the intended vendors. Payment status, on-hold inclusion, and payment schedules do not produce the requested selection.

The vendor posting profile is the bridge between the sub-ledger (Accounts Payable) and the General Ledger. It dictates which ledger accounts are hit when a vendor transaction is recorded (e.g., invoice, payment). Using posting profiles ensures that payables are consistently classified, making the financial statements accurate and reducing the effort required for manual month-end reconciliation or accounting corrections.

The Vendor collaboration module allows vendors to interact directly with the company through a portal. Vendors can view purchase orders, confirm delivery dates, and submit invoices. This functionality reduces manual administrative tasks for the accounts payable team and increases accuracy by allowing vendors to provide information directly, which then populates the application and streamlines the procurement and invoicing lifecycle.

To route vendor invoices by amount, the workflow must include a conditional decision that evaluates the invoice total and branches accordingly. The approval element on the high-value branch must be assigned to the accounts payable manager. Together, these elements ensure invoices over $10,000 are routed for approval while lower-value invoices follow an auto-approval path.

Vendor payment fees allow organizations to define charges associated with specific payment methods, such as bank processing fees for electronic transfers. These fees are automatically calculated and added to the vendor payment journal during the generation process. This ensures that the financial ledger accurately reflects the total cost of payments, including bank-related charges, which is vital for precise cash management and bank reconciliation.

To enforce two-way matching with tolerance-based posting prevention, the AP manager must create an invoice matching policy with a two-way matching rule and assign it to the vendor. Additionally, price and quantity tolerances must be defined in that policy so the system knows when a variance is acceptable and when it should block posting. These two configurations together provide the required control.

Cash discounts are configured through payment terms such as 2/10 Net 30 and can be overridden at the invoice line level. When the payment proposal selects an invoice within the discount date, Dynamics 365 Finance automatically calculates the discount and reduces the payment amount, ensuring the company captures the 2% savings without manual calculation.

The Vendor payment proposal function inside a payment journal is designed exactly for this scenario. It accepts filters such as vendor group and due date, automatically excludes invoices that are on hold, and produces editable journal lines. Because the lines are editable before posting, the team can review the proposal and remove specific invoices, which satisfies both the filtering and the manual review requirements.

Vendor payment proposals utilize proposal parameters and criteria filters to determine which invoices are selected during batch processing. Configuring minimum and maximum payment limits alongside cash discount preferences ensures cash flow optimization and adherence to liquidity targets established by treasury management.

Payment fees in Dynamics 365 Finance are configured in the Payment fee setup, where you define the fee amount or percentage and associate it with a payment method, such as wire transfer. When a payment journal line uses that method, the fee is automatically calculated and added, ensuring consistent charging without manual intervention.

The policy action is configured as 'Warn' rather than 'Reject' or 'Block'. In Dynamics 365 Finance, a 'Warn' action displays a notification to the user but does not prevent the document from being saved or posted. To stop the transaction entirely, the policy action must be updated to a restrictive level, ensuring strict adherence to the defined financial threshold and preventing manual overrides.

When a vendor has a cash discount code and payment is made within the discount period, the system automatically reduces the payment amount by the discount and posts the discount to the cash discount ledger account. In this scenario, the payment becomes $9,900 and $100 is posted to the discount account. Manual adjustment is not required.

Expense policies in Dynamics 365 Finance are the correct mechanism to enforce category-specific reimbursement rules such as percentage limits, receipt requirements, and approval conditions. By creating a policy with a 100% limit for Bar Dues and an approval-required rule for CLE, the AP manager ensures the system validates each expense line against firm policy at submission, preventing non-compliant reimbursements without manual intervention.

Default accounts for vendor payments are defined in the Vendor posting profile. The posting profile maps the vendor transactions to the correct General Ledger accounts, such as the AP trade account, when an invoice is posted or paid. This mapping is fundamental to the system's ability to maintain an accurate and balanced General Ledger, ensuring all financial activities are correctly categorized and traceable.

The vendor invoice journal is the correct entry point for a non-PO vendor invoice because it immediately posts to the vendor balance and creates an open payable. Only posted, open vendor transactions are considered by the payment proposal. The invoice register holds invoices before approval, so it would not make the invoice available in time.

A vendor group is a mandatory classification used to group vendors for common posting profiles, payment terms, and reporting. It determines which ledger accounts the vendor's transactions will post to by linking to the vendor posting profile. This setup ensures consistent accounting treatment across all vendors within a specific group, simplifying the management of accounts payable and improving the accuracy of financial reporting.

The payment specification on the vendor payment method controls grouping of open transactions into payments. Selecting per vendor consolidates all due invoices for the vendor into a single payment and bank transfer, which is precisely the outcome requested. Payment fees, payment terms, and per-invoice specification affect amounts or timing but never merge multiple invoices into one disbursement.

When the EUR-to-USD rate increases after invoice posting, the USD-equivalent payable grows, creating an unrealized loss. Foreign currency revaluation for accounts payable debits the unrealized loss account and credits the vendor balance for the 60 USD difference. This keeps the payable aligned with the current rate without modifying the original invoice or the vendor master.

The Report 1099 field on the vendor record, along with the associated 1099 box, is the correct configuration to make a vendor reportable for 1099 purposes. When set to Yes, it ensures that all posted invoices for that vendor are automatically included in 1099 reporting without requiring per-invoice changes. This meets the requirement of automatic eligibility upon vendor creation.

Cash discounts in Dynamics 365 Finance are defined through cash discount codes, which store the discount percentage, the number of days the discount is available, and the ledger accounts for the discount. Assigning the code to the vendor or invoice enables the payment proposal and payment journal to calculate and post the discount. Without this setup, no discount logic is applied.

Approval routing is controlled by the expense report workflow, where approval elements can be conditioned on report total or cost center. Mandatory receipts are controlled per expense category through the Receipt required setting. Together these two configurations ensure reports reach the right approver and that receipts are enforced for the categories the controllers choose.

Three-way matching compares the vendor invoice against both the purchase order and the product receipt. Because the received quantity is lower than the invoiced quantity and the matching policy disallows discrepancies, the system blocks posting and reports a matching failure. The invoice can only be posted after the receipt is corrected or the invoice quantity is reduced to match what was actually received.

The Payment proposal feature is designed to aggregate multiple open invoices for a vendor into a single payment batch. It allows users to filter by date, vendor, or other criteria, making it the most efficient way to manage bulk disbursements. This streamlines the accounts payable workload, reduces the number of individual bank transactions, and simplifies the reconciliation process at the end of the month.

The vendor invoice journal is used to manually record invoices that are not associated with a purchase order. It allows for the direct entry of vendor invoices into the system so that they can be paid and tracked in the accounts payable sub-ledger. This is essential for invoices related to expenses like rent, utilities, or services where a formal purchase order process may not be required.

The currency for a vendor is defined on the vendor master record. This setting drives the currency used for all invoices and payments related to that vendor. By setting it correctly at the master level, the system automatically handles the conversion to the accounting currency based on the exchange rates defined in the system, ensuring multi-currency transactions are recorded accurately and financial statements reflect the correct valuation.

The vendor invoice journal posts vendor invoices directly to the ledger and vendor balance without requiring a purchase order or a pending invoice workflow. It is the standard journal for recording non-PO invoices that must be recognized immediately. The invoice register and invoice pool are intermediate stages that delay posting, and the disbursement journal records payments rather than invoice expenses.

Expense policies in Dynamics 365 Finance can be configured with actions such as Warn, Deny, or Allow. When the action is Warn, the employee can still submit the report, but a warning is displayed and the violation is visible to the approver. This allows the business to enforce awareness without hard-blocking submission, leaving the final decision to the approver.

Intercompany accounting is the mechanism that automatically mirrors a transaction posted in one legal entity into another legal entity. Configuring the vendor invoice posting type with the correct original and destination legal entities lets the LE-US invoice generate the LE-CA vendor invoice and liability without duplicate data entry, while a posting profile or reporting tool cannot create cross-entity documents.

To generate a payment proposal, the system must have identified vendor invoices that are due or have a discount date approaching. Additionally, the payment method must be correctly configured to define the bank account and file format for the electronic payment. Properly setting up these parameters ensures that the system can accurately filter invoices and create batch payments that meet the organization's cash flow strategy.

Realized exchange rate gains and losses are posted to accounts defined in General ledger > Currency > Exchange rate gain/loss accounts. These accounts are used when settling foreign currency transactions at a different rate than the original invoice. Configuring them correctly ensures accurate financial reporting.

Expense categories with the Billable option enabled expose the Customer and Project fields on expense lines, allowing employees to charge expenses to the appropriate client and project. This configuration directly supports the firm's policy of distinguishing client-billable from internal expenses within the same expense report, while internal lines can still use the default department.

The vendor invoice journal is designed for entering vendor invoices that are not associated with a purchase order. It lets the clerk record the vendor liability and the expense account directly. Purchase order based invoices use the pending vendor invoice form, while employee reimbursements use expense reports, so the invoice journal is the appropriate choice here.

Centralized payments let one legal entity pay invoices that belong to another legal entity. The originating vendor must have the centralized payment option enabled, and intercompany accounting must be configured between the two legal entities. When the payment journal is posted in the processing entity, the system automatically generates the corresponding vendor and ledger entries in the originating entity.

Three-way matching compares the invoice quantity to the product receipt quantity. With a 2% tolerance, a 5% difference (100 vs 95 units) exceeds the allowed variance, so the system places the invoice on hold. Releasing the hold requires either manual approval of the discrepancy or correcting the receipt quantity to match the invoice within tolerance.

The vendor's currency is defined on the Vendor master record. This setting dictates the default currency for all purchase documents created for that vendor. Ensuring the correct currency is set is vital for accurate accounts payable reporting, as the system will use this currency to calculate revaluations and exchange rate gains or losses, maintaining financial accuracy in a global business environment.

Expense report workflows support hierarchical assignment types that resolve the approver from the employee's position and cost center, so a manager step followed by a participant step for the travel approver creates the required automatic two-stage route. Approval limits and delegation settings affect thresholds or temporary reassignment but cannot construct an organizational approval chain on their own.

Activating the vendor invoice workflow is the primary mechanism to enforce hierarchical approval logic in Dynamics 365. When enabled, the invoice status transitions from 'Draft' to 'In Review', preventing posting until final approval. This ensures internal controls are satisfied by verifying that expenses align with departmental budgets and service expectations before financial impacts are recorded in the general ledger.

Expense policies define the categories employees may select and the rules that apply to them. Assigning the correct policy to an employee limits the category list on the expense report and ties into workflow so the controller can approve before reimbursement. Per diem and cost center settings support calculations and posting but do not control category availability.

A manual matching exception is the targeted control that releases a single invoice despite a quantity discrepancy without altering the corporate matching policy. Workflow approval, item model group settings, and editing the invoice quantity either do not affect matching or distort the vendor liability, so the exception record is the correct approach for a one-off short receipt.

Three-way matching and price tolerances are both defined inside an invoice matching policy. The policy is attached to a vendor or item and determines whether the system requires purchase order, product receipt, and invoice alignment. Setting a 5 percent price tolerance within that policy causes the system to hold or block posting when the calculated variance exceeds the limit, which is exactly what the manager needs.

Expense policies are the correct feature to enforce spending limits per expense category. By configuring a policy with a maximum amount for the Meals category and assigning it to employees, the system will automatically flag or prevent submission of expenses that exceed the limit. Other features like categories, per diem, and workflows do not provide this specific enforcement.