> 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/reports-queries/sale-registers/cash-card-status-report.md). # Cash Card Status Report Logic ERP has added four new columns to the **Cash Card Status Report**: **SCHEME AMOUNT**, **ACTUAL REFUNDABLE AMOUNT**, **LEDGER DEBIT** and **LEDGER CREDIT**. The scheme credit given on a recharge is now part of **TOTAL CARD AMOUNT**, the recharge columns now show the amount actually recharged, and, with **Document No.** ticked, a recharge is no longer counted as a refund. This release also corrects the opening balance of cards that carry a scheme amount. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Sale Registers**. * Open the **Cash Card Status Report**. *** ### **Step 2: SCHEME AMOUNT and ACTUAL REFUNDABLE AMOUNT columns** * The **SCHEME AMOUNT** and **ACTUAL REFUNDABLE AMOUNT** columns appear in the report on their own. To hide them, untick them in the report's column settings. * **SCHEME AMOUNT** shows the scheme (discount) credit given on the card's recharges in the report period. * **ACTUAL REFUNDABLE AMOUNT** shows the card balance less all the scheme credit the card has received, including scheme received before the report's start date. 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. * With **Configuration > Report Consolidation > Document No.** ticked, **ACTUAL REFUNDABLE AMOUNT** shows on every document row and on the **Opening Balance B/F** row, and runs on from one document of the card to the next. *** ### **Step 3: LEDGER DEBIT and LEDGER CREDIT columns** * The **LEDGER DEBIT** and **LEDGER CREDIT** columns appear in the report on their own. To hide them, untick them in the report's column settings. * They show the amounts posted to the customer's account for each row, so the report can be matched line by line with the customer's ledger. * **LEDGER CREDIT** shows the amount credited to the customer on a recharge: the card's new value, including its scheme credit. * **LEDGER DEBIT** shows the payments made out of the card and the card amount used on sale bills. Without **Document No.** ticked, it also includes journal entries against the card. * When a card that already has a balance is recharged, that balance is posted out of the account and back in with the new recharge, so it appears in both columns. *** ### **What's changed** * **TOTAL CARD AMOUNT** now includes the scheme credit given on recharges in the report period. Before, it showed only the opening balance and the recharges, so a card that received a scheme showed a balance lower than its real balance. This applies to every total, and to the rows when **Document No.** is not ticked. * Because of this, **TOTAL CARD AMOUNT** now **rises** by the scheme amount, and so do **CARD BALANCE AMOUNT**, **CLOSING BALANCE AMOUNT** and **REFUNDABLE TOTAL AMOUNT**, which follow from it. This is intended. * **CARD RECHARGES**, **CASH RECHARGE AMOUNT** and **CREDIT CARD RECHARGE AMOUNT** now show the amount actually recharged. Before, they could show the card's new balance after the recharge, which also included the balance the card already had. Recharges entered before 07-04-2021 do not hold the recharged amount on their own, so for them these columns still show the card's balance after the recharge. * The recharge columns now work the same way with and without **Document No.** ticked, so both views of the report show the same recharge figures. * With **Document No.** ticked, when a card that already has a balance is recharged, that existing balance is no longer counted in **CARD REFUND AMOUNT**. It is carried over on the card, not refunded to the customer. * With **Document No.** ticked, **CARD RECHARGES**, **CASH RECHARGE AMOUNT**, **CREDIT CARD RECHARGE AMOUNT** and **CARD REFUND AMOUNT** now **fall** by the balance the card had before each recharge. The card's closing balance is not changed by this, because the falls cancel out, and the recharge row no longer shows the old balance twice. This is intended. * Without **Document No.** ticked, **CREDIT CARD RECHARGE AMOUNT** now **falls** by the balance the card had before each credit-card recharge, and **CASH RECHARGE AMOUNT** can **rise** on cards that had credit-card recharges, because the balance carried over on those recharges is no longer taken off it. **CARD RECHARGES** stays the same. This is intended. *** ### **What's corrected** * In the first September update of this report, the card's opening balance counted the scheme amount twice. This happened when a recharge that carried a scheme amount fell before the report's start date, and the opening balance came out higher than the card's real balance by the scheme amount. * Because of this, for such cards, **CARD OPENING BALANCE** falls compared with that update by the scheme amount, and so do the balance and closing figures that follow from it. This is intended. A report that starts on or before the date of that recharge shows the same figures as before. * With **Document No.** ticked, **CARD OPENING BALANCE** now shows the card's brought-forward opening balance on every document row of that card, and on its **Opening Balance B/F** row. Before, it showed only on the totals row. A card with no activity before the start date has no **Opening Balance B/F** row, so this column stays blank for it, as before. * With **Document No.** ticked, the totals row now deducts the scheme amount in the opening balance from **ACTUAL REFUNDABLE AMOUNT**, the same as the **Opening Balance B/F** row does. Before, the totals row left it in, so the total can now be lower than before. This is intended. --- # 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/reports-queries/sale-registers/cash-card-status-report.md?ask=&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.