Module 11 of 13 · M111
Budgeting & Credit Control
Budgets before spend, limits before credit
Spending held to budget and exposure held to limit: account budgets, credit limits and age analysis of debt, so commitments are made with open eyes.
Grouped as Entries
- Definitions
- 2
- Transactions
- 1
- Periodic Processes
- 1
- Enquiries
- 1
- Reports
- 5
Total 10
Counted from the application’s own menu.
Screenshot reserved Accounts Budget — Budgeting & Credit Control
The inventory
What this module holds
Every module in Magnet ERP files its screens under the same five headings — Definitions hold the reference data the module works from, Transactions are the entries staff make day to day, Periodic Processes are the runs made at the turn of a period, Enquiries look up what is on record, and Reports print it — so a clerk who has learnt one module already knows where to look in the next.
Budgeting & Credit Control carries 10 entries across 5 of those headings. What follows is the module’s own menu, entry for entry, in the order the application lists it.
One thing to read the list with: a posted entry is never overwritten. A document is corrected while it is still unverified; once it has been endorsed it can only be undone by a reversal, and the reversal is a dated record of its own. Every module, this one included, opens with its Endorsement Officers for the same reason: someone named has to stand behind what is posted. That is what makes the books defensible when somebody comes to audit them.
Definitions 2
- Endorsement Officers
- Accounts Credit Limit
Transactions 1
- Accounts Budget
Periodic Processes 1
- Age Out Old Budget
Enquiries 1
- Accounts Budget Enquiry
Reports 5
- Account Information
- Account Managers Report
- Accounts on Facility Report
- Age Analysis of Debt Reports
- Budget Details Listing
One set of books
Where Budgeting & Credit Control meets the ledger
Budgeting & Credit Control keeps its own registers; it does not keep its own books. What is recorded in this module posts through to the Integrated General Ledger — the chart of accounts, the journal vouchers, the accounting periods and the period close. Every module posts here; the business keeps one set of books.
That single set of books is also where the project claim is settled. MagnetERP is called an Enterprise Projects Business Solution because every transaction can be linked to a registered chart of projects or to project-milestone codes — contract job batches, production job batches and procurement job batches. That applies to the entries this module makes as much as to any other.
Every transaction keeps its own currency and its exchange rate to the base currency. And because one organisation may run several companies in Magnet ERP, each company’s records are kept properly separate: a figure posted in one is never quietly counted in another.