You must update the process according to your Coupa and Netsuite service configurations as there are many possible limitations based on different service business rules. You can find some limitations in this topic that have been defined for the objects synchronized in the recipe process.
Consider the following rules and guidelines when working with the Procure to Pay with Coupa and Netsuite recipe:
•The Subsidiary field for both the vendor and items must be identical. This enforces a restriction on the currency used. The currency must be the same as the currency specified in the Subsidiary settings.
•Discounts and taxes are not synchronized from Coupa because these fields are configured separately for the instance and are applied based on the settings within NetSuite.
•When creating a purchase order, the process passes the exchange rate. However, you must check if the NetSuite settings allow you to modify this value.
•The process creates one purchase order for each vendor but the purchase order can contain many items.
•Coupa sends different webhooks for different suppliers. If the Coupa purchase order contains products from different suppliers, the process creates a different purchase order in NetSuite but the custom field Coupa ID remains the same.
•If several processes are triggered simultaneously for synchronization, for example, several opportunities for different suppliers, the process might fail because of the concurrency limitation in Netsuite.