While many organisations rely on month-end variance analysis to catch budget overruns, Infor SunSystems offers Budget Check, a proactive, built-in mechanism that stops unauthorised spending before the money ever leaves the business.
Understanding how to configure and deploy Budget Check properly lets organisations move from reactive damage control to real-time financial discipline without creating unnecessary operational bottlenecks.
Learn more: What’s New in the Infor SunSystems Cloud October 2026 Release?
What is a budget check in Infor SunSystems?
The budget check function in Infor SunSystems is a set of budget checking rules that tells the system where the budget for an account, or range of accounts, is held. Whenever a ledger, purchase invoice or purchase order transaction is entered for that account, SunSystems uses those rules to decide whether enough budget is available to cover it, and warns or stops the user if it is not.
According to Infor’s documentation, SunSystems budgeting lets organisations hold budget values against accounts and analysis codes to:
- Control expenses and notify users when a transaction exceeds the available budget
- Provide comparative figures for actual, budget, and forecast reporting
Budget checking is the first of these purposes in action.
SunSystems offers two types of budget checking, depending on which modules an organisation uses:
- Expenditure checking monitors actual spending against budget for selected accounts in SunSystems Financials. It applies to ledger transactions entered or imported, and to purchase invoices entered in SunSystems Order Fulfilment.
- Commitment checking monitors purchase orders as they are raised in Order Fulfilment Purchasing, so orders that would exceed the available budget can be caught before the commitment is made.
In both cases, the system works from the same simple formula:
Available budget = Budget − Actual expenditure − Committed expenditure
When a transaction is entered, SunSystems searches all budget check definitions to determine where the account’s budget is held, and whether commitment checking is required. These definitions are created in Budget Check Setup (BCS).
A budget check can link several actual accounts to the same budget account, for example, when travel, accommodation and meals all draw on one travel allowance. It can also identify multiple analysis codes when the budget is held at the analysis code level, such as by department or project.
Read more: Corporate Budgeting in Vietnam, Thailand and Cambodia: What the Data Says?
An account can also be checked against a combination of the budgets available at analysis code and account level. For instance, a marketing budget may be allocated across several departments at the analysis code level. If one department exhausts its allocation, it may still be able to draw on a budget held at the marketing account level.
For finance leaders, this layered approach means stricter as well as more flexible control without anyone having to step outside the system.
How does budget checking work in Infor SunSystems?
Budget checking links the accounts where money is spent to the budget accounts where the allowance is held, then checks every relevant transaction against that allowance as it is entered.
In Budget Check Setup, each record specifies the Budget Check Account Code, which is the budget ledger account holding the allowance for the selected account or range of accounts. Because budgets can be set at different levels and drawn from a combination of budget accounts, finance can choose how broad or how granular each control should be.
For organisations using SunSystems Order Fulfilment, a few additional settings in Purchase Business Setup (PBS) and Purchase Type Definitions switch on over-expenditure checking for purchase invoices and over-commitment checking for purchase orders. Notably, no ledger interface postings are required for budget checking in Order Fulfilment.
Read more: Meliá Paradisus Bali Chooses TRG for Infor SunSystems Cloud Implementation
Tips for setting up budget checks that work
A budget check is only as useful as the rules behind it. Set them too tight and users drown in warnings; set them too loose and the control exists only on paper. TRG recommends finance teams consider the following:
- Start with the accounts that matter most. Consider beginning with the discretionary or restricted spending lines where overspend actually hurts, then extend coverage over time.
- Agree the policy before the configuration. Decide with budget holders which navigation method and budget type reflect how each department really spends, instead of setting default rules everywhere.
- Use tolerances deliberately. Tolerances and operator group overrides are useful for small, legitimate overruns, but they should be documented and reviewed, not used to bypass the control.
- Keep budget values current. If the budget ledger is not updated after reforecasts or approved reallocations, the check will flag spending that has already been authorised, and users will quickly learn to ignore it.
- Train the people who see the warnings. A warning is only effective if the person seeing it knows what it means and what to do next. Budget holders and AP users need to understand the rule, not just the message.
Read more: In a World of AI and Automation, Don’t Leave Your Finance Team Behind
TRG’s perspective: budget control that people actually use
For TRG International, budget checking is one of the most underused controls in Infor SunSystems. The functionality is there, but it can end up switched off after go-live when the rules were never agreed with the people who live with them, or when warnings start appearing for spending that had already been approved elsewhere.
Getting it right is mostly about design and adoption. That is why our consultants typically help clients in three ways:
- Design the control framework with finance and budget holders to identify which accounts to check, how budgets should flow between periods and what tolerances are acceptable.
- Configure and test budget checks, commitment checking and Order Fulfilment settings in SunSystems so they reflect that policy.
- Train the users who will see and act on the warnings through TRG End-User Training, available online through TRG Academy, onsite or as a hybrid programme.
Want to see how budget checking could work for your organisation? Request an Infor SunSystems demo with TRG today!
FAQs
What is a budget check in Infor SunSystems? It is a set of rules that warns or holds the transaction if the budget would be exceeded.
How does Infor SunSystems’ budget checking work? Budget checking links the accounts where money is spent to the budget accounts where the allowance is held, then checks every relevant transaction against that allowance as it is entered.
What is the difference between expenditure checking and commitment checking? Expenditure checking monitors actual spending from ledger transactions and purchase invoices. Commitment checking checks purchase orders as they are raised, so spending can be stopped before it is committed.
Can users override a budget check? Yes, depending on operator group settings and the tolerances defined by finance. Transactions within tolerance trigger a warning; purchase invoices outside it are held.
References:
- https://docs.infor.com/sunsystems/6.3.x/en-us/ssolh/ssfiaolh/lsm1457708252266.html (Infor, What Budget Controls are Available?, SunSystems 6.3.x)
- https://docs.infor.com/sunsystems/6.3.x/en-us/ssolh/ssfiaolh/lsm1457708252328.html (Infor, What is Expenditure Checking?, SunSystems 6.3.x)
- https://docs.infor.com/sunsystems/6.4.x/en-us/ssolh/ssfiaolh/etq1539549342723.html (Infor, Budget Check Setup (BCS): General, SunSystems 6.4.x)
- https://docs.infor.com/sunsystems/6.4.x/en-us/ssolh/ssfiaolh/lsm1457708252921.html (Infor, Setting Up Expenditure and Commitment Checking, SunSystems 6.4.x)
- https://docs.infor.com/sunsystems/6.3.x/en-us/ssolh/default.html?helpcontent=lsm1457708252531.html (Infor, What is a Budget Check?, SunSystems 6.3.x)
