e-Archive Invoice (e-Arşiv)
Issue e-Archive invoices from SAP for non-registered customers and consumers, and file the daily GİB report automatically.
What problem does it solve?
When the buyer is not an e-invoice taxpayer, or is an end consumer, the invoice is issued as an e-Archive document and a daily e-Archive report is filed with GİB. Retail, e-commerce and dealer structures carry high volumes here, and manually tracked reporting carries penalty risk.
How does the solution work?
The solution routes each invoice automatically to e-Invoice or e-Archive based on the taxpayer query, creates the e-Archive document, has it delivered to the customer and files the daily report on time. Cancellations and returns run linked to the SAP document, and report status is tracked on the document itself.
What changes in practice?
The invoice-type decision is made by the system, not the user. The daily reporting obligation is never missed, and the e-Archive is reachable in one click from the SAP document.
Benefits
- The system decides between e-Invoice and e-Archive from the recipient's taxpayer status
- The status of the daily e-Archive report is tracked on the SAP document
- Cancellations and returns run together with the SAP document
Where it sits in SAP
Integrated with SD billing and FI; covers choosing the document type from the taxpayer query, generating the e-Archive document and reporting to GİB. The customer delivery channel and the integration method are decided during implementation.
Who it is for: Finance, Sales Operations, retail and e-commerce finance teams
Frequently asked questions
When and on what basis is the e-Invoice versus e-Archive decision made, and what if a customer later becomes an e-invoice taxpayer?
The decision is made at the moment of posting by querying the GİB taxpayer registry with the recipient's tax or national ID number; registered taxpayers receive an e-invoice and everyone else an e-Archive invoice. Because the registry is refreshed regularly, when a customer later becomes an e-invoice taxpayer their next invoice is automatically routed to the e-invoice scenario. Users do not need to maintain a manual flag in the customer master.
How does the package work when high-volume channels such as retail or e-commerce create invoices in a system outside SAP?
The e-Archive document is generated from the invoice document created in SAP, so sales from sources such as POS, e-commerce platforms or dealer systems must first be transferred to SAP as invoices. This transfer is handled through existing integrations or a bulk invoice interface; after that, e-Archive generation, customer delivery and the daily report run automatically on the SAP side. If invoices are issued outside SAP and only the report is to be filed from SAP, that is a separate setup and is clarified during scoping.
How are e-Archive cancellations and returns handled in relation to the daily report?
An e-Archive invoice can be cancelled within the window regulation allows; the cancellation is created together with the SAP cancellation document and enters the daily report as a cancellation record. Errors discovered outside that window are corrected with a return invoice, which appears in its own daily report. Which report each invoice was sent in and with what status is tracked on the SAP document; when a report submission fails, an exception list is created and the report is resubmitted.