How Refunds Sync

Every Shopify refund on a synced order creates a matching return sales order in Acumatica.

What happens in Acumatica

Each Shopify refund creates a return sales order in Acumatica. InSyncer does not post the credit memo directly — the credit memo comes from processing that return order in Acumatica, the same as any other return.

Document numbering

The return order number derives from the parent sales order, with a prefix:

Refund type	Prefix	Example
Full refund	R	R1039
Partial refund	PR	PR1039

A partial refund against SO1039 becomes PR1039. Prefixes are configurable if R and PR conflict with your own numbering.

Confirming a refund reached Acumatica

Check the order tag

When InSyncer creates the return order successfully, it writes a tag back onto the Shopify order: AcumaticaRefundOrderNbr: PR1039. The tag is only written once the document exists in Acumatica, so it is the reliable way to confirm a refund has gone through. No tag means no document yet.

Timing

InSyncer checks Shopify for new refunds every 15 minutes, but it only creates the Acumatica document once the refund has completed at the payment gateway, not when it is first issued in Shopify. Shopify commonly holds a card refund as pending for around 24 hours before the gateway confirms it.

Nothing appears immediately

A refund not showing in Acumatica within minutes of being issued is expected, not a fault. InSyncer waits for gateway confirmation deliberately, to avoid creating a credit against a refund that later fails.

Pushing pending refunds

An optional setting, Push Pending Refunds, creates the Acumatica document as soon as Shopify records the refund, while it is still pending at the gateway. This removes the wait, but it means a document can exist in Acumatica for a refund that later fails or is reversed at the gateway. Turn it on only if faster visibility matters more than that risk.

This setting is available in InSyncer for Acumatica. It is not currently available in InSyncer for MYOB Acumatica.