{"section":"known-issues","requestedLocale":"en","requestedSlug":"space-in-invoicenumber-causes-failure-in-postpurchase-flow","locale":"en","slug":"space-in-invoicenumber-causes-failure-in-postpurchase-flow","path":"docs/en/known-issues/Order Management/space-in-invoicenumber-causes-failure-in-postpurchase-flow.md","branch":"main","content":"## Summary\n\nCurrently, the SNO (Shipping Notification Order) accepts receiving an invoice number with a \"space\" (special character) at the end, for example: \"123456 \", but when receiving the invoice number in this way some flows carried out post-purchase such as update tracking, giftcard system that use this data fail because the system cannot use the data correctly.\n\n## Simulation\n\n1- Invoice an order, inserting the following example invoice number: \"**123456**\"; (space at the end of the number)\n2- Try to insert a tracking update, according to the Update order tracking status API: https://developers.vtex.com/vtex-rest-api/reference/updatetrackingstatus\n2.1- Informing the invoice number **without** the \"space\", for example: \"**123456**\", we will have the following error: \"message\": \"**Invoice Not Found**\"\n2.2- Informing the invoice number **with** the \"space\", for example: \"123456 \" (space at the end of the number), we will have the following error: \"**500 Internal Server Error**\"\n\n## Workaround\n\nFor these cases, the workaround would be not to use the \"space\" at the end of the invoice number."}