Hello All, I need your guidance on an issue related to the Secondary Accounting Book exchange rates in NetSuite. If we update the Secondary Book exchange rates now, will it update the exchange rates on the existing Sales Orders? This issue appears to have affected all Sales Orders, as the Revenue Team had not updated the applicable exchange rates since November 2024. As a result, the existing Sales Orders continued using the old rates, which are incorrect. Additionally, when we edit an existing Sales Order, there does not appear to be an option to update the exchange rate specifically for the Secondary Book. Currently, we are seeing a difference between the books: • Primary Book: Correct value in INR • Secondary Book: USD value is showing a difference due to the incorrect exchange rates We need to determine the safest way to correct the Secondary Book without impacting the already-correct Primary Book. One possible option is to create a book-specific Journal Entry to adjust the difference. However, the concern is that such a JE may not flow to the Project level, which could result in a mismatch in project-wise revenue reporting. Could you please advise on the recommended approach to: 1. Correct the historical Secondary Book exchange-rate impact. 2. Ensure the correction is reflected at the Project/Revenue Plan level. 3. Avoid impacting the correct Primary Book values. 4. Determine whether a book-specific JE is appropriate, or whether there is a better way to correct the Revenue Plans/Revenue Recognition. Thanks.

Hi! I can help with this. Based on your description, updating the Secondary Accounting Book exchange rates now typically won't retroactively update existing Sales Orders or Revenue Plans that were created using the old rates. The best approach depends on how Multi-Book Accounting and Revenue Recognition are configured. I've worked with NetSuite Multi-Book Accounting and can help evaluate the safest correction method—whether that's book-specific journal entries, Revenue Plan adjustments, or another approach that preserves the Primary Book while ensuring accurate project-level reporting. Feel free to reach out if you'd like to review the setup in detail. @Amol Bodke