Common procurement errors in COINS ERP+ include budget validation alerts, buyer limit errors and goods receipt note (GRN) posting issues. This article explains each error and the steps to resolve it.
Budget validation errors on purchase orders
Budget validation alerts appear when a purchase order exceeds the budget set for a job or service order. The behaviour depends on how the PO/BUDCCWRN parameter is configured in your environment.
Parameter value | Behaviour |
W | Displays a warning but allows you to continue. |
E | Displays an error and prevents you from continuing. |
N | No alert is displayed when the budget is exceeded. |
If you receive a budget validation error and cannot proceed, check with your finance team whether the purchase order amount is correct or whether the budget needs updating before the order can be raised.
Change the validation behaviour
Go to Parameter Maintenance.
Search for PO/BUDCCWRN.
Update the value to W (warning), E (error) or N (no alert) as required.
Save your changes.
⚠️Important: Only system administrators should change parameter values. Incorrect configuration may affect budget controls across all purchase orders.
Buyer limit exceeded errors
When adding or editing a purchase order line, the total value of all lines on the order cannot exceed your buyer limit. If it does, an error is displayed and you cannot save the order.
Resolve a buyer limit error
Check the total value of all lines on the purchase order.
Reduce the order value to bring it within your buyer limit, or split the order into separate orders.
If your buyer limit needs to be increased, contact your system administrator.
📌Note: A buyer limit of 0 means there is no limit set for that buyer.
GRN not posting or missing from the system
If a goods receipt note (GRN) has not posted correctly or is missing from the system, this can cause month-end discrepancies — particularly when using the stock module.
Confirm the GRN has been entered in COINS ERP+ and is not still in a draft or uncommitted state.
Check for any unwanted accruals linked to the GRN and clear them if required.
If you are running month end, confirm all GRNs are entered before running the close procedure.
If the GRN is missing or cannot be located, raise a support ticket with the order reference and expected GRN details.
⚠️Important: Confirming all GRNs before month end is especially important when using the stock module. Missing GRNs can cause stock and financial reporting discrepancies.
Raise a support ticket
Raise a support ticket if:
A budget validation error blocks a purchase order you believe is correctly budgeted.
A GRN cannot be located after entry.
You experience errors not covered in this article.
Include the purchase order or GRN reference, the module name, the exact error message and a screenshot where possible.