> For the complete documentation index, see [llms.txt](https://guide.acumensystems.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.acumensystems.com.au/system-parts/master-files/customers/miscellaneous-customers.md). # Miscellaneous Customers These are customer types rather than individual customers. By designating a customer record as Miscellaneous you are instructing the system that this is a group of people/companies that have many things in common but are not the same entity each time they are referred to. When a sale, quote or order is made to a miscellaneous customer you are provided with the ability to identify the customer in detail specifically for that document. This means that for each document a miscellaneous customer can have a different name, address and price method. All miscellaneous customers are automatically set to cash only terms. This is to prevent account sales being made to a customer where the receipt would not easily be identifiable to the original invoice, given that each invoice may have a different name. The classic example of a miscellaneous customer is given in the default customer record. (dot \[.] customer code). The purpose of this record is to allow definition of the customer and pricing for over the counter, casual, cash in hand sales. It is not intended that this be the only record that can be used for cash sales. A cash sale can always be made to a customer who typically buys on regular terms (eg. 30 days). If a customer regularly buys goods from you and pays cash you may wish to add that customer as their own separate entry rather than using the default customer. This has the benefit of recording the sales for that customer, allowing customer pricing and saving the repeated entry of customer delivery and other details. --- # 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://guide.acumensystems.com.au/system-parts/master-files/customers/miscellaneous-customers.md?ask=&goal= ``` `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.