Controls for Escrow and Cash-Flow Monitoring Workflows

By Gradivus Corp · 16 October 2026 · Insights

The controls that make escrow and cash-flow monitoring work are: release conditions defined precisely, with the evidence each one needs; a dedicated account at a designated bank with clear mandates; a documented payment waterfall; maker-checker approval for every instruction; regular reconciliation of inflows and outflows against the agreement; a defined path for escalating exceptions; and a complete audit trail. They need to be designed as carefully as the legal agreement. Without them, an escrow is just a bank account with an expensive agreement attached.

The same controls apply across uses: an M&A transaction, debt servicing on a loan or NCD, a settlement, a share or demat transfer, or a regulated arrangement such as a real-estate project account.

Where escrow and cash-flow monitoring are used in India

• Transaction escrows in the purchase and sale of businesses or shares, with funds released on completion conditions.
• Debt-servicing escrows and trust and retention accounts (TRAs). Borrower revenues are routed through the account and distributed in a fixed order of priority. The TRA mechanism in Indian infrastructure finance is commonly traced to a 1999 RBI circular (Mondaq overview).
• Regulated escrows. Under section 4(2)(l)(D) of the Real Estate (Regulation and Development) Act, 2016, promoters deposit 70% of amounts realised from allottees in a separate account with a scheduled bank. Withdrawals are linked to project completion and certified by an engineer, an architect and a chartered accountant (India Code). Separately, RBI's directions for peer-to-peer lending platforms require fund transfers to go through escrow accounts operated by a bank-promoted trustee (RBI).
• Demat, document and source-code escrows, where the asset is securities, original documents or software rather than cash.

The control framework, step by step

1. Define release conditions as testable facts

Each condition in the escrow agreement should answer three questions: what event triggers release, what evidence proves it (a board resolution, regulatory approval, completion certificate or joint instruction), and who may certify that evidence. Unless the agreement expressly provides for it, avoid conditions that ask the escrow agent to exercise commercial judgement. In practice, the question that causes most delay at release is not whether the event happened but whether the document produced is the one the agreement names.

2. Set up the account with clean mandates

• Open a dedicated account with the designated bank, separate from operating accounts.
• Record the authorised signatories and their limits, and the channel through which instructions are accepted (signed instruction, secure portal, bank API).
• Complete KYC on every party and on anyone who gives instructions.
• Block every debit route other than those set out in the agreement.

3. Document the waterfall

For debt-servicing and project structures, write the waterfall as an ordered table. For example: statutory dues, operating expenses, senior debt service, debt-service reserve top-up, subordinated debt, and only then distributions. Each line needs a calculation basis, a payment date and an approval rule. Ambiguity in the waterfall is the most common source of disputes in cash-flow structures, and setting it out as a table tends to expose gaps that the prose version hid.

4. Apply maker-checker to every instruction

No one person should both prepare and approve a payment out of escrow. Log every instruction with the maker, the checker, the time and the supporting evidence. Larger releases call for a second-level approval or a call-back confirmation with the instructing party.

5. Reconcile inflows and outflows

Reconcile the bank statement against expected inflows (receivables, subscription money, sale proceeds) and permitted outflows on a fixed cycle. That means daily for active accounts and at least monthly for the rest. Investigate unidentified credits and debits immediately, rather than carrying them to the next cycle.

6. Monitor against agreed conditions

Put each condition precedent, milestone and deadline on a calendar, with reminders to the party responsible. On debt-servicing accounts, check before each payment date that the balance is enough. Flag any shortfall early enough for the borrower or sponsor to cure it.

7. Escalate exceptions on a defined path

Define what counts as an exception: a shortfall, an unauthorised instruction, a missed condition, or conflicting instructions from the parties. Then fix who is notified, within what time, and what the escrow agent does in the meantime. The safe course is usually to hold the funds and seek joint instructions.

8. Report and keep a complete audit trail

Send the parties periodic statements of balances, movements and condition status. Keep every instruction, approval, evidence document and communication in a tamper-evident record. If the transaction is later disputed or audited, that record protects all parties.

9. Close out properly

On completion, document the final release, confirm a zero balance, close the account and give the parties a closure report. Escrow accounts left open with residual balances are a recurring audit finding.

Technology controls that make the framework work

• Role-based access, so each user sees and does only what the role permits.
• Immutable activity logs recording every view, instruction and approval.
• Automated alerts for approaching deadlines, low balances and unmatched entries.
• Bank integration through statement feeds or APIs, which cuts manual re-keying and reconciliation errors.
• Secure document storage, linked to each condition and payment.

Risks and dependencies

• Poorly drafted agreements. Vague conditions or waterfalls cannot be operated consistently, so involve the escrow operator before signing.
• Conflicting instructions. The agreement must say what happens when the parties disagree.
• Dependence on the bank. Cut-off times, holidays and processing delays all affect payment dates. Build buffers in.
• Role boundaries. An escrow agent acts only within the agreement. It is not a guarantor and does not make commercial decisions for the parties.
• Regulatory change. From 27 October 2026, SEBI-registered debenture trustees must run activities outside SEBI's purview (which commonly include escrow and agency mandates) through separate business units, under Regulation 9C and SEBI's circulars of 25 November 2025 and 28 April 2026. Parties should check the regulatory status and disclosures of any escrow provider they appoint.

Frequently asked questions

What does an escrow agent do? It acts as a neutral party appointed under an escrow agreement. It holds funds, securities or documents and releases them only when the agreed conditions are met and properly evidenced.

What is a fund-flow waterfall? The agreed order in which money in an escrow or retention account is applied. Operating costs might come first, for example, then debt service, then reserves, and distributions to shareholders last.

Who holds the money in an escrow, the agent or the bank? Normally the bank. The funds sit in an account with a designated bank, and the escrow agent administers that account, giving or approving instructions in line with the agreement.

How often should an escrow account be reconciled? Active transaction or debt-servicing accounts are usually reconciled daily or weekly. Low-activity accounts should be reconciled at least monthly, and before every scheduled release.

What happens if the parties give conflicting instructions? A well-drafted agreement requires the agent to hold the funds until it receives joint instructions or a binding order. Choosing between the parties is not the agent's job.

Can an escrow hold shares or software instead of cash? Yes. A demat escrow holds securities in a designated demat account. Document and source-code escrows hold original documents or software deposits, which are released on defined triggers.

How Gradivus can help

Where appointed as escrow agent, Gradivus structures and administers escrow mechanisms for the transparent, condition-based movement of funds, documents and digital assets. The work includes aligning the structure with the transaction terms, opening and administering accounts with designated banks, defining waterfalls and payment priorities, monitoring flows against agreed conditions, and coordinating with banks and stakeholders. Our escrow and cash-flow monitoring systems support these workflows. Explore our Escrow Services and Investment Monitoring pages, or contact us for a consultation. Agency roles apply only where Gradivus is specifically appointed.

This article is general information, not legal, tax or investment advice.