tally_get_cash_flow
Discover why cash flow data is unsupported and get the alternative approach: retrieve cash and bank ledger transactions to compile the statement yourself.
Instructions
Cash flow statement — NOT AVAILABLE. This tool always fails with TALLY_UNSUPPORTED_OPERATION and returns an explanation.
It is registered rather than omitted so that the limitation is discoverable: calling it tells you why the data cannot be produced and which tools to use instead.
WHY: A cash flow statement requires classifying movements into operating, investing and financing activities. That classification is a judgement about the business, and this server holds no business rules — producing one from an assumed mapping would present an invented classification as fact. TallyPrime own cash flow report also has no retrieval path confirmed against a real install.
INSTEAD: The underlying data IS available. Use tally_get_ledger_transactions on the cash and bank ledgers (find them with tally_search_ledgers for the "Bank Accounts" and "Cash-in-Hand" groups) to get every movement with dates, counterparties and a running balance. You can then classify them yourself and state the basis you used.
Do not call this expecting data. Go straight to the tools named above, and tell the user that this statement has to be assembled rather than fetched.
This server is strictly read-only and cannot create, modify or delete anything in TallyPrime.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| toDate | No | End of the period, ISO YYYY-MM-DD. Must be on or after fromDate. | |
| company | No | Company name. Optional — when omitted, the currently loaded company in TallyPrime is used. If given and it does not match the loaded company, the call fails with TALLY_COMPANY_NOT_LOADED rather than silently returning another company data. | |
| fromDate | No | Start of the period, ISO YYYY-MM-DD. Optional — if both dates are omitted, the current financial year is used and the resolved range is echoed back in the response. |