
A controller at a foreign-owned distribution subsidiary in Türkiye described her closing routine like this: the first three days go to matching bank statements against the accounting ledger by hand, because the bank feed and the ERP don't talk to each other. The next two go to chasing down invoices that were issued but never matched against the delivery notes that triggered them. By the time the numbers are stable enough to send to the parent company, the local VAT filing deadline is already close behind, and the same data has to be checked twice — once for the group report, once for the statutory return.
None of this is unusual. What makes it specific to a Turkish subsidiary is that the local statutory calendar — monthly VAT returns, withholding tax declarations, e-Defter output — runs on its own fixed schedule regardless of when the parent company wants its consolidation numbers. A close process built around manual reconciliation has to satisfy both calendars separately, which is usually where the extra days come from.
Where do the days actually go?
Broken down, a slow close is rarely one big bottleneck — it's several small manual steps that each take longer than they should:
- Bank reconciliation. Bank statements are downloaded separately and matched against ledger entries by eye, one line at a time, especially when the subsidiary holds accounts in more than one currency.
- Sales order, delivery note, and invoice matching. When these three documents live in different tools or spreadsheets, confirming that everything shipped was actually invoiced becomes a manual cross-check.
- Accruals and provisions. Expenses that belong to the closing month but haven't been invoiced yet (utilities, year-end bonus provisions, freight not yet billed) get estimated in a side spreadsheet rather than posted directly.
- Intercompany and cost-center allocation. Shared costs — rent, shared staff, group service charges — get split across departments or cost centers manually, often re-deriving the same allocation logic every month.
- Dual-format reporting. The local books need to satisfy VUK (Vergi Usul Kanunu — the Turkish Tax Procedures Law) formatting for e-Defter, while the parent company usually wants an IFRS-style summary in a different currency. Producing both from a single set of transactions, rather than keeping two parallel versions, is where many subsidiaries still rely on a spreadsheet bridge.
Each of these steps is individually manageable. Stacked together in a system that doesn't connect them, they add up to a close that takes days instead of hours.
Why does the local filing calendar make this harder, not easier?
A domestic-only company can, in theory, push its close date around if something runs late. A foreign-owned subsidiary in Türkiye generally can't: monthly VAT returns and withholding declarations are filed against a fixed statutory calendar set by the tax authority (Gelir İdaresi Başkanlığı, GİB), independent of whatever date the parent company has set for its own consolidation. When the two calendars land close together, the finance team ends up doing two closes in the same week — one for the tax filing, one for the group report — often from the same underlying transactions but assembled twice by hand.
The practical effect is that a close process built for a single deadline usually breaks under a second one. The fix isn't negotiating either calendar; it's making sure both views come out of the same close, rather than two separate manual efforts.
What actually shortens a close?
| Manual step | What replaces it |
|---|---|
| Matching bank statements by eye | Bank feed imported and reconciled against ledger entries automatically, flagging only the exceptions |
| Manually checking every shipment was invoiced | Sales order → delivery note → invoice matched automatically, with unmatched documents surfaced as a list, not discovered at close |
| Estimating accruals in a side spreadsheet | Recurring accrual templates posted automatically each period, adjusted only where the estimate needs a manual override |
| Re-deriving cost allocation logic monthly | Allocation rules (by department, cost center, or project) set up once and applied automatically at close |
| Rebuilding an IFRS summary from VUK books by hand | Chart of accounts mapped once so both statutory (VUK) and group-currency views are generated from the same transactions |
None of these changes require abandoning the statutory format — VUK bookkeeping stays exactly as required for tax and audit purposes. What changes is how much of the reconciliation between the two views is done by a person versus done automatically from a single source of transactions.
Does this apply to a small subsidiary too?
The logic holds even at a small scale, sometimes more sharply. A three-person finance function covering accounting, banking, and reporting for a small subsidiary doesn't have the headcount to absorb a slow manual close — the same person who reconciles the bank statement is usually also the one who has to answer the parent company's questions during consolidation week. In a small team, a close that depends on one person's manual cross-checking is also a continuity risk: if that person is on leave when the filing deadline lands, the close doesn't get shorter, it gets riskier.
How does Birasyo handle this?
Birasyo posts sales orders, delivery notes, and invoices against the same stock and accounting records at the moment each document is created, so matching them at close is a review step rather than a reconstruction. Bank statements can be imported and reconciled against the ledger rather than checked line by line. Recurring accruals and cost-center allocations run from templates set up once, not rebuilt every period. The chart of accounts is mapped so that VUK-compliant statutory output and a group-currency summary come from the same underlying transactions, rather than a second version assembled separately for the parent company. Finance teams can review the close through Reports & Analytics — live tables rather than a file someone exported and stitched together the night before the deadline.
Summary
- A slow month-end close is rarely one bottleneck; it's usually several manual steps — bank reconciliation, sales-to-invoice matching, accruals, cost allocation, dual-format reporting — stacked on top of each other.
- A foreign-owned subsidiary in Türkiye closes against two calendars that don't move for each other: the statutory tax filing schedule and the parent company's consolidation date.
- The fix is not negotiating either deadline; it's producing both the statutory (VUK) view and the group-currency view from the same close, instead of assembling them separately.
- Smaller finance teams feel this more acutely, since the same person usually owns both the manual reconciliation and the parent company's questions during consolidation week.
- Automating the matching and allocation steps — not changing the statutory format itself — is what actually shortens the close.
Sources: This article reflects general ERP and closing-process practices and does not constitute tax or accounting advice. Statutory filing deadlines, VAT and withholding declaration rules, and e-Defter requirements are set by the Turkish Revenue Administration (GİB) and can change; confirm current deadlines and formats with your financial advisor (SMMM/CPA) before relying on any date mentioned here.
Share this on LinkedIn
Headline, summary and hashtags copy to your clipboard and the LinkedIn composer opens — paste (Cmd/Ctrl+V) and post.

