An e-Invoice is not just a scanned copy of a paper invoice. It is a document generated in a specific format, electronically signed, and delivered to the recipient through a closed network.
The difference is significant. You hand over, mail, or email a paper invoice. With an e-Invoice, the document leaves you, lands in the recipient's inbox via the system, and this movement is officially recorded. This largely puts an end to the "I sent it, but it didn't arrive" debate.
In this article, we explained what an e-Invoice is, how it is issued, and most importantly, how the issued invoice connects to your daily operations. Because an invoice is not a standalone document; it is a continuation of the order, shipment, and collection process.
Table of Contents
What exactly is an e-Invoice?
An e-Invoice is an invoice generated in a standard data format defined by the Revenue Administration (GİB). The content of the document is created in XML format, signed with a financial seal or electronic signature, and transmitted to the recipient via the closed system managed by GİB.
The phrase "closed system" is the key point here. An e-Invoice is only valid between taxpayers registered in the system. If the other party is not an e-Invoice taxpayer, you cannot issue an e-Invoice to them; a different document type comes into play. We detailed this distinction in the difference between e-Invoice and e-Archive invoice article.
The visual appearance of the document and its data are also separate. The data is standard; the recipient system reads it. The visual appearance depends on your design. The logo, field layout, and color scheme are determined by a template — we covered this side in the XSLT document design article.
Who is required to use e-Invoices?
The scope of obligation is determined by revenue thresholds, business sectors, and certain special circumstances. Thresholds are updated periodically; therefore, it is best to confirm the current threshold with your financial advisor or through GİB announcements.
In practice, we see three groups. First, businesses that fall into the scope because they exceeded the revenue threshold. Second, those included due to e-commerce or specific sector activities. Third, those who transition voluntarily even though it is not mandatory — because their customers are e-Invoice taxpayers and the process moves faster that way.
Steps skipped during the transition process cause problems on the first invoice day. We gathered a sequential checklist in the e-Document transition checklist article.
How to issue an e-Invoice step by step?
1. Verify the recipient
Check whether the recipient is an e-Invoice taxpayer using their tax ID or national ID (TCKN). If they are a taxpayer, you issue an e-Invoice; if not, you issue an e-Archive invoice. When this check is done automatically, the risk of selecting the wrong document type is eliminated.
2. Fill in the document header
The invoice date, current account, currency, payment terms, and branch/warehouse information, if any, are included in the header. In the standard document entry approach, the header remains in the same place on every document; the team doesn't have to relearn the screen when switching modules.
3. Enter the line items
You enter the product or service lines, quantity, unit price, discount, and VAT rate. If the lines are linked to a stock card, the quantity generates a stock movement simultaneously. Without this connection, the invoice and warehouse reality diverge.
4. Select the scenario and document type
You select the appropriate scenario from options such as Basic, Commercial, or Export. The selection determines the recipient's right to object and how the process will proceed.
5. Sign and send
The document is signed with a financial seal and transmitted through the integrator. Post-dispatch status tracking is important: statuses such as delivered, accepted, and rejected should appear in the same list.
Why is scenario selection critical?
In the basic scenario, the recipient has no right to reject through the system; objections are made via other channels. In the commercial scenario, however, the recipient can reject the document within a certain period. The operational outcomes of the two situations differ from each other.
Selecting the wrong scenario cannot be corrected afterward; the document must be reissued. Therefore, defining a default scenario in the current account card is a practical habit. We covered the details in the e-Invoice scenarios article.
Integrating the invoice into operations
The invoice is the final link in the chain. Before it comes the order, and after it comes the collection. When this chain operates disjointedly, the same information is entered three times, increasing the probability of error with each entry.
When transfer is established from order to dispatch note, and from dispatch note to invoice, the lines are carried over; the operator only adjusts the difference. We explained this flow in the sales document chain article.
A similar order is required on the incoming invoices side. Comparing the document coming from the supplier with the order catches price and quantity discrepancies early; the document matching article explains this control.
The e-Document module keeps this flow aligned with inventory, sales, and finance in the same account. Your existing accounting software can stay in place; the operational side speeds up on the platform.
Five common mistakes
Incomplete current account info. If the tax office, address, or company title is missing, the document may be rejected. Filling out fields completely when opening a card is cheaper than dealing with it later.
Incorrect VAT rate. If the rate is not defined in the product card, the operator enters it manually every time; sooner or later, it gets entered incorrectly.
Applying discounts to the total instead of the line. This creates a mismatch with the other party's record and a reconciliation variance at the end of the period.
Failing to track dispatch status. If a rejected invoice goes unnoticed, collection is also delayed.
Not tracking credits. When document credits run out, invoices cannot be issued. We explained volume planning in the e-document credit planning article.
Frequently asked questions
Is a financial seal mandatory to issue an e-Invoice?
A financial seal is used for legal entities, and an electronic signature is used for sole proprietors. The application process is the first step of the transition.
Can I cancel an invoice I issued?
It depends on the scenario and timeframe. We compared the options in the cancellation and objection process article.
How long do I need to store the invoice?
You can check the e-document archiving article for the legal retention period and accessibility conditions.
Do I need to change my current accounting software?
No. A system like Mikro, Logo, or similar can remain as the master record. System sync keeps both sides aligned.
When set up correctly, an e-Invoice is not an extra workload; on the contrary, it is a bond that closes the gap between order, shipment, and collection. The critical thing is not to think of the invoice in isolation.
By scheduling a brief discovery session with EQLEM, you can discuss how to run your e-document flow within the same account as inventory and sales.