Implement Accounts Receivable, Credit, Collections, and Subscription Billing practice questions

Billing schedule with a custom interval

Why it fails: A billing schedule with a custom interval can define irregular billing periods, but it does not automatically calculate prorated amounts for a partial first month. It would still generate a full charge for the defined interval unless combined with a proration method. The scenario specifically requires proration, so a custom interval alone is insufficient.

Charge setup with a specific start date

Why it fails: Charge setup defines the price and start date for a subscription charge, but it does not inherently prorate the first invoice. The start date determines when billing begins, but without a proration method, the system would bill the full period amount. Proration logic must be explicitly configured to calculate the partial period.

Billing cycle with a start date of the 15th

Why it fails: Billing cycles define the frequency and start date for recurring invoices, but they do not automatically prorate the first period. Setting a billing cycle start date to the 15th would generate full monthly charges, not prorated amounts. Proration requires additional configuration beyond the billing cycle itself, such as using a proration method.

Enable 'Automatic settlement' on the customer posting profile.

Why it fails: Automatic settlement on the posting profile controls whether transactions are automatically settled during posting, but it does not define the order in which open invoices are selected for payment application. It is used for ledger integration and does not support oldest-first logic. This setting is not the correct place to configure payment application rules.

Use a collection letter sequence to apply payments to the oldest invoices.

Why it fails: Collection letter sequences are used to generate and manage collection letters for overdue customers. They do not apply payments to invoices. This feature is part of collections management, not payment application. Using it would not achieve automatic payment settlement to oldest invoices.

Set up a settlement priority on the Accounts receivable parameters.

Why it fails: Settlement priority in Accounts receivable parameters determines the order in which transactions are settled when multiple transactions exist, but it is not the feature that automatically applies payments to the oldest invoices during payment journal posting. It is used for settlement of invoices against credit notes, not for payment application. This does not meet the requirement for oldest-first automatic application.

Set the customer's credit rating to 'Poor' and enable the 'Credit limit' check in the Customer detail form.

Why it fails: Credit rating is an informational field used for reporting and does not trigger automatic credit holds. The 'Credit limit' check in the Customer detail form is a display of whether a credit limit exists, not a control that enforces holds. Neither action evaluates the customer's balance against the limit nor automatically changes the credit status to 'Credit hold'.

Configure a credit limit of 50,000, set the credit limit type to 'Balance due', and enable the 'Credit hold' checkbox in the Accounts receivable parameters.

Why it fails: Enabling the 'Credit hold' checkbox in Accounts receivable parameters does not automatically place customers on hold when their credit limit is exceeded. That parameter controls whether credit hold functionality is available, but the automatic hold must be triggered by a credit limit rule or a credit management posting profile. Without a rule that evaluates the credit limit and sets the hold, the order would not be blocked.

Set the credit limit type to 'Balance due with packing slip' and enable the 'Mandatory credit limit' parameter.

Why it fails: Changing the credit limit type to include packing slips does not trigger automatic credit hold; it only changes the balance calculation to include posted packing slips. The 'Mandatory credit limit' parameter forces a credit limit to be defined but does not automatically place the customer on hold when exceeded. This configuration would not achieve the required automatic blocking of the sales order.

Enable the Credit management feature in Feature management and configure credit management parameters.

Why it fails: Enabling the Credit management feature and configuring parameters is a prerequisite for using credit management, but it is not sufficient to enable automatic credit hold. You must also create and assign credit hold rules. This option is necessary but not one of the two specific actions required to define the rules and their application to customers.

Configure aging period definitions and link them to the credit hold rule.

Why it fails: Aging period definitions are used to categorize overdue amounts by age for reporting and collections. They are not directly linked to credit hold rules. Credit hold rules evaluate conditions like overdue balance, but they do not require aging period definitions. Aging periods are separate from the credit hold rule configuration.

Set up collection letter sequences and assign them to the credit management group.

Why it fails: Collection letter sequences are used for collections, not for credit hold automation. They generate letters to customers with overdue balances. While they are part of the collections process, they do not trigger credit holds. Assigning them to a credit management group does not contribute to automatic credit hold functionality.

Configure a credit management rule of type 'Credit limit' with a threshold of $10,000 and set the action to 'Place on hold'.

Why it fails: Credit limit rules in Dynamics 365 Finance are used to calculate and enforce credit limits based on various factors, but they do not directly place a customer on hold based on overdue balances. The action 'Place on hold' is not a standard action for credit limit rules. Overdue balance holds are managed through aging period definitions and credit management parameters.

Set up a collection letter sequence with a condition that places the customer on hold when the overdue balance exceeds $10,000.

Why it fails: Collection letter sequences are designed to send dunning letters to customers; they do not automatically place a credit hold on the customer account. While collection letters can be generated for overdue balances, they do not block sales order confirmation. A credit hold must be applied through the credit management features, not through collection letters.

Create a credit limit rule that sets the credit limit to $10,000 and enable the 'Mandatory credit limit' parameter.

Why it fails: This approach would block all new orders once the total credit exposure exceeds $10,000, regardless of how overdue the balance is. The scenario specifically requires a hold triggered by an overdue amount, not a static credit limit. Mandatory credit limits apply at order entry, not based on aging, and would incorrectly prevent orders even when the customer is current.

Set the billing schedule to 'Monthly' with a billing start date of January 15 and a proration method of 'Daily'.

Why it fails: A billing schedule of 'Monthly' with a start date of January 15 and daily proration would generate the first invoice for a partial month and then subsequent invoices on the 15th of each month, not full calendar months. The requirement is for subsequent invoices to cover full calendar months (e.g., February 1 to February 28), which this configuration does not achieve. Proration affects only the first period, but the billing dates remain on the 15th.

Create a billing schedule with a billing frequency of 'Monthly' and a billing period start date of January 15, and set the 'Align billing periods' option to 'Calendar month'.

Why it fails: The 'Align billing periods' option in subscription billing does not align periods to calendar months; it aligns billing periods to the subscription start date or a specified day. There is no out-of-box option to align to calendar months directly. Therefore, this configuration would still bill on the 15th of each month, not on the first of the month as required for full calendar months.

Use a billing schedule of 'Monthly' with a billing start date of February 1 and manually create a separate invoice for January 15 to January 31.

Why it fails: This approach requires manual intervention to create the first invoice, which is not automated and prone to error. The requirement is to configure the subscription so that the first invoice automatically covers January 15 to February 14, and subsequent invoices cover full calendar months. Manually creating an invoice does not achieve the automated billing schedule and does not align subsequent invoices to calendar months.

Create a new sales order for the additional 5 units with a start date of the change date and a billing schedule that covers the remainder of the quarter.

Why it fails: Creating a separate sales order for the additional units would not adjust the existing subscription's future billing schedules. The existing subscription would continue to bill at the old quantity, leading to incorrect future billings. While it might bill the difference for the current quarter, it does not meet the requirement to adjust future billing schedules for the subscription.

Cancel the existing subscription and create a new subscription with the new quantity starting from the change date.

Why it fails: Canceling and recreating the subscription would lose the continuity of the subscription and may not correctly prorate the current quarter. It also creates unnecessary complexity and does not use the built-in quantity change functionality. This approach does not adjust future billing schedules on the same subscription and could result in incorrect revenue recognition.

Create a credit memo for the unused portion of the original quantity and a new invoice for the new quantity for the remainder of the quarter.

Why it fails: While credit memos and new invoices can adjust billing, this manual approach does not automatically update the subscription's future billing schedules. The subscription would still generate future billings at the old quantity unless the subscription itself is changed. This method is error-prone and does not use the subscription billing features designed for quantity changes.

Set up a recurring sales order with a recurrence pattern of every 3 months and an end date of December 31, 2025.

Why it fails: While recurring sales orders can generate periodic invoices, subscription billing in Dynamics 365 Finance uses billing schedules specifically designed for subscription scenarios. Recurring sales orders are a different feature used for standard sales orders and do not provide the same subscription management capabilities, such as proration or milestone billing. The scenario requires subscription billing, so a billing schedule is the appropriate configuration.

Configure a collection letter sequence that sends invoices quarterly based on the contract start date.

Why it fails: Collection letter sequences are used for dunning customers with overdue balances, not for generating invoices. They do not create invoices; they send reminders for outstanding payments. This option is completely unrelated to the requirement of generating quarterly invoices for a subscription contract. The correct feature is billing schedules within subscription billing.

Create a free text invoice template with a quarterly recurrence and assign it to the customer.

Why it fails: Free text invoice templates do not support automatic recurrence. They are used for manual invoice creation with predefined lines. While you can create a free text invoice with multiple lines, it does not automate the generation of invoices on a schedule. Subscription billing requires a billing schedule to automate invoice generation based on frequency and duration.

Use the 'Settle transactions' form in Accounts receivable to apply the vendor bill against the customer invoice.

Why it fails: The 'Settle transactions' form in Accounts receivable is used to settle customer transactions with customer payments or credit notes, not with vendor bills. Vendor bills are in Accounts payable. To offset customer and vendor balances, you must use the centralized payment or netting functionality, not the standard settlement form in Accounts receivable.

Configure a credit limit rule that allows offsetting between customer and vendor balances.

Why it fails: Credit limit rules are used for credit management and do not provide offsetting functionality. They calculate credit exposure and enforce limits. Offsetting customer and vendor balances is done through vendor netting, not credit limit rules. This option is incorrect because credit limit rules are unrelated to settlement between customer and vendor accounts.

Create a journal entry to debit Accounts payable and credit Accounts receivable for $5,000.

Why it fails: While a manual journal entry can offset the balances, it does not link the transactions for settlement purposes and may create reconciliation issues. The proper way to offset customer and vendor balances is through the vendor netting functionality, which allows you to select specific invoices and bills to settle against each other. A manual journal entry would not mark the original transactions as settled.

Specify a default 'Offset account' for automatic settlement in the Accounts receivable parameters.

Why it fails: The offset account defines the ledger dimension used when posting the settlement transaction; it does not control which documents are matched. Automatic settlement matching is driven by the customer's open transactions and the settlement priority configured on the customer record or in the payment terms. Changing the offset account would affect financial posting, not the automatic application of a credit note to an invoice.

Set the credit note's 'Collection letter code' to 'Settle' in the Free text invoice form.

Why it fails: Collection letter codes drive dunning and statement output, not automatic settlement priority. Configuring a collection letter code on a free text invoice does not instruct the settlement engine to consume the credit note against open invoices; it only affects how overdue balances are communicated. Automatic settlement relies on the customer's payment terms and the 'Settle automatically' parameter, not on collection letter codes.

Configure the customer's 'Settlement priority' to 'Oldest first' on the Customer form.

Why it fails: Settlement priority on the customer record determines the order in which open invoices are considered for payment proposals, but it does not automatically apply credit notes. Credit notes are applied through the 'Settle open transactions' process or during payment journal posting if 'Settle automatically' is enabled. The priority setting alone does not ensure the credit note is consumed against the oldest invoice.

Configure interest codes and assign them to the customer profile.

Why it fails: Interest codes calculate interest on overdue balances and post interest notes, but they do not enforce credit limits or automatically block customers. They are used for finance charges, not credit control. Setting up interest codes would not meet the stated goals of enforcing credit limits during sales order entry and automatically blocking overdue customers.

Set up collection letter sequences for each aging bucket.

Why it fails: Collection letter sequences generate customer communications for overdue balances but do not enforce credit limits or automatically block customers. They are a separate collections tool. While useful for dunning, they do not satisfy either requirement of enforcing credit limits at order entry or automatically blocking overdue customers, so they are not part of the correct setup.

Define credit rating values on the customer master record.

Why it fails: Credit rating values are informational attributes that can be used in blocking rule conditions, but by themselves they do not enforce credit limits or trigger automatic blocks. The analyst could use credit ratings as part of a rule, but the requirement is to enable enforcement and blocking, which is done through parameters, not by populating ratings alone.

Collection letter journal

Why it fails: There is no such thing as a 'Collection letter journal' in Dynamics 365 Finance. Collection letters are generated through the collections process, not through a journal. Writing off a balance requires a dedicated write-off journal or a general journal. The collection letter journal is not a valid journal type and would not achieve the write-off.

General journal

Why it fails: This option is incorrect because while a general journal can be used to write off a customer balance, it requires manual entry of the customer account and offset account. It does not have a dedicated write-off functionality that automatically updates the customer balance and uses a designated write-off account. The write-off journal type is specifically designed for this purpose, making it more efficient and less error-prone.

Payment journal

Why it fails: A payment journal is used to record customer payments, not write-offs. Using a payment journal to write off a balance would incorrectly record it as a payment, which could affect customer payment history and reporting. The write-off journal is the correct journal type for removing uncollectible amounts from the customer balance.

Create a single billing schedule with a 24-month term and include the setup fee as a line item in month 1.

Why it fails: A single billing schedule with a line item for the setup fee would recognize the setup fee according to the revenue recognition method assigned to the schedule, which may defer it over 24 months. The requirement is immediate recognition for the setup fee, so mixing it into the recurring schedule does not achieve the desired revenue timing without additional revenue split configuration.

Create a billing schedule for the recurring fee and post the setup fee as a free-text invoice with immediate revenue.

Why it fails: Posting the setup fee as a free-text invoice bypasses the subscription billing module and its revenue recognition controls, and it may not integrate with the subscription's revenue schedule. While immediate revenue might occur, this approach lacks the structured tracking and reporting that subscription billing provides, making it an inferior and unsupported design for a subscription setup fee.

Use a single billing schedule with a revenue split that allocates the setup fee to a separate revenue account.

Why it fails: A revenue split changes the account distribution but does not alter the timing of revenue recognition. The setup fee would still be recognized according to the schedule's recognition method, likely over the term. To recognize immediately, a separate schedule or a different recognition method is needed, not just a different revenue account.

Set up a collection letter code for each escalation level and assign them to the customer's posting profile.

Why it fails: Collection letter codes are assigned to a collection letter sequence, not directly to a posting profile. The posting profile controls ledger accounts for transactions, not collection letter generation. Assigning codes to a posting profile would not trigger automatic letters based on overdue days. The sequence is the correct mechanism to define the order and timing of collection letters. This option misplaces the configuration.

Configure the Accounts receivable parameters to enable 'Collection letter' and set the 'Collection letter sequence' to 'Automatic'.

Why it fails: Enabling 'Collection letter' in Accounts receivable parameters and setting a default sequence is part of the setup, but it does not define the escalation levels. The actual escalation is defined by the collection letter sequence itself, which contains the individual letter codes and their day thresholds. Simply setting a default sequence does not create the escalating letters; the sequence must be configured with the appropriate codes and days. This option is incomplete.

Create a collection letter sequence and assign it to each customer's 'Collection letter' FastTab on the Customer form.

Why it fails: While assigning a collection letter sequence to a customer is necessary for the letters to be generated, it does not define the escalation. The escalation is defined by the sequence's letter codes and their day thresholds. Without configuring the sequence with multiple codes, assigning it to the customer would not produce escalating letters. The primary configuration is the sequence itself, not the customer assignment. This option focuses on the wrong step.

Create a billing schedule with two lines: one for the setup fee with a 'One-time' frequency and one for the monthly fee with a 'Monthly' frequency, and assign it to the subscription.

Why it fails: Billing schedules in subscription billing are assigned to items, not directly to subscriptions with multiple lines. A billing schedule defines the frequency for a single item. You cannot combine multiple frequencies in one billing schedule; each item must have its own schedule. Therefore, creating a billing schedule with two lines of different frequencies is not supported. The correct approach is to create separate items for each fee type.

Set up a subscription with a billing schedule of 'Monthly' and configure the setup fee as a 'Recurring' charge with a frequency of 'One-time'.

Why it fails: The term 'Recurring' charge with a frequency of 'One-time' is contradictory and not a standard configuration in subscription billing. Billing schedules define the frequency of charges; a one-time charge should be on an item with a 'One-time' billing schedule, not a recurring charge. This option misuses the concepts and would not produce the desired billing behavior. The system does not support a 'One-time' frequency within a recurring charge setup.

Create a single subscription billing item with a 'Monthly' billing schedule and add the setup fee as a one-time charge on the first invoice.

Why it fails: While you can add a one-time charge to the first invoice of a subscription, this approach does not use a separate billing schedule for the setup fee. It may be possible manually, but the requirement is to automate the billing of the setup fee immediately and the monthly fee on the first of each month. Using a single item with a monthly schedule would not automatically separate the one-time charge; it would require manual intervention or customization. The standard, automated approach is to use separate items with distinct billing schedules.

Create a billing schedule with a monthly frequency, and set up a price increase in the subscription billing parameters.

Why it fails: Subscription billing parameters control global settings, not per-schedule price increases. You cannot define a percentage increase there. Price escalation must be configured on the billing schedule itself, typically via a price escalation rule. This option would not apply the 5% annual increase correctly.

Create a billing schedule with a monthly frequency and define a charge schedule with a 5% increase annually.

Why it fails: Charge schedules are used for miscellaneous charges, not for adjusting the base subscription price. They cannot apply a percentage increase to the subscription price. While you could add a separate charge, it would not change the base price as required, and it would complicate reporting.

Set up a billing schedule with a monthly frequency and use a price adjustment in the item's sales price.

Why it fails: Price adjustments on the item's sales price are static and do not support periodic percentage increases. They are used for discounts or surcharges, not for scheduled escalations. This would not automatically increase the price every 12 months; it would require manual updates.

Modify the billing schedule to change the quantity for the remaining periods.

Why it fails: The billing schedule defines the timing of invoices but not the quantity of items. Quantity is set on the subscription line or via a change order. Modifying the schedule would not change the quantity on the invoice; it would only affect when invoices are generated.

Create a new subscription for the additional quantity and link it to the existing subscription.

Why it fails: Creating a new subscription would result in separate billing and reporting, and it would not immediately update the existing subscription's quantity. This approach is cumbersome and does not meet the requirement of a seamless mid-term change on the same subscription.

Cancel the subscription and create a new one with the updated quantity.

Why it fails: Canceling and recreating the subscription would lose history and require new setup. It would also disrupt billing continuity. This is not the recommended method for a simple quantity change, as subscription billing provides a dedicated function for this purpose.

Create a collection letter sequence and assign it to the customer's posting profile.

Why it fails: Collection letter sequences are used to generate collection letters for overdue customers. They do not automatically place customers on credit hold when a balance threshold is exceeded. Collection letters are part of the collections process, but they are not the mechanism for credit hold automation. This configuration would send reminders but would not enforce credit holds on new orders.

Configure credit card processing for the customer and set up payment terms to require prepayment.

Why it fails: Credit card processing and prepayment terms are payment methods, not credit hold mechanisms. They can reduce risk but do not automatically place a customer on hold based on overdue balances. The requirement is for automatic credit hold when a threshold is exceeded, which is handled by credit management rules, not by payment processing or terms.

Set up aging period definitions in Accounts receivable parameters and assign them to customer posting profiles.

Why it fails: Aging period definitions are used for aging reports and collections, not for credit hold automation. They do not control credit limits or hold rules. While aging periods are part of collections management, they do not enable the credit management feature or define credit thresholds. Therefore, this step alone will not fulfill the requirement to automatically place customers on credit hold.

Proration method

Why it fails: Proration methods calculate amounts for partial periods, such as when a subscription starts mid-cycle. They do not affect how multiple charges are grouped into one invoice. The scenario does not mention proration; it focuses on consolidating charges for a customer, which is handled by invoice grouping, not proration.

Charge setup

Why it fails: Charge setup defines the pricing and billing details for individual subscription charges, such as the amount and start date. It does not control invoice consolidation across multiple subscriptions. While charge setup is necessary for billing, the grouping of charges into a single invoice is managed by the invoice grouping setting, not by charge setup.

Billing cycle

Why it fails: Billing cycles define the frequency and timing of recurring invoices, but they do not determine whether charges from different subscriptions are combined. Even with a common billing cycle, charges might be invoiced separately unless invoice grouping is enabled. Billing cycles control when invoices are generated, not how charges are consolidated.

Use a billing schedule with a monthly frequency and set the Prorate option to No, then create separate billing schedule lines for the first and last periods with adjusted amounts.

Why it fails: Setting Prorate to No disables automatic proration. Creating separate lines with adjusted amounts is a manual workaround that does not leverage the system's proration logic. This approach is cumbersome and not scalable. The Prorate option is designed to handle partial periods automatically, so disabling it contradicts the requirement.

Set the Billing frequency to Daily and manually adjust the invoice amounts for the first and last periods.

Why it fails: Changing the billing frequency to Daily would generate daily invoices, which is not the requirement. Manually adjusting amounts is error-prone and not automated. The Prorate option exists specifically to handle partial periods automatically without changing the frequency. This approach would create unnecessary overhead and potential billing errors.

Configure a billing schedule with a monthly frequency and set the Invoice now option to Yes for all periods.

Why it fails: The Invoice now option controls when invoices are generated relative to the period start, not proration. It does not prorate amounts for partial periods. Setting it to Yes for all periods would simply generate invoices immediately for each period, but the first and last periods would still be billed at the full monthly amount unless proration is enabled.