- Home
- Blog
- EDGEBIC How-To
- How to Set a Customer Credit Limit in EDGEBIC
To set a customer credit limit in EDGEBIC by User Solutions, open the Customers tab, edit the customer, enter the value in the Credit Limit field under Financial Information, and click Save Customer. The limit must be zero or positive. It is purely informational: EDGEBIC warns when the customer's balance exceeds it and never blocks an order. For the concepts behind customer records, read customers and departments explained.
Before you start
- The customer record exists. If not, see how to add a customer.
- You have the limit from whoever owns credit in your business. This is a finance number, not a planning number.
- You have the current balance to hand too, because the warning compares the two and a stale balance produces noise.
- Decide who will refresh both figures and how often. That decision matters more than the initial value.
Steps
- Open the Customers tab from the main navigation.
- Find the customer. Type in the grid's search panel to filter, and untick Active Only if the record is inactive.
- Click the edit button in the row's Actions column. The dialog opens with the heading Edit Customer.
- Go to the Financial Information section.
- Enter the Credit Limit. It must be zero or positive. Enter
0if you do not want the check to run at all. - Update Current Balance in the same visit if you have a fresher figure. That field is usually maintained from your accounting system.
- Enter the Tax ID while you are there if the customer's documents need it.
- Click Save Customer.
If the balance you entered exceeds the limit, a Validation Warnings prompt lists the issue and asks "Do you want to continue saving?" Click Yes to save anyway.
What changes when you save
| Surface | Effect |
|---|---|
| Customer grid | The Credit Limit and Balance columns show the new figures |
| Saving the customer | A warning appears whenever the balance exceeds the limit |
| Manufacturing orders and quotes | Nothing is blocked. Orders can still be raised for the customer |
| The schedule | Nothing. The scheduler never reads customer data |
The design here is deliberate. Credit control is a business process with people and judgment in it, so EDGEBIC surfaces the condition and leaves the decision where it belongs. If you need production actually held for an over-limit account, control that through the manufacturing order, because that is the object the scheduler reads.
How to check it worked
- Confirm the new value in the Credit Limit column of the customer grid.
- Re-open the customer and save without changing anything. If the balance exceeds the limit, the warning should appear. If it does not and you expected it to, check that the limit is not zero.
- Raise a test order or quote for the customer and confirm it is not blocked. That is the correct behavior.
- Check the balance figure against your accounting system. A limit is only meaningful next to a current balance.
Common mistakes
Setting a limit nobody refreshes. The check compares two maintained fields. If neither is updated, the warning fires on every save until people stop reading it.
Expecting the limit to enforce anything. It does not block orders, quotes, or scheduling. It raises a prompt.
Entering a negative value. The field must be zero or positive, and a negative entry is rejected.
Treating the balance as calculated. EDGEBIC does not derive a receivable balance from orders. The number is whatever was last entered.
Once the financial fields are current, the other half of the account picture is the work itself: how to view a customer's order history puts every order and quote for one account in a single dialog. All the single-task recipes are indexed in the EDGEBIC how-to library, and the EDGEBIC product page shows how order data meets finite capacity.
Expert Q&A: Deep Dive
Q: Every save on our biggest account throws a credit warning. Is something misconfigured?
A: Almost certainly the two numbers are stale rather than the setup being wrong. The check simply compares the current balance field to the credit limit field, and both are planner-maintained, so a balance entered at go-live against a limit that was never revised will trip on every edit forever. Refresh both from your accounting system on whatever rhythm you can sustain, monthly at minimum. If nobody will own the refresh, set the limit to zero and turn the check off rather than training everyone to click through a warning, because a warning people always dismiss stops being a warning.
Q: We want production held for over-limit customers. Can the credit limit do that?
A: Not on its own. The limit raises a warning and nothing more, and the scheduler never reads customer data at all, so a job for an over-limit account schedules exactly like any other. The workable pattern is procedural: use the credit warning as the trigger for a human check, and control the work through the manufacturing order rather than the customer record. Holding or not releasing the order is what actually keeps capacity free, because that is the object the scheduler reads.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
