Escrow, Settlement and Customer Fund Accounting & Reconciliation in Fintech

Fintech companies often handle large volumes of money that do not economically belong to them. Depending on the business model, funds may move through escrow accounts, settlement accounts, nodal or designated accounts, customer fund accounts, merchant settlement accounts, collection accounts and other separately maintained bank accounts.

From an accounting perspective, these balances can be deceptively complex. The company may process ₹100 crore of transactions in a month but earn only a small percentage as fees or commission. If accounting systems are not designed correctly, there is a risk of overstating revenue, misstating liabilities, delaying merchant settlements or losing visibility over unmatched balances.

This is where a Virtual CFO for Fintech companies can add substantial value. The role is not limited to reviewing bank reconciliations after month-end. A strong VCFO helps design the accounting architecture, reconciliation process, control framework and management reporting needed to ensure that customer and merchant funds are properly identified, safeguarded and settled.

Why Customer Fund Accounting Is Different from Normal Bank Accounting

In a conventional business, money received in the bank account is often linked directly to sales or receivables.

In fintech, this assumption can be dangerous.

Amounts received may represent:

• Funds collected on behalf of merchants
• Customer balances awaiting settlement
• Refunds pending processing
• Amounts held temporarily in escrow
• Settlement balances receivable from payment partners
• Amounts payable to merchants or beneficiaries
• Chargeback or dispute reserves
• Platform fees belonging to the fintech
• Taxes or other deductions

Therefore, cash movement and revenue recognition must be separated.

A transaction flowing through a fintech bank account should not automatically be recognised as revenue. The finance system must first identify whose money it is, what obligation exists and when the fintech becomes entitled to recognise its own income.

The VCFO Starts with Fund-Flow Mapping

Before designing accounting entries, a Virtual CFO should understand the complete movement of funds.

A typical review should map:

Customer → Payment Gateway / Bank → Escrow or Settlement Account → Merchant / Beneficiary → Fintech Fee

The exact flow will differ across payments, lending, marketplaces, WealthTech, InsurTech and other fintech models.

The VCFO should document:

• Who collects the funds?
• In whose name is the bank account maintained?
• Who has beneficial ownership of the money?
• How is the fintech compensated?
• What is the settlement cycle?
• What deductions are made before settlement?
• Who bears refunds and chargebacks?
• How are failed transactions treated?
• What regulatory restrictions apply to the account?

Without this fund-flow understanding, accounting entries are often built incorrectly from the beginning.

Designing the Right Accounting Structure

A good fintech accounting system should distinguish between company funds and third-party funds.

Separate ledger accounts may be required for:

• Escrow bank balances
• Settlement bank balances
• Customer funds payable
• Merchant settlement payable
• Settlement receivables
• Refund payable
• Chargeback balances
• Fees receivable
• Processing charges
• GST and other taxes
• Suspense and unidentified transactions

The accounting architecture should allow management to answer a basic question at any point:

How much money are we holding, who does it belong to and when must it be settled?

This is much more important than merely ensuring that the bank ledger agrees with the bank statement.

Three-Way Reconciliation Is Critical

For many fintech businesses, a normal bank reconciliation is insufficient.

A strong control framework generally requires reconciliation between three sources:

Bank / Escrow Statement → Transaction or Platform Data → Accounting Ledger

For example, if a platform records ₹10 crore of customer collections, the finance team should verify:

1. Whether the corresponding funds were actually received in the designated bank or escrow account.
2. Whether the platform has correctly identified the customer or merchant.
3. Whether the accounting system records the correct liability and fee income.
4. Whether settlement to the merchant occurred within the agreed or applicable timeframe.

Differences between these three records should be investigated promptly.

Common reconciliation breaks include:

• Failed transactions
• Duplicate settlements
• Partial settlements
• Bank charges
• Timing differences
• Refunds
• Chargebacks
• Unidentified receipts
• Settlement deductions
• Incorrect merchant mapping
• Interface or system failures

A VCFO helps establish rules for identifying, ageing, resolving and escalating such exceptions.

Daily Reconciliation, Not Only Month-End Reconciliation

For high-volume fintech businesses, month-end reconciliation is often too late.

Escrow and customer-fund accounts should usually be reconciled at a frequency aligned with transaction volumes and settlement risk, often daily.

The process should clearly identify:

• Opening balance
• Collections received
• Settlements processed
• Refunds
• Fees deducted
• Charges
• Closing balance
• Unsettled customer or merchant liabilities
• Reconciling items

The objective is to detect exceptions before they accumulate.

A small daily mismatch can become a major accounting and operational problem if allowed to remain unresolved for several weeks.

Internal Controls Around Customer and Merchant Funds

Customer money requires stronger controls than normal operating cash.

A Virtual CFO should help establish controls such as:

• Separate bank accounts for designated purposes
• Restricted user access
• Maker-checker approval for settlements
• Defined settlement-authorisation limits
• Daily bank and transaction reconciliation
• Independent review of reconciliation reports
• Automated exception reporting
• Ageing of unmatched transactions
• Escalation of long-outstanding items
• Controlled changes to merchant bank details
• Audit trail for refunds and adjustments
• Periodic confirmation of closing balances
• Clear segregation between operations and finance teams

For regulated fintech activities, the control framework must also be aligned with the applicable RBI or other regulatory requirements governing customer funds, escrow arrangements and settlements.

Handling Suspense and Unidentified Transactions

One of the most common weaknesses in fintech accounting is the uncontrolled use of suspense accounts.

Unidentified transactions are sometimes parked in suspense and forgotten.

A better system should classify suspense items by:

• Date
• Amount
• Transaction reference
• Merchant/customer
• Reason
• Responsible team
• Ageing
• Resolution status

Management should monitor ageing buckets such as:

0–2 days | 3–7 days | 8–30 days | More than 30 days

Long-outstanding reconciliation items can indicate system weaknesses, settlement issues, customer disputes or potential financial leakage.

Revenue and Settlement Accounting Must Be Connected

The settlement system and revenue-recognition system should not operate independently.

Suppose a fintech processes ₹50 crore of merchant transactions and earns a 1% platform fee.

The business should not recognise ₹50 crore as revenue merely because that amount passed through its settlement infrastructure.

The finance system must identify:

Transaction Value → Merchant Liability → Fintech Fee → Taxes → Net Settlement

This distinction improves the accuracy of revenue, margins, receivables, liabilities and cash flows.

It also makes investor reporting, statutory audit and due diligence significantly easier.

What Management Should Review

A good VCFO should convert reconciliation data into a monthly management dashboard covering:

• Total transaction value
• Total customer/merchant funds handled
• Outstanding settlement liabilities
• Average settlement cycle
• Unreconciled items
• Ageing of reconciliation breaks
• Refunds and chargebacks
• Failed settlements
• Fee income
• Settlement losses or leakages
• Bank-account-wise balances

The important question is not simply whether the reconciliation is complete.

It is:

Are there recurring exceptions that indicate a process, technology or control weakness?

Conclusion

Escrow and settlement accounting in fintech is not merely a bookkeeping exercise. It is a combination of accounting, treasury, operations, technology, risk management and internal control.

A strong Virtual CFO helps fintech companies design the entire system—from fund-flow mapping and chart of accounts to daily reconciliation, exception management and management reporting.

The objective is clear:

Every rupee moving through the system should be identifiable, reconcilable, attributable to the correct party and settled appropriately.

When this foundation is strong, the fintech company gains better financial visibility, stronger controls, cleaner audits and greater confidence from management, investors, banks and regulators.

This also supports the broader objective discussed in “Virtual CFO for Fintech Companies in India: Complete Guide”—moving the finance function from basic accounting toward financial control, financial intelligence and strategic decision-making.