You do not have to drop Mikro or Luca
Most exporters and importers in Turkey keep their books in an accounting program such as Mikro or Luca. When they look at trade-specific software, many ask the wrong question: “How do I move my customers off Mikro?” The right question is: “How do I speed up my export operation without touching Mikro?”
Ripping out Mikro or Luca means touching the backbone of accounting, which is both costly and risky. Sighthem takes the opposite approach: your accounting software stays in place, Sighthem does the work it cannot, and hands the finished data back to it in one click.
The accounting backbone stays in Mikro
Mikro and Luca are primarily accounting and statutory-ledger systems. E-ledger, tax filings, VAT and the financial-adviser process all flow through them. Replacing that legal backbone means data migration, retraining and compliance risk. No firm wants to risk its accounting system just because it adopted a new operations tool. So the right design is to leave accounting where it is and run the export side as a separate layer.
Where Mikro falls short in foreign trade
Accounting tools are domestic-accounting first; the export operation is their weak spot. In most firms these tasks run scattered across spreadsheets, email and WhatsApp:
- Prospecting and lead tracking, email campaigns, communication history
- Multi-currency quotes and proforma invoices
- Orders, warehouse, stock, production and bill of materials (BOM)
- Shipments, container tracking, packing lists and dispatch documents
- Letters of credit (L/C), inward processing (DIIB), customs and HS codes, sanctions screening
- Lot and expiry-date traceability
Sighthem fills exactly this gap. Your competitor is not Mikro; it is the chaos of scattered spreadsheets and disconnected communication.
The coexistence model: which work lives where
A clear division of labor both speeds up the operation and stays out of the accountant’s way:
| Task | Where it lives |
|---|---|
| Statutory accounting, e-ledger, tax filings | Mikro / Luca |
| E-invoice / e-archive issuance and GIB submission | Mikro / Luca (or integrator) |
| Customer and lead pipeline, email, campaigns | Sighthem |
| Quotes, multi-currency proforma | Sighthem |
| Orders, warehouse, stock, production, BOM | Sighthem |
| Shipments, containers, packing lists, customs/HS, L/C, DIIB | Sighthem |
| Sync of customer, stock and order cards | Sighthem → Mikro (CSV/XLSX) |
| Invoice data for e-invoicing | Sighthem → Mikro / Luca (UBL/XML) |
Run the operation in Sighthem: enter the customer and order, manage production and shipping, prepare the invoice. Then export customers/stock/orders as CSV and the invoice as UBL/XML into Mikro or Luca. The accountant only imports; no data is keyed twice.
Exporting customers, stock and orders into Mikro
Sighthem exports customer accounts, product/stock cards and sales orders with the Turkish field headers each program’s own import screen expects: DB EXIM for Mikro, ExcelTrans for Logo, Transfer for Netsis. Output is CSV (UTF-8 BOM, semicolon) or Excel (XLSX). You map the columns once in the program’s transfer screen and reuse it, so you never type the same data twice.
Sending the invoice as UBL/XML to Mikro, Luca and any integrator
This is the critical part. You download the invoice you prepared in Sighthem as a UBL-TR XML, then upload it into your accounting program or e-invoice integrator to be issued as an e-invoice. On the final-invoice step of the Dispatch screen the “e-Invoice XML (UBL)” button, and on the Invoices page the XML button next to each invoice, generate the file in one click.
The file works not only with Mikro or Luca but with any e-invoice program or integrator that accepts UBL/XML import; it is not tied to a single vendor. UBL-TR 1.2 is the official and only standard e-invoice format in Turkey. Mikro and Luca are the most common examples; the same file uploads cleanly into Logo eLogo, Nilvera, EDM, Uyumsoft, Izibiz and Foriba, and any other UBL-TR-capable system. Sighthem selects the profile automatically: export (IHRACAT) for a foreign buyer, commercial e-invoice (TICARIFATURA) for domestic.
Export e-invoice (UBL-TR): what to watch
The export e-invoice is GIB’s most detailed profile and requires several mandatory fields, which Sighthem fills automatically: foreign buyer details, HS code per line, Incoterms delivery term, transport-mode code and VAT-exemption reason. The document title prints as COMMERCIAL INVOICE for the foreign buyer.
The official invoice serial number is always assigned by your e-invoice program (Mikro, Luca or the integrator) from its own GIB series; the number in the XML is only a placeholder. Also, for exports every product must have its HS code filled in your catalog, otherwise the export e-invoice will be incomplete.
How the transition starts
The transition starts not by moving accounting, but by bringing the operation together:
- Import customer and product/stock cards into Sighthem once (from Excel).
- Start running new quotes, orders and shipments in Sighthem.
- At invoicing time, download the UBL/XML and upload it into Mikro or Luca.
- At month end, sync customer/stock movements to accounting via CSV.
In this model the accounting team changes nothing, while the sales and operations team prepares proformas, dispatch documents and invoices in seconds instead of minutes. Data fed from a single source removes duplicate entry and copy-paste errors.
Does Sighthem replace Mikro or Luca?
No. Sighthem does not replace your accounting software; it sits on top of it. Statutory accounting, e-ledger and tax filings stay in Mikro or Luca, while Sighthem runs the export operation (prospecting, quote/proforma, orders, warehouse, production, shipping, L/C, customs documents) and hands the finished data back to your accounting tool. It works without disturbing your accountant.
How do I move an invoice created in Sighthem into Mikro or Luca?
You download the invoice as a UBL-TR (e-invoice) XML and import it from your e-invoice program (Mikro, Luca, Logo eLogo, Nilvera, etc.). In Sighthem it downloads in one click via the "e-Invoice XML (UBL)" button on the Dispatch screen or the XML button on the Invoices page. For customer, stock and order records there is a separate CSV/XLSX export.
Is the e-invoice XML compatible only with Mikro and Luca?
No, it is not tied to a single vendor. Because it is produced in the UBL-TR 1.2 standard, it is compatible with any e-invoice program or integrator that accepts UBL/XML import. Mikro and Luca are the most common examples; the same file also uploads into Logo eLogo, Nilvera, EDM, Uyumsoft, Izibiz and Foriba, and any other UBL-TR-capable system. Both domestic (TICARIFATURA) and export (IHRACAT, via Customs) profiles are supported, and the XML passes GIB schema validation.
My accountant uses Mikro. Can I use Sighthem without disrupting their setup?
Yes, and that is the recommended pattern. The accountant keeps working in Mikro; Sighthem feeds them clean, complete data (customers, stock, orders, invoices) in a ready format. The system does the data entry, not you, and the accountant simply imports it. There is no need to rip out Mikro, which removes the biggest source of resistance to adoption.
Can I export customer and stock cards into Mikro?
Yes. Sighthem exports customer accounts, product/stock cards and sales orders as CSV (UTF-8 BOM) or Excel (XLSX) with the Turkish field headers expected by the import screens of Mikro (DB EXIM), Logo (ExcelTrans) and Netsis (Transfer). You map the columns once in the program’s own transfer screen and reuse it afterwards.
Are export invoices supported?
Yes. Because the buyer is abroad, the export invoice is produced in the IHRACAT profile that routes through the Ministry of Customs and Trade: the foreign buyer details, HS code (per line), Incoterms delivery term, transport mode and VAT exemption reason are filled automatically. The document title prints as COMMERCIAL INVOICE for the foreign buyer.
Does this XML also cover e-Archive invoices?
This export covers e-Invoice (between registered taxpayers) and the export e-invoice. For e-Archive (an invoice to a buyer that is not an e-invoice taxpayer), your accounting software or integrator issues it; Sighthem provides the invoice data, and the GIB submission and serial number are assigned on the integrator side.
When does it make sense to move fully to Sighthem?
For small exporters with no accountant, newly founded firms, or those without an established accounting tool, consolidating into one system can make sense. But if you already run a settled Mikro/Luca setup, the right strategy is not to switch but to add a layer: accounting stays there, and the operation speeds up in Sighthem.