How much do Turkish SMBs lose to late collections each year?
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:
- Opportunity cost: ₺100,000 collected 58 days late produces about ₺3,200 (net deposit-interest) of lost yield.
- Financing substitution: Instead of the delayed receivable, payroll is covered with credit cards or an SMB loan — and that short-term borrowing costs 65–85% annually.
- Management time: The phone-and-WhatsApp hours spent chasing payments. The average owner/manager spends 3–4 hours a week on this; in an SMB that time cannot flow into sales or production.
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:
- 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.
- 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).
- 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.
| Metric | Start | After 3 months | Change |
|---|---|---|---|
| Average payment time (DSO) | 58 days | 41 days | -29% |
| Share of 90-day+ overdue amount | 14% | 6% | -57% |
| Weekly collections hours | 3.4 hrs | 0.8 hrs | -76% |
| Annual cash-flow gain (avg.) | — | +₺310,000 | — |
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:
- Your first collections automation — code example (coming soon)
- WhatsApp Business API — approval in 2 weeks (coming soon)
- What is DSO, and how does an SMB measure it? (coming soon)
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.