# Correct an e-invoice without creating duplicate tax or accounting records Before reversing an invoice, establish what happened to the legal document. A buyer dispute, a failed validation, an issuer cancellation and a credit note require different evidence. Changing the ERP balance alone can leave a valid invoice outstanding elsewhere. **Diagram:** Keep the original and trace each permitted correction. Recommended document-history control. Permitted cancellation, correction and replacement actions are jurisdiction-specific. Use the [invoice correction case worksheet](#template) to record one commercial problem and every related document. The procedure below recommends operating controls. Your country rules determine the permitted adjustment, authorized party, time limit and tax period. Assign a billing or AP case owner to coordinate the correction. The tax owner approves the legal mechanism and period. The integration owner confirms external results. The controller approves the accounting effect, and treasury handles any refund or payment allocation. ## Establish the state before choosing the action Retrieve the original payload, legal number, external identifier, issue and validation times, delivery evidence and accounting entries. Include any customer payment and earlier adjustments. Preserve the document as issued. Ask which statement the evidence supports: - The document has not been issued and remains a draft. - An external validation rejected the submission. - The external system validated the document, but the buyer disputes it. - The issuer completed a recognized cancellation. - An adjusting document already changes some or all of its value. Do not assume external rejection means the commercial debt or tax obligation vanished. The consequences depend on the regime. Ask the tax owner whether to repair a technical submission, issue a legal adjustment or do both. If the result is unknown after a timeout, preserve the attempt and establish its state before creating another invoice. A second accepted document creates a duplicate problem even when the first attempt looked unsuccessful. ## Separate a buyer request from a completed cancellation Record who sent the response and what it legally changes. A buyer can dispute a charge while the invoice remains valid. Notify the issuer of the reason and keep the case open until the required document action succeeds. Malaysia's MyInvois rejection API makes this distinction explicit. The buyer requests cancellation, and the document remains valid until the seller cancels it. The API describes a rejection window of 72 hours from validation. [LHDN, reject document API](https://sdk.myinvois.hasil.gov.my/einvoicingapi/04-reject-document/). Use precise internal labels such as "cancellation requested" and "cancellation confirmed" if those match the scheme. Keep a commercial dispute separate from a technical rejection. Avoid a single "rejected" label that can mean either. When a customer sends a free-text email, record the request and contact the authorized operator. An email may be useful evidence of the dispute, but it does not prove that an authority or network changed the document state. ## Check the local mechanism and time limit Record the current source, relevant document type, permitted actor and action deadline in the case. Calculate from the legally specified event. Store its time zone and the timestamp you used. For MyInvois, the cancellation API states a 72-hour window from when the document was marked valid. After that, the appropriate credit, debit or refund note adjusts the document. The API also describes document-state restrictions and special treatment of the acting party for self-billed documents. [LHDN, cancel document API](https://sdk.myinvois.hasil.gov.my/einvoicingapi/03-cancel-document/). Consider this hypothetical Malaysian timing example. All recorded times are expressed in UTC for a consistent calculation. A document becomes valid on 1 October at 10:00. The nominal 72-hour point is 4 October at 10:00. A buyer request on 3 October does not establish that cancellation succeeded or extend the stated window. Obtain the seller's confirmed result within the applicable conditions. If the issue is first found on 4 October at 11:00, do not backdate an attempted cancellation. Follow the permitted adjustment route. Verify the current document workflow and timestamps in the actual service before acting. The example does not define a timer for another country. Choose the adjustment based on the error. Wrong legal buyer, an agreed price reduction, returned goods and an incorrect tax rate may require different treatment. Distinguish a refund of money from a reduction of the invoice. Avoid issuing a new full invoice merely because the old one needs a partial reduction. ## Preserve the complete document chain Create separate records for the original, credit or debit note, cancellation and replacement. Link each to the commercial case and required original identifiers. Retain reasons, approvals and external responses. Where a replacement is required, establish what neutralizes the original before releasing the new liability or receivable. The case should explain why both records exist and the resulting amount due. Never overwrite the original file with its corrected version. HMRC's electronic-invoicing notice requires credit-note information that identifies the original invoice and stresses correct posting of amending documents. [HMRC, VAT Notice 700/63, section 3.4](https://www.gov.uk/guidance/electronic-invoicing-notice-70063). Follow the local reference requirements for each branch of your process. Validate the adjustment with the required document profile and release. [Peppol](https://erplocalization.com/glossary/core/#core-peppol-and-openpeppol) BIS Billing publishes invoice and credit-note specifications and validation rules, providing a technical basis for supported exchanges. Those specifications do not themselves determine whether a national tax adjustment is permitted. [OpenPeppol, BIS Billing, May 2026 release](https://docs.peppol.eu/poacc/billing/3.0/). ## Work a partial return without issuing another sale The following example is synthetic. It uses a fictional currency and a fictional 10% tax rate. Assume the local rules permit a credit note for the agreed return and the tax owner confirms the adjustment period. The original invoice I-100 covers 100 units at 50 net each. Net value is 5,000, tax is 500 and gross value is 5,500. The customer returns 20 units, and the warehouse accepts the return. The remaining 80 units are validly supplied. Create credit note C-100 for 20 multiplied by 50, or 1,000 net. Tax is 100 and the gross credit is 1,100. Reference I-100 and retain the return authorization and receipt evidence. The document chain now has original net value 5,000 less credited net value 1,000, giving 4,000. Tax is 500 less 100, giving 400. Gross receivable is 5,500 less 1,100, giving 4,400. If the original was unpaid, allocate the credit to its receivable so the customer owes 4,400. Confirm any automated collection process uses the adjusted amount. Do not issue a second invoice for 4,400 alongside the active original and partial credit. That would create another charge for the same remaining supply. If the customer already paid 5,500, the credit creates a customer credit balance of 1,100 under this example's posting design. Treasury must execute an approved refund or authorized offset. The credit note does not prove that the bank transferred money. After a cash refund, the customer has paid a net 4,400 and the customer balance is zero. The supplier's correction should reach the buyer's AP process too. The buyer records the credit against the original and checks any input-tax adjustment. Agreement on the commercial return does not automatically synchronize both ERPs. ## Handle a failed or partially completed correction If the adjustment fails validation, keep the original invoice and receivable visible. Repair the adjustment and confirm its final state. Decide any necessary collection hold separately. A draft credit note cannot prove that the legal invoice was reduced. If cancellation fails because another document references the invoice, investigate the chain. MyInvois exposes an active-referencing-documents restriction in its cancellation API. Do not delete references to bypass it. Obtain the permitted sequence and approvals, then preserve every completed action. [LHDN, cancellation state restrictions](https://sdk.myinvois.hasil.gov.my/einvoicingapi/03-cancel-document/). If the wrong invoice was adjusted, open a second controlled correction case linked to the first. Establish the permitted remedy instead of editing the accepted note. Reconcile both customer accounts and any reports affected. If the invoice crosses a filed return period, have the tax owner decide the tax correction procedure. A commercial credit and a correction to an earlier return are separate decisions. HMRC's VAT error-correction guidance provides different procedures according to the error and circumstances. Do not assume a current-period posting resolves a prior return error. [HMRC, VAT Notice 700/45](https://www.gov.uk/guidance/how-to-correct-vat-errors-and-make-adjustments-or-claims-vat-notice-70045). ## Confirm the result in every affected system Reconcile the original and adjustment values in the external service, ERP subledger, general ledger and return working papers. Confirm customer delivery where required. Track stock movements separately if goods returned. Ask treasury to confirm the refund, offset or revised collection amount. Preserve bank or allocation evidence separately from invoice status. If a customer still sees the wrong amount, send a statement showing the original, adjustment and settlement rather than another invoice. The case owner can close the correction when all these checks pass: - The approved reason, mechanism, actor and period are recorded. - The original and all related documents are retrievable and linked. - Required external actions have confirmed results. - Receivable or payable, tax, inventory and settlement effects agree with the commercial outcome. - The other party has the required documents and explanation. - A reviewer can reproduce the remaining amount due and identify any open refund or claim. Carry unresolved actions into the next close using the same case ID. Use [the reconciliation guide](https://erplocalization.com/guides/reconcile-e-invoices-erp-tax-return/) for period-level differences and [the AP guide](https://erplocalization.com/guides/inbound-e-invoicing-accounts-payable/) for buyer controls. Include the corrected scenario in your [localization acceptance tests](https://erplocalization.com/guides/erp-localization-acceptance-tests/) before automating similar cases. Source verification date: 17 October 2026. ## Worksheet: Invoice correction case worksheet Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment. Show the worksheet Use one case for the commercial problem and separate linked records for its legal documents and technical attempts. Follow the [correction guide](https://erplocalization.com/guides/correct-cancel-replace-e-invoice/). ### Preserve the original - Case ID, entity, customer or supplier and case owner: ____ - Original legal number, ERP ID and external ID: ____ - Original payload and rendering location: ____ - Issue, validation and delivery times with time zones: ____ - Currency, net, tax and gross values: ____ - Ledger and subledger postings: ____ - Existing payments, credits and other referenced documents: ____ Record the actual external state. If an outcome is unknown, investigate before creating a replacement. ### Approve the action - Commercial reason and supporting evidence: ____ - Applicable jurisdiction, document type and rule source checked on: ____ - Authorized actor: ____ - Permitted mechanism and approval: ____ - Trigger timestamp, time-zone basis and action deadline, if applicable: ____ - Tax treatment and adjustment period: ____ - Customer or supplier communication plan: ____ Keep a buyer request separate from confirmed issuer cancellation. Do not assume a request extends any deadline. ### Record each completed event Copy this block for every cancellation, adjustment, replacement, retry or correction to an earlier action. - Action ID, type, actor and time: ____ - Original and related identifiers: ____ - Payload or request evidence: ____ - External result, identifier and response location: ____ - Accounting entry and effective period: ____ - Effect on payment, collection, refund or stock: ____ - Remaining exception, owner and date: ____ Preserve failed actions. Do not replace the original file with a corrected rendering. ### Reconcile the monetary result - Original net, tax and gross: ____ - Each legal adjustment with signs: ____ - Remaining net, tax and gross: ____ - Cash already paid or received: ____ - Refund or offset due and confirmation evidence: ____ - Final balance and settlement state: ____ The guide's synthetic example assumes a fictional 10% tax and an approved partial-return credit. Original 5,000 net plus 500 tax equals 5,500 gross. Credit 1,000 net plus 100 tax equals 1,100 gross. Remaining value is 4,000 net plus 400 tax, or 4,400 gross. If 5,500 was paid, a refund of 1,100 leaves net payment 4,400 and a zero customer balance. The example uses no replacement invoice. Record why any replacement in your real case is necessary and what neutralizes the original. ### Close the case - ☐ The action, actor, period and deadline calculation have approval. - ☐ Required external results are confirmed. - ☐ Original and related documents have complete references. - ☐ Ledger, subledger, tax and stock effects reconcile. - ☐ Refund or offset remains separately tracked until confirmed. - ☐ The other party has the required adjustment evidence. - ☐ Any earlier return correction has a documented decision. Case owner and date: ____ Tax approver and date: ____ Controller or reviewer and date: ____ ## Related on this site - [Country pages](https://erplocalization.com/countries/): key facts with sources - [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support - [All guides](https://erplocalization.com/guides/) Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17. Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more). --- Canonical: https://erplocalization.com/guides/correct-cancel-replace-e-invoice/ · Last updated: 2026-10-17 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".