Cancelling and correcting an invoice: which route when

Last working day of the month, and the first call of the morning at a wholesaler's bookkeeping desk opens with a sentence nobody wants to hear: this invoice is not ours. The document issued a week earlier went to the wrong one of two companies in the same group; the trade name looks right, the tax number belongs to somebody else. The bookkeeper finds the invoice on screen and tries to delete it. The system refuses. By now the document has already posted to the customer account, stock has been reduced, the month is about to close, and a second document has been issued to the correct company for the same shipment. There is no single error here. There are three records feeding each other, and all of them have to be unwound.

Invoice errors are unavoidable; what determines their cost is the route taken after they surface. This article opens the decision step by step: why the document cannot be deleted, the three questions it starts with, why e-Fatura and e-Arşiv invoices follow different cancellation paths in Türkiye, where an objection differs from a cancellation, how to choose between a correcting invoice and a return invoice, what happens when the error appears after the period closes, what a cancellation leaves behind, which controls stop it repeating, and what to measure. One thing upfront: what follows explains mechanism. Which route fits your specific case is a decision to make with your accountant.

Why you cannot just delete an invoice and reissue it

The moment it is issued, an invoice stops being only your record. It reaches the counterparty, creates a purchase or expense entry in their books, and electronically leaves a central trace. Deletion therefore does not exist as an operation. What exists is a second transaction that voids the first or reverses its effect. Accounting logic runs one way here: you do not change the past, you write on top of it.

The distinction decides a great deal in practice. A document you believe you deleted can turn up alive in the counterparty's records months later, and then the two sides do not agree on a single figure. The number on a cancelled document does not vanish either; the sequence stays intact, and why that number went unused has to remain explainable afterwards. We collected how documents get issued in the first place, and which type applies when, in our guide to issuing invoices; this article is about what happens after.

The decision starts with three questions

Settle three things before choosing a route. First, the document type: an e-Fatura, an e-Arşiv invoice, or a paper document. Second, the timing: was the error caught the same day, within the same month, or after the return was filed and the period closed. Third, the nature of the error: should the document never have been issued at all, is the customer information wrong, is the amount or quantity off, or were goods physically returned.

Those three answers narrow the options fast. A wrong recipient caught on the day and the same error caught three months later are resolved through different routes, because the second drags the filing side in too. Teams lose the most time jumping straight to a fix without asking these three.

Turning them into a short checklist also fixes an internal problem: whoever spots the error brings the right information to the right person. When a message to the accountant does not carry those three answers, the reply is always the same — send me the document and the date.

Why e-Fatura and e-Arşiv follow different cancellation paths

The two documents reach different recipients, and that difference sets the route. An e-Fatura goes to a recipient registered in the system, so cancelling or rejecting it usually depends on that counterparty's response inside the system. An e-Arşiv invoice is issued to recipients not registered there, so the cancellation notice comes from your side and the counterparty's approval works differently.

The scenario you issue under changes who can do what as well. A commercial scenario gives the buyer a way to reject the document within the system; under a basic scenario there is no such reply path and any objection travels through other channels. You cannot pick a route without knowing which scenario applies to that customer. We cover the difference between the two document types, and when each is issued, in our article on e-Fatura versus e-Arşiv invoices.

The timing window matters here too. Cancellation and rejection are valid only within defined periods, and because those periods vary by regulation and document type, the useful rule is not a number of days: start on the day you find the error, since delay usually means falling back to a heavier route.

An objection is not a cancellation

A cancellation is a request to void the document. An objection is a written, date-provable notice that you dispute it, sent through channels such as a notary, registered mail with return receipt, or registered electronic mail. An objection on its own does not make the document disappear; the counterparty still has to accept it or a corrective document has to be issued.

In practice, objection is the route where the buyer cannot reject the document inside the system. The most common mistake is objecting by phone or message and skipping the written step: if the other side never corrects their records, you are left with no evidence. The second is objecting and then waiting. An objection is a notification; what closes the matter is the step the counterparty takes next.

The mirror image of all this, on the receiving side, deserves the same setup. When a wrong document reaches you, the first move is to notify the seller in writing before posting it, stating in one sentence which detail is wrong. Pulling a posted document back out of your records is far harder than never posting it, which makes a short check on incoming invoices as valuable as the check on the ones you issue — and most teams skip it entirely.

Correcting invoice or return invoice?

The two get confused constantly. A correction is what the seller does to repair an error in their own document; a return invoice is what the buyer issues when sending goods back. The direction matters, because who issues the document determines on which side the tax is calculated. On a return invoice the movement reverses: tax charged by the seller is recovered through a document raised by the buyer.

How the return flow is wired into stock and the customer account, especially when goods physically come back, is covered in our article on consignment sales and return invoices. To recall how the tax is computed on each side, our piece on VAT calculation is worth a look; in corrections the item most often missed is not the amount but the direction of the tax.

When the error surfaces after the period closes

An error found within the month is a bookkeeping job. An error found after the return is filed is a filing job. In the second case, alongside fixing the document, correcting that period's return comes into play. Because penalties arise in this territory, do not decide alone: whether a corrective return is filed, whether voluntary-disclosure provisions apply, and the order of the steps depend entirely on the case and require your accountant's assessment.

The bookkeeping desk's job here is not to decide but to bring complete information so a decision is possible: the document date, the amount, whether the counterparty has posted it, and whether the goods were actually delivered. We describe the general landscape of which notification route arises when in our article on tax penalties, voluntary disclosure and settlement.

A quiet side effect of crossing periods is the reporting forms. When document amounts change, the purchase and sales totals reported for that period change too, and if the two sides do not make the same correction, the cross-check shows a gap. The logic of those forms is in our piece on the Ba-Bs form.

What a cancelled invoice leaves behind

Cancelling an invoice means unwinding every record it triggered, and teams routinely void the document and forget the rest. The receivable still sits on the customer account, the stock movement is not reversed, and a payment stays matched to a dead document. The invoice disappears; its footprints stay. That is why a cancellation is not a single action but a short checklist.

If you keep electronic books the job stretches one step further, because entries must stay consistent with the ledger and it has to remain provable which document sat in which period against which entry. How the ledger side works is covered in e-Defter.

Why reconciliation is the last checkpoint

The only place that shows whether your cancellations and corrections truly landed is where your figure meets the counterparty's. If a document you consider cancelled is still live in their records, the process is half finished, and nothing but reconciliation reveals it. A monthly rhythm of customer account reconciliation is the cheapest way to catch correction errors. Finding them all at year end is the most expensive.

Controls that stop the same error repeating

The way to cut your cancellation count is not more care but an issuing flow that does not allow the error. The controls below stop most bad documents before they exist.

• Customer data from the record: Trade name, tax number and address should be pulled from the customer card rather than typed; the single most common cause of cancellation is a hand-typed wrong recipient.
• Order and dispatch link: When invoice lines derive from the order and delivery note, quantity errors largely disappear.
• A draft stage: Define a short holding period before the document goes out; those few minutes between issuing and sending catch a meaningful share of errors.
• An approval threshold: Require a second pair of eyes for specific line types or new customers; approving every document locks the flow, approving none lets errors run free.
• Separation of rights: Who can issue a document and who can open a cancellation request should be defined separately.
• Mandatory cancellation reason: Force a standard reason on every cancellation; without that field you will never see what keeps repeating.
• Templates for recurring customers: For customers billed with fixed lines, templates speed the work and eliminate typing errors at the same time.

Every cancelled invoice is the record of a question nobody asked before issuing it.

These controls pay off on the revenue side as well. Time spent chasing bad documents is time not spent noticing work that is waiting to be billed; both problems grow from the same root. How unbilled work quietly disappears is the subject of our article on revenue leakage.

Which numbers to watch

Four indicators are enough to manage this area. First, cancellations and corrections against documents issued; a universal threshold is meaningless, what matters is the direction of your own trend. Second, the distribution of error types: if half your cancellation reasons cluster on one cause, that is where the fix belongs. Third, the time from issue to discovery; the shorter it gets, the more options you keep. Fourth, concentration: are errors piling up on one customer, one product group, or one rep? Reading the second and fourth together gets you to the cause fastest; when the error type and the place it clusters overlap, the fix is almost always a single field, a single template or a single habit.

The unexpected part is usually this: most cancellations come out of the most routine documents, not the complicated ones. Routine work feels like it needs no attention, runs on autopilot, and a template built wrong once repeats the error every month. Reading the correction log once a month therefore returns more than fixing cases one by one.

Where to start

Pull the last three months of cancellations and corrections and ask one question of each: which check, performed before issuing, would have prevented this? The answers usually cluster into three or four themes, and those themes are your control list. Then define one written internal flow: who spots the error, who takes the first step, and in which situations the accountant is brought in with what information.

Finally, this article explains mechanism; the applicable procedure, deadlines and practical details in Türkiye can change. For a specific document, confirm with your accountant which route fits, whether a period correction is needed and how the entry is made. How to put that working relationship on a productive footing is covered in our article on working effectively with your accountant.

Invoice corrections feel heavy less because of the document than because the document, the stock, the customer account and the payment live in separate places. In Rocketly the invoice, the customer record, stock and collections sit in one flow, so cancelling a document shows you every record it touched on the same screen — open a free account and set up your own invoicing flow.