What Is Luca Net?
Luca Net is the cloud application that Luca — the accounting software most widely used by accountants in Türkiye — opens to businesses. Invoices, customer accounts, stock, dispatch notes, collections and payments are kept in Luca Net, and your accountant sees the same records from their own Luca package. That is why a business on Luca Net does not split its books across two separate tools.
The problem starts when order volume grows. Entering every order from your e-commerce site and marketplaces into Luca Net by hand — opening the customer account, issuing the invoice, recording the collection — becomes a full-time job at a few dozen orders a day. Luca Net offers a set of REST services so this work can be done from outside; we connect those services to your sales channels.
What Is İşNet and How Does It Work with Luca Net?
İşNet is a private integrator authorized by GİB, the Turkish Revenue Administration. Your e-fatura and e-arşiv documents reach GİB through İşNet. An electronic invoice issued in Luca Net is passed to İşNet through Luca Net’s dispatch service; if your account is linked to the Türmob integrator, the same service sends it to Türmob.
This two-step structure matters for the integration:
- The invoice is written to Luca Net — with customer, lines, VAT, discounts, withholding and exemption codes
- The document is sent to the integrator — İşNet assigns the invoice its series and sequence number
- The status is read back — the invoice’s current status at GİB and its PDF link are queried
- It reaches the customer — the PDF link is added to the order email or the customer panel
Many off-the-shelf plugins only do the first step and leave the invoice as a draft in Luca Net. We automate the chain end to end.
What Can Be Transferred to Luca Net?
Luca Net’s services go well beyond invoices. We pick the scope based on your business flow:
Customer and Stock Cards
- Customer card: A new buyer gets a customer account automatically; existing accounts are found by tax ID or national ID, so duplicates are not created
- Customer update and balance query: Accounts are updated when an address or title changes, and balances can be read
- Stock card: Your products are opened as stock cards with units and ledger account codes, and the stock list can be read
Invoices, E-Fatura and E-Arşiv
- Sales invoice: Including currency and exchange rate, discounts, withholding, VAT exemption, special base and due date
- Online-sale e-arşiv: Payment type (card, bank transfer, cash on delivery, payment intermediary), payment date and web address are filled from the order
- Dispatch to the integrator and status query: Sending to İşNet or Türmob, current status and PDF link
- Order linkage: The order number and date are written to the invoice, so order-to-invoice matching survives reconciliation
Dispatch Notes and E-İrsaliye
For goods that ship, dispatch notes and e-irsaliye are transferred to Luca Net, including shipment date, driver and trailer details. If you have a shipping integration, the dispatch note is created together with the shipment.
Collections, Payments and Accounting Records
- Collections: Collections from your payment gateway or marketplace settlement are posted to the customer account
- Payments: Supplier payments are recorded
- Journal entries and ledger accounts: Items such as marketplace commissions and shipping deductions are posted as journal entries
- Expense vouchers: Issued for purchases from individuals who are not taxpayers
Order Flow for Marketplaces and E-Commerce
Trendyol, Hepsiburada and Other Marketplaces
Marketplace orders are pulled from the API at set intervals, turned into invoices in Luca Net and sent to İşNet. Commissions and service fees deducted by the marketplace can be read from the settlement report and posted as journal entries, keeping the gap between gross sales and net settlement visible in the books.
Shopify, ikas, WooCommerce and Ticimax
Invoicing is triggered when an order on your e-commerce site moves to “paid” or “shipped”. We decide together at setup which status should trigger the invoice.
Corporate vs. Individual Buyers
If the buyer entered a tax ID and is an e-fatura taxpayer, an e-fatura is issued; otherwise an e-arşiv. Because marketplaces often do not share an individual buyer’s national ID, we define the default rule for that case at setup.
Problems We See in the Field
The four most common problems in Luca Net integrations and how we prevent them:
- Duplicate invoices. A request retried after a network failure writes the same invoice twice. Fix: send every document with a unique integration ID tied to the order; Luca Net does not accept the same ID twice.
- Period errors. A Luca Net session is opened for a specific company and fiscal period; documents dated outside the period are rejected. If the period code is not updated at year end, January orders are not invoiced. Fix: handle the period rollover automatically.
- Invoices stuck as drafts. If the invoice is written to Luca Net but never sent to the integrator, it never reaches GİB. Fix: make dispatch and status queries part of the flow, and report invoices that could not be sent.
- Missing e-arşiv fields. Payment type and web address are mandatory on online-sale e-arşiv invoices; if they are empty, the invoice is rejected. Fix: map these fields from the order for every sales channel.
Integration Process
1. Discovery (1-2 Days)
- Your sales channels, order volume and invoicing rules are reviewed
- Ledger account codes and customer/stock creation rules are agreed with your accountant
- Scope is set: invoices only, or collections, dispatch notes and journal entries as well
2. Setup in the Test Environment (3-5 Days)
- The connection is built in the test environment opened by Luca Net’s technical team
- Invoice, e-arşiv, return and collection scenarios are tested with real order samples
- Your accountant checks the test documents
3. Go-Live and Monitoring
- Switch to the live company and period credentials
- Every invoice and integrator status is monitored in the first days
- Under a maintenance agreement, Luca Net service updates and regulatory changes are tracked
Total timeline: 1-2 weeks for invoices and e-arşiv only; 3-4 weeks for a full setup including customer accounts, stock, collections and dispatch notes. Luca Net and İşNet licenses stay on your side; setup, maintenance and support come from us.
If you prefer to run your books in a panel other than Luca, also consider our Paraşüt integration or Bir-Fatura integration.
Why Zeisoft?
- End-to-end flow: We don’t leave the invoice in Luca Net; we send it to İşNet and read its status back
- Aligned with your accountant: We set up ledger codes and posting rules together with your accountant
- Multi-channel experience: We build integrations that work with marketplaces, e-commerce platforms and payment gateways
- Safe retries: With duplicate-record protection, documents are not doubled after an outage
- Maintenance: We track Luca Net service versions and e-document regulations and keep the integration current
Get in touch to move your orders into Luca Net automatically and have your e-invoices issued through İşNet on their own. Let’s map your flow together on a free discovery call.