TREN
Request a Demo

TecT Standart

Core e-transformation hub

End-to-end, flexible and secure creation, submission to the Turkish Revenue Administration (GİB), receipt and legal archiving of electronic documents. Beyond compliance, it makes your financial data more transparent.

Request a Demo See how it looks in SAP
Diagram: e-Invoice, e-Archive, e-Waybill and e-Ledger documents are managed from SAP screens; TecT Standart sends and receives them to and from GİB systems over TecT BTP Bridge.Turkish Revenue Administration (GİB)e-document systemssend · receive · statusTecT StandartProcessing outside SAPe-InvoiceSend, receive, statuse-ArchiveReporting and storagee-WaybillDispatch and responsese-LedgerCertificates and storageTecT BTP BridgeSAP R/3 · S/4HANA · Public CloudDocuments are managed from SAP screens

Modules

Four document types, one hub

These four document types are the e-document mandates of Türkiye; mandates in other countries are covered under Global Compliance. Every module is operated from SAP screens; processing runs outside SAP through TecT BTP Bridge, and documents are sent and received via GİB systems.

e-Invoice

The electronic invoice that replaces paper, created and delivered through GİB. Issue, send, receive and track status directly from SAP.

Basic and commercial invoice scenarios

e-Archive

Electronic creation, reporting and GİB-standard storage of invoices issued to recipients outside the e-Invoice system.

e-Archive report consistency check

e-Waybill

The electronic waybill that replaces paper; matching with goods issue and managing recipient responses from inside SAP.

Waybill–invoice–goods receipt chain

e-Ledger

Production in e-format of the journal and general ledgers required under the Tax Procedure Law (VUK) and the Turkish Commercial Code (TTK), submission of their certificates to GİB, and storage.

Journal and general ledger certificates

Life cycle

What happens to a document after it is issued in SAP?

All four document types follow the same path. The document is issued from SAP screens; its format is converted and its mandatory fields checked in the TecT processing layer; it travels over TecT BTP Bridge to the systems of the Turkish Revenue Administration (GİB); the recipient's acceptance, rejection or cancellation is written back to the SAP document; and the document enters the legal archive. No native ABAP add-on is installed for this flow, the same integration covers R/3 through Public Cloud, and regulatory changes are updated on the product side.

Diagram: the life cycle of an electronic document — issued in SAP, prepared in the TecT processing layer, sent to the systems of the Turkish Revenue Administration (GİB), its response written back to the SAP document, and archived to legal standards.Issued in SAPThe invoice, waybill or ledger entry is created from SAP screensPrepared in the TecT processing layerFormat conversion and mandatory-field checks run outside SAPSent to GİB systemsThe document travels over TecT BTP BridgeResponse written back to SAPAcceptance, rejection or cancellation updates the SAP documentKept in the legal archiveDocuments and ledger certificates are archived to GİB standards

Inside SAP

Documents are managed inside SAP

Outgoing e-Document Panel: preview, send, status update, GİB cancellation and bulk PDF download on one screen.

Outgoing e-Document Panel · document list and e-Invoice view
Outgoing e-Document Panel · document list and e-Invoice view

Artificial intelligence

AI in document processes

Capabilities added to TecT Standart modules; every answer is generated from product data.

e-Invoice & e-Archive

  • Natural-language document queries
  • 3-way matching suggestions on incoming invoices
  • Duplicate invoice and anomaly detection

e-Waybill

  • Waybill–invoice–goods receipt chain control
  • Delivery delay alerts

Technology

The same product from SAP R/3 to Public Cloud

TecT Standart runs outside your SAP system, preserves your Clean Core and talks to every SAP release through TecT BTP Bridge.

  • No native ABAP add-ons
  • The same integration for SAP R/3, S/4HANA and Public Cloud
  • GİB regulatory changes are updated on the product side
Diagram: SAP Public Cloud, SAP S/4HANA and SAP R/3 connect through TecT BTP Bridge to GİB, banks and global e-invoicing networks; the SAP core is not modified.YOUR SAP RELEASECONNECTED SYSTEMSSAP Public CloudFuturefully isolated cloudSAP S/4HANAModernhigh performance, agileSAP R/3Legacystable data extractionTecT BTP BridgeGİBe-document exchangeBanksEHÖ · DBS · paymentsGlobal e-invoicing9 country mandatesClean CoreNo changes to the SAP core

Start with TecT Standart

TecT Standart can be used on its own or together with TecT Plus. Tell us your SAP release in your demo request, and we'll map the rollout path and e-document scope together.

Your request is delivered to info@tecteknoloji.com; how we process your details is explained in our Privacy Notice (KVKK).