> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/billing/cash-card-manager.md).

# Cash Card Manager

Logic ERP has corrected the **Card Log Viewer**, the window that opens from **View Card History** in the **Cash Card Manager**. A recharge no longer appears twice, and the **Previous Balance** and **Total Amount** of a recharge now show the right figures. The window also adds a new **Actual Refundable Amount** column, shows the history correctly when you narrow the dates, and opens faster.

To learn about the Cash Card Manager, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/billing/cash-card-manager.md).

***

### **Step 1: Open the Card Log Viewer**

* Navigate to **Billing** and select **Cash Card Manager**.
* Enter or scan the card **Number** to show the card.
* Click **View Card History**. The **Card Log Viewer** opens with that card's recharges, sales, refunds and journal entries.

***

### **Step 2: Actual Refundable Amount column**

* The new **Actual Refundable Amount** column appears between **Total Amount** and **Refund Amount**.
* On a recharge row it shows the card balance after that recharge **without** the scheme credit. The scheme credit can be spent on the card but is not refunded in cash, so this is the amount that can be refunded to the customer.
* **Total Amount** still shows the full value on the card, including the scheme credit. The difference between the two columns is the scheme credit on the card.
* The column is filled on recharge rows only. It stays blank on sale, refund and journal entry rows.

> **Example — recharge with a scheme**
>
> Priya's card has ₹7,200 on it. She recharges ₹1,000 and receives a scheme credit of ₹100 on that recharge.
>
> On the recharge row, **Previous Balance** shows ₹7,200, **Recharge Amount** ₹1,000, **Current Scheme** ₹100 and **Total Amount** ₹8,300. **Actual Refundable Amount** shows ₹8,200, because the ₹100 scheme credit can be spent but not refunded.

***

### **What's corrected**

* **A recharge no longer appears twice.** Each recharge used to show a second, identical-looking line. That extra line has been removed, so the window now shows one line per recharge.
* **Previous Balance and Total Amount on recharge rows.** A recharge row could show a minus **Previous Balance** (for example, -₹5,000 on a card's first recharge of ₹5,000) and a **Total Amount** of ₹0, or only the scheme amount. These now show the card's balance before the recharge, and the total value on the card after it, including any scheme credit.
* **Narrowing the dates.** When **Date Start** and **Date End** covered only part of a financial year, the window showed nothing. It now shows the entries between those dates, and a range that runs across more than one financial year shows the entries from each year.
* **Time End now defaults to 11:59 PM.** It used to default to 12:00 PM (midday), so entries made after midday on the **Date End** day were left out.
* **Entries without a user record.** An entry with no record of the user who made it could be left out of the list. It is now shown, dated by its bill date, with **User Name** and **Workstation Name** left blank.
* **Computers with a month-first date format.** On such a computer, entry times and the date filter were read wrongly, so entries could be missing or out of order. This is now corrected.
* **Refund highlighting.** Refund rows are shown with a light blue background. The highlight used to fall on the row above the refund (and on the heading row when the first entry was a refund). It now falls on the refund row itself.
* **Faster.** The window opens faster, especially for a card with a long history.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/billing/cash-card-manager.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
