Posting Returns To Teamwork

outline once a return is closed in refundid, it is written back into teamwork commerce as a receipt against the original sale the receipt is negative negative quantities, negative amounts and a negative tender line so teamwork treats it as a return rather than a new sale when it happens the receipt is created when the return reaches a closed state in refundid in other words once your team has processed it, or once it has been auto approved nothing is written to teamwork at lodgement, so a return that is later declined or cancelled never reaches your teamwork environment what gets created one receipt per return, containing the original receipt reference the receipt is linked back to the receipt the item was originally sold on, so teamwork can tie the return to the sale the location returns are booked into the location you nominate during setup usually your distribution centre or a returns holding location the customer identified by the email on the original order one line per returned item , with a negative quantity and a negative line total item matching uses the sku first, then the barcode tax , pro rated where only part of a line is returned the discount that applied to the returned units , pro rated per unit and written to a custom field on both the line and the receipt header, so discounted returns can be reported on a tender line for the refunded value, recorded against the dedicated refundid payment method configured in your teamwork environment the web order number is carried as the transaction reference so the return can be traced back a memo naming the refundid rma reference and return id returns spanning multiple original receipts if the items in a single return were originally sold across more than one receipt which happens on split shipments and consolidated orders refundid creates one teamwork receipt per original receipt, each containing only the lines that belong to it this keeps every returned line correctly attributed rather than forcing them onto one receipt value mismatches the amount refundid refunds isn't always the same as the value teamwork holds against the line fees, deductions, partial approvals and price changes can all cause a difference refundid calculates that difference and writes it to a custom field on the line, and the total for the receipt to a custom field on the header your finance team can then report on any return where the refunded value differs from the value teamwork expected, instead of having to reconcile line by line identifying refundid receipts every receipt is stamped with refundid as the source and carries a unique reference, so refundid returns are easy to filter in teamwork and a return can never be posted twice under the same reference