Module 13 of 13 · M113
Bank Accounts Reconciliation
Matched under your own banking rules
The books proved against the bank: statement transactions matched to ledger records under defined banking rules, with differences surfaced rather than buried.
Grouped as Entries
- Definitions
- 2
- Transactions
- 4
- Enquiries
- 2
- Reports
- 1
Total 9
Counted from the application’s own menu.
Screenshot reserved Reconcile Real Bank Account Transaction — Bank Accounts Reconciliation
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.
Bank Accounts Reconciliation carries 9 entries across 4 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
- Banking Business Rules
Transactions 4
- Reconcile Real Bank Account Transaction
- Delete / Value Date / Reconcile Real Bank Account
- Bank Account Transactions Register
- Simulate Bank Transactions Processes
Enquiries 2
- Banking Business Rules
- Bank Account Transactions Register
Reports 1
- Bank Reconciliation Report
One set of books
Where Bank Accounts Reconciliation meets the ledger
Bank Accounts Reconciliation 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.