Payment Entity
This topic provides reference information about the standard filtering and field mapping used for the Payment entity during the synchronization between MYOB Acumatica and BigCommerce.
Payment Filtering
Filters are applied during the import of payments to MYOB Acumatica. A payment is skipped if any of the following is true:
- I[1]Just to be clear, this is a status that exists only in BigCommerce, right? And it is a status of the payment document as a whole, right (as opposed to a transaction status or processing status)? Mostly I did not ask that we tell the reader where statuses are (which area or tab on which form or page) because at least in Acumatica ERP they're really obvious--always in the same general part of the entry form. But if this is not a document status, we need to get into detail about where it is on the BigCommerce page, and IF applicable, what element in Acumatica ERP it equates to (again, because it is not the overall document status).2020/05/1222:23:26-04:00ts status is Error—for example, if the credit card payment transaction was not successful.
- The manual payment method used for purchase is not supported.
- The sales order related to the payment has not been synchronized.
If the mapping of the store payment method has not been configured or is inactive on the Payments tab of the BigCommerce Stores (BC201000) form, the system creates a synchronization record for the payment on the Sync History (BC301000) form and assigns it the Filtered status.
Payment Import Mapping
The following table shows the mapping of BigCommerce fields to MYOB Acumatica fields that is used during the import of payment data from BigCommerce.
| Source Fields (BigCommerce) | Target Fields (MYOB Acumatica) | |||
|---|---|---|---|---|
| Field Name | Page Object | Field Name | Form Object | Notes |
| Payments and Applications (AR302000) form | ||||
| Type | Summary area | Default: Prepayment | ||
| Customer | Summary area | The customer ID is the same as the customer ID on the related sales order. | ||
| Location | Summary area | The location is the same as the location on the related order. | ||
| Currency | Edit an Order page > Transactional Currency section | Currency | Summary area | This box is shown only if the Multicurrency Accounting feature is enabled on the Enable/Disable Features (CS100000) form. |
|
Date |
Payment transaction | Application Date | Summary area | The payment transaction date is used. |
|
Amount |
Payment transaction | Payment Amount | Summary area | The payment transaction amount is used. |
| GatewayTransactionId or ReferenceTransactionId | Payment transaction | Payment Ref. | Summary area | If GatewayTransactionId is empty, ReferenceTransactionId is used. |
| Payment Method | Payment transaction | Payment Method | Summary area | The payment method that is mapped to the store's payment method on the Payments tab of the BigCommerce Stores form. |
| Cash Account | Summary area | The cash account corresponds to the payment method that is mapped to the store's payment methods used for the purchase and the transaction currency of the sales order. | ||
| Description | Summary area | Default: <store name> | Payment Method: <the payment method used for purchase> | Order: <order number> | Payment ID: <payment number> | ||
| Branch | Financial tab > Link to GL section | The branch specified in the General section on the Orders tab of the BigCommerce Stores form. | ||
| Status | Summary area | The status depends on the state of the Release Payments and Refunds check box in the row of the payment method in the table on the Payments tab of the BigCommerce Stores form. If the check box is selected, the status is Open (meaning that the payment is released). If the check box is cleared, the status is Balanced (indicating that the payment is not released). | ||