| Client | M&T Bank Corporation |
| Industry | Financial Services — Regional Banking |
| Oracle Version | Oracle E-Business Suite 11i |
| Modules | GL AP AR CM |
| Engagement Period | 2003 – 2005 |
| Project Type | Oracle Financials Implementation — Multi-Entity Bank Structure |
| Complexity | High · Regulated Banking · Multi-Entity Ledger · SOX Environment |
M&T Bank Corporation, a major US regional bank headquartered in Buffalo, New York, implemented Oracle EBS 11i Financials to support the back-office financial operations of its growing multi-entity banking structure. M&T had grown through acquisition in the late 1990s and early 2000s — integrating multiple bank charters, holding companies, and financial subsidiaries under the M&T umbrella — and needed a unified Oracle Financials environment to consolidate financial reporting, standardize AP disbursement, and support Cash Management across its treasury operations.
The banking sector adds distinctive requirements to any Oracle Financials implementation: regulatory reporting obligations (Call Report data, SEC filings for a public company), internal controls environments shaped by bank examination standards, and treasury operations that involve high-value, time-critical cash movements requiring tight Oracle Cash Management controls. The Sarbanes-Oxley Act (SOX) environment of 2003–2005 added additional internal control documentation requirements to every system implementation.
The engagement delivered a multi-entity GL structure aligned to M&T's bank charter organization, AP disbursement processing for corporate and bank operational expenses, AR for inter-entity and customer billing, and Cash Management for treasury account reconciliation across M&T's extensive bank account network.
Banks are unusual Oracle EBS clients because their core banking system (for loan origination, deposit management, and transaction banking) is not Oracle EBS — it is a specialized banking platform (in M&T's era, typically platforms like Jack Henry, FIS, or Fiserv products). Oracle EBS serves the back-office financial operations: corporate purchasing, accounts payable for non-loan expenses, general ledger consolidation, and treasury cash management. The integration between the core banking system and Oracle GL is one of the highest-risk technical components of any bank Oracle implementation.
The SOX environment in 2003–2005 was particularly demanding — the Act had just been enacted following the Enron and WorldCom scandals, and audit firms were interpreting and applying its internal control requirements aggressively. Every Oracle system implementation in this period needed to document its internal control design, test controls, and produce evidence of control effectiveness — adding significant documentation overhead to what would otherwise have been a standard Oracle implementation.
M&T's multi-entity structure, spanning several bank charters and non-bank subsidiaries, required an Oracle GL design that could produce both consolidated financial statements for M&T Corporation and standalone financial statements for each regulated bank charter — a reporting requirement that influences chart of accounts design, intercompany accounting, and financial statement generation in material ways.
The GL chart of accounts was designed to support both entity-level and consolidated financial reporting. Each bank charter and significant subsidiary was assigned a company segment value in Oracle's flexible chart of accounts, allowing entity-level trial balances alongside corporate consolidation. Intercompany elimination rules were configured to automatically eliminate intercompany balances during the consolidation process, reducing manual adjustment workload at month-end.
The chart of accounts structure was also designed with bank regulatory reporting in mind — account codes were mapped to FFIEC Call Report schedules, allowing automated generation of regulatory filing data from Oracle GL balances rather than manual extraction and reconciliation.
AP covered corporate-level disbursements: real estate and facilities expenses across M&T's branch network, technology vendor payments, professional services, and employee benefits administration. The high volume of recurring payments (rent, utilities, insurance) were managed through Oracle's recurring invoice functionality, reducing manual invoice entry. Payment controls — dual approval for payments above defined thresholds, segregation of invoice entry from payment approval — were configured as SOX control requirements.
Cash Management was implemented for bank account reconciliation across M&T's corporate treasury accounts. The integration between Oracle CM and the banking system's electronic bank statement feeds was a key technical component. Oracle's bank statement AutoReconciliation program was configured with tolerance rules and matching priorities to maximize automated matching rates, minimizing daily manual reconciliation effort for the treasury team.
AR supported intercompany billing between M&T entities (shared services chargebacks) and billing to external customers for fee-based services. Customer account setup, transaction type definitions, and auto-accounting rules were configured to align with the GL chart of accounts and produce correct entity-level revenue recognition.
| Deliverable | Type | Purpose |
|---|---|---|
| Multi-Entity Chart of Accounts Design | Architecture | GL segment structure supporting entity-level reporting, consolidated reporting, and regulatory account mapping |
| Intercompany Elimination Configuration | Configuration Document | Oracle GL intercompany balancing and elimination rules for multi-entity consolidation |
| SOX Internal Control Documentation | Compliance Document | Oracle AP and CM internal control design documentation for SOX 404 compliance — segregation of duties, payment approval controls |
| AP Payment Control Configuration | Configuration Document | Dual-approval payment rules, threshold-based authorization, and payment batch audit trail setup |
| Cash Management AutoReconciliation Setup | Configuration Document | Bank statement import configuration, AutoReconciliation matching rules, and exception handling procedures |
| Regulatory Account Mapping | Reference Document | Oracle GL account-to-Call Report schedule mapping for regulatory reporting automation |
| Period-End Close Procedures | Process Documentation | Multi-entity close sequence with regulatory filing deadlines and SOX control evidence requirements |
The multi-entity GL architecture used Oracle's standard consolidation workbench — each subsidiary maintained its own Oracle operating unit and ledger, with period-end consolidation journal imports feeding the M&T Corporation consolidation ledger. Intercompany accounts were configured with Oracle's standard intercompany balancing rules, ensuring that every intercompany debit had a corresponding intercompany credit before period close.
The Cash Management bank statement integration required coordination with M&T's treasury technology team to establish the electronic bank statement feed format (BAI2 was the standard of the era), the transmission schedule, and the reconciliation tolerance parameters. The AutoReconciliation matching priority — statement line to payment by check number, then by amount-and-date, then manual — was configured to match M&T's reconciliation workflow.
The SOX environment required documenting internal controls for every Oracle financial process — invoice approval, payment processing, journal entry, account reconciliation. This documentation effort was significantly larger than initially estimated. Resolution was a structured control documentation template aligned to COSO framework categories, allowing systematic documentation of each control with consistent format and completeness — reducing the time per control document once the template was established.
Each bank charter's finance team had preferences for account coding that reflected their existing practices. Achieving consensus on a single chart of accounts that served all entities was politically challenging. Resolution was a COA governance committee with representation from each entity's finance leadership, chaired by corporate accounting — with explicit authority to make binding decisions when entity preferences conflicted with consolidation requirements.
Journal entries from the core banking system needed to post to Oracle GL for financial consolidation. The core banking system's account structure did not align with Oracle's chart of accounts, requiring a mapping and transformation layer. The integration used a file-based transfer (the banking system produced a flat file of journal entries; a custom transformation program mapped account codes and loaded them into Oracle GL interface tables).
M&T's corporate treasury accounts processed high daily transaction volumes, producing bank statements with hundreds of individual statement lines per account. Oracle's AutoReconciliation program performance degraded with high statement line volumes. Resolution required database optimization (indexes on the reconciliation matching tables) and configuration of batch-level processing to run AutoReconciliation by account group rather than all accounts simultaneously.
| Area | Lesson | Apply On Next Engagement |
|---|---|---|
| SOX Scope | SOX compliance documentation is a design constraint, not a post-implementation audit — incorporate from day one | Include SOX control design as a concurrent workstream from project kickoff; assign dedicated SOX documentation resource |
| COA Governance | COA without governance drifts — post-go-live governance is as important as the initial design | Deliver COA governance process documentation as a mandatory go-live deliverable for all multi-entity GL implementations |
| Reconciliation Volume | AutoReconciliation performance degrades at high statement line volumes — test with realistic data volumes before go-live | Load representative bank statement volumes into test environment and run AutoReconciliation performance test before UAT begins |
| Scope Clarity | Oracle EBS scope at banks must be explicitly bounded against core banking system scope in the project charter | Include explicit scope boundary statement in every banking sector Oracle project charter |