Once all the data from the settlement report is moved as the individual settlement transaction records and summary record in NetSuite using the Amazon Settlement Report to NetSuite Add flow, the NetSuite Settlement Transaction to NetSuite Payment Add flow reads the individual settlement transaction records > TRANSACTION TYPE as Order from NetSuite and creates corresponding customer payments in NetSuite.
Once the Amazon Settlement Report to NetSuite Add flow has run successfully, the Integration app automatically executes this flow. When this flow is run, the integration app accesses the open invoice in NetSuite for every individual settlement transaction record associated with TRANSACTION TYPE > Order and attempts to create customer payments for these invoices. The flow identifies the sales orders (MFN), searches for the invoices, and creates customer payments for amounts that Amazon sends. For FBA, orders are directly imported as invoices, so payments are directly created.
Prerequisites: Billing should be in the form of invoices and payments and FBA orders should be imported as invoices. Turn on the NetSuite Order to NetSuite Invoice Add flow to create the invoices for orders imported in Amazon.
Notes
- Supported functionality
- Both MFN and FBA Orders
- Multi-domain/multi-account
- Unified accounts
- Non-Amazon orders
- Functionality not supported
Cash Sales
Example of the NetSuite Settlement Transaction to NetSuite Payment Add flow run
Let’s assume you have imported a settlement report with 34 successful individual transaction record as shown in the following image:
Out of these 34 transaction records, 11 records are of type TRANSACTION TYPE > Order. So when the NetSuite Settlement Transaction to NetSuite Payment Add flow is triggered, it selects only the 11 order pertaining transaction to be processed. The Dashboard page allows you to monitor the progress and success of the flow run.
The Dashboard page also informs you about any error that might occur during the flow run and allows you to fix the error and retry the flow run to successfully process the transaction that had caused an error to occur.
The following screen displays the Dashboard page where you can see all 11 transaction records have been successfully processed:
Once this flow has successfully run for all order transactions, the integration app automatically triggers the NetSuite Settlement Transaction to NetSuite Refund Add flow.
Criteria for payment transaction record selection during flow run
The Celigo AmazonIO Settlement Payment Transaction Search record in NetSuite controls which payment transaction records, among all the transaction records present in NetSuite, are selected by the flow to be processed. The following screen shot of Celigo AmazonIO Settlement Payment Transaction Search in NetSuite displays the criteria based on which the record is selected:
Impact of flow on transaction record in NetSuite
- Order transaction record before the flow run
The following screen displays the Transaction type: Order after the Amazon Settlement Report to NetSuite Add flow run. You can see that none of the fields except Status have any value in the Transaction Summary pane. At the start, the Status field will always be displayed as New. - Impact of this flow run on order transaction record
When you run the NetSuite Settlement Transaction to NetSuite Payment Add flow, it identifies the sales orders record to be processed based on the Celigo AmazonIO Settlement Payment Transaction Search save search. When it is a MFN order, the flow searches for the invoices associated with sales order and creates customer payments for amounts that Amazon sends. For FBA, orders are directly imported as invoices hence payments are directly created.
The following screenshot displays the order transaction record in which the values are populated in the Transaction Summary pane after the flow has run successfully:
Along with creating customer payments records, the integration app also links the customer payments record with the associated order transaction record and the settlement record.
Different statuses of order transaction record
After the invoices are attached and payment record is created for Transaction type: Order, Amazon payment amount is compared with the NetSuite payable invoice amount and Status: New is updated as one of the following statues:
- Applied
This status is updated as Applied for an order transaction record when total amount present in the invoice the NETSUITE TRANSACTION (TO APPLY) field is less or same as the amount present in the TRANSACTION AMOUNT field.
For example:
In the following transaction record, the amount in the TRANSACTION AMOUNT field is $35.74:
In the invoice for the NETSUITE TRANSACTION (TO APPLY) field, the total amount in the invoice is $35.74:
As amount mention in both fields is same, the status of the transaction record is updated as Applied. - Partially Applied
This status is updated as Partially Applied for an order transaction record when the amount present in the TRANSACTION AMOUNT field is more than the total amount present in the invoice the NETSUITE TRANSACTION (TO APPLY) field.
For example:
In the following transaction record, the amount in the TRANSACTION AMOUNT field is $461.04:
In the invoice for the NETSUITE TRANSACTION (TO APPLY) field, the total amount in the invoice is $430.80:
As when the amount present in the TRANSACTION AMOUNT field ($461.04) is more than the total amount present in the invoice the NETSUITE TRANSACTION (TO APPLY) field ($430.80), the status of the transaction record is updated as Partially Applied. - Unapplied
When the flow fails to process any transaction record due to any error, the status of the transaction record is updated as Unapplied. In this case, you can open the transaction record in NetSuite to know about the possible error in the ERROR CODE field and its details in the ERROR MESSAGE field.
You can avoid this by updating the externalid field (hidden field) which is a combination of marketplace and order ID. To find and edit the externalid field, add &xml=t in the NS URL.
Comments
Please sign in to leave a comment.