Testing Amazon Settlement Sync with NetSuite Connector
Test the Amazon settlement sync in NetSuite Connector to ensure accurate transaction importing and error management.
TL;DR Opening
To verify the Amazon settlement sync functionality within NetSuite Connector, follow a structured testing procedure ensuring proper transaction integration and efficient error resolution. This guide details each step to successfully test your settlement reports.
Overview of Amazon Settlement Reports
Amazon typically generates settlement reports biweekly, detailing transactions alongside any associated fees and credits. Before testing, ensure you have a relevant settlement report that should have been previously synced with NetSuite.
Preparing for Testing
- Settlement Report Selection: Choose a report that corresponds with orders already synced through the NetSuite Connector. Orders not previously synced will trigger errors.
- Report Generation: If you lack reports, request Amazon to generate one for you.
- Report ID Retrieval: Obtain the report ID required for testing before proceeding.
Testing Procedure for Settlement Sync
Follow these steps to initiate your testing:
-
Log into FarApp: Access app.farapp.com and log in with your credentials.
-
Select Connector: Choose the Amazon connector and select the relevant account.
-
Navigate to Data Flows: Go to the Data Flows section and select Settlements.
-
Retrieve Report: Click on Retrieve. This opens the Retrieve Settlement Report window.
-
Enter Report ID: In the Settlement Report ID field, input your obtained report ID.
-
Execute Retrieval: Click Retrieve to pull the settlement report from Amazon. This process may take a few minutes, and you will receive a success confirmation once completed.
-
Close Window: After retrieval, close the window.
-
Post the Report: Locate the imported report, click the Action menu (pencil icon), and select Post. The syncing will occur in the background; larger reports may take longer.
- Note the status of the reporting; If it shows Complete, you can proceed. Otherwise, errors must be addressed.
-
Error Management: If errors are present in the report status:
- Cancel Posting: This will prevent syncing the settlement data with NetSuite for those postings.
- Fix Errors: Address each error according to the provided information.
-
Repeat Posting as Necessary: Re-attempt posting from step 8 until the status changes to Complete.
Activating Settlement Sync
Once the settlement report displays a Complete status, activation of the settlement sync can proceed smoothly.
Key Takeaways
- Select existing settlement reports previously synced to avoid errors when testing.
- Follow the structured procedure for complete and accurate data retrieval and posting.
- Review and resolve any errors with specific actions as required before re-posting.
Source: This article is based on Oracle's official NetSuite documentation.
Frequently Asked Questions (4)
How can I select the correct report for testing Amazon Settlement Sync in NetSuite Connector?
What should I do if I encounter errors while posting a settlement report?
Do I need any specific credentials or access for testing Amazon Settlement Sync in NetSuite?
What happens if a settlement report is not previously synced when testing in NetSuite Connector?
Was this article helpful?
More in Integration
- Square Connector Integration in NetSuite 2026.1
Discover the Square Connector for seamless integration with NetSuite 2026.1, synchronizing transactions, orders, and inventory effortlessly.
- SuiteTalk Web Services
Documentation article about SuiteTalk Web Services
- SuiteTalk Web Services Enhancements in NetSuite
Explore the latest enhancements to SuiteTalk Web Services, improving integration and API functionalities in NetSuite.
- MCP Standard Tools for Natural Language Queries in NetSuite
Explore MCP Standard Tools for natural language queries, report access, and record management in NetSuite.
Advertising
Reach Integration Professionals
Put your product in front of NetSuite experts who work with Integration every day.
Sponsor This Category