Connecting your bank's feeds to your ERP sounds like a solved problem until you try to do it. Here's how Boomi fits into treasury and AP integration work, the patterns that hold up in production, and where these projects typically go sideways.
Every mid-market finance team eventually runs into the same wall: the bank has data your ERP needs — lockbox deposits, positive pay match results, ACH return codes, prior-day balances — and getting it there reliably, every day, without someone manually downloading a CSV, is a bigger project than it looks. Boomi has become one of the more common integration platforms we see firms reach for to solve this, largely because most banks already support the file formats and connection methods it handles well, and because it sits comfortably between "write custom code" and "wait for your ERP vendor to build a native connector."
Bank-to-ERP integration isn't really an API problem — it's a file-format-and-timing problem. Most banks still deliver core treasury data as flat files (BAI2 for prior-day balance and transaction reporting, NACHA for ACH, fixed-width or delimited files for lockbox and positive pay) dropped on an SFTP server on the bank's schedule, not yours. The ERP, meanwhile, expects data shaped a particular way, validated a particular way, and posted on its own batch cycle. Boomi's job is to sit in the middle: pick up the file, parse it, transform it into something the ERP's API or staging tables can accept, handle the exceptions, and alert someone when a file doesn't show up or doesn't parse.
This is the most common starting point. Boomi polls the bank's SFTP folder, parses the BAI2 file structure (group/account/transaction records), maps transaction codes to your chart of accounts or GL mapping table, and pushes a normalized feed into the ERP's cash management or bank reconciliation module. The failure mode to design around isn't the parsing — it's late or missing files. Build an alert for "expected file didn't arrive by X time," not just a retry loop, or finance won't know their cash position is stale until someone notices.
Positive pay is bidirectional: you send the bank your issued-check file, the bank sends back a file of items presented for payment that didn't match, and someone has to decide pay or return — usually within a same-day window. Boomi can automate both legs — generating the issued-check file from the ERP's AP data on a schedule, and routing the bank's exception file into a review queue or workflow tool rather than an inbox. The pattern that works best routes exceptions to a named owner with a hard deadline reminder, because the bank's decision window is unforgiving and doesn't care that someone was on vacation.
Generating NACHA files from ERP payment batches is the easier half; processing ACH returns (R01 insufficient funds, R03 no account, etc.) back into the ERP so AP or AR knows a payment failed is where most homegrown integrations fall apart. A solid Boomi process maps return reason codes to specific ERP actions — flagging a vendor payment for reissue, or an AR receipt for collections follow-up — rather than just dumping the return file into a shared drive for someone to interpret manually.
For AR-heavy organizations, lockbox files (deposit detail with remittance data, often OCR'd by the bank from paper checks) feeding automated cash application is one of the highest-ROI integrations to get right. Boomi's role here is matching remittance data to open invoices before the file ever reaches the ERP, so the ERP only sees clean, pre-matched application records instead of a pile of unapplied cash that AR has to chase down manually.
Boomi is a solid fit for bank-to-ERP integration because the hard part of this work is rarely the platform — it's understanding the bank's file specs, the ERP's expected inputs, and designing for the exceptions rather than just the clean-file case. Firms that treat this as "just connect two systems" tend to underbudget the exception workflows; firms that budget for reconciliation and alerting from day one get an integration that actually runs unattended.
Planning a Boomi integration between your bank and ERP? We've built lockbox, positive pay, and ACH integration workflows across multiple ERP platforms — happy to talk through what your specific bank and ERP combination will actually require.
Book a Free Consultation →