ERP & Accounting Integration: Logo, Netsis, Mikro & e-Invoice
We'd build an integration layer that synchronises accounts, stock, invoices, and orders two-way between e-commerce, field, and CRM and Logo, Netsis, or Mikro, automating e-Invoice/e-Archive and managing mismatches through an error queue.
In Turkey the accounting and account-ledger truth of almost every mid-sized and large business lives inside Logo, Netsis, or Mikro; but sales no longer arrive through a single channel. On one side an e-commerce site, on another a marketplace, on another the field sales team, on another a quote opened inside the CRM, all of them produce account, stock, invoice, and order data. In most businesses this data is still keyed into the ERP by hand: someone on the accounting team posts the morning's e-commerce orders into Logo one by one, another copies marketplace invoices out of Excel, another posts the collection a field rep brought back into the account ledger. The outcome is predictable: the same stock is sold across two channels, the account balance stays wrong for days, the e-Invoice is issued late, and month-end reconciliation turns into a nightmare. When we talk about ERP and accounting integration, this is exactly what we set out to solve: keeping the ERP as the central source of truth while connecting every channel around it in a two-way, automatic, and auditable way.
The Cost of Manual ERP Entry and Mismatch
E-commerce and marketplace orders are keyed into Logo/Netsis/Mikro by hand every morning; the accounting team spends 3 to 5 hours a day on data entry and an error rate of 3 to 10 percent creeps in per order.
Stock is updated in only one channel; when the same product sells from both the site and the marketplace, goods that do not exist get sold, leading to order cancellations and customer dissatisfaction.
The account balance is not real-time; a field rep visits the customer, takes an order without knowing the credit limit is full, the order gets stuck in the ERP, and the day is wasted.
e-Invoice/e-Archive is issued by hand or late; late submission to GİB, the wrong taxpayer type (e-Archive instead of e-Invoice), and lost UUID tracking pile up tax risk and rejected envelopes.
At month-end the two systems do not match; to find the source of the mismatch accounting spends days on Excel comparisons, closing slips, and management sees a reliable figure only at the weekend.
Our Approach
On ERP integration projects we'd first clarify the canonical data model: for which entity will which system be the single source of truth? Usually the ERP (Logo Tiger/Wings, Netsis, Mikro Fly) is the single truth for accounts, stock, and price; e-commerce or CRM is the truth for orders and customer interaction; GİB is the truth for invoices. Building an integration without drawing this ownership map means two systems writing the same field in opposite directions and entering an endless "who is right" loop. So we'd prefer to sit at a single table and decide the direction of every data field (ERP-to-outside, outside-to-ERP, or two-way) one by one; the architecture of the integration is born from that decision.
The second critical decision is the communication layer. Each ERP's access path differs: Logo Object services and Tiger/Wings tables for Logo, REST/OData services for Netsis, APIs or controlled database views for Mikro Fly. We do not make direct, synchronous calls to any of these; because when the ERP slows down or goes offline, the whole e-commerce site would lock up too. Instead we'd build an event-driven flow on RabbitMQ: when an order posts a message is produced, a worker picks it off the queue and writes it to the ERP idempotently. Even if the ERP is down for an hour the messages wait in the queue, get processed when it returns, and no order is lost. For older ERP versions with insufficient standard APIs we'd build an auditable RPA bridge with UiPath: a bridge that drives the ERP interface like a human but stays traceable.
The third layer is e-Invoice/e-Archive automation. When an order closes, an invoice draft is generated automatically, converted to UBL-TR format, and submitted to GİB through your chosen private integrator (Logo e-Çözümler, Uyumsoft, or Foriba). Whether the buyer is an e-Invoice taxpayer is queried automatically from the GİB taxpayer list; if they are, an e-Invoice is issued, if not, an e-Archive. Approval, rejection, cancellation, and objection states are tracked; a failed envelope lands in the error queue, is visible with its reason, and can be corrected and resent. UUID and KEP tracking is kept for audit. This turns tax compliance from a manually tracked task into a measurable flow.
The final layer is reconciliation and visibility. Even though the event-driven flow gives near-real-time consistency, small drifts in distributed systems are inevitable. So we'd build nightly reconciliation jobs: account balances, stock counts, and invoice totals in the ERP are compared against the external systems, a difference report is produced where there is a gap, and an alert is raised. All errors flow into Sentry and all events into an audit table in PostgreSQL; so the "the two systems do not match" surprise is caught the next morning rather than at month-end, and the root cause (rounding, VAT difference, missing mapping) quickly becomes visible.
Process
Data Ownership & Field Mapping
We decide which system is the single truth for accounts, stock, price, orders, and invoices. The direction of every data field (ERP-to-outside / outside-to-ERP / two-way) and its transformation rules are settled one by one.
ERP Adapter & Bridge
We write adapters for Logo Object, Netsis REST/OData, or Mikro Fly APIs; for older versions with weak standard APIs we build an auditable RPA bridge with UiPath. Every write is idempotent and keyed by an external reference.
Event-Driven Sync Layer
Order, stock, account, and collection events flow over RabbitMQ; workers write to the ERP. During ERP downtime messages wait in the queue, retry kicks in, and failures land in the dead-letter queue.
e-Invoice / e-Archive Automation
UBL-TR invoice generation through the Logo e-Çözümler / Uyumsoft / Foriba integrator, GİB taxpayer lookup, e-Invoice/e-Archive split, approval-rejection-cancellation tracking, UUID/KEP logging, and error-queue management.
Reconciliation, Monitoring & Go-Live
Nightly reconciliation jobs produce account/stock/invoice difference reports, with Sentry error tracking and a PostgreSQL audit log. Pilot on a single channel, then roll out to all channels after validation, with training and hyper-care.
Our Preferred Technology Stack
We typically reach for the following, adapted per project to your ERP version, integrator, and channel count.
Sıkça Sorulan Sorular
Let's Talk About Your ERP & Accounting Integration
Book a 15-to-30-minute discovery call, free, no commitment. We learn your ERP version, channels, and e-Invoice integrator, then come back with an architectural direction and a clear cost range.