We are using the Multibook feature in NetSuite, and I have a vendor bill where we use an item that can impact either an expense account or a prepaid expense account, depending on whether we specify a start and end date on the transaction. In the primary book, when no start or end date is entered, the correct expense account is impacted, as expected. However, in the secondary book, for some reason, an amortization schedule is generated, and we’re unsure why this happens.

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the issue you're experiencing with the Multibook feature in NetSuite, where an amortization schedule is generated in the secondary book even when no start or end date is entered, could be due to the way the secondary book is set up. In NetSuite, vendor bills and vendor credits include a button labeled Update Amortization. This button is available when you view the saved transaction record. Clicking it opens the Update Amortization page, where you can change the amortization schedule, its start and end dates, and check or clear the Residual box for secondary accounting books. This is the only way to modify the schedules in secondary books. However, it's important to note that the premise of the secondary book is based on the modification of item settings. Therefore, if you're using items, you can set a template for the secondary book. If you're just booking expenses on a vendor bill, you might need to manually generate book-specific Journal Entries (JEs) based on the amortization template and dates filled in on the bill, and then link the JEs back to the original Bill. This way, you have references all on the originating transaction. As for creating an amortization schedule from an Expense Report, it is possible. Each expense account you want to use for amortization needs to be set up with the prepaid account at the Chart of Accounts (COA) Account setting. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******