Paid on time, without the chase.
Payments land as bank files, deductions land in the inbox, and overdue invoices age inside the ERP. Corin matches the payments in SAP or Infor, works the exceptions, and drafts the chase — you approve every send.
Illustrative matching run — sample data, not a customer record.
Accounts receivable automation for SAP S/4HANA and Infor M3
Overnight bank statements match to open invoices with a confidence per match. High-confidence matches post on their own; anything below your floor asks a person.
Invoice to paid, one loop.
Invoice out, payment in — every step files into the ledger, a record of every decision: what changed, who approved it, when.
01The invoice goes out
Issued from the ERP in the structured format the destination country mandates — not a PDF on an email.
02Open items stay watched
Every open invoice tracked against its terms. Nothing ages unnoticed.
03Dunning becomes a decision
Per account: tone, timing, and channel, weighed against payment history and the amount at stake. The recommendation lands as a decision card.
04A human confirms the send
No dunning letter leaves without approval. Gold means a person said yes.
05Payments match back
ACH and bank credits arrive as BAI2 and camt.053 statements and match to open invoices. Unmatched remittances and deductions surface with their best candidate.
Collections, under your name.
Every dunning letter is drafted under your tone Procedure and goes out only after a person approves it. Corin never moves money, signs, or sends without your confirmation — until you tell it to.
DSO is a decision problem.
E-invoicing stops being optional.
Country by country, structured e-invoicing becomes law — and each mandate names the rails AR must run on. The clock below carries the dates; the loop on this page already issues on those rails.
Statutory dates, verified as of the marker.
7:58 — the bank file. 9:31 — the dunning sent.
7:58
overnight BAI2 statements land; 41 bank credits match to open invoices on their own.
8:05
three remittances stay unmatched — each surfaces with its best candidate invoice.
9:30
account 20881 crosses 45 days. Corin weighs tone, timing, and channel against payment history and the amount at stake.
9:31
the dunning recommendation lands as a decision card. Tom edits the first line, then approves.
9:31
the letter goes out under Tom's name — the decision and his edit are in the ledger.
An illustrative morning in AR — sample data, not a customer record.
Built for collections and the ERP team.
- Dunning arrives as a recommendation — edit it, then approve the send.
- Remittances match themselves; only the unmatched few surface, with their best candidates.
- Nothing chases a customer without a person saying yes.
- Invoices issue on the structured rails each e-invoicing mandate requires.
- BAI2/camt.053 statements match against open AR through released interfaces.
- Payment matching and every dunning decision leave a ledger entry.