Corrections and customer documents
Choose the right action without duplicating accepted documents.
Demonstration recorded in a development store using Hacienda sandbox.
Transcript
Start in the order’s TicoSync block. Read the main document and any credit notes separately. An accepted invoice does not mean every credit note is accepted. Identify whether you need to correct data, retry a failed document, or simply send existing files again. For a rejection, read Hacienda’s specific explanation. Correct the issuer, customer or product data that caused it. For example, an issuer location mismatch belongs in the company configuration. Once corrected, use Reprocess order when available. Repeating the same unchanged submission will not repair the underlying data.
If an accepted invoice’s customer needs another copy, use Resend customer documents. This sends the stored documents; it is not a request to create another invoice. Confirm the recipient first. Available files and email behavior depend on the document type. If a customer asks for an invoice after an accepted ticket, add the required billing identification first. Use Convert TE to FE when the action is eligible. The recovery flow credits the ticket before issuing the replacement invoice. Verify the resulting documents instead of creating an unrelated duplicate order.
Return to the order after processing and check the new result. Analytics helps find orders needing attention, but the order shows the specific document and files. If a document remains rejected, keep its consecutive number and rejection message for support. Do not manually force an accepted tag.