# Accounting and ERP integration: connecting your website and CRM to Logo, Mikro or Paraşüt

> Accounting software integration sends sales data from your online shop or CRM into accounting and ERP systems such as Logo, Mikro or Paraşüt, and brings stock and balances back where needed. The usual data is customer accounts, stock, orders, invoices and payments. If the software has an API, the link is direct; if not, a database, a local service or file transfer is used. Before building, decide which system owns each piece of data.

- URL: https://radkod.com/en/blog/accounting-erp-integration
- Publisher: RadKod
- Published: 2026-09-10

## In short

- Accounting software integration usually moves customer accounts, stock, orders, invoices and payments.
- Each type of data gets one owner system, agreed on day one.
- With an API the link is direct. Without one, a local service, database reads or file transfer can do the job.
- E-invoicing is often issued from the accounting system or its provider, so both are designed together.
- Your accounting team and accountant should check test records before go-live.

## What is accounting software integration?

Accounting software integration is a software link that moves data between the system where you sell and the system where you keep the books, with no retyping. Sales happen on your website, a marketplace or in your CRM. Records live in the accounting software. Without a link, someone enters every order, customer and payment a second time. That costs hours and produces errors that surface at month end.

We use Logo, Mikro and Paraşüt as examples because they are common in Turkey. The same principles apply to other accounting and [ERP](/en/glossary/erp) systems. We have no partnership with these vendors. They are simply the names we meet most often.

## What data flows in an accounting integration?

Five kinds of data usually flow: customer accounts, stock, orders, invoices and payments. Not every project needs all five. How your business runs decides which ones matter.

**Data that flows in an accounting integration**

| Data | What it includes | Usual direction |
| --- | --- | --- |
| Customer account | Name, tax number, address, contact | Website or CRM to accounting |
| Stock | Product code, quantity, warehouse, unit | Accounting or ERP to website |
| Price | List price, customer group price, VAT rate | Accounting or ERP to website |
| Order | Items, quantities, totals, delivery | Website, marketplace or CRM to accounting |
| Invoice | Number, date, amount, document type | Accounting to website and customer |
| Payment | Card, bank transfer or balance movement | Payment system to accounting, balance back to website |

## How are customers and products matched?

Customers are matched on a unique value such as a tax number, and products on a shared product code. If a company that orders on your site already exists in accounting, a new account must not be created, or the same company ends up with three accounts and three balances. Retail customers are often grouped under one general account. Agree the approach with your accountant. If product codes differ between systems, cleaning them up comes first. It is dull work, but without it the integration is never reliable.

## One-way or two-way integration?

A one-way integration moves data from one system to another; a two-way integration lets both systems write the same data. For most businesses the right answer is several one-way flows: orders go from the website to accounting, stock goes from accounting to the website. Together they form a loop, but each piece of data still has one owner. True two-way sync, where a customer address can be edited in both CRM and accounting, needs a conflict rule. Without one, data gets silently overwritten.

## What if the accounting software has no API?

Without an [API](/en/glossary/api), the link is built through a local service, database reads, the software's own import tools or file transfer. Cloud products usually offer a documented API. For installed software, it depends on the version and setup, so check with the vendor, reseller or support team.

- **Cloud API:** the cleanest route, managed according to the vendor's documentation.
- **Local service:** a service next to the installed software, using its supported tools.
- **Database reads:** reading is fine. Writing directly skips the software's own rules and is usually not advised.
- **File transfer:** slowest, but sometimes the only way.

If the software runs on an office computer, your website cannot reach it directly. We install a small agent in the office that connects outward, picks up pending jobs, writes them into the software and reports back. No inbound port is opened on the office network.

## How does it relate to e-invoicing?

In Turkey, e-invoices are often issued from the accounting software or the provider it connects to, so the two flows are designed together. Either the website sends the order and the invoice is issued in accounting, with the number sent back, or the website issues the invoice through the provider and accounting receives the record. The key rule is that one invoice is never issued from two places. We explain the details in [e-invoice integration in Turkey](/en/blog/e-invoice-integration-turkey). Ask your accountant about document types.

## How are payments and balances synced?

Payments are posted to the right customer or invoice using data from the payment provider or bank. Card commission and settlement dates matter to accounting, so agree whether to post gross or net. Dealers and business customers often want their balance, open invoices and credit limit on your portal, which means that data flows back from accounting. Your sales team may want it in the CRM as well. We compare CRM options in [off-the-shelf or custom CRM](/en/blog/off-the-shelf-or-custom-crm).

## How we build an accounting integration

1. **Map today's process** — We write down who enters which data, where and how often, together with your accounting team.
2. **Pick an owner for each data type** — Customers, stock, prices, orders, invoices and payments each get one owner system.
3. **Choose the connection** — API, local service, database reads or file transfer, depending on your software version.
4. **Match codes and fields** — Product codes, customer codes, VAT rates, warehouses and units are mapped between systems.
5. **Test on a copy** — Real scenarios run against a test company or database copy. Your accountant checks the records.
6. **Go live and monitor** — We review the first days of live records together. Failed records trigger alerts and retries.

## How are errors tracked?

Errors are tracked on a monitoring screen that logs every transfer, with alerts for repeated failures. Accounting software may reject a record because of a missing tax number, a closed period or an unknown product code. That record must not vanish. It is listed with the reason and resent once fixed. Each record also carries its source ID, so a retried request never creates a duplicate. A simple month-end report comparing totals between the website and accounting catches what slips through.

## What drives the cost?

The cost depends mainly on the connection route, the number of data types and how tidy your existing data is. Sending orders to a documented cloud API is a different job from a two-way link to office software through an agent. Our one-page quote states which data flows where, which route we use and when the work is done: test scenarios passed, first live records checked with your accounting team, monitoring running. Bugs found within 30 days of handover are fixed free.

Selling on marketplaces too? See [marketplace integration](/en/blog/marketplace-integration). This work sits under our [integrations](/en/services/integrations) service, and customer and sales tracking under [CRM and internal systems](/en/services/crm-and-internal-systems).

## Frequently asked questions

### Can you integrate with Logo, Mikro or Paraşüt?

Usually yes, if your version offers an API or another way to exchange data. We check the version and route on the first call. We have no partnership with these vendors.

### My accounting software runs on an office PC. Can it still connect?

Often yes. We install a small agent in the office that connects outward, so no inbound port is opened.

### Do I need to change my accounting software?

Usually not. We build around what you use. If it offers no way to exchange data at all, we tell you plainly.

### Is one-way integration enough?

For most businesses, one-way flows per data type are enough. If the same data changes in two places, we write a conflict rule.

### Should the website or the accounting software issue invoices?

Either can. What matters is that an invoice is never issued from both. We decide with your accounting team and accountant.

### How often does stock update?

From near real time to a few minutes, depending on the route. File transfer can mean longer intervals.

### What happens to a rejected record?

It appears on the monitoring screen with the reason and is resent once fixed. We test these cases before go-live.

### Who owns the code afterwards?

You do. The code lives in your repository and API keys in your accounts. We work as authorised users.

## Sources

- [e-Belge](https://ebelge.gib.gov.tr/), Revenue Administration of Türkiye (GİB)
- [Revenue Administration of Türkiye](https://www.gib.gov.tr/), Gelir İdaresi Başkanlığı

**Stop typing the same data twice** [Get a quote](https://radkod.com/en/get-a-quote)