Core Operations Console Basics

Chinese source: 核心柜面入门
Locale: en-US
Audience: Internal learning

Key Terms

Chinese	English	Usage Note
核心柜面	Core Operations Console	A better fit for a digital-bank internal system than teller counter.
交易码	Transaction Code	A stable code that identifies a system function or transaction page.
柜员	Operations User / Teller	Use teller only when the branch teller context matters.
流水	Reference / Transaction Record	Use business reference or system reference when the type is clear.
授权	Authorization / Approval	A risk control step before a high-risk action is completed.

Concept

The core operations console is the internal workspace where bank users run core banking transactions. It connects customers, accounts, products, transaction posting, institutions, users, permissions, approvals, and audit records.

In one sentence:

The core operations console is where operations users turn banking work into core system transactions.

Do not treat it as a normal back-office admin page. Many buttons can affect account balances, account status, customer rights, internal accounting, or audit trails once submitted.

Menus, Transaction Codes, and Pages

Core systems often identify each function by transaction code.

Example	Meaning
[3001] Customer Account Information Inquiry	Retrieve customer-level account information.
[1001] General Transfer	Initiate an accounting transfer.
[2001] Account Freeze	Place a freeze or control on an account.
[9104] User Transaction Balancing	Reconcile or balance user transaction records.

When studying a page, read it in four layers:

1. Which menu does it belong to?
2. Is it an inquiry, maintenance, accounting, control, or operations workflow page?
3. What inputs does it require, and what outputs does it return?
4. Can it change balances, status, restrictions, or transaction records?

Core Objects

Object	Plain-English Meaning	Typical Fields
Customer	The person or entity served by the bank.	Customer ID, customer name, ID document.
Account	The container for customer funds or internal accounting.	Customer account number, sub-account, internal account number.
Product	A configured rule set that drives account behavior.	Product code, term, rate, minimum opening amount.
Operations user	The person running the transaction.	User code, role, permissions.
Institution	The branch, office, or operating unit.	Institution code, opening branch, operating branch.
Reference	The trace left by a transaction.	Business reference, system reference, user transaction record.

Common Page Types

Page Type	Purpose	Does It Usually Change Business Results?
Inquiry	Look up accounts, transactions, status, permissions, or institutions.	Usually no balance or status change.
Maintenance	Update account information, limits, restriction codes, or maturity instructions.	Changes parameters or status.
Accounting	Transfer, reverse, charge fees, or withdraw funds.	Changes balances and accounting records.
Special account operation	Freeze, release, renew a freeze, or process a legal debit.	Changes fund availability or ownership.
Operations workflow	Sign in/out, reconcile, submit requests, or process work items.	Changes workflow state and audit trails.

Recommended Learning Order

1. Start with inquiry pages to understand customers, accounts, sub-accounts, balances, and status.
2. Move to maintenance pages to understand how account rules are changed.
3. Study accounting pages to understand how funds move and how transactions are posted.
4. Study special operations to understand freezes, legal debits, restrictions, and high-risk controls.
5. Finish with operational closeout: users, institutions, approvals, references, business date rollover, EOD processing, and balancing.

Common Misunderstandings

Misunderstanding	Better Reading
Inquiry pages have no risk.	They expose customer information and still require permissions and audit controls.
One account number always identifies the exact account.	You must distinguish customer ID, customer account number, sub-account, internal account, and liability account number.
Submit only means save.	On accounting and special operation pages, submit can directly affect balances or status.
A failed transaction always means insufficient funds.	It may also be caused by account status, restriction codes, limits, product rules, or user permissions.
A reference number is just a number.	It is the key trace for reversal, audit, reconciliation, and exception handling.