> 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-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/pos-options/pos-options-1/do-not-allow-manual-credit-entry-in-billing.md).

# Do not allow Manual Credit Entry in Billing

**YouTube:** [How to Disallow Manual Credit Amount Entry in Sale Bill?](https://www.youtube.com/watch?v=iwkPs8zjL9M) 

## How to Disallow Manual Credit Amount Entry in Sale Bill?

In this tutorial, we will walk you through a feature in **Logic ERP** that **restricts manual credit amount entry** during billing, ensuring better control and accuracy in payment processing.

***

### Default Behavior

By default, when making a payment using the **credit card option**, users are allowed to **manually enter the credit amount** in the credit card details window.

***

### Access Global Settings in Logic Admin

* Open **Logic Admin**.
* Navigate to **Global Settings**.
* Under **POS Options**, go to the **POS Options 1** section.
* Locate and enable the option labeled as:&#x20;

> **"Do not allow Manual Credit Entry in Billing"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FNMDIUq4T2DXicrvuJuPf%2FDo%20not%20allow%20Manual%20Credit%20Entry%20in%20Billing.png?alt=media&amp;token=d4203f55-efda-40c0-9f90-6ef7977528f3" alt=""><figcaption></figcaption></figure>

* Click **Save** and **restart the software** to apply the changes.

***

### Implement the Feature

* Open the **Sale Bill – Touch Screen** window and create a new transaction.
* Proceed to the **Multi-Pay Details** screen.
* You will observe that the **credit amount field is now disabled**, preventing any manual entry.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FXaR2T9aHpzZ2LWsixBJF%2FCred%20desable.png?alt=media&amp;token=79736598-90a7-4e24-9da7-42d5c97c1265" alt=""><figcaption></figcaption></figure>

***

### Summary

This feature ensures that credit amounts are system-calculated, reducing the chances of manual errors or unauthorized credit adjustments — helping maintain financial integrity at the point of sale.


---

# 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-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/pos-options/pos-options-1/do-not-allow-manual-credit-entry-in-billing.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.
