Explanation

A Posted invoice is considered a legally finalized financial record and cannot be directly modified or deleted. The recommended method is to use Cancel and Rebill, which automatically generates a credit note to offset the original invoice and then resets the related Order Products so a corrected invoice can be created and posted.

✅ Correct Option: A. Cancel and rebill, correct the order, create and post a new invoice.
The "Cancel and Rebill" button on a posted invoice initiates a process to automatically Credit the original invoice amount. Once the original invoice is offset, the admin must then correct the error on the source Order or Order Products before triggering a new invoice run to create and post a new, corrected invoice.

❌ Incorrect Option: B. Change the status from Posted to draft on the invoice, correct the invoicing error and repost it
Posted invoices are locked and immutable financial records, preventing direct status changes or edits to maintain data integrity and audit compliance. Any action attempting to manually revert the status to 'Draft' will either fail due to system validation or violate accounting standards.

❌ Incorrect Option: C. Delete the invoice record, correct the order, create and Post a new invoice
Deleting a Posted invoice is a severe violation of financial audit and compliance rules in almost every jurisdiction. Salesforce Billing prevents the deletion of Posted invoices to protect the financial integrity of the system and maintain an accurate ledger.

❌ Incorrect Option: D. Credit the invoice, correct the order, create and post a new invoice
The Credit button is typically used when the intent is only to write off the invoice amount, not to rebill the product. While Cancel and Rebill uses a credit note, using the manual Credit button does not reset the Order Product for rebilling, leading to a complex multi-step manual correction.

📝 Summary
Correcting a Posted invoice error requires the Cancel and Rebill process in Salesforce Billing. This action offsets the original erroneous invoice by generating a credit note, after which the underlying Order is corrected. Finally, a new invoice run uses the corrected Order to produce and post the accurate invoice, ensuring a clear and auditable record of the change.

🔗 Reference
Salesforce Help Documentation on Cancel and Rebill an Invoice confirms this process: Cancel and Rebill is the systematic way to reverse a posted invoice, correct the source data (Order/Order Product), and re-invoice the customer correctly.

Explanation

Revenue Cloud (especially CPQ) relies on high-speed, controlled calculations. Formula fields, especially those spanning multiple objects, are prone to hitting Salesforce's governor limits, are computationally expensive due to real-time calculation, and, crucially, their values are not always available to CPQ's calculation service when needed, leading to inaccurate pricing or errors.

✅ Correct Option: C. They can easily exceed limits if not carefully designed and tested
Salesforce imposes a limit on the number of unique relationship traversals (spanning relationships) that can be referenced across all formula fields, validation rules, and workflow rules on a single object (the limit is typically 15). Overusing complex cross-object formulas can quickly exhaust this critical platform limit.

✅ Correct Option: D. Formulas field data is not always available during CPQ quote calculation
Formula fields are calculated dynamically upon record view or request, meaning their data might not be reliably available or properly updated during the CPQ native calculation service (e.g., when the Calculate button is pressed). This can lead to pricing or discount logic errors if CPQ relies on the formula output.

✅ Correct Option: E. They are computationally expensive
Cross-object formulas require the system to traverse relationships and perform real-time calculation logic every time the record is accessed or referenced, making them computationally expensive. Excessive use can significantly impact application performance, leading to slower page load times and sluggish CPQ configuration/save actions.

❌ Incorrect Option: A. Formula fields have unlimited access to objects many relationships away which makes it vulnerable to data changes
This is incorrect because formula fields have a strict limit on the number of relationships they can cross (typically 10 levels deep). The vulnerability to data changes is a generic risk, but the core risk is hitting the relationship span limit before the design is complete.

❌ Incorrect Option: B. Formula field are editable after the calculation completes the Sales user or process automation can overwrite its value
This is incorrect. Formula fields are read-only by definition and cannot be edited by sales users or directly overwritten by process automation (Flow, Workflow Rule field updates). They are dynamically calculated based on the source fields, which protects their value from manual override.

📝 Summary
The primary risks of over-relying on cross-object formula fields in a Revenue Cloud project center on system constraints and performance. These formulas can quickly exceed platform limits on relationship spanning, are computationally expensive due to dynamic calculation, and their values may not be consistently available to the CPQ engine during critical pricing runs, potentially causing data inconsistency and performance degradation.

🔗 Reference
Salesforce Help Documentation on Formula Field Limits and Restrictions confirms the limits on spanning relationships and the general best practice to limit complex formulas for performance reasons.

Explanation:

To securely store a credit card for future payments, the recommended process is:
Navigate to the Account record (where the customer is stored).
Go to the Payment Method related list.
Click “New Payment Method – Credit Card”.
Enter the card details and tokenize the card using the integrated payment gateway (e.g., Stripe, Authorize.net).
The tokenized card is stored securely and can be reused for future invoices or subscriptions.

This method ensures:
PCI compliance via tokenization (Salesforce never stores raw card data)
Reusability for recurring billing or one-time payments
Integration with Salesforce Billing’s payment processing engine

❌ Why the other options are incorrect:

A. Enter details + click Tokenize
Tokenization is part of the flow, but this oversimplifies the process and skips the UI path via Account.

B. Payment Credit Cards related
list This list is not standard in Salesforce Billing; may refer to legacy or custom objects.

C. Use platform encryption
While encryption is important, tokenization is the required method for PCI compliance—not just encryption.

🔗 Reference:
Salesforce Billing: Payment Methods Overview
Salesforce Revenue Cloud Implementation Guide

Explanation

When an invoice is moved from Draft to Posted status in Revenue Cloud (Billing), the system must finalize the financial record and update the related source and line items to reflect the billing event. This process locks the invoice for modification and prepares it for payment and downstream financial processes like revenue recognition. It is a critical step in the quote-to-cash process, ensuring financial integrity and accurate record-keeping.

Correct Options

A. Order Product ✅
The Order Product is the source record for billing, and it must be updated during the posting process. The Next Billing Date field on the Order Product is advanced to the start date of the next billing period to ensure the product is correctly picked up for subsequent invoices. This marks the current billing cycle as complete on the source line.

C. Invoice Line ✅
Every Invoice Line is automatically updated to have its Status field set to Posted. This status change is fundamental because it locks the specific line item, preventing further changes and making it a finalized record against which payments can be allocated and revenue schedules can be created for reporting.

E. Invoice ✅
The primary object updated is the Invoice itself, where the Status field changes from 'Draft' or 'Pending' to 'Posted'. Additionally, the system updates the Posted Date field, effectively locking the entire invoice record and making it available for collection, payment processing, and integration with external financial systems.

Incorrect Options

B. Quote ❌
The Quote object is part of the CPQ stage, which precedes Order creation and, ultimately, Invoicing. Once an Order is generated, the Quote and its lines are no longer directly updated by the Billing engine when an invoice is posted. The Invoice-to-Order relationship is the one that matters for financial processing updates.

D. Quote Line ❌
Similar to the Quote object, the Quote Line is part of the initial sales configuration process. Once the Quote Line data is transferred to the Order Product upon contract or order creation, it is the Order Product record that is maintained and updated by the Billing system, not the original Quote Line.

Summary
Posting an Invoice in Salesforce Revenue Cloud (Billing) is the finalization step before payment collection. This action immediately updates the Invoice record's status to 'Posted' and stamps the Posted Date. Crucially, every related Invoice Line is also marked as 'Posted', and the source Order Product is updated by advancing its 'Next Billing Date' to trigger the subsequent billing cycle.

Reference:
Official Salesforce Help documentation on the Posting Invoices

Explanation:

A. Multiple automation types on a single object:
This can lead to race conditions, unpredictable behavior, and inefficient processing. When different automation tools (like triggers, workflows, and multiple flows) are triggered by the same event on the same object, their execution order isn't always guaranteed, making debugging difficult and increasing transaction times.

B. External API calls within the pricing sequence:
In Salesforce CPQ and Billing, pricing calculations need to be as fast as possible to provide a good user experience. Making synchronous API calls to external systems during this process introduces latency and potential points of failure, which can significantly slow down the user interface and overall system performance. For this reason, it's a best practice to keep the pricing sequence self-contained and free of external dependencies.

C. Extensive use of quote line custom fields:
While custom fields are necessary for specific business logic, having an excessive number of them on high-volume objects like Quote Line can impact performance. It increases the data load and processing time for a quote, particularly during quote generation, recalculation, and document creation. Instead of relying on a large number of custom fields, metadata-driven approaches (like Revenue Cloud Advanced's dynamic attributes) are more performant and scalable.

❌ Why other options are incorrect

D. Routine generation of quotes having 200 quote lines:
While large quotes can impact performance, especially if poorly configured, it is a common business scenario that Salesforce CPQ is built to handle. With best practices in place, generating quotes with 200 lines should be manageable and doesn't represent a negative design pattern in itself, but rather a factor to be managed through careful design.

E. Routine generation of invoices having 200 invoice lines:
Similar to large quotes, generating invoices with many lines is a standard function of Salesforce Billing. The system is designed to handle this through batch processing and asynchronous jobs. This is a large-volume process that should be handled efficiently with proper design, not an inherently negative design example.