Tools · Accounting · SQLite Mirror
Prepare and validate cash payment entry allocation using only actual source payment dates. The tool checks totals, the configured daily limit and the permitted source-date window; it never invents or changes dates.
{% else %}Analyse cash-payment compliance directly from the client's local SQLite Accounting Mirror. TallyPrime is not contacted during this review.
{% endif %}No Tally connection, company selection, extraction queue or day-by-day cache is used here.
Source: {{ mirror.path or mirror_status.mirror_db_path or '' }}
{% else %}| Date | Party / ledger | Amount | Reason | Voucher(s) |
|---|---|---|---|---|
| {{ row.date }} | {{ row.party }} | ₹{{ '%.2f'|format(row.amount) }} | {{ row.reason }} | {{ row.voucher_numbers|join(', ') }} |
| No above-limit exception found for the selected period. | ||||
These rows are indicators for auditor review; they do not by themselves determine tax treatment.
| Party / ledger | Period | Total | Daily amounts |
|---|---|---|---|
| {{ row.party }} | {{ row.date_from }} → {{ row.date_to }} | ₹{{ '%.2f'|format(row.total_amount) }} | {% for item in row.days %}{{ item.date }}: ₹{{ '%.2f'|format(item.amount) }}{% if not loop.last %} {% endif %}{% endfor %} |
| No near-limit multi-day pattern found. | |||
Use this when the source records establish that one accounting amount was actually paid on multiple dates. Enter the real dates and amounts. The tool validates totals, daily limits and the configured date window; it does not fabricate dates or automatically rewrite Tally vouchers.
{% if allocation_plan %}| Actual Date | Proposed Entry Amount |
|---|---|
| {{ row.date }} | ₹{{ '%.2f'|format(row.amount) }} |
{{ allocation_plan.note or 'No accounting dates are generated automatically.' }}
{% if allocation_plan.status == 'ready' %} {% endif %}