Refunds are actual funds, money that go back to the customer. There are two modes of refund: External, as in manual, e.g. a refund check, Electronic, issued through a payment gateway.
The Payment Scheduler is a built-in functionality and it works similarly to the Invoice Scheduler, except that it doesn't create invoices, obviously, but creates payments.
While the Payment record is still in Draft status, it's not eligible for Allocations. When its status changes to Posted, the Allocations button becomes available in the top right corner on the Payment record.
When a customer sends in a payment for an invoice, we want to be able to record that in Salesforce and be able to allocate it against the correct invoices. Salesforce Billing tracks and allocates payments using several objects.
If you contract from Opportunity, the Terminated Date on the original Order Product doesn't get populated. This happens only when you contract from Order.
There are different scenarios when a product or a group of products needs to be hidden (disabled) from Product Selection/Configuration. Let's take a look at some examples.
What if you need to only disable reconfiguration on certain types of quotes (e.g. Renewals) for all bundles while it should be possible to reconfigure them on new quotes or amendment quotes?
So you need to automatically add a product if a customer hasn't got any active subscriptions belonging to a specific Product Family (e.g., Software). You can achieve this with the help of a summary variable and a product rule.
When a product reaches End-of-Life, there are multiple scenarios to consider. Will a completely new Product replace the EOL Product? Or should the Product be available to customers who already purchased it (on amendments and renewals) while unavailable for new sales?
