When a paper invoice had an error, the document was torn up and a new one was written out. There is no such chance with electronic documents. An invoice is recorded the moment it is sent, and the other party sees it immediately.
This does not mean errors cannot be corrected. However, the path to correction depends on the document type, the chosen scenario, and the elapsed time. Choosing the wrong path only delays the process.
In this article, we compared the cancellation, rejection, objection, and return invoice options side by side, explaining which one works in which situation.
Table of Contents
Four different paths
Four mechanisms are used in practice, and they are not interchangeable.
Cancellation. This means the document is considered never to have been issued. Its scope is narrow; it is not possible for every document and at all times.
Rejection. This is the buyer declining the document through the system. It only works within the commercial scenario and timeframe.
Objection. This is an official notification made through channels outside the system. Channels such as a notary or registered mail are used.
Return invoice. Instead of retrieving the document, this involves issuing a new document in the reverse direction. This is the most commonly used method in commercial life.
How scenarios open up paths
The scenario you choose when issuing the invoice determines which correction path will be available later. Therefore, scenario selection is not a formality, but an operational decision.
In the basic scenario, the buyer has no right to reject through the system. When an issue arises, the parties resort to an objection or a return invoice.
In the commercial scenario, however, the buyer can reject the document within a specified period. This means a period of uncertainty for the seller; however, it ensures the rapid correction of erroneous documents.
We compared which scenario is suitable for which customer in the article e-invoice scenarios.
Rejection: the buyer's in-system right
If you are on the buyer side, rejection is the cleanest correction path. The document is returned before entering the system; no accounting record is created.
However, the right of rejection is subject to a time limit, and that time passes quietly if you do not open your inbox. This is one of the most concrete reasons for daily inbox scanning; we covered this routine in the incoming e-invoice inbox management article.
Writing the reason for rejection ensures the supplier makes the correct correction. Writing "unit price does not match the agreement" instead of just "rejected" prevents a second round.
If you are on the seller side, you should track rejected documents in a separate list. A rejected invoice means an uncollectible invoice.
When is a return invoice used?
If the rejection period has expired or the basic scenario was used, the remaining practical path is a return invoice. The buyer issues an invoice in the reverse direction to the seller; the transaction is mutually closed.
If there is a product return, this method is naturally the right one. Since the product has physically returned, a stock entry is also required; we covered the e-commerce workflow in the return process management article.
If there is only a pricing error, a difference invoice can also be used instead of a return invoice. It is appropriate to clarify with your financial advisor which method suits your situation.
Point to note: return and difference documents affect the current account balance. If the record remains incomplete, the reconciliation will not match at the end of the period.
The situation with e-archive invoices
There is no in-system rejection mechanism for e-archive invoices; the document does not drop into the buyer's inbox. Therefore, correction methods work differently.
Cancellation is easier in the period before reporting. After reporting has been made, a return invoice or objection path is generally used.
We detailed the differences between the two document types in the difference between e-invoice and e-archive invoice article.
Reducing the need for corrections
The best cancellation is the one that is never needed. Most correction requests stem from three sources: incomplete current account information, incorrect pricing, and erroneous quantities.
Current account information relates to card quality. If the tax office, title, and address fields are complete, the document will not be rejected; you can check out the opening a current account card article.
Pricing errors are usually caused by manual entry. When customer-specific pricing and discounts are defined, the operator does not type the price, the system brings it in; the discount matrix and price list article explains this setup.
Quantity errors stem from a broken document chain. When the invoice is generated from the dispatch note, and the dispatch note from the order, the quantity is not re-typed. We explained this chain in the sales document chain article.
Finally, the cancellation authority should be kept strict. Allowing anyone who can issue a document to cancel it creates audit risks; we addressed this distinction in the sensitive transaction permissions article.
Recording corrections
Every correction points to the point where a process has failed. When this information is not recorded, the same mistake repeats, and the number of corrections increases over time.
The only thing needed for recording is a reason field. Using selectable categories instead of free text generates reportable data later on.
Practical categories are: pricing error, quantity error, wrong current account, missing information, customer request, and return. A monthly distribution chart immediately shows which side needs improvement.
If pricing errors are dominant, price definitions should be reviewed; we explained this setup in the discount matrix and price list article.
If quantity errors are dominant, it means the document chain is broken; when the transfer from dispatch note to invoice is established, this group almost entirely disappears. You can check out the document chain article.
The correction rate is also a cost indicator. Every re-issued document consumes additional credits and delays collection; we touched upon this impact in the credit planning article.
Frequently asked questions
Can I cancel an invoice I sent myself?
It depends on the document type, scenario, and time elapsed. In most cases, unilateral cancellation is not possible; a return invoice is used.
If the buyer rejects it, do I get the VAT back?
A rejected document is considered un-accounted for. Consult your financial advisor for intra-period and post-period differences.
I selected the wrong scenario, can I fix it?
The scenario cannot be changed on the document afterwards. The document needs to be re-issued.
Does a cancelled document refund credits?
The consumption model varies by provider. We explained volume planning in the e-document credit planning article.
In short: cancellation is a narrow door, rejection is a time-bound right, and a return invoice is the solution for daily life. Knowing the right path reduces correction time from days to hours.
By consulting with EQLEM, you can plan your document correction workflow and authorization setup together.