NetSuite Syncing Errors

Please see below common syncing issues with Bills and Payments to NetSuite from MakersHub.

Error: Failed to create vendorbill: Bad Request | Details: Concurrent request limit exceeded. Request blocked. Verify your concurrency limits at Setup > Integration > Integration Management > Integration Governance.

Solution: This error occurs because of a data exchange limit on your NetSuite account. To raise it, go to Setup > Integration > Integration Management > Integration Governance and increase the concurrency limit to the maximum your account allows.

Error: Failed to create vendor: Bad Request | Details: Error while accessing a resource. There is already a vendor using that entity name. All vendors must have a unique entity name. Go back, change the entity name and resubmit.

Solution: This error means a vendor with that name already exists in NetSuite. Check your account to confirm the vendor isn't already there before creating a new one.

Error: Failed to create vendorbill: Bad Request | Details: Error while accessing a resource. This record already exists.

Solution: This means an invoice number already exists in NetSuite for the same vendor. Check your list of bills in NetSuite to see if this is a duplicate. Note: MakersHub will flag duplicates within our system, but only for bills it has already processed.

Error: Failed to create vendorbill: Bad Request | Details: Error while accessing a resource. Invalid combination of entity and subsidiary.

Solution: The vendor isn't listed under this subsidiary. Check the vendor record to confirm the subsidiary is listed for this vendor.