Refunds generate payment transactions by default

Refunding line items in bulk now creates a transaction as well. When you import Refund Line rows, the app generates the matching refund transaction for you, so a refund import needs fewer columns and the order’s payment status reflects the refund.

What’s New

#

• Refund: Generate Transaction - refund imports generate the refund’s payment transaction by default. Set this column to FALSE to record a refund without returning money (see Refund: Generate Transaction).
• Suggested amount - the generated transaction refunds the unit price times the refunded quantity plus the tax on those units, using the gateway of the original payment.
• Explicit transactions win - a Transaction row that shares the Refund: ID is used as-is, so files that state their own refund amount work unchanged.

Improvements

#

• Clear result messages - the import result notes each refund whose transaction was generated (ORD040) and warns when no transaction could be generated, for example on an unpaid order (ORD041) (see error codes).
• Refund guide - the line-item refund guide covers the default, the FALSE option, and when to use a Transaction row instead.