Retail and Commercial Banking Operations

01Purpose and scope

• This manual supports the course Retail and Commercial Banking Operations. It describes how the operations side of a bank actually gets work done for individual customers and business customers, from the moment an account is requested to the point where a transaction posts, reconciles, and is archived.
• Operations is the function that keeps promises made by sales and lending teams. A branch may open a checking account in a few minutes, but the operations group confirms identity, sets up the account in the core system, routes the first deposit, applies the correct fees, handles exceptions, and makes sure the general ledger agrees with what customers see. This manual is written for operations analysts, team leads, branch operations staff, and learners who need a working reference rather than a theory text.
• The scope covers deposit accounts, payments and transfers, check and item processing, cash handling, loan servicing support, commercial treasury services such as cash management and lockbox, and the controls that sit across these areas. It does not cover credit underwriting decisions, trading, or investment advice, although operations staff touch all of them.
• Practices differ by institution size, charter, core processing platform, and the mix of products offered. A community bank may still process a large share of items manually, while a large regional bank may run most of its servicing through automated queues. Where this manual describes a rule or a typical threshold, treat it as an example of how teams commonly work, not as a requirement for your institution.

02Core principles

• Accuracy comes before speed. A payment that posts a day late creates a support call. A payment that posts to the wrong account creates a customer harm, a potential regulatory finding, and a rework effort that can take weeks. Teams that run well set their queues so that exceptions are visible early instead of being pushed forward until month end.
• Every balance has an owner. Deposit balances, suspense balances, clearing balances, and general ledger accounts each have a named person or team responsible for clearing them. If an item sits in a suspense account with no owner, it will grow. Operations managers usually review aging reports for each owned balance on a fixed cadence.
• Segregation of duties is a basic protection. The person who keys a wire, approves it, and releases it should not be the same person. The same applies to changing customer address, contact, or account ownership details, and to adjusting fee waivers. Small branches sometimes cannot fully separate these roles, so they rely on dual review, system-enforced limits, and periodic supervisory reports to compensate.
• Customer data is handled on a need-to-know basis. Operations staff routinely see account numbers, Social Security numbers or taxpayer identifiers, and transaction histories. Access should follow job function, be reviewed periodically, and be removed promptly when a person changes roles or leaves.
• Documentation is part of the work product. A decision to waive a fee, reverse a payment, or override a limit should record who approved it, why, and what evidence supported it. Examiners and auditors look for this trail, and so do colleagues who inherit the file later.

03Planning and preparation

• Start by defining the product or service in operational terms. For a new business checking product, the operations design needs to specify eligibility, required documents, fee schedule, statement cycle, overdraft handling, transaction limits, and which system codes apply to each feature. A product that looks simple to marketing may need ten or more configuration decisions before it can be opened by a customer.
• Confirm the policy and procedure inventory before changing a process. Each operational activity should map to a written procedure that names the owner, the trigger, the steps, the systems used, and the controls. Where a procedure is missing or out of date, correct it before training staff on a new process, because staff will otherwise learn the informal version that circulates on the floor.
• Identify stakeholders early. Typical parties include the deposit product manager, the core system administrator, compliance, the bank security group, the lending operations team for loan-linked accounts, treasury management for commercial clients, the call center, and the branch network. Each has a different tolerance for delay and error, and their requirements sometimes conflict. For example, a fraud team may want a hold on new accounts for several days while a sales team wants same day access.
• Prepare the data. Conversion projects and product changes depend on clean customer and account data. Before moving accounts to a new platform, reconcile record counts, balances, signatory cards, beneficial ownership fields, and open items. Plan for a cutover window, a rollback path, and a parallel reconciliation period that is long enough to catch month-end and fee cycle effects.
• Set expectations for volume. A branch opening pipeline, a seasonal spike in cash deposits near holidays, or a merchant acquiring a large batch of recurring payments can overwhelm a team that was staffed for normal volumes. Operations leads usually forecast volumes using prior periods and the sales pipeline, then decide whether to add temporary staff, shift work between queues, or defer nonessential projects.

04Recommended workflow

1. 1
   : Intake and verification. Every new account starts with a request, whether it comes from a branch banker, an online application, or a commercial relationship manager. Operations verifies that the required identity documents are present and that the customer information matches the documents. Customer identification program requirements under the Bank Secrecy Act apply to accounts in the United States, and the specific data elements and verification methods are set by federal rule and the bank's own program, so check the current requirements with your compliance team.
2. 2
   : Screening and risk rating. Before an account is opened, the customer is screened against sanctions lists and other watch lists, and a risk rating is assigned according to the bank's customer due diligence policy. Business accounts also require identification of beneficial owners under the Customer Due Diligence rule. Screening hits are reviewed by trained analysts who decide whether a match is a true match, a false positive, or something that requires escalation. Do not release an account while a hit is open.
3. 3
   : Account setup. Operations creates the customer record and account in the core system, assigns the product code, sets fee schedules and statement options, attaches signatories and authorized users, and applies any restrictions. Dual review is common for changes to signatory authority and for setups above a defined dollar threshold. A second person checks the setup against the signed application before the account is activated.
4. 4
   : Funding and first transaction. The initial deposit is recorded against the account. For checks, the availability of funds is governed by Regulation CC, which sets maximum hold periods and disclosure obligations. Operations staff apply the hold schedule and the exceptions that the regulation allows, such as large deposit or redeposit of a returned item. The customer receives the funds availability disclosure at account opening.
5. 5
   : Daily processing. Each business day, teams work through queues for item returns, wire and ACH exceptions, deposit adjustments, and stop payment requests. Queues should be sorted by cutoff time and by age, not by who happens to be available. Returns and exceptions for ACH have time limits set by the network rules and the Nacha operating rules, so missing a return window can shift a loss to the bank.
6. 6
   : Cash and reconciliation. Branch cash is counted against the teller system at the end of the day, and vault or cash center balances are reconciled to the general ledger. Differences are logged, investigated, and cleared within the timeframes set by the bank's cash policy. Settlement accounts with correspondent banks and the Federal Reserve are reconciled daily, because a timing break can hide a missing item until it becomes a loss.
7. 7
   : Exception and dispute handling. Customers dispute transactions through branches, phone, or digital channels. For electronic transfers, Regulation E governs error resolution timelines and provisional credit obligations for consumer accounts. Operations logs each claim, gathers the transaction record, decides whether the claim is an error under the regulation, and communicates the outcome in writing. Commercial disputes follow contract terms and the network or cash management agreement instead.
8. 8
   : Closing and monthly processing. Dormant account rules, fee assessments, interest postings, and statement generation run on defined cycles. Escheatment or unclaimed property reviews occur on a schedule that depends on the state where the account holder resides, so the closest authority is the state unclaimed property office. Month-end close requires the suspense, clearing, and reconciling accounts to be cleared or explained before the books are sealed.
9. 9
   : Records and retention. Operations keeps account records, signature cards, statements, and item images for the periods set by federal and state rules and the bank's record retention schedule. Retention periods vary, so do not rely on a number in a training binder without checking the current schedule with records management and legal.

05Quality checks, risk controls and compliance

• Operations quality programs combine preventive controls, detective controls, and periodic testing. Preventive controls include system edits that block a transaction when a field is missing, dual approval for high-value changes, and limits on how much a single user can release in a day. Detective controls include daily reconciliations, exception reports, and reviews of overrides. Periodic testing is a sample-based check by a team that does not perform the work, often a quality assurance or internal audit function.
• Key indicators that operations leaders commonly watch include the number of items in suspense beyond an aging threshold, the percentage of new accounts that require rework after setup, the volume of overrides by user, the average time to resolve a dispute, the rate of returned ACH items, and the count of reconciliation differences that remain open at month end. Each institution sets its own targets. Be cautious about comparing your numbers with published peer figures, because the definitions and product mixes often differ.
• Risk controls should be tied to specific risks. Fraud on deposit accounts may appear as check kiting, account takeover, or synthetic identity. Operations controls for these include velocity checks on transfers, callback procedures for changes to contact details, and review of new accounts that move funds quickly. Money laundering risk is managed through the bank's Bank Secrecy Act and anti-money laundering program, including suspicious activity monitoring and reporting. Suspicious activity reports are confidential, and staff must not disclose to customers that a report was filed.
• Compliance requirements depend on jurisdiction, charter, and product. Federal banking agencies, the Consumer Financial Protection Bureau, state banking regulators, and the Financial Crimes Enforcement Network each have roles. The current authoritative sources are the regulators' own published rules and examination manuals, and your compliance function should confirm which apply to your institution and products. Outside the United States, the framework and terminology differ substantially.
• This guidance does not replace qualified professional judgment, approved bank procedures, or required authorization. Decisions about account closure for risk reasons, sanctions matches, suspicious activity, dispute outcomes, and fee waivers should follow the bank's written policy and the escalation path set by compliance and legal.

06Collaboration and documentation

• Operations works across many handoffs. A new commercial account may pass from the relationship manager to credit to deposit operations to treasury management to the call center. Each handoff should have a defined owner, a service level, and a shared record. When handoffs happen by email with no ticket, work gets lost. A common practice is a single case or ticket per request, with status notes that anyone on the team can read.
• Documentation should be written for someone who has never seen the account. A good note states the request, the evidence reviewed, the decision, the person who approved it, and the next step. Avoid vague notes such as checked and fine. Use standard reason codes where the system supports them, because they make trend reporting possible.
• Service level agreements between operations and the business lines define how fast a queue should be cleared, for example same day for wire exceptions or two business days for address changes. These agreements are most useful when they are measured and reviewed monthly. A missed target should trigger a root cause review rather than a quiet reassignment of work.
• Change management matters because banking systems are interconnected. A change to a fee code can affect statements, the general ledger mapping, customer notices, and a regulatory report. Before a change goes live, the team should list the affected downstream processes, test them in a nonproduction environment, and confirm the customer notice requirements with compliance. Notice periods for fee or term changes are set by product agreements and by consumer protection rules, so confirm the exact lead time.

07Measures and continuous improvement

• Measure the work at the level where people can act on it. A weekly report showing aged suspense items by owner is more useful than a single bank-wide average. Pair quantitative measures with periodic sample reviews, where a reviewer checks whether the procedure was followed, not only whether the output looked correct.
• Root cause analysis is the usual method for turning a pattern of exceptions into a process fix. A cluster of returned deposits from a single merchant may point to a data feed problem, a missing address validation rule, or a cutoff that was set incorrectly. Fixing the cause usually costs less than repeatedly clearing the symptom, but it takes coordination with the people who own the feed or the system.
• Continuous improvement works best when it is scheduled. Many teams hold a monthly review of the top exception categories, a quarterly review of procedures against actual practice, and an annual review of controls against the risk assessment. Changes to procedures should go through the same approval path as policy changes, so the written version stays accurate.
• Trade-offs are real. Adding a manual review step reduces error but slows the customer experience and adds staff cost. Tightening a velocity limit may reduce fraud losses while increasing false declines on legitimate activity. Shifting work to a centralized operations center can improve consistency but may reduce local knowledge of a commercial client's needs. Measure both sides of a trade-off before deciding.

08Common mistakes and how to prevent them

• One common mistake is treating a suspense or clearing balance as a parking lot. Items sit there because no one owns the decision, and they age until they become write-offs or audit findings. Prevent this by assigning an owner to each suspense category, setting an aging threshold, and escalating items that exceed it.
• A second mistake is changing account details without verifying the request. Account takeover often begins with a changed phone number or email address that is used later to reset access. Require a callback to a number already on file, or a verification step that the customer cannot easily bypass, before processing sensitive changes.
• Another frequent error is applying the wrong hold or availability rule to a deposit. Teams sometimes apply the standard schedule to deposits that qualify for an exception, or they fail to give the required notice when a hold is extended. Build the hold logic into the system where possible, and review a sample of holds each month.
• Teams also overlook timing. ACH returns, check returns, and stop payment cutoffs are all tied to specific deadlines. A missed deadline may mean that the bank bears the loss for an item it could have returned. Post cutoff times in the queue tools, and review missed deadlines as a standing item in the daily huddle.
• Finally, undocumented overrides are a persistent problem. A supervisor may approve a fee waiver in person and never record it. Require a reason code and a second approver in the system for any override above a defined threshold, and review override reports weekly.

09Practical checklist

• Confirm the product configuration matches the approved product specification before activation.
• Verify identity documents and complete screening, with all hits resolved, before opening the account.
• Obtain beneficial ownership information for business accounts and record it in the customer file.
• Apply the current funds availability schedule and confirm the disclosure was provided.
• Work exception queues by cutoff time and age, not by convenience.
• Reconcile settlement, cash, and suspense accounts daily and document each open difference with an owner.
• Require callback verification or equivalent controls before changing contact details or signatories.
• Review override and waiver reports weekly and confirm each has a reason code and approval.
• Confirm the current retention schedule and dispute timelines with compliance before changing any procedure.
• Record each decision in the case file with the evidence reviewed, the approver, and the next step.

★Learning sources

• Micro Degree: Retail and Commercial Banking Operations
• Micro Degree: Accounts Payable Management
• Micro Degree: Bank Reconciliation Operations
• Micro Degree: FinTech Fundamentals