Bachelors Program in Banking Finance and Insurance
Fundamentals of Banking, Finance & Insurance
•
Bachelor
Banking Operations and Payment Systems
Introduction and context
Banking operations convert customer instructions and institutional decisions into controlled movements of money, information, and legal obligations. They include opening and maintaining accounts, identifying customers, accepting deposits, processing payments, clearing instruments, settling obligations, reconciling records, and managing cash. Although customers often experience banking as a mobile application or a branch counter, reliable service depends on coordinated people, processes, technology, controls, and regulatory duties.
Operational failure can create financial loss, legal exposure, liquidity pressure, reputational damage, and harm to customers. This chapter therefore treats operations not merely as clerical activity but as a control system in which accuracy, timeliness, security, resilience, and fairness must be managed together.
Learning objectives
By the end of this chapter, students should be able to:
Explain the stages of account opening and customer due diligence.
Distinguish authentication, authorization, validation, processing, clearing, and settlement.
Describe domestic and international payment methods and their risks.
Explain reconciliation, cash operations, operational controls, and service-quality measures.
Apply control principles to a banking workflow and diagnose an operational problem.
1. Account opening and customer due diligence
An account-opening process establishes a contractual relationship between a customer and a bank. It normally includes product selection, collection of customer information, identity verification, risk assessment, approval, account creation, and communication of terms. The exact requirements vary by jurisdiction and product, but the underlying principles are broadly similar.
1.1 Customer identification and KYC
Know Your Customer (KYC) is the process through which a bank identifies and understands its customer. Core information may include legal name, date and place of birth or incorporation, address, identity-document details, occupation or business activity, tax information, expected account activity, and source of funds.
Customer Due Diligence (CDD) uses this information to understand risk. Enhanced Due Diligence (EDD) is applied where risk is higher, for example with a politically exposed person, complex ownership, unusual geography, or high-risk business. Simplified due diligence may be permitted for genuinely low-risk relationships where local law allows it. KYC is not a one-time event: customer information and expected activity must be reviewed periodically and when circumstances change.
For a company, the bank must identify beneficial owners—the natural persons who ultimately own or control it—and persons authorized to act. A business registration certificate alone does not necessarily reveal beneficial ownership.
1.2 Risk-based control
A risk-based approach allocates greater investigation and monitoring to relationships presenting greater money-laundering, terrorist-financing, fraud, sanctions, or other risks. It does not mean ignoring low-risk customers; it means applying proportionate controls. A bank should document its risk rationale, use reliable data, protect personal information, and avoid discriminatory decisions unrelated to legitimate risk factors.
1.3 Account creation and maintenance
After approval, the bank creates a unique customer and account record, assigns a product type and currency, sets transaction limits, records signing mandates, and issues account terms. Maker-checker control is valuable: one employee enters or prepares the record and another independently reviews and approves it. Changes to addresses, beneficiaries, mandates, limits, and contact details require authentication, authorization, evidence, and—where appropriate—customer notification.
2. Transaction-processing control lifecycle
A transaction is an instruction to transfer value or update an account. A sound workflow separates four controls that are frequently confused:
Authentication: establishing that the user, device, employee, or system is the claimed identity.
Authorization: determining whether that authenticated party has permission to perform this particular action.
Validation: checking completeness, format, account status, limits, balances, sanctions requirements, and business rules.
Processing: posting entries, generating messages, and updating status.
Authentication does not prove that a person is entitled to make every transaction. Authorization does not prove identity. Validation checks whether an authorized instruction is acceptable under the rules.
Controlled banking transaction lifecycle showing authentication before authorization and validation
Figure: Controlled banking transaction lifecycle showing authentication before authorization and validation
Figure: A controlled transaction lifecycle distinguishing authentication from authorization and validation.
A practical workflow is therefore: capture the request; authenticate the party; authorize the requested action; validate data and rules; screen where required; calculate fees and value dates; post or transmit; notify the customer; and retain an audit trail. Some systems perform format validation during capture, but the conceptual control decision remains distinct from identity authentication and permission authorization.
2.1 Double-entry effects
For a customer transfer within the same bank, the bank may debit the payer’s deposit liability and credit the recipient’s deposit liability. From the bank’s perspective, both deposits are liabilities, so one liability decreases and another increases. For a cash deposit, cash (an asset) increases and the customer deposit liability increases. Every posting must balance:
Total debits = Total credits
This identity applies to a balanced accounting entry; it does not imply that every individual customer account has a zero balance.
Worked example: payment availability
A customer has an available balance of 2,000 monetary units. A payment instruction is 650 and the applicable fee is 15. If no other holds or restrictions apply, the post-transaction available balance is:
2,000 − 650 − 15 = 1,335 monetary units
The system must validate both the payment amount and the fee, record them transparently, and prevent a second transaction from spending the same available funds.
3. Clearing and settlement
Clearing is the exchange, validation, and calculation of obligations arising from payment instructions. Settlement is the final discharge of those obligations through transfers of funds, usually between banks’ settlement accounts at a central bank or through a designated settlement institution. A payment can be cleared but not yet settled.
Net settlement systems aggregate obligations. If Bank A must pay Bank B 100 and Bank B must pay Bank A 70, the net obligation is 30 from A to B. Gross settlement systems settle transactions individually, usually in real time. Netting can reduce liquidity needs but introduces timing and settlement risk; gross settlement offers prompt finality but may require more liquidity and processing capacity.
Payment status should be explicit: received, authenticated, authorized, validated, accepted, pending, rejected, returned, settled, or reversed. “Processed” is not necessarily equivalent to “settled.” Finality and irrevocability depend on system rules and applicable law.
4. Domestic payment systems
Domestic payments include cash, cheques, card payments, automated clearing-house transfers, instant payments, and high-value bank-to-bank transfers. Their characteristics differ in speed, cost, finality, operating hours, fraud exposure, and dispute mechanisms.
Instrument
Typical use
Principal operational issue
Cash
Retail and face-to-face payments
Physical security, counting, counterfeit risk
Cheque
Credit-based or legacy payments
Returns, alteration, delayed availability
Card
Retail purchases and cash access
Authorization, chargebacks, card fraud
ACH or batch transfer
Payroll and recurring payments
File controls, cut-off times, returns
Instant payment
Near-real-time retail transfer
24-hour fraud detection and rapid irrevocability
High-value transfer
Large or urgent payments
Liquidity, sanctions screening, finality
Banks should publish cut-off times, expected availability, fees, dispute channels, and limits. A customer-facing “instant” service may still depend on a receiving institution’s availability and system rules.
5. International payments
International payments normally involve currency conversion, correspondent banks or payment networks, sanctions screening, beneficiary information, and different legal regimes. A correspondent bank holds an account relationship that permits another bank to access payment services in a foreign currency or jurisdiction.
A wire instruction may include ordering customer, beneficiary, account or international identifier, beneficiary bank, amount, currency, purpose, and fee allocation. Missing or inconsistent information can cause repair, delay, rejection, or return. Banks must screen relevant parties and messages against applicable sanctions requirements and investigate alerts consistently rather than automatically treating every alert as a confirmed match.
Foreign-exchange calculation
If a bank quotes 1.10 domestic currency units per euro and a customer buys 500 euros, ignoring fees and spread adjustments:
The quote direction matters. If the quote instead states euros per domestic currency unit, division—not multiplication—would be required. A complete customer disclosure should identify the exchange rate, fee, value date, and expected received amount where determinable.
International payments face correspondent-bank deductions, time-zone differences, holidays, sanctions holds, exchange-rate movement, and settlement risk. “OUR,” “SHA,” and “BEN” fee conventions may allocate charges differently, but their legal meaning depends on the relevant payment scheme and jurisdiction.
6. Reconciliation and exception management
Reconciliation compares two independently generated records to identify differences. Typical comparisons include the core banking ledger with the general ledger, payment messages with account postings, ATM cash records with physical cash, and nostro statements with internal records.
A useful control model is:
Obtain source records for the same date, currency, and scope.
Match by transaction identifier, amount, account, and value date.
Investigate, correct through an authorized adjustment, and preserve evidence.
Escalate aged or high-value exceptions.
Certify completion independently.
A reconciliation is not complete merely because the totals agree: offsetting errors can produce a false balance. Independent evidence, sampling, exception ageing, and review of unusual manual entries strengthen the control.
A simple exception-age measure is:
Exception age = Current date − Date first identified
Both dates must use the same calendar convention. Banks commonly set risk-based thresholds for escalation, such as immediate escalation for suspected unauthorized transactions and daily review for unsettled high-value items.
7. Cash operations
Cash operations manage forecasting, ordering, receiving, storing, issuing, transporting, counting, and reconciling physical currency. Branches forecast withdrawals and deposits using historical patterns, payroll dates, holidays, local events, and minimum service levels. Excess cash creates security and opportunity costs; insufficient cash damages service quality.
Controls include dual custody for vault access, documented cash counts, counterfeit detection, segregated cash drawers, secure transport, alarm and camera controls, surprise counts, and prompt investigation of differences. A teller should not independently approve and conceal a cash shortage. Access rights must be role-based, and cash adjustments require evidence and supervisory approval.
8. Operational controls and service quality
The control environment should combine preventive, detective, and corrective controls.
Control type
Example
Preventive
Transaction limits, segregation of duties, input validation
Important controls include least-privilege access, maker-checker approval, immutable audit logs, encryption, secure authentication, segregation of duties, business continuity, and incident escalation. Controls should be tested for both design and operating effectiveness.
Service quality can be assessed using accuracy, timeliness, first-contact resolution, complaint recurrence, availability, accessibility, and customer-outcome measures. Speed should not be pursued at the expense of fraud prevention or fair treatment. A useful root-cause method is to distinguish an isolated employee error from a process design defect, unclear policy, inadequate training, system failure, or unrealistic workload.
When a customer reports a failed payment, staff should verify identity, retrieve the transaction status, explain facts without speculation, protect confidential information, provide a case reference, correct errors promptly, and explain escalation and compensation rights where applicable. Complaint data should feed process improvement rather than being treated only as individual cases.
9. Governance, ethics, and technology
Banks must comply with applicable laws on KYC, anti-money laundering, sanctions, privacy, consumer protection, payment finality, record retention, and operational resilience. Requirements differ across jurisdictions; employees must follow local rules and the bank’s current procedures rather than relying on generic guidance.
Ethically, banks must balance security with inclusion. Excessive documentation or poorly designed digital identity checks can exclude legitimate customers, while weak controls expose customers to fraud. Personal data should be collected for legitimate purposes, accessed only by authorized staff, retained appropriately, and protected from unauthorized disclosure.
Automation and artificial intelligence can support document extraction, fraud detection, anomaly monitoring, routing, and customer-service triage. They do not remove accountability. Models require quality data, explainable decisions where appropriate, bias testing, human escalation, access control, monitoring for drift, and protection against adversarial manipulation. A high-risk automated account closure or payment block should have a controlled review and a meaningful customer-redress process.
Background. A medium-sized company submits a payroll file through online banking. The file is uploaded twice after a user receives a timeout message. The first file is accepted and the second is also released.
Problem. Employees may be paid twice, the company’s balance may be insufficient, and the bank faces complaints and operational loss.
Analysis. Authentication succeeded for the user, but authorization and file-level controls did not prevent duplicate submission. The timeout obscured status. The system lacked a strong idempotency key—a unique reference allowing repeated submission of the same instruction to be recognized as a duplicate. Monitoring detected the second file only after release.
Approach. The bank immediately confirms both file statuses, places a controlled hold where scheme rules permit, contacts the corporate customer, and uses the approved return or recovery process. It preserves logs and investigates whether the customer, bank, or network caused the duplication. It then introduces a visible submission receipt, idempotency checking based on customer, file reference, date, count, and total, dual approval for payroll release, and an alert for near-identical files. Customer communications explain the event and available remedies.
Outcome. The immediate financial impact is contained, affected employees are informed through the employer, and the bank measures recurrence, recovery time, and complaint outcomes. The control change is tested before deployment and reviewed after implementation.
Learning points. Authentication alone is insufficient; transaction authorization, validation, status visibility, duplicate detection, reconciliation, and incident response must operate as a system. Good service recovery is both prompt and evidence-based.
Challenges and limitations
Operational controls can create friction, false-positive fraud alerts, delays, and costs. Net settlement reduces liquidity needs but can concentrate settlement risk. Automation improves scale but may reproduce data bias or conceal errors. Reconciliation identifies differences but cannot guarantee that the underlying records are correct. KYC can reduce financial crime while imposing burdens on customers with limited documentation. These trade-offs require proportionality, monitoring, documented decisions, and periodic control redesign.
Chapter Summary
Banking operations manage the controlled movement of customer instructions, funds, and information. Account opening requires identification, risk-based due diligence, beneficial-owner analysis, approval, and secure record creation. In transaction processing, authentication establishes identity, authorization confirms permission, validation checks rules and data, and processing posts or transmits the instruction. Clearing calculates and exchanges obligations, whereas settlement discharges them with finality under system rules. Domestic and international payments differ in speed, cost, currency, intermediaries, screening, and risk. Reconciliation, cash controls, segregation of duties, audit trails, exception management, and service recovery protect both the bank and its customers. Technology and AI can strengthen operations only when governance, human accountability, privacy, resilience, and fair treatment remain in place.
Key Terms
Account mandate: Rules specifying who may operate an account and how.
Authentication: Verification of a claimed identity.
Authorization: Permission to perform a particular action.
Beneficial owner: Natural person who ultimately owns or controls an entity.
Clearing: Exchange and calculation of payment obligations.
Correspondent bank: Bank providing payment or account services to another bank.
Customer Due Diligence: Risk-based investigation and understanding of a customer.
Enhanced Due Diligence: Additional investigation for higher-risk relationships.
Idempotency: Property by which repeating an instruction does not create an unintended duplicate effect.
KYC: Know Your Customer identification and understanding procedures.
Maker-checker: Separation between preparation and independent approval.
Net settlement: Settlement of aggregated net obligations.
Nostro account: An account held by a bank with another bank, commonly in a foreign currency.
Reconciliation: Comparison of independent records to identify differences.
Sanctions screening: Checking relevant parties or transactions against applicable restrictions.
Settlement: Final discharge of payment obligations.
Straight-through processing: Automated processing with minimal manual intervention.
Value date: Date on which funds are treated as effective for interest or settlement purposes.
Review Questions
Short Answer Questions
Distinguish authentication from authorization.
What is the purpose of beneficial-owner identification?
Define clearing and settlement.
State two controls used in cash operations.
Why is reconciliation more than comparing grand totals?
Long Answer Questions
Explain the account-opening lifecycle from customer application to account maintenance.
Compare net settlement and gross settlement, including their operational trade-offs.
Describe the risks and controls associated with international payments.
Explain how preventive, detective, and corrective controls work together.
Discuss the ethical and governance challenges of AI in payment operations.
Analytical / Application Questions
A customer was authenticated successfully but attempts a transfer outside the account mandate. Identify the failed control and propose a workflow response.
A branch’s cash total agrees with its ledger, but two drawer records contain offsetting errors. Explain why the reconciliation may be misleading and design follow-up tests.
A corporate customer uploads the same payment file twice after a timeout. Using the case in this chapter, design preventive, detective, and customer-service controls.
Multiple Choice Questions with Answers
Question 1
Which control establishes that a user is the claimed identity?
A. Authentication
B. Authorization
C. Settlement
D. Reconciliation
Correct Answer: A. Authentication
Question 2
Which statement best describes authorization?
A. Checking whether required fields have the correct format
B. Determining whether an authenticated party may perform a requested action
C. Exchanging payment obligations between banks
D. Comparing two independent accounting records
Correct Answer: B. Determining whether an authenticated party may perform a requested action
Question 3
A customer has 2,000 monetary units available and makes a payment of 650 with a fee of 15. What is the remaining available balance, assuming no other holds?
A. 1,315
B. 1,335
C. 1,350
D. 2,665
Correct Answer: B. 1,335
Question 4
What is the principal function of clearing?
A. Physically storing banknotes
B. Issuing identity documents
C. Exchanging and calculating payment obligations
D. Setting retail interest rates
Correct Answer: C. Exchanging and calculating payment obligations
Question 5
What does settlement represent?
A. The final discharge of payment obligations
B. The initial capture of a customer instruction
C. The identification of a beneficial owner
D. The counting of cash in a branch drawer
Correct Answer: A. The final discharge of payment obligations
Question 6
Which control most directly helps prevent one employee from preparing and approving the same account change?
A. Dual or maker-checker control
B. A customer newsletter
C. A currency exchange quote
D. A settlement holiday calendar
Correct Answer: A. Dual or maker-checker control
Question 7
If a bank quotes 1.10 domestic currency units per euro, how much domestic currency is needed to buy 500 euros, excluding fees?
A. 454.55
B. 500
C. 550
D. 1,100
Correct Answer: C. 550
Question 8
Which is an example of a detective control?
A. Input format validation before submission
B. A transaction limit that blocks excessive payments
C. Post-event reconciliation of payment records
D. A user selecting a product type
Correct Answer: C. Post-event reconciliation of payment records
Question 9
Why can a payment marked “processed” still require further review?
A. Processing always means the payment has been reversed
B. Processing may occur before clearing or final settlement
C. Processed payments cannot be recorded in an audit trail
D. Processing applies only to cash withdrawals
Correct Answer: B. Processing may occur before clearing or final settlement
Question 10
What problem is an idempotency key primarily designed to reduce?
A. Currency depreciation
B. Duplicate effects from repeated submission of the same instruction
C. A shortage of beneficial-owner information
D. Physical counterfeit notes
Correct Answer: B. Duplicate effects from repeated submission of the same instruction
Fundamentals of Banking, Finance & Insurance
Chapter 5
of 15