Every payment finds its invoice.
eventsBank files and lockbox feeds, matched and posted in SAP or Infor. High-confidence matches post; everything else arrives as a decision with the evidence attached.
Bank lockbox automation — statements in, cash applied
on the wire: BAI2 · camt.053 · NACHA
01The day's files land
Prior-day and intraday statements arrive as BAI2 or camt.053. Balances and transactions reconcile against open AR the moment they land.
02Lockbox remittance matched
Lockbox files — still how a large share of B2B checks clear — are read line by line and matched to open invoices with a confidence per match; deductions are flagged for review.
03NACHA generated, never released
Payment files are generated with the full reasoning attached — who, how much, which invoices. Release is always a human confirmation; there is no autonomy level that moves money on its own.
04Every match on the record
Each match and each staged payment writes to the ledger — a record of every decision: what changed, who approved it, when — replayable later, exportable to your auditors.
Confidence decides who posts and who asks.
Matches at or above your floor post on their own. Below it, Corin asks — with the payment, the candidate invoice, and the gap laid out.
Illustrative matching run — sample data, not a customer record.
Statements in. Payments staged.
38 credits, 12 debits — 36 credits matched to open invoices on arrival.
Lockbox batch LB-2204: $184,220.15 across 9 remittances — 8 matched, 1 short-pay flagged with the deduction attached.
Sample documents — representative data, not a customer record.
Not a bank.
Not a funds holder. Corin connects to your bank's files and portals; money stays where it is until your process releases it.
Not autonomous payments. The NACHA file is a staged artifact — a person releases it, every time.
Not a treasury replacement. It feeds the AR and AP loops you run; your banking relationships stay untouched.
Corin never moves money, signs, or sends without your confirmation — until you tell it to.