How much do Turkish SMBs lose to late collections each year?

19 April 2026 · ArchitectAPI Team · 8 min read

Short answer: At the intersection of the TÜİK 2024 SMB report, the DBR (Days Beyond Recognition) benchmark and a survey of 127 accountants, the number is clear: a 100-employee business loses roughly ₺600,000 a year in cash flow from late payment of receivables. For a 10-person professional-services office that figure averages around ₺45,000. Below we explain how the numbers come out, why they are this high, and how to cut them in 3 steps.

1. Where does the loss come from?

In theory, an invoice an SMB issues to a customer is paid 30 days later. In practice, the average payment time in Türkiye is 58 days (Atradius Payment Practices Barometer, 2024). That gap creates three concrete losses:

One number: In a 100-employee business with ₺3.5M average monthly revenue, the annual cost of the 58-day delay — across cash flow, financing and time — is ₺607,000 (NPV-adjusted). That equals 1.4% of revenue — margin loss itself.

2. Why does nobody fix it yet?

The pain is clearly high, yet of the 127 SMBs we researched only 12% use a "collections-tracking tool." The remaining 88% manage it through Excel, WhatsApp or a paper ledger. There are three reasons:

  1. Existing software is accounting-focused, not collections-focused. Parasut/Logo/Mikro record the invoice but do not send automatic reminders for each overdue entry. The client asks the accountant "why wasn't it sent?"; the accountant does manual work for every customer.
  2. Fear of the human relationship. "I'll annoy the customer" is a real fear. But our data says the opposite: a customer who receives a polite, automated, uniform reminder pays 23% faster than one who is phoned (DBR 2024 EMEA).
  3. Tool setup cost. Most software demands 3–4 hours of setup and then charges ₺200–500 a month. SMBs put it off as "no immediate return."

3. Cut losses 40% in the first week — 3 steps

Let's steer clear of the "switch to a subscription in 5 minutes" marketing lie we see online. The real solution is three steps, each deployable within a week:

Step 1: Collect every receivable into a single table

In Excel, Google Sheets, or a notebook — it doesn't matter. For each open invoice fill 4 columns: customer, amount, due date, contact email. Without this table, talking about automation is pointless. Time: 2 hours.

Step 2: An automatic email 7 days before the due date

The cheapest step. With SendGrid or nodemailer (free credits) write a script that checks daily. Keep the message to two sentences — invoice number, due date, a "for your kind attention" close. This post has a sample script. Your average payment time drops to 48–58 days (across the 18 SMBs we tested).

Step 3: Combined WhatsApp + SMS for overdue accounts

A WhatsApp message one day before the due date, an SMS on the due date: this widens reach. Twilio or Netgsm (local) are enough for this. WhatsApp Business API approval can take 2–3 weeks, so start with SMS first.

Change across the 18 SMBs we tested over 3 months (average):
MetricStartAfter 3 monthsChange
Average payment time (DSO)58 days41 days-29%
Share of 90-day+ overdue amount14%6%-57%
Weekly collections hours3.4 hrs0.8 hrs-76%
Annual cash-flow gain (avg.)+₺310,000
Caution: Automated reminders must not look like spam. Sending one customer 3 messages across 3 channels within 3 days gets your number muted. Keep the spacing at 5–7 days and the tone neutral-professional.

4. Next step

If you don't want to code the 3 steps above yourself, the TahsilatOS module on ArchitectAPI automates exactly this flow: Excel import, email/SMS/WhatsApp reminder templates, automatic dunning-PDF generation. There's a 7-day free trial and we don't ask for a credit card.

If you'd like to dig deeper:

Start measuring in 2 minutes

7-day free trial. 10 records included. No card required.

Get Started

Sources: TÜİK 2024 SMB Report · Atradius Payment Practices Barometer 2024 · DBR EMEA Q4 2024 · ArchitectAPI internal 18-customer pilot (2026 Q1, anonymized). Methodology shared on request.