{"section":"known-issues","requestedLocale":"en","requestedSlug":"input-invoice-is-not-triggering-the-refund-process-at-the-gateway","locale":"en","slug":"input-invoice-is-not-triggering-the-refund-process-at-the-gateway","path":"docs/en/known-issues/Order Management/input-invoice-is-not-triggering-the-refund-process-at-the-gateway.md","branch":"main","content":"## Summary\n\n\nIt was identified that the invoice API (invoices and returns) does not allow specifying the different selling prices that a SKU may have in the same way as specified in the order. This means that the merchant does not need to explicitly \"duplicate\" the same SKU in invoices/returns to represent all these selling prices.\n\nExample:\nSKU-1 with quantity 2, with a total value of $101.\n\nTo solve the rounding problem, 2 different selling prices are specified: 1 of $51 and another of $50.\n\nWhat happens is that when the account is going to invoice the order, SKU-1 is duplicated to inform the values contained in the sellingPrice.\n\nSOS validates duplicate items and if they are identified, it will not be possible to make a \"refund\".\n\n\n#### Simulation\n\n\nIt is possible to simulate this scenario by creating an order with one item and a quantity greater than two, and having the sellingPrice values rounded so that they are different between items, for example:\nOrder with two units of SKU-10, with a total value of $101, and in the sellingPrice, we have 1 item with a value of $51 and the other with a value of $50.\nWhen entering an invoice, the account duplicates the item, informing the sellingprice values.\nWhen the invoice is input, it makes the same duplication.\nAt this time, the SOS will be checked for the duplicated items and the refund will not be requested!\n\n\n#### Workaround\n\n\nInsert only one SKU on the invoice, specifying the quantity and total value."}