Türkiye e-Invoice, e-Archive and e-Waybill Outbound and Inbound Cockpit
Short answer: A custom interface cockpit that sends billing documents and deliveries from SAP to the integrator as e-Invoice, e-Archive or e-Waybill, and receives incoming e-Invoices, matches them to the purchase order and parks them. The status, ETTN (UUID), recipient response and error message of every outbound and inbound electronic document are monitored on one screen; a failed document is corrected and resent from the same screen.
- Estimated effort
- L · 15–20 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- TR
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
VF31 prints or sends the billing output but does not show the status of the electronic document at GİB, the recipient's accept/reject response or the ETTN. Incoming e-Invoices are downloaded from the integrator portal and entered manually in MIRO; MIR4 only shows a document once it has been entered. The cockpit puts outbound and inbound documents in one list, matches an incoming invoice to the purchase order and parks it, and resends failed documents.
Who uses it? Accounting and billing teams, purchase invoice verification teams, shipping teams and SAP FI/SD support teams.
Closest standard alternatives
- VF31 Output from Billing Documents. Processes billing output; the GİB status, ETTN and recipient response of the electronic document are not tracked.
- MIR4 Display Invoice Document / Change Status. Shows an entered invoice document; does not receive the incoming e-Invoice from the integrator or match it to the order.
Localization and legal basis
Türkiye · Turkish Revenue Administration (GİB)
Legal basis: The e-Invoice, e-Archive Invoice and e-Waybill schemes regulated by Turkish Tax Procedure Law General Communiqué No. 509.
Sending and receiving run through the interface of the company's private integrator or the Revenue Administration (GİB) portal; the connection is adapted to the integrator during installation.
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| VBRKBilling Document Header | Outbound billing header: billing type, date, payer and amount (driving table) | Read | ECC + S/4 |
| VBRPBilling Document: Item Data | Billing items: material, quantity, net value and tax | Read | ECC + S/4 |
| LIKPDelivery Header | Deliveries with goods issue for the e-Waybill | Read | ECC + S/4 |
| KNA1Customer Master (General Section) | Buyer name, address and tax number | Read | ECC + S/4 |
| LFA1Vendor Master (General Section) | Finding the vendor by the sender's tax number on an incoming e-Invoice | Read | ECC + S/4 |
| EKKOPurchasing Document Header | Matching the purchase order by the order reference in the incoming invoice | Read | ECC + S/4 |
| RBKPDocument Header: Incoming Invoice | Logistics invoice document parked from the incoming e-Invoice | Write | ECC + S/4 |
BAPIs and functions used
- BAPI_INCOMINGINVOICE_PARKPark Incoming Invoice. Creates the incoming e-Invoice matched to a purchase order as a parked invoice
- SCMS_XSTRING_TO_BINARYConvert XSTRING to Binary Table. Converts the UBL-TR XML and PDF content to binary for sending and archiving
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BKPF-BUKRS | Yes | 1000 |
| S_FKDAT | Document date | Range / multiple | VBRK-FKDAT | Yes | 01.11.2026 – 17.11.2026 |
| R_OUT | Outbound documents (e-Invoice, e-Archive, e-Waybill) | Radio button | — | No | X |
| R_IN | Incoming e-Invoices | Radio button | — | No | — |
| S_STAT | Document status | Range / multiple | — | No | Hata, Red |
| P_TEST | Test mode (check without sending or parking) | Checkbox | — | No | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Direction | Calculated Outbound or inbound |
| 2 | Scenario | Calculated e-Invoice when the recipient is a registered user, otherwise e-Archive; e-Waybill for deliveries |
| 3 | SAP document | Calculated VBRK-VBELN for invoices, LIKP-VBELN for waybills, RBKP-BELNR for incoming invoices |
| 4 | Document date | VBRK-FKDAT |
| 5 | Counterparty | Calculated KNA1-NAME1 for outbound, LFA1-NAME1 for inbound |
| 6 | Net amount | VBRK-NETWR |
| 7 | Currency | VBRK-WAERK |
| 8 | ETTN (UUID) | Calculated Universally unique number assigned to the document by the integrator |
| 9 | Status | Calculated Queued, sent, accepted, rejected, parked or error |
| 10 | Message | Calculated Message returned by the integrator, GİB or the matching check |
Sample result list
| Direction | Scenario | SAP document | Document date | Counterparty | Net amount | Currency | ETTN (UUID) | Status | Message |
|---|---|---|---|---|---|---|---|---|---|
| Outbound | e-Fatura | 90031482 | 11/16/2026 | Örnek Tekstil A.Ş. | 184,500 | TRY | 3f2a9c1e-7b4d-4e21-9a6f-2c8d5b1e0a47 | Accepted | The recipient accepted the invoice |
| Outbound | e-Arşiv | 90031490 | 11/16/2026 | Demo Retail Ltd. | 12,750 | TRY | Error | City is missing in the recipient address | |
| Inbound | e-Fatura | 5105603318 | 11/15/2026 | Anadolu Ambalaj San. Ltd. | 46,200 | TRY | a81c47d2-0e5f-4b93-8c1a-6d2e9f7b3c05 | Parked | Matched to purchase order 4500021876 |
How does the program work?
- Outbound documents: billing documents from VBRK and deliveries with goods issue from LIKP are read for the selected company code and date range. The recipient’s tax number is looked up in the integrator’s registered user list; if registered, the e-Invoice scenario is used, otherwise e-Archive.
- The document is built in UBL-TR format: seller and buyer data come from KNA1, items from VBRP, taxes from the billing conditions. XML and PDF are converted to binary and sent to the integrator service.
- The ETTN and status (queued, sent, accepted, rejected, error) returned by the integrator are stored in the program’s status record; a scheduled job polls the status of open documents periodically.
- Inbound documents: new e-Invoices are received from the integrator. The vendor is found in LFA1 by the sender’s tax number and the purchase order in EKKO by the order reference in the document.
- A matched invoice is parked with BAPI_INCOMINGINVOICE_PARK (RBKP); the invoice verification team checks and posts it in MIR4. Unmatched documents wait in the cockpit with the reason.
- For commercial invoices the recipient response (accept/reject) is tracked; for a rejected outbound invoice the cancel-and-reissue step is started from the cockpit.
- In test mode no document is sent or parked; only the XML to be created and the matching result are shown.
Performance notes
Limit outbound documents to those not yet sent or still open; query statuses in batches through the integrator's bulk query service. Run inbound receipt and status updates as a background job every 15-30 minutes.
Features
- ALV list (sort, filter, subtotals)
- Double-click drill-down to the document From a row you can jump to the invoice, delivery or parked document and view the XML and PDF.
- Runs as a background job Sending, inbound receipt and status queries run as scheduled jobs.
- Test mode (check without posting)
- Line-by-line result and error log
- Send the result by email A daily summary e-mail can be sent to the responsible team for failed documents.
Authorization objects
- F_BKPF_BUKDocument display authorization by company code
- V_VBRK_FKABilling authorization by billing type
- M_RECH_WRKInvoice verification (parking) authorization by plant
Frequently asked questions
Is it tied to a specific integrator?
No. The document creation and status logic stays the same; only the connection layer is adapted to the service of the company's private integrator during installation. If the integrator changes, only this layer is updated.
How does it decide between e-Invoice and e-Archive?
The recipient's tax number is looked up in the GİB registered user list. If registered, an e-Invoice is issued, otherwise an e-Archive invoice. The list is refreshed daily, so newly registered customers move to the e-Invoice scenario automatically.
Is it needed on S/4HANA?
On S/4HANA, SAP Document and Reporting Compliance offers the Türkiye scenarios as standard; if it is licensed and set up, it is evaluated first. The cockpit covers the same need on ECC systems or in integrator setups where the standard solution is not used.
Related reports
Duplicate Vendor Invoice Check Report
A custom ALV report that compares posted vendor invoices by reference number, amount and document date and lists possible duplicates in groups. …
Blocked Vendor Invoices with Price and Quantity Variance Report
A custom ALV report that lists vendor invoices blocked for payment in invoice verification with the block reason, the received quantity, the price …
Billing Documents Not Posted to Accounting Report
A custom ALV report that lists billing documents which exist in SD but have no accounting document yet, with the reason code, age and amount. At …
Sales Order – Delivery – Invoice Status Report
A custom ALV report that shows every sales order item on the same line as its delivery and invoice documents. You see in one list which orders have …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.