How is bank reconciliation configured in an ERP system — the accounts and settings it requires, including for manual bank reconciliation?

What belongs to configuration rather than to running the function?

Configuration is what the reconciliation function reads: the bank account record and its ledger link, the starting point, posting-date limits, how statements arrive, the matching and posting rules, and who may change each. Loading, matching and posting a statement is running it; that, the tie-out itself and finding the function in your menus are separate questions.

The boundary moves between products: Microsoft's bank reconciliation help for Dynamics 365 Business Central online has the automatic-matching date tolerance entered at each run, while Oracle's tolerance-rules overview for Oracle Fusion Cloud Financials 26C stores it as a rule attached to a matching rule. The details below come from those two products; object names and locations, whether an object is mandatory and in which path, whether a setting is stored or entered at run time, and how predefined roles bundle rights vary by product and release, so confirm anything you skip in your own product's documentation. Microsoft's Business Central help described below was last updated between September 2022 and April 2026; confirm it for your version and for any on-premises deployment.

How should the ledger cash account and the bank master record be linked?

Give each bank account its own ledger cash account. Oracle's guidance on creating bank accounts assigns each a unique general ledger cash account for all its cash transactions, because this facilitates book-to-bank reconciliation, and offers an optional GL Cash Account Segments setting that reconciles several cash account combinations sharing one natural account; decide whether you use it and record why.

In Business Central the link runs through the bank account posting group; Microsoft's page on setting up bank accounts says accounts sharing a posting group post to the same G/L accounts, and Microsoft's bank reconciliation help says it does not recommend using the same G/L account for multiple banks. The same help adds a rule: avoid direct posting on that G/L account, which breaks the link between bank ledger entries and G/L entries.

The bank master record carries the rest of what the function depends on:

• Ledger link. The posting group or cash account field decides where every movement lands.
• Currency. Microsoft's setup page says every transaction and check on a Business Central bank account with a currency code must use that currency.
• Access. Oracle's account-creation guidance secures Payables and Receivables access to a bank account by business unit, limited to business units on the owning legal entity's ledger.
• Opening balance. Microsoft's setup page has it posted through a bank account reconciliation, or through Migrate Business Data in a new company, and the amount then reaches the G/L cash account.

Do not also post the opening cash balance directly to that G/L account; Microsoft's setup page requires any direct posting there to be balanced before the first reconciliation, especially for a foreign-currency account, and describes reversing such an entry out of the G/L account used to balance the opening general ledger.

What changes with several bank accounts, entities or currencies?

Configure per account whatever identifies an account or reads its statements, and check what a shared setting reaches before changing it. Microsoft's bank reconciliation help attaches an import format to one bank account, but Microsoft's posting-periods page applies General Ledger Setup posting dates to the whole company. Oracle's automatic reconciliation topic uses the rule set assigned to each bank account, and Oracle's transaction-creation overview assigns creation rules to accounts as separate objects, so list every account a rule set or rule serves before editing it.

Should payments pass through a clearing or in-transit account?

Decide before the first posting: the choice changes what the reconciliation proves and is hard to reverse.

Posting straight to the cash account (no clearing account) is the simpler design. Microsoft's setup page says a Business Central bank payment creates entries in the bank account and its G/L account at once, so payments the bank has not processed sit in cash as reconciling items.

Posting through a clearing account moves issued but uncleared payments out of cash. Oracle's guidelines for payment accounting options in release 26C describe a Payables setting that decides when payment accounting entries are created; with accounting at payment issue and clearing, issue credits cash clearing and clearing moves the amount to cash. The same guidelines offer three values: at payment issue, cash is credited when the payment is created, so uncleared payments are reconciling items in cash; at payment clearing, cash is credited only when the payment clears, so the liability stays open and no clearing account is used; and at payment issue and clearing, shown below. For a payment of 1,000.00:

The clearing account holds 1,000.00 between the two events, then returns to zero. The option covers payments only; check separately how your product accounts for deposits and transfers between your own accounts. The same Oracle guidelines say not to update the setting after the first implementation, because changing it causes the accounting to be stuck; their route to a different option is a new business unit.

What should a clearing balance contain?

Only items on their way through. That is a recommendation adapted from a screening step, not a rule from an accounting standard or control framework: the National Credit Union Administration's examiner job aid for credit union examinations flags suspense and clearing accounts that do not regularly clear to a zero balance, and bank reconcilements that contain stale items. A payments clearing account carries a balance whenever payments are outstanding, so test items rather than a zero balance: each should be a specific payment you can name and date that is still expected to clear, with anything old investigated rather than carried. Consider holding in-transit accounts for transfers between your own bank accounts, and suspense accounts for unidentified bank items, to the same test.

Which settings govern how statement lines are matched and posted?

How should statement numbers and posting dates be set?

Microsoft's bank reconciliation help says Business Central takes each new reconciliation's statement number and Balance Last Statement from the bank account, and that the number matters for imported CAMT files carrying statement numbers and for printed statements, so start both from your first statement. The same help says both values can be changed before each new reconciliation, so the approver should check each reconciliation's Balance Last Statement against the previous posted statement's ending balance. In the North American version, the same help requires the Bank Recon. with Auto-Match toggle on General Ledger Setup to be on before Undo can correct a posted reconciliation; clearing it switches to the Bank Rec. Worksheet page, whose posted statements cannot be undone, so decide it before the first reconciliation.

Microsoft's posting-periods page sets date limits with Allow Posting From and Allow Posting To on General Ledger Setup, lets User Setup limits overrule them, and evaluates date formulas against a work date users can change, so use fixed dates for any boundary users must not move.

How are matching rules defined and ordered?

Oracle's automatic reconciliation topic defines a rule set as matching rules and tolerance rules sequenced in the order they run, assigned to each bank account reconciled automatically. That topic does not say which order to choose; the configuration owner decides it.

How wide should matching tolerances be?

Only as wide as a reason you can name. Oracle's tolerance-rules overview gives rounding and conversion-rate differences and bank processing fees as uses for amount tolerances, and checks that clear days or weeks after issue for date tolerances. Its rules show why width matters:

• No tolerance. A rule without a date or amount tolerance requires an exact match.
• Amount tolerance. It works only for one-to-one matches, and in automatic reconciliation any difference within it is created as an external transaction. Where a percentage and an amount both apply, the most conservative is used.
• Date tolerance. In automatic reconciliation, when the matching rule matches on date, a breach prevents reconciliation.

Microsoft's bank reconciliation help says a Business Central date tolerance of 0 or blank limits Match Automatically to the ledger entry's posting date. An over-wide tolerance reports agreement nobody established, and an Oracle amount tolerance also books the difference, so revisit tolerances whenever an unexpected match appears.

Where do items that start at the bank post?

Bank charges, fees and interest reach the statement first, so decide which account each posts to. Oracle's transaction-creation overview says its rules create and account for transactions from unreconciled lines for such first-notice items, and requires autoreconciliation and any manual reconciliation to be finished first so that lines already recorded are not duplicated. Oracle's automatic reconciliation topic offers a Generate Cash Transactions option that submits the creation process after autoreconciliation completes. That topic does not say how this fits the transaction-creation overview's required order; if it runs before you match by hand, the process could create transactions for lines you would have matched, so test the combination with line 6 of the test pack below.

Oracle's automatic reconciliation topic also lists subledger accounting rules for external transactions among its prerequisites; since the tolerance-rules overview turns amount-tolerance differences into external transactions, those accounting rules decide where the differences post. Microsoft's bank reconciliation help has Business Central's Transfer to General Journal create lines for statement lines missing ledger entries, with the preparer completing the balancing account, so give preparers the target accounts in writing and have the approver check each line posted from Transfer to General Journal against the statement and those accounts.

What changes when statements arrive electronically?

Electronic loading adds objects that exist only to read the bank's file, configured per bank and per format. Oracle's electronic-statement page lists these prerequisites:

• Format. Oracle delivers one format for each supported statement format, and you can add more.
• Codes. Oracle provides ISO 20022 balance codes and lets you define more, and its automatic reconciliation topic says transaction codes must match your bank's.
• Code map groups. They map the bank file's codes to internal ones, and the delivered groups provide only basic mappings, so check them against your bank's file.
• Parsing rules. Oracle calls them optional but relevant to reconciliation.

Name who corrects failed loads, since Oracle's electronic-statement page expects reported import errors to be corrected. Microsoft's bank reconciliation help says Business Central bank feeds require the Envestnet Yodlee Bank Feed service with your bank accounts linked, and file imports use the per-account import format described above; Microsoft's setup page adds a data exchange definition that maps the file to Business Central's fields. If some accounts' statements arrive by file and others are keyed, configure each account for its own path. Switching on automatic reconciliation in a live system is a separate question.

What does a reconciliation keyed and matched by hand still need?

A manual reconciliation still posts, so it still needs these objects:

• The ledger cash account and the bank master record linked to it
• The opening balance, first statement number and statement balances
• Open posting dates
• Accounts for bank charges, interest and suspense items
• Separate roles for configuring, reconciling and reviewing

It can usually skip formats, code maps, parsing rules and matching rule sets, but confirm each skipped object in your own product's documentation. Microsoft's bank reconciliation help lets you enter transactions manually, skip automatic matching and link lines with Match Manually. Its Suggest Lines action fills statement lines from Business Central invoices with outstanding payments, your own records rather than the bank's, so check each suggested line against the bank statement. Oracle's tolerance-rules overview makes a tolerance rule optional for manual reconciliation, and an assigned date tolerance only warns, so it advises rather than controls.

Who should configure the function, and who should run it?

Keep configuration rights away from the people who run and approve reconciliations: an owner configures, the preparer runs, and someone holding neither role approves. The Public Company Accounting Oversight Board's standard AS 2110 lists among IT risks to internal control over financial reporting unauthorized changes to data in master files and unauthorized changes to systems or programs. Someone who can widen a tolerance and approve the reconciliation it produces can report agreement nobody established.

Oracle's security reference for the predefined Cash Manager job role in 26C shows it granting all of these together:

• The Cash Management Administration duty, with privileges to manage tolerance rules, matching rules, rule sets and transaction creation rules
• The Reconcile Bank Statement privilege
• The Mark Bank Statement Reconciliation Reviewed privilege

The same reference describes its reconciling duty as also managing setup information for bank statement processing and reconciliation. Do not give the predefined Cash Manager role to the preparer or the approver. Oracle's account-creation guidance documents creating a custom role with a privilege removed; build the preparer's role without the Cash Management Administration duty and without Mark Bank Statement Reconciliation Reviewed, and the approver's role with that privilege but without the Cash Management Administration duty or Reconcile Bank Statement.

In Business Central the preparer enters the date tolerance when running Match Automatically, which configuration rights cannot prevent, so the approver should review automatic matches; Microsoft's bank reconciliation help says Match Details shows the fields that contained matching values. Microsoft's permissions page describes a permission set as a collection of permissions for database objects, lets you add your own, and shows which sets enable a task; use that to confirm the preparer cannot change bank accounts, bank account posting groups, General Ledger Setup, User Setup or General Journal Templates. If you cannot change configuration yourself, hand the checklist below to whoever can.

How do you prove the setup before it touches live books?

Never let the first live statement be the first test: every error then becomes a correction to entries that already exist. NIST's security and privacy control catalog, SP 800-53 Revision 5.1, though not written for accounting, calls for changes to a system to be tested, validated and documented before their implementation is finalized. Microsoft's sandbox page describes a Business Central sandbox as isolated from production, and an administrator can create one that includes production data.

Build a known-answer test: for each bank account and format, a statement in which you decide in advance what every line should do, such as this pack for one account:

Then sign in with each role. In Oracle, where its security reference leaves open which setup the reconciling duty manages, confirm the preparer's role cannot mark a reconciliation reviewed or create or edit tolerance rules, matching rules, rule sets or their bank account assignment, transaction creation rules, bank statement transaction codes, parse rule sets, code map groups, formats, or a bank account's cash account and security. Confirm the Oracle approver's role can mark reconciliations reviewed but cannot reconcile or edit any of those objects. In Business Central, confirm the preparer cannot edit the bank account card, its posting group, the G/L account's direct-posting setting, General Ledger Setup, User Setup or General Journal Templates.

The setup passes when every line ends where you predicted and every posting lands on the intended account; a line that matched when it should have stayed open fails even if the totals agree. Microsoft's bank reconciliation help offers a Test Report that previews a reconciliation before posting. Rerun the pack after every configuration change and every change to the bank's file.

What record should the configuration leave behind?

Treat the finished setup as a baseline configuration, which NIST's glossary defines as a documented set of specifications, formally reviewed and agreed on at a given point in time, that can be changed only through change control. For bank reconciliation, the record should hold:

• Every checklist element, its value and what it reaches
• The reason for each non-obvious choice, especially tolerance widths and the clearing decision
• Who approved each setting and when
• The test pack, its results and who signed them off
• Decisions that are hard to reverse, such as Oracle's payment accounting value and why it was chosen

Update the record with every change, so the next person can tell an intentional setting from an accident.

What should the configuration checklist hold?

The elements below come from the two documented products; check each against your own release: