> 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-2/credit-amount-posting-for-retail-customers.md).

# Credit Amount Posting for Retail Customers

**YouTube:** [How to Configure Global Settings for Credit Amount Posting to Retail Customers in Sale Bill?](https://www.youtube.com/watch?v=UU0wQIFUCLM\&t=59s)

## How to Configure Global Settings for Credit Amount Posting to Retail Customers in Sale Bill?

In this tutorial, we’ll learn how to configure **credit amount posting behavior** for retail customers based on the type of sale (Regular, Home Delivery, or Takeaway) in **Logic ERP**.

This setting controls whether the **credit amount** is posted to the **retail customer's account** or the **default customer account**.

***

### Access Global Settings in Logic Admin

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

> **"Credit Amount Posting for Retail Customers"**

<figure><img src="/files/bzqD8zwoRLCs2NCBaQY3" alt=""><figcaption></figcaption></figure>

> This option is also available per **Sale Voucher Configuration but** setting it from **Global Settings** ensures uniform behavior across **all series and branches**.

***

### **Post Against Retail Customer for Non-Home Delivery Only**

* **Behavior:**\
  Credit will be posted to the **retail customer account** for **Regular** and **Takeaway** bills.\
  For **Home Delivery**, credit goes to the **default customer account**.
* **Steps to Implement:**
  * Enable this option
  * Save settings and **restart the software**
  * Create a new sale bill
  * Select a retail customer
  * Choose **bill type** (Regular or Takeaway)

<figure><img src="/files/Q87HPKC8WYu1fWdy4nqu" alt=""><figcaption></figcaption></figure>

* Enter partial cash + credit payment

<figure><img src="/files/pOu8Hlt9yocQX0adKWjL" alt=""><figcaption></figcaption></figure>

* Save and check the **Journal Report**
* **Result:**\
  Credit amount is posted under the **Retail Customer** account (for non-home delivery types)

<figure><img src="/files/3ynQXfS4Ry0zLrXhmg0f" alt=""><figcaption></figcaption></figure>

**Best For:** Restaurants and retail setups where home deliveries are billed to a central account, but walk-ins are billed directly to the customer.

***

### **Do Not Post the Entry**

* **Behavior:**\
  The credit amount is **never posted** to the retail customer account—**regardless** of bill type. It is posted under the **default customer account**.
* **Steps to Test:**
  * Enable this option
  * Restart the software
  * Create a bill with any **bill type**
  * Select a customer
  * Use cash + credit for payment (Do as same as we did in previous step)
* Save and check the **Journal Report**
* **Result:**\
  Credit amount is posted to the **Default Customer Account**, not the retail customer

<figure><img src="/files/h0INYM3DDLCo8w8XeFYh" alt=""><figcaption></figcaption></figure>

**Best For:** Environments where customer-level ledger tracking is **not required**, and a central ledger is preferred.

***

### **Always Post Against Retail Customer**

* **Behavior:**\
  Credit is **always** posted to the **retail customer account**, regardless of the bill type—**Regular**, **Takeaway**, or **Home Delivery**.
* **Steps to Test:**
  * Enable this option
  * Save and restart the software
  * Create a sale bill
  * Select or create a retail customer
  * Choose any bill type
  * Make a partial payment + credit (Do as same as we did in previous step)
  * Save and check the **Journal Report**
* **Result:**\
  Credit is posted under the **Retail Customer’s Account**

<figure><img src="/files/NDAZ6HcPCUi13Tg8Qxu7" alt=""><figcaption></figcaption></figure>

**Best For:** Businesses that require **individual customer credit tracking** for all types of sales.

***

### Summary Table

| Option                                                      | Credit Posted To                            | Applies To Bill Type | Ideal For                                      |
| ----------------------------------------------------------- | ------------------------------------------- | -------------------- | ---------------------------------------------- |
| **Post Against Retail Customer for Non-Home Delivery Only** | Retail Customer (only for Regular/Takeaway) | Regular, Takeaway    | Restaurants with central home delivery billing |
| **Do Not Post the Entry**                                   | Default Customer Account                    | All types            | Centralized ledger usage                       |
| **Always Post Against Retail Customer**                     | Retail Customer                             | All types            | Customer-wise credit tracking                  |

***

### Final Notes

* Always **restart the software** after changing global settings to apply changes.
* If you’re using **series-wise configuration**, ensure consistency across branches.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/pos-options/pos-options-2/credit-amount-posting-for-retail-customers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
