Docs
You are viewing:
Product Catalog 1.0
Scenario: You may encounter an error such as "NetSuite request failed (Invalid revenue recognition rule reference key xxx) at the plan item or addon item level.
Resolution: Follow these steps to resolve this error,
Scenario: If you encounter an error during the synchronization of an invoice to a customer, specifically receiving the message "NetSuite request failed (Invalid currency reference key x for entity xxx)."
Resolution: These steps will help you identify and address the issue related to an invalid currency reference key during the synchronization process. Envision that you are in the process of syncing an invoice denominated in EUR currency.
Scenario: If you receive an error message prompting, "Please enter the value(s) for Refund Method," follow these steps for resolution.
Resolution: Follow these steps, to resolve the issue related to the missing refund method value in your transaction.
Scenario:
You can experience a transaction sync error if your invoices have old invoice dates or the accounting books are closed in Netsuite to update the dates.
Resolution: To resolve this error follow the below steps:
Scenario: Invalid item reference key XXX for subsidiary Y Resolution : Follow these steps if you encounter an error message in Netsuite when the item reference linked to an invoice is either invalid or deleted.
Scenario You may encounter this error for invoices when some invoice line item products post directly to the item revenue account while others post to the deferred revenue account. To resolve this issue: Resolution Step 1: Identify Products:
Review the invoice line items to identify which products are causing the error.
Step 2: Verify Product Settings:
Navigate to each product in NetSuite, go to Lists > Accounting > Items.
Check the Direct Revenue Posting checkbox for each item. If checked, then the item is posted directly to the revenue account.
Learn more about it here.
Step 3: Ensure Consistency:
Ensure that all items associated with the invoice are posted to the same type of revenue account— direct or deferred. Mixing these revenue account types in a single transaction will trigger errors.
You can resolve the mixed revenue posting error by ensuring consistency in revenue posting settings for all invoice items.
Offline payments are integral to the synchronization process across various platforms. Following best practices ensures a seamless payment application and synchronization experience.
Offline payments are applied during the auto/manual sync process, where all payments made from the last synchronization to the current one are gathered and processed. This synchronization is pivotal for maintaining accurate and up-to-date payment records across different systems.
Single Platform Application: It is highly advisable to apply offline payments in a single platform during synchronization. Simultaneous application in both systems may result in synchronization errors or incomplete payment applications.
Sequential Application: Applying offline payments sequentially ensures a systematic and error-free synchronization. Avoid parallel applications across different platforms to minimize conflicts during the sync process.
Sync Frequency: Regular auto or manual sync should be conducted to capture all payments since the last synchronization. Frequent synchronization ensures consistency between platforms and reduces the likelihood of discrepancies.
Show more
Was this article helpful?