{"audience":"Accounting and billing teams, purchase invoice verification teams, shipping teams and SAP FI/SD support teams.","authorization_objects":[{"note":"Document display authorization by company code","object":"F_BKPF_BUK"},{"note":"Billing authorization by billing type","object":"V_VBRK_FKA"},{"note":"Invoice verification (parking) authorization by plant","object":"M_RECH_WRK"}],"components":[],"countries":[{"country":"TR","legal_basis":"The e-Invoice, e-Archive Invoice and e-Waybill schemes regulated by Turkish Tax Procedure Law General Communiqué No. 509.","note":"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."}],"effort_days_max":20,"effort_days_min":15,"effort_size":"L","faq":[{"a":"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.","q":"Is it tied to a specific integrator?"},{"a":"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.","q":"How does it decide between e-Invoice and e-Archive?"},{"a":"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.","q":"Is it needed on S/4HANA?"}],"features":[{"code":"alv","label":"ALV list (sort, filter, subtotals)","note":""},{"code":"drilldown","label":"Double-click drill-down to the document","note":"From a row you can jump to the invoice, delivery or parked document and view the XML and PDF."},{"code":"background","label":"Runs as a background job","note":"Sending, inbound receipt and status queries run as scheduled jobs."},{"code":"test_run","label":"Test mode (check without posting)","note":""},{"code":"log","label":"Line-by-line result and error log","note":""},{"code":"email","label":"Send the result by email","note":"A daily summary e-mail can be sent to the responsible team for failed documents."}],"functions":[{"name":"BAPI_INCOMINGINVOICE_PARK","role":"Creates the incoming e-Invoice matched to a purchase order as a parked invoice"},{"name":"SCMS_XSTRING_TO_BINARY","role":"Converts the UBL-TR XML and PDF content to binary for sending and archiving"}],"gap":"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.","id":"tr-einvoice-earchive-ewaybill-cockpit","industries":[],"input_columns":[],"kind":"program","language":"en","lastmod":"2026-11-17","logic":"1. 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.\n2. 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.\n3. 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.\n4. 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.\n5. 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.\n6. 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.\n7. In test mode no document is sent or parked; only the XML to be created and the matching result are shown.","module":"FI","object_type":"interface","output_columns":[{"calculated":true,"formula":"Outbound or inbound","label":"Direction","source_field":null,"source_table":null},{"calculated":true,"formula":"e-Invoice when the recipient is a registered user, otherwise e-Archive; e-Waybill for deliveries","label":"Scenario","source_field":null,"source_table":null},{"calculated":true,"formula":"VBRK-VBELN for invoices, LIKP-VBELN for waybills, RBKP-BELNR for incoming invoices","label":"SAP document","source_field":null,"source_table":null},{"calculated":false,"formula":"","label":"Document date","source_field":"FKDAT","source_table":"VBRK"},{"calculated":true,"formula":"KNA1-NAME1 for outbound, LFA1-NAME1 for inbound","label":"Counterparty","source_field":null,"source_table":null},{"calculated":false,"formula":"","label":"Net amount","source_field":"NETWR","source_table":"VBRK"},{"calculated":false,"formula":"","label":"Currency","source_field":"WAERK","source_table":"VBRK"},{"calculated":true,"formula":"Universally unique number assigned to the document by the integrator","label":"ETTN (UUID)","source_field":null,"source_table":null},{"calculated":true,"formula":"Queued, sent, accepted, rejected, parked or error","label":"Status","source_field":null,"source_table":null},{"calculated":true,"formula":"Message returned by the integrator, GİB or the matching check","label":"Message","source_field":null,"source_table":null}],"parameters":[{"example":"1000","kind":"select_option","label":"Company code","name":"S_BUKRS","ref_field":"BKPF-BUKRS","required":true},{"example":"01.11.2026 – 17.11.2026","kind":"select_option","label":"Document date","name":"S_FKDAT","ref_field":"VBRK-FKDAT","required":true},{"example":"X","kind":"radio","label":"Outbound documents (e-Invoice, e-Archive, e-Waybill)","name":"R_OUT","ref_field":"","required":false},{"example":"","kind":"radio","label":"Incoming e-Invoices","name":"R_IN","ref_field":"","required":false},{"example":"Hata, Red","kind":"select_option","label":"Document status","name":"S_STAT","ref_field":"","required":false},{"example":"X","kind":"checkbox","label":"Test mode (check without sending or parking)","name":"P_TEST","ref_field":"","required":false}],"part_of":[],"performance":"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.","process":"O2C","quote_url":"https://nekuhub.com/en/request-a-quote/?report=tr-einvoice-earchive-ewaybill-cockpit","related":["fi-duplicate-vendor-invoice-check","mm-blocked-invoices-variance","sd-billing-not-posted-to-accounting","sd-order-delivery-invoice-status"],"releases":[],"source":"custom","standard_alternatives":[{"note":"Processes billing output; the GİB status, ETTN and recipient response of the electronic document are not tracked.","tcode":"VF31"},{"note":"Shows an entered invoice document; does not receive the incoming e-Invoice from the integrator or match it to the order.","tcode":"MIR4"}],"summary":"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.","tables":[{"access":"read","join_on":"","role":"Outbound billing header: billing type, date, payer and amount (driving table)","table":"VBRK","variant":"both"},{"access":"read","join_on":"VBRP-VBELN = VBRK-VBELN","role":"Billing items: material, quantity, net value and tax","table":"VBRP","variant":"both"},{"access":"read","join_on":"LIKP-VBELN = VBRP-VGBEL","role":"Deliveries with goods issue for the e-Waybill","table":"LIKP","variant":"both"},{"access":"read","join_on":"KNA1-KUNNR = VBRK-KUNAG","role":"Buyer name, address and tax number","table":"KNA1","variant":"both"},{"access":"read","join_on":"LFA1-STCD2 = gönderen vergi numarası","role":"Finding the vendor by the sender's tax number on an incoming e-Invoice","table":"LFA1","variant":"both"},{"access":"read","join_on":"EKKO-EBELN = belgedeki sipariş no AND EKKO-LIFNR = LFA1-LIFNR","role":"Matching the purchase order by the order reference in the incoming invoice","table":"EKKO","variant":"both"},{"access":"write","join_on":"RBKP-LIFNR = LFA1-LIFNR","role":"Logistics invoice document parked from the incoming e-Invoice","table":"RBKP","variant":"both"}],"title":"Türkiye e-Invoice, e-Archive and e-Waybill Outbound and Inbound Cockpit","url":"https://nekuhub.com/en/programs/turkey-e-invoice-e-archive-e-waybill-cockpit/","vendor_id":"nekudos"}