e-Fatura or e-Arşiv: The Difference Only Shows Up After Something Goes Wrong

A homeware store in Bursa issued two invoices in the same week with the same mistake on them — a wrong line item, caught the next morning by the same person, in both cases within a few hours.

The first one took about thirty seconds to fix. They cancelled it themselves, issued a corrected one, and forgot about it.

The second one is still open six weeks later. It went to a small business that bought in bulk, so it went out as an e-Fatura rather than an e-Arşiv invoice. The buyer never rejected it, the eight-day window closed, and now correcting it means either a return invoice or a formal written objection. Nobody in the store did anything differently between the two. The only thing that changed was who was on the other end.

This guide is about the difference between e-Fatura and e-Arşiv, and specifically about the part of that difference that shows up after the invoice exists. The textbook answer is that one goes to businesses and the other to consumers. That is correct, and on the day you need it, it is nearly useless. What matters operationally is what each document lets you undo, what extra fields an internet sale forces onto one of them, and what has to be printed and put in the box.

Two companion guides sit next to this one. E-commerce invoicing in Turkey is about issuing these invoices without re-typing every order, and it covers when to invoice. Returns management is about the goods coming back. This one is about the document itself.

None of this is tax advice. The rules below reflect the framework in force at the time of writing, the figures are revalued most years, and your own obligations depend on your business. Confirm everything here with your accountant before you act on it.

The Textbook Answer, and Why It Doesn't Help You

Both documents are electronic invoices inside the same tax system. The split is decided by the recipient:

• e-Fatura is issued when the buyer is also registered in the e-Fatura system. It moves through the tax authority's closed system in a structured format and lands in the buyer's own e-Fatura account.
• e-Arşiv fatura is issued when the buyer is not registered, which describes essentially every individual consumer you sell to. It is delivered to the customer electronically.

For a normal online store, the overwhelming majority of documents are e-Arşiv invoices, and e-Fatura shows up on the minority of orders where the buyer is a registered business.

Here is the part the textbook answer leaves out. You do not choose. The buyer's tax status chooses, and your system finds out by checking a tax number against the registry. So the document type is downstream of a data field — which means a missing tax number, a mistyped one, or a customer who enters a company name in a personal checkout produces the wrong document type without anybody making a decision.

That is the whole reason the rest of this guide matters. If you chose the type, you would choose the one with better properties. You don't, so you need to know what each one costs you when something goes wrong.

Who Has to Be in the System at All

Two numbers decide whether any of this applies to you yet, and e-commerce sits on the harsher one.

The general threshold is 3 million TL of gross sales revenue in the accounting period, with the obligation starting on 1 July of the following year. For sellers trading over the internet — along with real-estate and motor-vehicle traders — the threshold drops to 500,000 TL of gross revenue, on the same timetable.

That figure arrives far earlier than most first- and second-year stores expect, and the deadline is not the day you cross it. Crossing it during a year sets a clock that expires the following July, which is exactly why sellers are caught by it: the event that creates the obligation and the date it bites are twelve months apart, and nobody puts a reminder in between.

If you are not in the system yet, there are still amount-based rules requiring certain documents to be issued as e-Arşiv invoices through the tax authority's own portal, with separate limits for invoices to taxpayers and to non-taxpayers. Those figures are revalued every year, so they are a question for your accountant rather than a number worth memorizing from a blog post.

Asymmetry One: Cancelling an Invoice

This is the difference that costs real money, and it is almost never the one people can recite.

e-Arşiv: eight days, and it is yours alone

An e-Arşiv invoice can generally be cancelled within eight days of issue, and the buyer plays no part in it. You do it from your own system or the tax authority's portal, usually in the same session you noticed the problem.

That is as forgiving as invoicing gets in Turkey, and it covers the overwhelming majority of an online store's documents. It is also why most sellers have never experienced invoice correction as difficult.

e-Fatura, commercial scenario: only the buyer can reject it

A commercial-scenario e-Fatura is voided by the buyer sending a rejection response through the system, within eight days. You cannot do it. If the buyer does nothing for eight days, the invoice is treated as accepted and the system route closes.

Read that again in operational terms: correcting your own mistake depends on somebody at another company noticing your message and acting on it inside a week. During a busy period, or across a holiday, that is a coin flip.

e-Fatura, basic scenario: there is no rejection at all

In the basic scenario the buyer has no ability to reject through the system. Cancellation runs through the tax authority's cancellation and objection portal as a request, and the process rests on the agreement of both sides — you raise it, and the other party has to approve it.

So across three document situations you have three completely different levels of control: full, borrowed, and negotiated. The same typing error costs thirty seconds, a phone call, or a formal process depending on a property of the customer you had no say in.

Past the window, the remaining routes are an accounting correction through a return invoice, or a formal objection under the Commercial Code using a channel that leaves proof — a notary, registered electronic mail, or registered post. Each of those is fine. None of them is thirty seconds.

An Internet Sale Puts Your Carrier on Your Tax Document

This is the fact almost nobody outside accounting knows, and it changes how invoicing and shipping have to be wired together.

When the sale is made over the internet, an e-Arşiv invoice has to carry four things a counter sale does not:

1. A statement that the sale was made over the internet, along with the website address.
2. The carrier company's name and its tax number.
3. The date the goods were dispatched, or the service performed.
4. A returns section the customer can complete and sign, with their name, address, signature, and the item, quantity, unit price and amount.

Look at what the middle two of those four actually are. They are not facts about the order. They are facts about the shipment — who carried it and when it went — and neither is known at the moment the order is paid for.

That creates a specific, extremely common failure. Invoicing is usually wired to the order, because that is where the customer and the amounts live. So the invoice gets drafted when the order comes in, hours or days before anyone picks a carrier, and the carrier field is filled with whatever is configured as the default. It is right whenever you happen to ship with the default and wrong the rest of the time, and nothing anywhere flags the difference.

There is a second-order effect worth naming, because it quietly shapes decisions. If your invoice template hard-codes one carrier, then every time you compare rates and pick a different one you create a document that does not match the parcel. Faced with that, plenty of stores stop rate shopping rather than fix the mapping — an accounting field silently making a procurement decision.

Fix it: make the invoice depend on the shipment rather than the order. If the document is created at hand-off, the carrier and the dispatch date are known facts rather than defaults, and the two of them stop drifting apart.

What Actually Has to Be in the Box

There is a widespread belief that printing the invoice and putting it in the parcel takes care of the dispatch note. It can, but only under conditions that are easy to miss.

For the printout to serve in place of a sevk irsaliyesi, it has to carry all three of the following:

• The issue date including the hour and minute, not just the date.
• The phrase stating that the document serves in place of a dispatch note.
• A signature from the seller or an authorized person.

Miss any one and the paper in the box is a copy of the invoice, nothing more, and the goods have moved without a dispatch document. What makes this worth checking rather than assuming is that all three are template and process settings. Nobody re-checks them, they were configured once by whoever set the system up, and a template change months later can quietly drop the timestamp or the phrase without anyone noticing, because the parcel still ships and the customer still gets their order.

This is the same failure shape as a label that renders correctly but is missing something the carrier needs: the document looks right, the process completes, and the defect only surfaces when somebody official asks.

Returns Look Different on Each Document Too

The returns section on an e-Arşiv invoice for an internet sale is not decoration. When a consumer who is not a taxpayer sends something back, they cannot issue you an invoice, because they have nothing to issue one with. The completed and signed returns section on the printout is what documents the return on your side.

Which means the physical copy in the box has a job after delivery, not just during it. If your packing process stopped including a printout because the invoice is emailed anyway, the return documentation route changes, and that is worth a conversation with your accountant rather than a quiet process change made in a busy week.

When the buyer is a registered taxpayer, the shape reverses: the return is documented by an invoice issued in the other direction, from them to you, and your job is to chase it rather than to collect a signature.

None of this changes who pays for the return leg. Since 1 January 2026 the return shipping cost in a withdrawal is the seller's, regardless of which document type sits behind the order. What changes with the document type is the paperwork you need in order to book it correctly.

The Daily Report Nobody Watches

e-Arşiv invoices are reported to the tax authority on a daily cycle, with the report for a day due by the end of the following day. In practice a provider or integrator generates and transmits it automatically, which is exactly why nobody looks at it.

It is still worth knowing the mechanism exists, for one reason: it is the only place where "we issued an invoice" and "the tax authority knows about it" can come apart. If a document failed to generate — a provider outage, a rejected record, an order that never reached the invoicing step — the gap is in that report, and the first sign of it on your side is usually nothing at all.

The practical habit is small: once a month, compare the count of orders shipped against the count of invoices issued, and look at anything sitting in an error state in your invoicing tool. It is the same discipline as reconciling the carrier invoice, applied to the other document your business produces in bulk.

Where This Breaks in a Real Store

1. The wrong document type from a bad tax number. A customer types a company name into a personal checkout, or a tax number with a digit missing. The registry check fails or returns the wrong answer, and you issue the type with worse cancellation properties without knowing it.
2. The invoice is created before the parcel is handed over. The carrier name and dispatch date are then defaults rather than facts. This is the most common one and the least visible, because the invoice itself looks complete.
3. A cancelled order whose invoice is past day eight. Order cancellations cluster exactly where invoices age: a customer changes their mind, the order sits, and by the time anyone acts the easy route has closed.
4. Two carriers on one order. A split shipment, or a reshipped parcel after a failed delivery, produces one invoice and two carriers. Only one of them can be on the document.
5. A parcel that was invoiced but never shipped. The invoice exists, the shipment does not, and the two systems have no reason to talk to each other about it.
6. Nobody owns the reconciliation. Shipping is one person's job and invoicing is the accountant's, and the question "did every order we shipped this month get an invoice" belongs to neither.

What Not to Do

• Don't assume the document type is your decision. It is derived from customer data. The lever you actually control is the quality of that data at checkout.
• Don't wire invoicing to the order when the invoice needs shipment facts. An internet sale's e-Arşiv invoice needs to know who carried the parcel and when it went.
• Don't let a template change go out without re-checking the dispatch-note elements. The timestamp, the phrase and the signature are the three things a redesign drops.
• Don't treat the eight-day window as a comfortable amount of time. It spans one weekend, and on an e-Fatura it depends on someone else's attention, not yours.
• Don't drop the printout from the box because the invoice is emailed. The returns route on a consumer sale may depend on the paper copy.
• Don't change how you issue documents during your busiest month. Our peak season guide puts the change freeze at roughly thirty days out, and invoicing belongs inside that freeze.
• Don't take any of this as a substitute for your accountant. The framework is stable, the figures and the fine print are not.

Why This Matters Before November

Nothing above is seasonal in itself. The reason to deal with it in September and October is that peak multiplies both halves of the problem at once.

Volume multiplies the invoice side: more documents, more of them issued under time pressure, and a higher share of them created by someone who is covering for somebody else. Then January multiplies the correction side, because the returns wave and the cancellations arrive together, and every one of them is a document that has to be undone or offset. The eight-day window is not a problem at forty orders a day in October. It is a problem at four hundred orders a day in late November, when the mistake and the deadline are both moving faster than the person handling them.

So the work is the boring kind, and it has to be done while things are quiet: check which trigger creates your invoices, check that the carrier and dispatch date come from the shipment, check the three dispatch-note elements on a real printout, and confirm with your accountant that the document types you are issuing are the ones you should be. All of that is an afternoon in September. None of it is possible in November.

What Shipink Does With This

Shipink does not issue your invoices and it is not your accountant. What it does is remove the gap between the shipment and the document.

1. Connect the e-invoice provider you already use — Kolaybi, BizimHesap or Paraşüt — and issue through it rather than through a separate tool nobody wants to maintain.
2. Choose when invoices are created, per sales channel: when the parcel is handed over to the carrier, or when it is delivered to the customer. This is the setting that decides whether the carrier name and dispatch date on an internet sale are facts or guesses.
3. Invoices drafted automatically from the order data, so nobody is re-typing a customer's details into a second system at the end of a long day.
4. Sign from the order, with the serial number and the signed PDF saved straight back onto that order.
5. A clear signed, unsigned or error state on every order, which is what makes the monthly "did everything get invoiced" check a glance instead of a project.
6. Fix and retry in one click when a document fails — a wrong tax number being the usual culprit, and the exact error that produces the wrong document type.
7. Everything on the same order record as the shipment, so the carrier that actually carried the parcel and the invoice that describes it are looking at the same row.

The honest limits: your provider issues the document and the e-Fatura versus e-Arşiv determination sits with the provider's registry check, not with Shipink. Shipink does not cancel invoices for you, does not file your e-Arşiv report, and cannot make an eight-day window longer. What it contributes is the shipping half of the record — which carrier, which date, on which order — and the timing that lets the document be created once, correctly.

The e-Fatura and e-Arşiv Checklist

Know where you stand

• You know whether your gross revenue has crossed the threshold that applies to e-commerce sellers
• You know the date your obligation starts, not just the date you crossed the line
• Your accountant has confirmed which document types you should be issuing
• You know which of your orders go out as e-Fatura rather than e-Arşiv, and roughly how many

The internet-sale fields

• The invoice carries the statement that the sale was made online, with the website
• The carrier company name and tax number are on the document
• The dispatch date on the invoice matches the day the parcel actually went
• The returns section is present on documents going to consumers
• The carrier field is populated from the shipment, not from a default

What goes in the box

• The printout shows the issue date with hour and minute
• It carries the phrase stating it serves in place of a dispatch note
• It is signed by the seller or an authorized person
• Someone has checked an actual printed copy since the last template change

Corrections and control

• Whoever handles cancellations knows the eight-day window and which type it applies to
• Order cancellations reach the invoicing step fast enough to stay inside it
• Failed and errored invoices are reviewed rather than left in a queue
• Orders shipped and invoices issued are compared once a month

Two Documents, One Order

The reason this distinction stays confusing is that it is taught as a classification problem — here are two document types, here is how to tell them apart — when in practice it is a control problem. One of them you can correct alone. One of them you can correct if someone else cooperates in a week. One of them carries facts about a parcel that your invoicing system has no natural way of knowing.

None of that is difficult once it is written down. All of it is expensive to learn in the last week of November.

Want the shipment and the invoice to stop being two separate systems? Start free with Shipink, connect the e-invoice provider you already use, and let the document be created when the parcel actually moves.