Hours back every day
A 60-line bank file that used to take an AP clerk most of a morning is parsed, matched, and queued for the Payment Journal in under a minute.
Accounts Payable
Corporate Direct Debit BAI2 Import
Turn your bank's direct-debit file into reviewed, ready-to-post Payment Journal lines.
Business Central extension that imports BAI2 bank files, identifies vendor direct-debit transactions, matches them to open purchase invoices, and stages validated lines in the Payment Journal — with clear validation indicators and a built-in audit trail.
The challenge
Vendors like insurance carriers, payroll providers, healthcare networks, utilities, and fleet companies pull funds directly from your corporate bank account. Today AP re-keys each of those debits from a bank statement PDF, then hunts for the matching invoice — a daily routine that eats most of a morning and invites mis-applied payments.
How Corporate Direct Debit BAI2 Import solves it
Corporate Direct Debit BAI2 Import reads the BAI2 file from your corporate banking portal, identifies vendor direct-debit transactions, matches them to open purchase invoices, and stages validated lines in the Payment Journal — ready for your AP team to review and post in the standard Business Central workflow.
Key benefits
Fewer mis-applications
Vendor and invoice matches are validated against open vendor ledger entries before a line ever reaches the journal, with clear green/red indicators on every staged line.
Audit-ready by default
The original bank file is archived inside Business Central against the import header, so every posted payment traces back to the exact file the bank delivered.
No bank-side change
Works with the BAI2 file your bank already produces — no API enablement, no portal contract changes, no IT ticket with the bank.
What it does
BAI2 file import
Imports BAI2 v2 files straight from Bank of America CashPro and other banks that publish standard BAI2 output.
Smart transaction parsing
Parses Type-16 transaction records — ACH debits (455), EDI/CTX debits (464), book wires (491), external wires (495), and other debit codes. ZBA sweep entries (275) are excluded from vendor matching automatically.
Remittance extraction
Pulls vendor name, vendor tax ID, invoice numbers, and per-invoice amounts out of the remittance and addenda data.
Vendor and invoice matching
Matches each transaction to a Business Central vendor and to one or more open purchase invoices in the Vendor Ledger before anything reaches the journal.
Clear validation indicators
Every staged line shows its status at a glance — vendor found, invoice found, amount matches. Green means a clean match; red flags an exception that needs a decision.
Payment Journal hand-off
Transfers selected lines into the Payment Journal with Applies-to Doc. Type and Doc. No. pre-populated, ready to post in the standard Business Central workflow.
Built-in audit trail
Archives the original bank file and parsed line detail against the import header, so every posted payment traces back to the exact byte stream the bank delivered.
How it works
- 1
Download
Export your BAI2 file from your corporate banking portal.
- 2
Upload
In Business Central, open Corporate Direct Debit BAI2 Import and upload the file.
- 3
Review
Scan the staged lines. Green indicators mean a clean match; red indicators flag exceptions that need a manual decision.
- 4
Create journal lines
Click Create Payment Journal Lines. The validated debits land in a Payment Journal batch with vendor application already wired up.
- 5
Post
Post the journal in the standard Business Central process.
Pricing
Subscription with a free trial
Start a free trial from the Microsoft Marketplace listing, or contact us for a quote.
Get a quoteFrequently asked questions
Which banks and file formats does it support?
Any bank that publishes standard BAI2 v2 output, including Bank of America CashPro. It works with the file your bank already produces — no API enablement or portal contract changes.
Which transaction types does it handle?
Type-16 transaction records including ACH debits (455), EDI/CTX debits (464), book wires (491), and external wires (495). ZBA sweep entries (275) are automatically excluded from vendor matching.
Does it post payments automatically?
No. It stages validated lines in the Payment Journal with vendor application pre-populated. Your AP team reviews and posts them in the standard Business Central workflow.
What happens when a line doesn't match cleanly?
Exceptions are flagged with a red indicator so AP can make a manual decision before anything is posted. Clean matches show green.
Related apps
Bank-initiated direct debits are convenient for your vendors and a daily chore for your AP team. The money leaves the corporate account on the bank’s schedule, and AP is left re-keying each debit from a statement PDF and tracking down the invoice it paid.
Corporate Direct Debit BAI2 Import takes the file your bank already produces and does that work in seconds — parsing every transaction, matching it to the right vendor and open invoice, and staging clean lines in the Payment Journal. Your team reviews the exceptions, posts the batch, and moves on. The original bank file stays archived in Business Central for the next audit.