What is a Current Account Transfer (Virman)?

What is a Current Account Transfer?

A current account transfer, known in Turkish accounting practice as virman, is the internal transfer of a balance from one current account to another within the same business — without involving an external cash movement. It is a bookkeeping mechanism used to keep accounting records consistent, balance receivables and payables across related accounts, and ensure the accuracy of financial statements.

The transfer is purely an entry on the books: no money leaves the company. Yet without it, parallel accounts can drift out of sync, intercompany positions become hard to reconcile, and reporting accuracy degrades. Virman entries are common in large multi-branch businesses, multi-entity groups, and any organization that maintains separate current accounts per customer, supplier, branch or department.

Why Businesses Use Current Account Transfers

• Clearing aged balances: moving an old receivable from one account to another related account where it can be netted off.
• Correcting bookkeeping errors: reclassifying an entry posted to the wrong current account.
• Consolidating positions: combining multiple sub-account balances into a parent account for reporting.
• Intercompany netting: offsetting amounts owed between two entities of the same group without an actual cash payment.
• Customer-supplier offset: the same counterparty is both a customer and a supplier; the virman nets the two positions.
• Branch / department reclassification: moving a balance from one branch’s books to another when the underlying transaction was misallocated.

One-Sided vs Reciprocal Virman

One-Sided Virman

Only one party (account) is adjusted. Example: balance is moved from “Customer A receivable” to “Doubtful debts” to reflect a write-down. The other side of the entry is a different ledger category, not another current account.

Reciprocal Virman

Both current accounts are adjusted in equal and opposite amounts. Example: Customer A also operates as Supplier A; their TRY 50,000 receivable is netted against their TRY 50,000 payable, with both balances closing simultaneously. Reciprocal virman is the most common form in customer-supplier offset scenarios.

Accounting Treatment

Although the exact ledger account numbers differ by national chart of accounts, the structure of a current account transfer entry is universal:

• Debit the receiving current account (the account whose balance is increasing in absolute terms or moving toward zero).
• Credit the originating current account (the account whose balance is decreasing or moving toward zero).

The two amounts are always equal. The entry has zero net effect on total assets, total liabilities or P&L — it simply reshapes how the same financial position is allocated across accounts.

Example

Customer A owes the business 50,000. Supplier A (same counterparty) is owed 50,000 by the business. A reciprocal virman:

• Debit: Supplier A payable 50,000
• Credit: Customer A receivable 50,000

After the entry, both balances are zero, and the counterparty position is correctly reflected as netted.

Common Use Cases in Modern Business

B2B Companies with Mixed Counterparty Relationships

Companies that both buy from and sell to the same partner regularly use virman to net positions, reducing the amount of physical cash that needs to move and simplifying reconciliation.

Multi-Branch and Multi-Entity Groups

Inter-branch settlement is one of the most common virman scenarios — moving a receivable from one branch to the central account, or vice versa, so that consolidated reporting reflects reality.

E-Commerce and Marketplace Operations

Marketplaces routinely virman commissions, refunds and adjustments between merchant current accounts to keep settlement balances accurate without daily cash movement.

Group Treasury Operations

Treasury teams use virman within an ERP-supported intercompany structure to net positions before initiating actual physical cash transfers — minimizing bank fees and counterparty exposure.

Best Practices

1. Always document the reason: every virman entry should have a clear narrative explaining why the transfer was made and which underlying transaction it relates to.
2. Get authorization: virman entries can mask errors or fraud if used without controls. Require dual approval above a defined threshold.
3. Reconcile after every transfer: confirm both affected accounts close to expected balances before posting is finalized.
4. Use ERP-supported workflow: modern ERP systems provide structured virman screens with audit trails, approval flows and automatic offsetting entries.
5. Avoid using virman to fix forecast or reporting issues: virman corrects accounting facts, not management expectations.

Risks and Controls

The flexibility of virman makes it both useful and risky. Common pitfalls:

• Concealing real bad debt: moving an uncollectible receivable to a “parking” account so it doesn’t appear in aging reports.
• Masking duplicate invoices: virman to “balance” an account where a duplicate was posted, without correcting the underlying error.
• Bypassing approval workflow: using virman to recategorize an expense after the fact.

Strong internal controls — segregation of duties, threshold-based approval, periodic audit sampling — turn virman from a control risk into a control tool.

Frequently Asked Questions

Is a current account transfer the same as a bank transfer?

No. A bank transfer involves real cash moving between bank accounts. A virman is purely an internal accounting entry — no money moves; only the allocation between books changes.

Can virman entries affect taxable income?

Generally no, because the entry has no P&L impact. However, virman entries that reclassify something between balance-sheet and P&L accounts (which is not strictly a current-account virman but is sometimes called one informally) can affect taxable income and should be reviewed carefully.

Do all ERP systems support virman?

Most modern ERPs and accounting platforms support some form of inter-account transfer. The user experience and audit trail quality varies significantly. Look for: approval workflow, reason codes, automatic offsetting entries and full audit log.

How often should virman entries be audited?

Quarterly review of all virman entries by an independent person, plus an annual deep dive as part of internal audit. Spot checks during month-end close prevent issues from compounding.

What is the difference between virman and journal entry?

A virman is a specific type of journal entry — one that transfers a balance between two current accounts. All virman entries are journal entries; not all journal entries are virmans.

Conclusion

The current account transfer (virman) is a simple but powerful accounting mechanism. Used well, it keeps the books clean, accelerates reconciliation and supports efficient intercompany netting. Used poorly, it becomes a hiding place for bookkeeping errors and worse. The line between the two is internal control: documented reasons, approval thresholds, periodic audit and ERP-supported workflow. With those controls in place, virman is one of the routine entries that quietly makes modern multi-account accounting work.