Bank reconciliation compares the company’s accounting records with the bank’s record of activity and explains the differences. Acumatica Cash Management brings together cash-related activity from financial modules for clearing and reconciliation. Its Bank Feeds offering supports transaction imports and matching, with unmatched items available for review. Acumatica Cash Management, Acumatica Bank Feeds
The important distinction is between a difference that has an explanation and a difference that has not yet been investigated. Two balances can differ because they describe different timing or activity. Making them numerically equal without understanding the cause can conceal the problem.
A useful reconciliation process therefore establishes the period, checks the completeness of the information, and reviews the evidence behind each exception.
Begin with the account and cutoff
Confirm which bank account and accounting cash account are being compared, along with the relevant statement date or period. An accurate report for the wrong account will not become useful through more detailed matching.
Also identify the date basis used by each record. A transaction date, processing date, and bank-posting date can describe different events. The reviewer needs to know which one governs the report or statement being examined.
Before investigating individual amounts, check whether the imported activity covers the full intended period. A partial feed can create apparent exceptions that disappear when the missing activity arrives. That does not mean the reviewer should wait indefinitely; it means completeness should be established as part of the investigation.
Importing a transaction does not explain it
Acumatica describes both connected bank feeds and bank-file import options, noting that imports may be needed for institutions not supported by a feed. It also describes scheduled retrieval and automated matching. These are capabilities to confirm against the bank and accounts the company actually uses. Acumatica bank connectivity
The import gives the accounting team a bank record to work with. The team still needs to establish which business event it represents and whether the corresponding accounting record is complete.
A bank description may be abbreviated, a payment may cover several invoices, or a deposit may represent a processor batch. Those situations require context rather than a new accounting entry created solely to make an unmatched line disappear.
Timing differences can be legitimate
Consider a hypothetical month-end review. The company has recorded a $3,000 payment that has not yet appeared on the statement through the selected cutoff. The absence of the bank entry at that cutoff does not automatically establish that the payment record is wrong.
The reviewer needs the relevant payment evidence and an explanation of the timing. If the item later clears as expected, that supports the explanation. If it remains unresolved beyond the anticipated process, it requires further investigation.
The same reasoning can apply to incoming activity that is recorded in one part of the process before it appears as a bank deposit. The customer payments guide separates invoice application from settlement so the reviewer can identify which evidence is still missing.
A timing explanation should be recorded precisely enough for another person to understand it. “Will clear later” is weaker than an identified item with a known source, amount, date, and follow-up.
Matching needs more than an equal amount
Two transactions can have the same amount without representing the same event. A proposed match should be assessed using the available reference, date, counterparty, and supporting documents.
Acumatica’s Bank Feeds page describes matching a bank transaction to one or more financial documents. That can help with grouped activity, but the grouping still needs a sound basis in the underlying records. Acumatica transaction matching
A hypothetical $5,000 deposit might represent one customer payment, several customer receipts, or a settlement batch. The number alone cannot determine which interpretation is correct.
During implementation, test how the company’s actual bank descriptions and references appear in the proposed process. A demonstration with unusually clean sample data may not reveal the review work required by real statements.
Classify exceptions by the next investigation
A small set of working categories can make the unresolved population easier to manage.
| Exception | First investigation |
|---|---|
| Bank activity without a recognized accounting record | Identify the source event and whether it was recorded elsewhere |
| Accounting activity absent from bank information | Confirm timing, submission evidence, and data completeness |
| Similar amounts with different references | Compare supporting documents before accepting a match |
| Deposit differs from customer receipts | Examine settlement grouping, fees, and other adjustments |
| Possible duplicate import | Confirm source records before creating or changing accounting entries |
This is a review framework, not a list of prescribed adjustments. The correct accounting treatment depends on what the investigation establishes.
Assign an owner and follow-up to unresolved items. Otherwise, a report can remain visually tidy while the same unexplained transactions roll forward each period.
Recording a cash transfer and executing it are separate questions
Acumatica Cash Management includes support for cash transfers and related accounting activity. When evaluating that function, ask what the company’s implementation records and what, if anything, it sends through a bank or connected payment arrangement. Acumatica cash-transfer capabilities
Do not assume that creating an accounting transfer automatically instructs a bank to move funds. Confirm the actual authorized process and the evidence available for both sides.
This distinction is useful when reviewing a transfer between company accounts. The accounting records and bank activity should tell a coherent story about the same movement without relying on the appearance of a single completed document.
Close the reconciliation with an explanation
A completed review should show the agreed balances, identified reconciling items, approved corrections, and unresolved matters with owners. Its value is the explanation, not simply the absence of a difference on one screen.
Use the reporting guide to ensure that any cash dashboard uses a clearly defined balance and cutoff. Connect supplier-payment investigations to the AP workflow where appropriate.
When the evidence is organized this way, reconciliation becomes a way to understand cash activity and detect missing information. It is no longer an exercise in forcing two totals to agree.