How to Integrate Bank, Tax and Court Systems With Your ERP in 2026
ERP bank integration for cities and counties in 2026: positive pay, BAI2 and lockbox files, tax and court receipts, file vs API, reconciliation and testing.
On this page
- Key takeaways
- What is ERP bank integration (and what counts as an integration in government)?
- How to integrate bank, tax and court systems with your ERP in 2026: 7 steps
- Who should own each integration after go-live?
- Common ERP integration mistakes to avoid
- Frequently asked questions
- Conclusion: get the money trail right before go-live
To integrate bank, tax and court systems with your ERP, list every system that moves money into or out of your general ledger, decide file or API for each one, map fields and accounts down to the individual bank account, build reconciliation into the design, and test every interface end to end with real files before go-live. In government, ERP bank integration reaches well past the bank.
Key takeaways
Inventory every money-moving interface before configuration starts, including the treasurer’s tax system and the clerk’s court system.
Give each bank account its own GL cash account. Shared cash accounts make reconciliation slow and error-prone.
Send deposit-level detail, not daily totals. A summarized feed that spans several deposit days can’t be matched to the bank.
Scheduled files over SFTP still carry most bank traffic (KCT rule of thumb). APIs are licensed products, so confirm what you actually own.
Test with real bank files and real rejects, then run the outputs through your parallel test.
Name one owner per interface after go-live, with a daily check and an escalation path.
In KCT’s experience, it’s usually not the ERP that breaks your bank reconciliation. It’s the interfaces around it.
In a November 2024 audit, the Clay County, Florida Clerk of Court’s Division of Inspector General found that bank reconciliations “had not been completed on an ongoing basis since the implementation of Workday”. The problems the report describes sit in the process and in the feed from the court system, not in a software defect.
This guide walks through seven steps: inventory, file vs API, mapping, bank files, tax and court feeds, reconciliation and testing.
What is ERP bank integration (and what counts as an integration in government)?
ERP bank integration is the automated exchange of payment files, bank statements and confirmations between your ERP and your bank. In a city or county, the same problem extends to every system that collects money outside the ERP: property tax, court and clerk case management, cashiering, online payments and utility billing.
Workday’s administrator documentation, for example, lists bank statement support for BAI2, BTRS, ISO 20022 and MT940/942, plus custom formats such as CSV.
The risk lives in the legacy systems. Washington State’s auditor flagged, during the state’s One Washington ERP program, the risk that the new system “might not effectively communicate with legacy systems at state agencies”.
Use this table as a starting list for your government ERP integrations. Formats vary by bank and vendor.
Swipe to see all columns →
| Integration | Direction | Typical format | What usually breaks |
|---|---|---|---|
| Positive pay | ERP to bank | Check issue file (bank layout) | Voids not sent, check numbers or amounts out of sync |
| ACH payments | ERP to bank | NACHA file | Unverified vendor bank changes, batch totals that don’t tie |
| Bank statement | Bank to ERP | BAI2, BTRS or ISO 20022 | Duplicate loads, unmatched lines |
| Lockbox | Bank to ERP | BAI2 lockbox or bank layout | Remittance that doesn’t match an account, invoice or parcel |
| Property tax collections | Tax system to GL | GL export or batch file | Collections posted late, twice or not at all |
| Court and clerk receipts | Case system to GL | Daily GL export | Summarized or multi-day deposits |
| Cashiering and online payments | Portal to ERP | Vendor file or API | Settlement timing versus posting date |
How to integrate bank, tax and court systems with your ERP in 2026: 7 steps
Build an integration inventory that lists every system moving money into or out of the general ledger.
Decide file or API for each interface based on what the bank and vendor actually support.
Map fields, accounts and bank accounts so each bank account has its own GL cash account.
Set up the bank files: positive pay, ACH, BAI2 statements and lockbox.
Integrate property tax and court receipts at the same level of detail as the bank deposit.
Design reconciliation into each integration with control totals and a regular tie-out.
Test every interface end to end with real files, then run the outputs through your parallel test.
Step 1. Build an integration inventory before configuration starts
You can’t test or reconcile an interface that isn’t on the list, and the list must include systems finance doesn’t own, like the treasurer’s tax system and the clerk’s case system.
Gallatin County, Montana shows how long a gap between a tax system and the general ledger can last. The county runs two Tyler Technologies programs, TaxWise for the treasurer and Munis for finance. According to Explore Big Sky’s November 2025 reporting, bank statements showed about $237,000 more than the financial system at the end of fiscal year 2023.
Cash reconciliation findings had appeared in every audit report since fiscal 2018, and multiple outside firms had not found the cause. Officials suggested the overlap of the two systems may contribute, but that hasn’t been confirmed.
In 2026 reporting, KXLF noted that the county’s 2023 audit received a disclaimer of opinion and identified eight system failures, including an “inability to reconcile cash and investments.”
The lesson: a tax-to-GL handoff that nobody fully owns can go unresolved for years.
Build your inventory as a simple table with these columns:
System and owner department (treasurer, clerk, utilities, parks, police)
Direction (into the ERP, out of the ERP or both)
Frequency (real time, daily, per check run, monthly)
Format and transport (BAI2 over SFTP, API, manual upload)
Bank account and GL accounts affected
Control total (record count, dollar total or both)
Failure contact at the vendor, the bank and in house
Then put every interface in your statement of work with a named owner. If it isn’t in the SOW, nobody is contracted to build it. Our guide to writing a public sector ERP implementation SOW covers how to word that.
Step 2. Decide file vs API integration for each interface
In KCT’s experience, most bank integrations still run on scheduled SFTP files, and APIs are licensed products that need support from both your bank and your ERP vendor.
Don’t ask your vendor “do you have an API?” Ask what’s licensed. Tyler’s Enterprise ERP API catalog, for example, separates API Toolkits covering a whole module such as General Ledger or Accounts Receivable from narrower API Connectors built for a specific integration type, such as cashiering.
Swipe to see all columns →
| Factor | File (SFTP) | API |
|---|---|---|
| Best for | Statements, positive pay, ACH, lockbox, nightly GL batches | Payment status, intraday balances, cashiering and portal postings |
| Timing | Scheduled (daily or per run) | Near real time |
| Setup effort | Bank spec, SFTP keys, test cycle | Licensing, authentication, developer time on both sides |
| Monitoring | File arrived, record count, control total | Error logs, retries, rate limits |
| Typical failure | Late, empty or duplicate files; expired credentials | Silent failures, version changes after upgrades |
| Ask your bank or vendor | Which layout, which test environment, what cutoff time? | What is licensed, who supports it, what happens on upgrade? |
Pick per interface, not per project. KCT rule of thumb: don’t build an API where the bank only supports files, and don’t accept a manual portal upload for anything that runs daily.
Step 3. Map fields, accounts and bank accounts (one bank account, one GL cash account)
Mapping is where precision and meaning get lost. Map at the field level, and give every bank account its own GL cash account.
In Clay County, the Inspector General found that of 10 bank accounts in Workday, eight were tied to the same general ledger asset account. The recommendation was a separate GL asset account for each bank account.
The Washington State Auditor’s Office says the same thing in its “Best Practices for Bank Reconciliations” guide (January 2020): limit one-to-many, many-to-one and many-to-many relationships between bank accounts and GL accounts, and create unique GL accounts for bank accounts with unique transaction types. At the state level, One Washington’s response to its audit included building a map to translate data from older systems into Workday, plus rules for transaction codes.
Your mapping checklist should cover:
Fund, department and object segments
Bank account to GL cash account, one to one
Payment type codes (cash, check, card, ACH, wire, eFiling)
Void, stop payment and reissue codes
Date fields: transaction date versus deposit date versus settlement date
Reference fields that must survive to the bank, such as check number, case number or parcel number
Step 4. Set up bank files: positive pay, ACH (NACHA), BAI2 and lockbox
These four files carry most of your cash. Each one needs a bank-approved spec, a test cycle with the bank and a named owner.
Start with positive pay. The Washington State Auditor’s Office describes it as “a service banks offer that allow them to match checks issued by the government with those presented for payment”, with suspicious checks returned to the issuer for a decision.
Check fraud makes it essential. A February 2023 FinCEN alert reported more than 680,000 check fraud suspicious activity reports in 2022, nearly double 2021. In the 2026 AFP Payments Fraud and Control Survey (465 U.S. treasury practitioners across industries, underwritten by Truist, not government-only), 58% said checks were subject to fraud in 2025, more than any other payment method.
Here’s what each file needs:
If your government originates ACH for payroll or vendor payments, add one more conversation. Since June 19, 2026, Nacha’s Fraud Monitoring Phase 2 rules have extended fraud monitoring to the remaining non-consumer Originators. You need risk-based processes reasonably intended to identify unauthorized entries or entries authorized under false pretenses, reviewed at least annually. Ask your bank how your ERP’s ACH process fits that program.
KCT rule of thumb: bank onboarding is on the critical path, so request specs and a test environment at kickoff.
Interfaces sit between the ERP vendor, the bank, the treasurer and the clerk, and often nobody owns the whole chain.
KCT’s Full-spectrum ERP Implementation team owns that chain from inventory to go-live. At the City of Oxnard, KCT’s scope since 2021 has covered program management, data conversion, integrations and post-go-live support, with Finance, HCM and EPL now in production (read the Oxnard case study).
Step 5. Integrate property tax and court case management receipts at the right level of detail
Property tax system integration and court system integration work the same way: both should post detail to the ERP, or at least totals by payment type and deposit, that match how money actually hits the bank. Post it on the day it’s deposited.
Clay County’s court example shows why. According to the Inspector General’s report, the integration from the Benchmark court system to Workday is the daily sum of all collections: cash and checks, card payments (nCourt), eFiling and wires.
The eFiling vendor, Civitek, groups transactions across several days into one bank deposit. So a daily total from the court system never lines up with what the bank shows.
Workday’s documentation notes that basic automatic reconciliation matches statement lines to transactions “based on only amount and date”. A three-day summarized deposit won’t match either.
The Inspector General recommended a separate eFiling export, exports split by payment type (check, card, cash) and vendor reports that match deposit dates.
Property tax collections deserve the same design attention, as Gallatin County’s unresolved mismatch shows.
For both tax and court feeds:
Export by payment type and by deposit, not one daily lump sum.
Make one deposit equal one batch wherever possible.
Carry the deposit date, not just the receipt date.
Agree a daily cutoff time with the treasurer or clerk and the bank.
For third-party payment processors, get settlement reports that line up with deposits.
Include refund, bond and trust (court registry) accounts in scope from day one.
Step 6. Design ERP bank reconciliation into the integration, not after it
Good ERP bank reconciliation starts in the interface design: every interface needs a control total and a regular tie-out to both the bank and the GL, built before go-live.
In Clay County, bank balances during fiscal year 2024 were “only reconciled to data files from Benchmark” and not to the Workday general ledger. Operational journals hadn’t been closed for any period that year. The report also flagged a segregation of duties gap: the person creating ad hoc bank transactions shouldn’t be the one reconciling them.
The Washington State Auditor’s January 2020 reconciliation guide sets out the basics:
Reconcile every account at least monthly.
Record transactions as they occur from source records, not from the bank statement at month end.
Set a reasonable period, such as two weeks, to resolve discrepancies. Many banks limit error resolution to 60 days after the transaction date.
Keep reconcilers away from deposits, AP and payroll checks, and from authorizing electronic transfers.
Update reconciliation procedures when new accounting software goes in.
Use a proof of cash (a four-column reconciliation) to catch timing and posting errors.
Design three levels of tie-out for each interface:
Interface control totals.
Records and dollars sent, received and posted all agree.
Subledger to GL.
The tax, court or AR subledger agrees with the GL accounts it feeds.
GL to bank.
Each GL cash account agrees with its one bank account.
When you configure automated matching, put the most specific rules first. Workday’s guidance is to place more specific matching rules before general ones, and the same logic holds in most ERPs.
Our guide to surviving your first month-end close on a new ERP shows how bank reconciliation fits into that first close.
Step 7. Run end-to-end integration testing with real files (then your parallel test)
End-to-end interface testing means real bank files, real rejects and real timing, not a sample record in a test folder.
One Washington’s leading practice is simple: test data before and after the transfer. Clay County’s report found reconciliations had not been done on an ongoing basis since Workday went live, and the multi-day eFiling deposits were one of the reasons.
Use these scenarios as a minimum. Pass criteria are a KCT rule of thumb.
Swipe to see all columns →
| Scenario | What to test | Pass criteria |
|---|---|---|
| Positive pay with voids | Check run with a void and a stale check | Bank accepts file; void and stale check flagged as exceptions |
| ACH vendor bank change | Batch that includes a changed vendor account | Change verified before release; batch totals tie |
| Duplicate statement | Load the same BAI2 file twice | Second load rejected; no duplicate lines |
| Lockbox mismatch | Payment with a missing or wrong account number | Lands in a suspense queue with an owner |
| Tax batch across two days | Collections that span two deposit days | Each deposit matches its bank line |
| Court eFiling grouping | Processor deposit covering several days | Settlement report ties deposit to receipts |
| Late or empty file | File arrives after cutoff or with zero records | Alert sent; nothing posts silently |
| Expired credentials | SFTP key or password expires | Failure alert reaches the named owner |
| Format reject | Bank rejects a file layout | Reject captured, fixed and resent within cutoff |
Then route the positive pay file, ACH totals and check register through your parallel test, not just the payroll register. Our guide to ERP parallel testing before go-live walks through that reconciliation checklist.
Who should own each integration after go-live?
Every interface needs one named owner, a monitoring routine and an escalation path to the vendor and the bank. Without that, reconciling items pile up quietly after go-live.
In Clay County, the Inspector General noted that the Controller was the sole responsible party for bank reconciliations within Workday.
The Washington State Auditor’s Office says a monthly bank statement review can take as little as 30 minutes a month, including spot-checking ACH batches against transmittal receipts and verifying vendor bank account numbers.
Swipe to see all columns →
| Interface | Business owner | Technical owner | Daily check |
|---|---|---|---|
| Positive pay | Treasury or finance | ERP admin | Exceptions decided before bank cutoff |
| Property tax | Treasurer | Tax system admin | Collections posted equal deposits |
| Court receipts | Clerk finance | Case system admin | Export by payment type ties to deposits |
Treat credential expirations, bank spec changes and vendor upgrades as re-test triggers. The Washington State Auditor’s January 2020 reconciliation guide calls for updating procedures whenever software or receipting processes change. For the wider post-launch plan, see our guide to the first 90 days after ERP go-live.
Common ERP integration mistakes to avoid
Most ERP integration failures in government trace back to a handful of avoidable decisions, not to the software. Watch for these:
Leaving the tax or court system “for later.” Gallatin County’s cash findings have repeated since fiscal 2018.
Sending daily totals instead of deposit-level detail. Summaries can’t match multi-day deposits.
Sharing one GL cash account across several bank accounts. Both Clay County’s auditors and the Washington State Auditor warn against it.
No owner for positive pay exceptions. Undecided exceptions default to pay or return, and either can hurt.
Testing with sample files instead of bank-validated files. A file your bank has never accepted proves nothing about go-live day.
Leaving interfaces out of the SOW. If it isn’t contracted, it isn’t scheduled. Our post on Tyler Munis implementation mistakes covers other scope gaps that show up the same way.
Frequently asked questions
What is a BAI2 file used for?
A BAI2 file is a standard bank statement format that reports balances and transactions from your bank to your ERP. Your ERP uses it for reconciliation. Many ERPs also accept newer formats such as BTRS and ISO 20022. Workday, for example, supports all three.
What is positive pay and how does it work with an ERP?
Positive pay is a bank service that matches checks your government issues against checks presented for payment. After each check run, your ERP sends an issue file to the bank. The bank flags mismatches and your staff decide pay or return, as the Washington State Auditor’s Office describes.
Is API integration better than file (SFTP) integration for banks?
API integration isn’t automatically better than file integration. APIs suit real-time status and balances but need licensing and support from both sides. SFTP files remain the workhorse for statements, positive pay, ACH and lockbox, so choose per interface.
How do you test bank and interface integrations before ERP go-live?
Testing bank and interface integrations means running real bank-validated files end to end, including rejects, voids, duplicate loads, late files and expired credentials. Then run the positive pay file, ACH totals and check register through your parallel test before you sign off on go-live.
What is a lockbox file?
A lockbox file is a data file your bank sends after processing payments mailed to a lockbox address. The bank deposits the checks and sends the remittance details, such as payer, amount and account or invoice number, so your ERP can apply each payment automatically.
How do you connect a court case management system to the general ledger?
Connecting a court case management system to the general ledger usually means a daily GL export from the case system into the ERP. Split that export by payment type and deposit so it matches the bank. Clay County’s Inspector General recommended exactly that, plus a separate eFiling export and vendor reports matching deposit dates.
Who owns an ERP interface after go-live?
An ERP interface should have one named business owner and one technical owner after go-live, both listed in your support plan. The business owner checks results daily and decides exceptions. The technical owner handles file failures, credentials and vendor or bank changes.
Conclusion: get the money trail right before go-live
In each example, the trouble showed up at a handoff, not in core ERP functionality: a court feed summarized across days, eight bank accounts sharing one cash account, and a tax-to-ledger gap that years of audits haven’t explained.
So before your next steering committee meeting, ask two questions. Where is the integration inventory? And when did each interface last pass an end-to-end test with real bank files?
If your project is still in flight, KCT’s Full-spectrum ERP Implementation team can own the integration chain across your vendor, bank, treasurer and clerk. If you’re already live and reconciling items keep growing, start with an ERP Health Check.
Scope depends on your modules, departments and stakeholders, so we start with an assessment. Contact KCT to talk it through.