Every incorporated company operating in Türkiye is legally obliged to engage a Serbest Muhasebeci Mali Müşavir (SMMM — Certified Public Accountant). There's no DIY accounting workaround. For a foreign-owned subsidiary, the CPA is not a vendor — they are an extension of your finance team with a state-issued seal and personal liability for what they sign. The most common mistake foreign GMs make is treating the CPA as "external bookkeeping" instead of building them into the ERP from day one. Below is a practical playbook for getting the relationship right.
Why the CPA matters more than you think
A Turkish CPA personally signs and files:
- Monthly VAT (KDV) returns
- Monthly withholding (Muhtasar + SGK) declarations
- Quarterly corporate provisional tax
- Annual corporate tax filing
- E-ledger (e-Defter) batches
- BA-BS (until phased out, replaced by mutual reconciliation)
- Year-end financial statements
If those filings are wrong, the CPA is held jointly liable with the company. That's why your CPA insists on seeing every transaction, asks for source documents you've forgotten about, and pushes back on creative accounting your HQ might propose. Their licence is on the line.
What it costs (2026 ranges)
CPAs in Türkiye charge by company size, transaction count and module scope:
| Company size | Monthly retainer | Notes |
|---|---|---|
| Holding / inactive entity | ₺6,000–10,000 | Filings only |
| Micro (1–5 employees) | ₺10,000–18,000 | Includes payroll |
| Small (6–25 employees) | ₺18,000–35,000 | Multi-warehouse, multi-bank |
| Medium (26–75 employees) | ₺35,000–70,000 | Foreign trade, multi-currency |
| Large (76+) | Custom | Often 2–3 CPAs as a team |
These are payments to an external SMMM office. An in-house junior accountant costs another ₺25,000–50,000/month and does not replace the licensed CPA — the CPA must still sign filings.
How an ERP should handle the CPA relationship
Three patterns work, three don't.
Works:
- CPA seat inside the ERP — the CPA logs in with their own credentials, has a scoped panel (no payroll editing, no master data deletion), files declarations from inside the system using GİB connectors. No emailing Excel files back and forth.
- Standardised handoff packets — at month-end the system auto-generates a packet (invoice journal, bank statements with reconciliation, payroll calculation, KDV summary, withholding base) ready for CPA review and sign-off.
- Two-way audit trail — every change the CPA makes is timestamped and attributed; every change you make is visible to them. No "who changed account 320 last week?" arguments.
Doesn't work:
- Emailing PDFs and Excel sheets — CPA rebuilds them in Luca, their own software, doubling the work.
- Giving the CPA admin access to the entire ERP — they don't need it, and one accidental delete creates real damage.
- Treating the CPA as a Q4 panic — by Q4 the books are wrong and you're in firefighting mode.
The 5 mistakes foreign GMs make
1. "Just use Logo / Mikro because the CPA knows it." The CPA's familiarity with one ERP is not a reason to choose it. A modern cloud ERP with a CPA panel + open API can ingest Logo/Mikro export formats and feed Luca via standard files; the CPA has a learning curve but no productivity loss after 2 weeks.
2. Cutting the CPA out of ERP selection. The CPA will tell you which features fail Turkish regulatory tests in 5 minutes. Cutting them out costs you 6 months later when month-end won't close.
3. Underpricing the CPA. A ₺6,000/month deal for a medium company is too good. Either the CPA is doing minimum work (filings only) or they're cutting corners. You'll pay more on a tax inspection.
4. No backup plan. Single-CPA dependency is risky. Insist on a CPA office with at least 2 licensed people on your account; verify in writing.
5. Skipping mutual reconciliation discipline. With BA-BS being phased out, mutual reconciliation between counterparties becomes critical. ERPs that automate the request/response and reconciliation cycle save weeks of CPA time.
Birasyo's CPA collaboration features
Every Birasyo plan ships with one free CPA (SMMM) user seat including:
- Dedicated CPA panel with read-only on master data, edit on chart-of-accounts mappings
- One-click export to Luca, Mikro CPA Pack, Zirve formats
- GİB e-Defter direct filing
- Monthly handoff packet auto-generation
- Audit trail visible to both client and CPA
- Mobile read-only access for spot checks
Ask any candidate ERP: "Show me how my Turkish CPA logs in, what they see, and how they file the monthly KDV declaration."
If the answer involves screensharing or sending Excel files, that's not 2026 Turkish accounting — that's 2010.
Closing
The CPA is not overhead — they're a co-pilot the law requires you to fly with. Build them into the ERP, give them their own seat, and treat their feedback as input from a regulated finance partner. Your monthly close goes from a 2-week marathon to a 3-day routine.
Want a demo tailored to a foreign-owned Türkiye subsidiary? We'll bring an ERP-aware CPA into the call so you see both sides at once.
Related reads:
Share this on LinkedIn
Headline, summary and hashtags copy to your clipboard and the LinkedIn composer opens — paste (Cmd/Ctrl+V) and post.
