ERP for the banking industry: what fits beside the core

An ERP for the banking industry belongs beside the core system, as the corporate back office. The core, or the core processor, keeps member and customer balances, deposits, payments, and loan servicing. The ERP keeps the general ledger, payables, fixed assets, and management reports. For a small insured bank, credit union, lender, or fintech whose core is staying, Business Central Essentials lists at USD 80 per user per month, paid yearly, as of October 2026. Core banking, loan origination, and Call Report production sit outside that product and outside our work.

NetSuite's banking guide uses this scope: "ERP in the banking industry refers to software that runs a bank's core back-office functions, such as accounting, treasury, procurement, and human resources". ERP Research states the pairing in one line: "The best banking ERP systems pair a core banking platform with a financial ERP for accounting, close, and regulatory reporting". Read that as a stack of two products. A page that states this split and then folds loans and channels back into the ERP is describing a second core. Refuse that scope.

What the core owns and what the ERP owns

DICEUS draws the split in plain language: "A core banking system is the main transaction engine for a bank. An ERP system for banks serves as the enterprise management layer." The same guide later lists loan management and transaction processing as typical banking ERP modules. If a proposal prices loan servicing, deposit transactions, or channel integration inside the ERP, put those lines back on the core and rebid the rest.

Use this split when you write the scope.

1. The core or core processor owns customer and member accounts, deposit and payment transactions, and loan servicing. It remains the system that knows the balance a customer sees.
2. The ERP owns the corporate books: chart of accounts, journals, payables, fixed assets, allocations, and the management pack your board and auditor read.
3. Specialist outputs stay in the tool that already produces them. ERP Research says Business Central has no native Call Report, asset-liability management, or expected-credit-loss content. Microsoft's Business Central finance page documents the ledger, dimensions, deferrals, allocations, receivables, payables, bank reconciliation, fixed-asset reports, intercompany, consolidation, payroll import, cost accounting, and cash-flow analysis. It does not describe deposits, loans, or Call Reports.
4. SAP's financial-services page sells S/4HANA finance, procurement, and human capital management as the corporate layer, and lists core banking separately as the partner application SAP Fioneer Cloud for Banking. A financial-products subledger sits between operations and finance for IFRS and US GAAP. Even the large-bank stack keeps those layers apart.

Odoo 19 Accounting documents double-entry journals, accrual and cash basis, multi-company and multi-currency books, branches, a US 1099 report, fixed assets, bank reconciliation, an audit trail, and analytic accounting. That page does not describe a core-banking, loan-servicing, or Call Report module. For a fintech or a credit union, the test is the same: if the workflow creates or services a customer balance, it stays on the core. If it records a vendor bill, a laptop, or a payroll journal, it can live in the ERP.

A smaller institution does not need a custom-built banking suite to get that split. Configuration of a general ledger, plus a priced import of summarized core totals, is the default. Custom development is for a gap you have seen on your own chart of accounts, with the interface specified as its own line.

What the ledger does after the core posts the loans

Once the core has posted the loans and deposits, the ERP's job is the corporate close. Picture a daily or monthly journal: cash, interest income, fee income, deposit balances, loan balances, and charge-offs, each as a summarized control total. Subledgers for each note and each account stay on the core. The general ledger holds the totals your financial statements need, with dimensions or analytic accounts for branch, product, and department.

Business Central's finance documentation is built for that corporate close. Deferrals and allocations spread prepaid expenses and shared costs. Bank reconciliation clears the institution's own operating accounts. Fixed-asset reports track furniture, branches, and equipment, which are balance-sheet items the core often ignores. Payroll import lands salary and benefits as journals, so HR cost reaches the ledger through a file. Intercompany and consolidation cover a holding company and a bank subsidiary when both are in the same product. Cash-flow analysis reads the corporate cash accounts. None of that replaces the deposit system.

Odoo covers the same corporate jobs in its accounting app: accrual or cash basis, more than one company, more than one currency, branches, fixed assets, and analytic accounts. A US 1099 report matters if you pay vendors and contractors from this ledger. Have the vendor post a sample core summary file into a test company and show the tie-out to your trial balance before you treat the fit as proven.

The Call Report is a different report. The Federal Reserve describes the FFIEC 031 as a quarterly collection, as of the last calendar day of March, June, September, and December, of a balance sheet, an income statement, and supporting schedules, used for supervision. The Board points readers to the FFIEC for the forms and instructions. Your general ledger needs to agree to the numbers that feed that return. It does not need to be the product that files it. Keep mapping and filing in the core or the specialist tool your compliance team already uses, and reconcile those outputs to the ERP each quarter.

Which insured banks fall under Part 363

Part 363 is a federal reporting rule for insured depository institutions. It is a reason the corporate ledger must stand up to an external audit. It is not a software module, and it does not apply to every lender.

Under 12 CFR 363.1(a), Part 363 applies to an insured depository institution in any fiscal year when consolidated total assets at the beginning of that year are USD 1 billion or more. 12 CFR 314.1 sets that USD 1,000,000,000 figure as the baseline as of January 1, 2026. The first CPI adjustment is not effective until October 1, 2027. Until that date, the published baselines are the ones to use in planning.

Institutions in scope must prepare annual GAAP financial statements audited by an independent public accountant, plus a management report. 12 CFR 363.2 describes that report as covering responsibility for the statements, internal control over financial reporting, and designated safety-and-soundness laws. The same section defines the heavier bar: management's assessment of internal control over financial reporting, and the independent accountant's attestation on that assessment, apply when consolidated total assets are USD 5 billion or more at the start of the fiscal year. The assessment must cover controls over regulatory financial statements as well as GAAP statements. The rule cites COSO's Internal Control Integrated Framework as a suitable framework. 12 CFR 363.3 covers the independent public accountant, including that attestation. 12 CFR 314.1(c)(11) and (c)(12) list the USD 5 billion internal-control thresholds as baselines as of January 1, 2026, with the same October 1, 2027 first adjustment.

Part 363's definition of financial reporting includes, at a minimum, both GAAP financial statements and financial statements prepared for regulatory reporting. Regulatory statements conform to GAAP and section 37 of the FDI Act for recognition and measurement. For the ERP, that means the close that produces the GAAP pack and the numbers behind regulatory statements need an audit trail, documented approvals, and a reconciliation to the core. It does not mean the ERP calculates capital ratios or credit-loss allowances. Those methodologies stay in the models and specialist tools your policy names. The ledger records the journal those tools produce.

Do not copy the USD 1 billion and USD 5 billion lines onto a credit union or a non-bank lender. These sections apply to insured depository institutions at the asset thresholds. A credit union follows its own audit rules. A fintech that is not an insured depository asks counsel which statements and attestations apply, then sizes the ledger to that duty. A small bank under the USD 1 billion baseline can still want a controlled close. The federal attestation clock is what changes at the thresholds above.

Which platform matches a smaller finance team

ERP Research's banking guide, updated August 2026, describes the practical stack as a core platform such as Temenos, FIS, Finastra, Mambu, or nCino, plus a financial ERP for accounting, close, and reporting. For a finance team that will import summarized core activity and leave the Call Report in the core, Business Central or Odoo matches the functions those vendors document. Dynamics 365 Finance is the step up in Microsoft's price list when you are already on Microsoft and you want that heavier finance app: USD 210 per user per month versus USD 80 for Business Central Essentials, both paid yearly, as of October 2026.

Business Central already documents intercompany transactions and consolidation, so a single entity or a small group can start there. Have both products post the same multi-entity close on a copy of your chart of accounts if someone is arguing for Finance on entity count alone. Our Business Central implementation work is aimed at that corporate scope for companies in the 20 to 100 person range, with the core left in place.

• Business Central (What the documented or published role is: Corporate ledger, payables, fixed assets, consolidation · License list, as of October 2026: Essentials USD 80, Premium USD 110, Team Members USD 8, per user per month, paid yearly · ERP Research three-year TCO, August 2026: USD 75,000 to USD 400,000 · Go-live: 2 to 6 months)
• Dynamics 365 Finance (What the documented or published role is: Heavier Microsoft finance app · License list, as of October 2026: USD 210 per user per month, Finance Premium USD 300, paid yearly · ERP Research three-year TCO, August 2026: USD 150,000 to USD 1 million-plus · Go-live: 6 to 14 months)
• Odoo (What the documented or published role is: Accounting app: multi-company, fixed assets, 1099, audit trail · License list, as of October 2026: Standard shows USD 31.10 and USD 38.90; Custom shows USD 61.00 and USD 76.20, per user per month · ERP Research three-year TCO, August 2026: No bank TCO band in that August 2026 guide · Go-live: None listed)
• Sage Intacct (What the documented or published role is: Placed by the analyst with community banks and credit unions · License list, as of October 2026: Starting price listed as custom · ERP Research three-year TCO, August 2026: USD 50,000 to USD 200,000 · Go-live: 3 to 6 months)
• NetSuite (What the documented or published role is: Analyst band for a bank or lender · License list, as of October 2026: Analyst card shows a USD 99 per user per month start · ERP Research three-year TCO, August 2026: USD 100,000 to USD 500,000 · Go-live: 4 to 9 months)
• Oracle ERP Cloud (What the documented or published role is: Large-institution band · License list, as of October 2026: Starting price listed as custom · ERP Research three-year TCO, August 2026: USD 400,000 to USD 3 million-plus · Go-live: 9 to 18 months)

Microsoft list prices are on the Business Central pricing page and the Dynamics 365 Finance pricing page. Odoo figures are on the Odoo pricing page. The three-year TCO column and the go-live column are ERP Research's published estimates from its August 2026 banking guide. They are not vendor quotes and not public contract awards. No separate public US award for a bank, credit union, or fintech ERP project sits behind these bands.

ERP Research's financial-services page describes S/4HANA Public Cloud as a corporate finance backbone alongside core banking or policy systems. It shows a starting price of USD 180 per user per month and a typical contract value of USD 150,000 to USD 600,000. That SAP typical contract overlaps the Finance band and the NetSuite band, and only its top end reaches the bottom of the Oracle band. A community institution with a small finance team should price Business Central, Odoo, or a similar corporate ledger against its own entity count.

For how other industries separate a general ledger from industry operations, see our ERP examples by industry. In banking the customer balance is a regulated record that stays on the core.

What licenses cost and what a rollout band adds

License list and project cost answer different questions. As of October 2026, a year of Business Central Essentials for one user is USD 80 times 12, or USD 960, before tax and before any partner services. Team Members is USD 8 per user per month on the same yearly plan. Finance is USD 210 per user per month, and Finance Premium is USD 300. Odoo's US page shows two figures for Standard, USD 31.10 and USD 38.90 per user per month, and two for Custom, USD 61.00 and USD 76.20. Yearly and monthly toggles both render, so match the figure to the toggle you are looking at, and read the 12-month discount note for initial users on that page. Custom includes all apps, Odoo Online, Odoo.sh, or on-premise, Studio, multi-company, and the external API. Odoo.sh hosting is extra. A Light User is USD 8.90 and is limited to that person's own expenses, time off, and similar employee tasks.

Assume 8 people need a full Business Central license and 4 people need only a Team Members license. Eight Essentials seats at USD 80 are USD 640 per month and USD 7,680 for a year on the yearly plan. Four Team Members seats at USD 8 are USD 32 per month and USD 384 for a year. The combined list is USD 8,064 for the year. The same eight full users on Dynamics 365 Finance at USD 210 are USD 1,680 per month and USD 20,160 for a year. That Finance comparison prices only those eight seats, because a Finance equivalent of Team Members is a separate check on the pricing page. None of these totals includes implementation, added apps, or the integration that posts core-processor summaries.

ERP Research's August 2026 banking card puts a three-year-style total around those products at a bank: USD 75,000 to USD 400,000 for Business Central with a 2 to 6 month go-live, USD 150,000 to USD 1 million-plus for Dynamics 365 Finance with a 6 to 14 month go-live, USD 100,000 to USD 500,000 for NetSuite with a 4 to 9 month go-live, and USD 50,000 to USD 200,000 for Sage Intacct with a 3 to 6 month go-live. The same card's Dynamics starting price of USD 50 per user per month does not match Microsoft's Finance list of USD 210. Use the Microsoft page for licenses. Treat each range as the publisher's three-year total-cost estimate, not a license quote and not a split of services, data, and run cost. Ask each bidder to replace the whole band with line items. Do not add the license total on top of the band.

Ask for these lines in every quote, each with hours and a named owner:

1. Licenses, by role, at the current list, with Team Members or Light users justified one person at a time.
2. Configuration of the chart of accounts, dimensions or analytic accounts, banks, fixed assets, and the close calendar.
3. Data migration of open payables, fixed assets, and the opening trial balance, separate from history you only need for lookup.
4. The import that posts summarized core totals, priced against a real sample file from your processor.
5. Training for the people who post, approve, and reconcile, plus a support window after go-live.
6. Anything excluded: Call Report filing, loan origination, deposit servicing, and credit-loss models.

A quote that buries the core import inside a general integration line hides the hours that usually move, and the license total gets mistaken for the project. Our finance implementation scopes the corporate close as its own phase so those lines stay visible. If you are still deciding whether a full ERP is more system than the close requires, our note on ERP vs accounting software is the comparison to read before you add procurement and assets to a ledger project.

What an auditor can trace in the ERP

At the USD 1 billion Part 363 baseline, an independent accountant audits the GAAP statements, and management reports on internal control. At USD 5 billion, management and the accountant both speak to internal control over GAAP and regulatory financial statements, against a framework such as COSO. Examiners and auditors will ask who posted a journal, who changed a vendor or a GL account, and whether the core tie-out was reviewed before the period closed. Capital ratios stay in the models your policy already names.

Business Central can log who changed a field, the old and new values, and when, through the change log, and it can email alerts on monitored sensitive fields. Microsoft's change-log guidance warns that logging every field hurts performance, and that the log is off during version upgrades. Turn the log on for the fields that move money or change a posted setup: GL accounts, vendors, bank accounts, user permissions, and posting groups. Leave high-volume operational fields off the log. Plan how you will evidence changes during an upgrade window, because the log will not cover that window for you. Odoo's accounting documentation includes an audit trail. Have the implementer show a changed bill, the prior value, the user, and the time on your test company, and write that check into the go-live script.

A practical evidence pack for the corporate ledger has four artifacts: the close checklist with dates and names, the reconciliation of ERP control totals to the core extract, the change log or audit trail export for sensitive fields, and the mapping from the trial balance to the GAAP statements. Regulatory statements still come from the reporting process you already file. The ledger's job is to make the numbers in both packs trace to the same journals.

Basel returns and allowance-for-credit-loss calculations are outside the vendor finance pages cited here. When a model owner calculates a provision, the ERP should accept that entry as a controlled journal, with support attached, and refuse a silent overwrite of the prior period. That is an approval design on a journal the model has already calculated.

How core totals reach the corporate books

Re-keying the core into the ledger is how small differences become month-end emergencies. The alternative is a summary journal from a file the processor already knows how to produce. You do not need the ERP to hold every account transaction to do this well.

1. List the totals finance already reconciles: cash, deposit balances, loan balances, interest income, fee income, and charge-offs, using the core's own names for those totals.
2. Pick the grain. A daily summary journal catches breaks sooner. A monthly journal is enough when volumes are low and the core file is only available at month-end. Either way, use a clearing account that must net to zero when the file is in balance.
3. Give every bidder the same sample file, including a day that does not balance, and require the import design, the error report, and the hours as a separate line.
4. Map each core total to one ERP account and one dimension or analytic value. Changes to that map go through the same approval as a new GL account.
5. Reconcile ERP control totals to the core before the period closes. The person who posts the file should not be the only person who signs the tie-out.
6. Leave Call Report lines in the filing tool. After the quarter, agree the filing tool's key totals to the ERP, and store that agreement with the close.

If the processor will only hand you a customer-level extract, summarize it before it hits the ledger. Loading every account into the ERP recreates the core and makes the close slower. Your accountant can say which totals the GAAP statements require. The processor's file layout says which of those totals already exist.

Where we work and where we stop

We implement the corporate back office on Business Central and on Odoo for companies of about 20 to 100 people in the United States and Canada. For a bank, credit union, lender, or fintech, that means the general ledger, payables, fixed assets, the close, and the import of summarized activity from a core that stays where it is. Core banking, loan origination, and Call Report production are out of scope for us, and they are outside the vendor finance documentation cited above.

Our target for a first usable phase is 8 to 12 weeks. On this kind of project that phase is the corporate chart of accounts, open payables, fixed assets, and a working import of core summaries, with the core untouched. Later phases can add purchasing detail or a tighter management pack once the tie-out holds for a full close. We sequence that work with the Flectic Accelerated Delivery Framework. Discovery, configuration, migration, training, and support after go-live are laid out in our ERP implementation for growing companies.

Bring the fit-check answers, a sample core file, and last quarter's trial balance. We will tell you whether Business Central or Odoo can carry the corporate books, which roles need a full license, and which parts of the wish list belong on the core you already run.

How Flectic can help

Flectic's ERP implementation service puts finance, payables and receivables on a single ledger for companies of 20 to 100 people in the US and Canada, so leadership decides on reconciled numbers. Each phase has a defined scope and price before it starts, and the first one delivers a working part of the system. Migrated opening balances are checked before anyone relies on them, because history and balances move across at cutover. If a core system already posts your balances, select Book a free discovery call and Flectic will confirm which back-office parts we would cover.

Sources

12 CFR § 363.1 Scope and definitions, Legal Information Institute (eCFR text), October 2026.

12 CFR § 363.2 Annual reporting requirements, Legal Information Institute (eCFR text), October 2026.

12 CFR § 363.3 Independent public accountant, Legal Information Institute (eCFR text), October 2026.

12 CFR § 314.1 Threshold indexing, Legal Information Institute (eCFR text), October 2026.

FFIEC 031 reporting form description, Federal Reserve Board, October 2026.

Financial management - Business Central, Microsoft, October 2026.

Auditing changes - Business Central, Microsoft, October 2026.

Business Central pricing (US), Microsoft, October 2026.

Dynamics 365 Finance pricing (US), Microsoft, October 2026.

Odoo Pricing, Odoo, October 2026.

Accounting and Invoicing, Odoo 19.0, Odoo, October 2026.

Financial services, SAP, October 2026.

ERP Software for Banking, ERP Research, August 2026.

Banking and Financial Services ERP 2026, ERP Research, October 2026.

ERP for banks, DICEUS, October 2026.

ERP Software for the Banking Industry: The Essential Guide, NetSuite, October 2026.