e-SMM in Turkey: How the Electronic Self-Employment Receipt Works and How to Automate It
What is e-SMM in Turkey, who must issue it, and which route fits: GİB Portal or private integrator? How to link receipts to payments and file them well.
Phone: 0 (552) 380 25 25 | Weekdays 10:00–18:00 · Technical support 24/7
API integration lets your ERP, e-invoicing, carrier, marketplace and payment systems pass data to one another without anyone re-keying it. We connect the software you already use: marketplace orders flow into Logo, SAP or Mikro, invoices reach the Turkish Revenue Administration (GIB) through your e-invoice provider, and tracking numbers go to the customer. Your team only handles failed records.
A familiar picture: an order arrives from a marketplace, someone retypes it into the ERP, someone else books the shipment on the carrier's portal, and accounts raise the invoice separately. Every hand-off costs time, lets in errors such as wrong quantities or missing addresses, and leaves stock figures that no screen shows correctly.
Integration automates every link in that chain: stock updates across every sales channel at once, dealer orders placed on a B2B portal reach the ERP without being retyped, and dispatch scans in a warehouse management system (WMS) book the shipment with the carrier. For international companies operating in Turkey, this is often the quickest way to fit a global ERP into local e-invoicing and carrier requirements.
Two-way links with Logo Tiger/GO/iK, SAP Business One, Mikro, Netsis, Nebim and bespoke ERPs. Orders, stock, customer accounts, invoices and delivery notes stay identical on both sides. If the ERP has no API, we set up a secure database-level transfer instead.
e-Invoice and e-Archive documents sent through your accredited provider (Uyumsoft, Logo, Foriba, Paraşüt and others). Invoices are generated when the order is confirmed rather than raised one by one; rejected documents trigger an alert and are resubmitted once corrected.
Connections to MNG, Yurtiçi, PTT, Sürat, Aras and other carriers. When an order is ready, the shipment is booked, the label and tracking number are returned, and the customer is notified by SMS and email. Nobody has to log in to the carrier portal.
Trendyol, Hepsiburada, n11, Amazon, IdeaSoft, Shopify or your own web shop, connected to your ERP and accounting. Orders are pulled in, stock and prices are pushed to every channel, and invoices are raised automatically, which cuts the risk of selling the same item twice.
iyzico, PayTR, Stripe, Yapı Kredi and other bank virtual POS services, including 3D Secure, instalments and refunds. Payment notifications post to the right customer account in your ERP or accounting system, so reconciliation no longer means combing through bank statements.
Where no ready-made connector exists, we build middleware that translates between formats: XML, JSON, CSV, EDIFACT. Failed transfers are retried automatically and every transaction is logged, so when something goes wrong you can see exactly where it stopped.
We start by agreeing which system holds the master record for each type of data; most sync conflicts come from skipping that decision. Then we choose the method that suits your systems. If you need to work with a legacy application that has no interface at all, RPA bots are another option.
For a wholesale food distributor in Gaziantep, we put live an integration that carries Trendyol and n11 orders into Logo ERP and connects them to GIB e-invoicing, in 3 weeks. Manual entry of more than 200 orders a day was no longer needed.
API integration lets your ERP, e-invoicing, carrier, marketplace and payment systems pass data to one another without anyone re-keying it. A marketplace order flows into the ERP on its own, the invoice reaches the Turkish Revenue Administration (GIB) through your e-invoice provider and the tracking number goes to the customer. Your existing software stays in place; your team only handles failed records.
ERPs including Logo Tiger/GO/iK, SAP Business One, Mikro, Netsis, Nebim and bespoke systems; e-invoice providers such as Uyumsoft, Logo, Foriba and Paraşüt; carriers including MNG, Yurtiçi, PTT, Sürat and Aras; marketplaces and shops such as Trendyol, Hepsiburada, n11, Amazon, IdeaSoft and Shopify; and payment services such as iyzico, PayTR, Stripe and bank virtual POS.
When an order is confirmed, the invoice is generated automatically and sent as an e-Invoice or e-Archive document through your accredited provider to the Turkish Revenue Administration (GIB). Nobody raises and uploads invoices one by one. A rejected or failed document triggers an alert and is resubmitted once corrected.
Yes. If an ERP has no API, we set up a secure database-level transfer. Where no ready-made connector exists, we build custom middleware that translates between XML, JSON, CSV and EDIFACT. For legacy applications with no interface at all, RPA bots are another option.
Failed transfers are retried automatically and every transaction is logged, so you can see exactly where a record stopped and resend it once fixed. At high volumes, messages are held in a RabbitMQ or Redis queue, and connections are encrypted with SSL and OAuth2.
It depends on how many systems are involved and whether they offer APIs; the timeline is set out in the written proposal. As an example, we put live an integration for a wholesale food distributor in Gaziantep that carries Trendyol and n11 orders into Logo ERP and connects them to GIB e-invoicing in 3 weeks, removing manual entry of more than 200 orders a day.
Have a different question? Ask Us