It's the last day of the month and a merchant is staring at a spreadsheet of 380 orders that shipped over the past four weeks — every one of them needing a sales invoice. So begins the ritual: open the accounting tool, copy a customer's name and tax number from the order, paste it in, key in the line items, check the total against the order, issue the invoice, download the PDF, move to the next one. Somewhere around order 190 a tax ID gets transposed, the invoice is issued to the wrong entity, and unwinding it will take a phone call and a correction. Three of the orders were returned two weeks ago and shouldn't be invoiced at all, but nobody flagged them. By the time it's done, most of a working day is gone — a day that produced nothing, sold nothing, and shipped nothing.
This is how invoicing works at a surprising number of Turkish online stores: as a manual, month-end chore bolted onto the side of the real operation. And it's strange, because invoicing isn't a nicety you do when you have time. In Turkey, issuing a proper sales invoice for every sale is a legal obligation — with filing rules, deadlines, and financial penalties for getting it wrong. Treating a legal requirement as an afterthought is how good businesses accumulate quiet, avoidable risk.
This guide is about closing that gap. It covers what you're actually required to issue (e-fatura versus e-arşiv), the point at which invoicing becomes mandatory for an online store, the one timing decision that trips almost everyone up, and — most importantly — how to stop invoicing by hand and make it an automatic step that happens on its own as orders move through your shipping workflow.
A note before we start: invoicing and tax obligations are specific to your business, your revenue, and your registration status. Everything below is general guidance to help you understand the shape of the problem — not tax advice. Confirm the specifics for your own store with your accountant (mali müşavir).
E-Fatura vs. E-Arşiv: What You're Actually Required to Issue
The first thing that confuses new sellers is the two names, so let's separate them cleanly. Both are electronic invoices in Turkey's tax system; the difference is who the invoice is going to.
- e-Fatura is issued between two parties who are both registered in the e-Fatura system — that is, business-to-business, taxpayer-to-taxpayer. It travels through the tax authority's (GİB) closed system in a structured format, and the recipient receives it inside their own e-Fatura account.
- e-Arşiv fatura is issued when the recipient is not an e-Fatura taxpayer — which describes almost every end consumer you sell to. It's generated as a PDF and delivered to the customer by email or SMS.
For a typical B2C online store, this means the overwhelming majority of your invoices are e-arşiv invoices, because you're selling to individual consumers. You'll issue an e-Fatura only when the buyer is a registered business that's also in the e-Fatura system. A good invoicing setup handles this distinction automatically — it looks at the customer's tax status and issues the correct document type — so you're not the one deciding invoice-by-invoice.
The practical takeaway: whichever type applies, an invoice has to be issued for the sale. There's no version of running a compliant online store in Turkey where you skip the invoice.
When Invoicing Becomes Mandatory — and What Happens If You Skip It
Two thresholds matter here, and they're often confused.
Becoming obligated to use the electronic system. Most businesses join the e-Fatura and e-Arşiv system once their gross sales revenue crosses a threshold. The general threshold is 3 million TL of annual gross revenue — but for e-commerce sellers (along with real-estate and motor-vehicle traders) it drops sharply to 500,000 TL. If your gross e-commerce revenue for a given accounting period is 500,000 TL or more, you're required to move onto e-Fatura and e-Arşiv, and the deadline to do so is July 1 of the following year. For a fast-growing store, that threshold arrives earlier than you'd expect — plenty of first- or second-year stores cross it without realizing the clock has started.
Issuing an invoice for a sale. Separately, an invoice has to be issued for the sale itself. For sellers not yet in the electronic system, there are amount-based rules for when a document must be issued as an e-arşiv invoice through the GİB portal (the 2026 figure being in the low-tens-of-thousands of lira per document). Once you're in the e-Arşiv system, though, your customer invoices are issued electronically as a matter of course.
The cost of getting it wrong. Failing to issue a required invoice — or issuing it late or incorrectly — falls under the özel usulsüzlük cezası (special irregularity penalty) in the Tax Procedure Law. It's applied per document, and the per-document figure runs into the tens of thousands of lira and is revalued upward every year. That's the detail that makes manual, month-end invoicing genuinely dangerous: a penalty that's charged per missing or wrong document turns a batch of forgotten invoices into a compounding liability, not a rounding error. Confirm the current figures and your own obligations with your accountant — but understand the direction: the tax authority treats invoicing as mandatory and prices mistakes accordingly.
Why Manual Invoicing Quietly Breaks as You Grow
At ten orders a day, invoicing by hand feels fine. The trouble is that it doesn't scale linearly — it scales against you, because every one of its failure modes gets more likely as volume rises. Here are the five ways it breaks.
1. It burns hours you can't get back
Every manually-issued invoice means re-typing data that already exists on the order: customer name, tax number or ID, address, line items, amounts. It's pure duplication — you're copying an order you already have into a second system by hand. At a hundred orders a week that's hours of skilled time spent on data entry that produces nothing, and it's time that gets pulled away from packing, sourcing, and customer service.
2. It creates compliance risk through timing
Manual invoicing tends to happen in batches — end of week, end of month — which means there's always a window where shipped orders haven't been invoiced yet. Miss a batch, lose the spreadsheet, or have the person who "does the invoices" go on holiday, and invoices slip past their proper timing. Because the penalty is per-document, a single forgotten batch isn't one problem — it's one problem per order in it.
3. It introduces data-entry errors
A transposed tax number, a wrong ID, a mistyped total — each one produces an invoice that's either rejected by the provider or, worse, issued incorrectly and now has to be cancelled and reissued. These are the same class of errors that cause failed deliveries from bad address data: small typos with outsized downstream cost. On a tax document, the cost includes a correction process and, potentially, a penalty.
4. It's impossible to reconcile
Once invoicing lives in a separate tool, answering "which orders still need an invoice?" becomes a manual cross-check between your order list and your invoice list. Nobody has a reliable, real-time view of what's invoiced and what isn't, so things fall through the cracks precisely because there's no single place that tracks invoice status against orders.
5. It creates customer friction
Customers expect their invoice, and in Turkey many need it for their own records or expense claims. When invoicing is a delayed manual batch, the invoice arrives late or after a customer has to ask for it — "faturam nerede?" — which turns a routine step into a support ticket and a small dent in trust. Post-purchase communication is where customer experience is won or lost, and a missing invoice is a needless way to lose a bit of it.
Fix it: none of these failures are about carelessness — they're structural. They exist because invoicing is detached from the order and done by hand. The fix isn't "be more careful"; it's to make invoicing a step that happens automatically, from the order data you already have, at a defined point in the order's life.
The Decision That Trips Everyone Up: When to Invoice
Once you decide to automate invoicing, you hit the one genuinely strategic question: at what point in the order's journey should the invoice be created? There are two sensible answers, and picking the wrong one for your business creates its own mess.
On hand-off to the carrier. The invoice is created the moment you ship — when the parcel is handed to the carrier. This is clean and immediate: the invoice goes out with (or right after) the goods, and the customer has it as soon as the order is on its way.
On delivery to the customer. The invoice is created when the carrier marks the parcel delivered. This delays the invoice slightly, but it aligns the document with the moment the sale is actually completed in the customer's hands.
The reason this matters comes down to two things: returns and cash-on-delivery.
If you sell in a high-return category (fashion and apparel being the classic example) and you invoice at hand-off, a meaningful share of those invoices will be for orders that come straight back. Every return then requires a return invoice (iade faturası) to reverse the original — so you've created two documents and a reconciliation task for a sale that never really happened. Invoicing on delivery doesn't eliminate returns, but it moves the invoice past the biggest source of "invoiced then immediately reversed" churn. If returns are a large part of your operation, invoicing on delivery is usually the calmer choice.
Cash-on-delivery adds the same logic from the payment side: with COD, the sale isn't truly settled until the customer accepts and pays at the door. Refusals happen. Tying the invoice to delivery keeps your invoicing aligned with sales that actually completed.
The best setups let you make this choice per sales channel, because your marketplace orders, your own storefront, and your COD orders may warrant different rules. There's no universal right answer — but there is a right process: decide deliberately based on your return rate and payment mix, rather than defaulting to whatever's easiest to configure. (And whatever you choose, confirm it fits your accounting treatment with your mali müşavir.)
How to Automate Order Invoicing
Here's the shape of an invoicing setup that runs itself. The goal is simple: an invoice should be drafted from the order automatically, need only a review and a signature from you, and then live on the order where you and the customer can find it — without anyone re-typing anything.
1. Connect the provider you already use. You almost certainly already have an e-invoice provider — a tool like Kolaybi, BizimHesap, or Paraşüt. The invoices should still be issued through your provider, on your official serials; automation isn't a new invoicing authority, it's a way to feed your existing provider automatically. So step one is connecting that provider to your order and shipping workflow, once.
2. Set the trigger — per channel. Choose the condition that creates an invoice: on hand-off to the carrier, or on delivery. As discussed above, set this deliberately per sales channel based on your returns and COD mix.
3. Let invoices draft themselves from order data. When an order hits the chosen status, a draft invoice is created automatically from the order — customer details, tax number, line items, amounts, all pulled from data you already captured at checkout. No re-typing, which removes the single biggest source of both wasted time and data-entry errors.
4. Review and sign. You review the draft and sign it. This is the one human step that should remain human — a quick check before the document becomes official — and it's genuinely quick because there's nothing to type, only to confirm. On signing, the official serial number and the signed PDF are captured.
5. Store it back on the order. The serial number and signed PDF are saved directly onto the order. Now there's one place that answers "is this order invoiced?" — the order itself shows a clear signed / unsigned / error status — and the PDF is right there to send to the customer or hand to your accountant. No more hunting across systems.
6. Handle errors in one click. Some invoices will fail — a wrong tax ID is the classic case. A good setup flags the failure with the provider's error message, so you fix the underlying issue and retry the invoice in one click, rather than discovering the gap weeks later at reconciliation time.
This is exactly the workflow Shipink's e-invoicing is built around: you connect your provider (Kolaybi, BizimHesap, or Paraşüt), choose the trigger per channel, and invoices are drafted from your orders for you to sign — with the serial number and PDF written back onto each order automatically. Because it sits in the same place you already manage orders and print labels, invoicing stops being a separate month-end job and becomes one more thing that happens on its own as orders flow through — the same principle behind automating the rest of your shipping workflow.
The Mistakes That Cost You
Even with automation available, a few specific mistakes show up again and again:
- Invoicing before delivery in a high-return category. As covered above, this generates a return invoice for every item that comes back. Match your trigger to your return rate.
- Trusting bad tax data. An automated invoice is only as correct as the customer data behind it. A wrong VKN/TCKN produces a failed or incorrect invoice, so it pays to validate customer details the same way you'd validate a shipping address before it causes a problem downstream.
- Batching everything at month-end. The whole point of triggering on a shipping status is that invoices spread evenly across the month, in step with orders. Reverting to a month-end batch — even with a tool that could automate it — reintroduces the timing risk you were trying to remove.
- Ignoring failed invoices. A flagged, un-retried invoice is a missing invoice. Failed invoices need to be worked the day they fail, not discovered at reconciliation.
- Letting the PDF live in a separate silo. If the signed invoice isn't stored on the order, you've automated the creation but kept the reconciliation headache. The document belongs with the order it's for.
- Applying one rule to every channel. Your marketplace orders, storefront orders, and COD orders may genuinely need different triggers. Treating them identically is convenient but not always correct — a point that generalizes to managing multiple channels as a whole.
Your Invoicing Checklist
Use this to pressure-test your current setup:
Compliance basics
- You know whether your gross revenue has crossed the 500,000 TL e-commerce threshold, and your registration status is confirmed with your accountant
- Every shipped order that should be invoiced actually is — with no month-end backlog
- The correct document type (e-fatura vs. e-arşiv) is issued based on the customer's tax status
Process
- Invoices are drafted automatically from order data — nobody re-types customer or line-item details
- Your invoicing trigger (hand-off vs. delivery) is set deliberately, based on your return and COD rates
- You can set that trigger per sales channel where your channels differ
- Invoices are still issued through your existing provider (Kolaybi / BizimHesap / Paraşüt) on your official serials
Control
- Every order shows a clear invoice status: signed, unsigned, or error
- The signed PDF and serial number are stored on the order itself
- Failed invoices are flagged with a reason and can be retried in one click
- You can answer "which orders still need an invoice?" in one view, not a manual cross-check
Make Invoicing a Step That Happens by Itself
Invoicing is the rare part of an e-commerce operation that is simultaneously a hard legal requirement and, at most stores, a neglected manual chore. That combination is exactly why it's worth fixing: the downside of getting it wrong is real — penalties charged per document, not per mistake — and the work itself produces nothing when done by hand. It's the definition of a task that should disappear into the background.
The way it disappears is by attaching it to something that's already happening. You're already shipping orders and tracking them from hand-off to delivery. Invoicing simply hangs off one of those events: the order reaches its trigger status, an invoice drafts itself from data you already have, you sign it, and it's stored on the order. Connect your existing provider once, set the trigger to match how you actually sell, and the month-end spreadsheet — with its transposed tax numbers and its forgotten batches — goes away for good. The invoice stops being a job you do and becomes a thing that's just... done.
