Back-office automation for Canadian lenders. Calls by phone or video.For Canadian lenders

Book a free call
AI Agency Canada.

Files, payments and screening, on schedule

Examples · No. 4 of 4

E-transfer and pay-by-bank emails into the loan workbook, every minute

Every minute, a Canadian consumer lender's customer payment emails (e-transfer and pay-by-bank) are picked up. The payer, amount and reference are extracted, pay-by-bank emails are matched to the payment provider's API to fill in the contract number, anything already added is skipped, and new rows go into a daily Excel workbook for the loan-management system.

Built by a member of the lender's team. Our part: the connection to the payment provider's API and the read-only transaction lookups.

We build payment-email automations like this for Canadian lenders and finance companies: $499 for notices copied into Excel, from $995 when pay-by-bank payments are reconciled to contract numbers against your payment provider, with a free working prototype first.

  • Live in production
  • A Canadian consumer lender
  • No AI: fixed rules
At a glance
RunsEvery minute
ReadsCustomer payment notification emails (e-transfer and pay-by-bank)
MatchesPay-by-bank emails to the payment provider's API, conservatively, to fill in the contract number
WritesNew rows in a daily Excel workbook for the loan-management system (LMS), through Microsoft Graph
ProtectsAgainst duplicates, with a processed-keys table
Toolsn8n, Microsoft Outlook, Microsoft Graph, SharePoint, JavaScript, OAuth 2.0
Our partThe connection to the payment provider's API and the read-only transaction lookups. The flow was built by a member of the lender's team.
StatusLive in production

What does it do?

  1. Polls the mailbox every minute for customer payment notification emails.
  2. Extracts the payer, amount and reference from each email.
  3. Matches pay-by-bank emails to the payment provider's API to fill in the contract number. Our part is this connection and its read-only lookups.
  4. Skips anything already added, using a processed-keys table.
  5. Appends new rows to the day's Excel workbook for the loan-management system, with a new workbook each business day.
Payment emails into the loan workbook Payment emails picked up every minute, payer, amount and reference extracted, pay-by-bank emails matched to the payment provider's API, duplicates skipped, rows appended to the daily workbook. Payment emails picked up every minute Extract payment details payer, amount, reference Match pay-by-bank payments provider API lookups (our part) Skip if already added processed-keys table Add row to the daily workbook Excel, via Microsoft Graph
The red box is the step that stops a payment being added twice.

What doesn't it do?

  • Post into the loan system itself. It fills the daily workbook for the loan-management system.
  • Force a match. Matching to the provider's records is conservative.
  • Use AI.

Will it work with our loan management system (LMS)?

If your loan system can export a report or import a file, we can usually work with it. In this example the flow fills a daily Excel workbook for the loan-management system. Where the vendor's API isn't open to you, files are the route.

What would this look like at your lender?

If your payments arrive as notification emails, we can build the whole flow for you, including the kind of payment provider connection we built here. In the free prototype we'd use a few of your real notice formats with customer details removed, your workbook template and your daily cutoff, and show it filling a test workbook from a test inbox.

  • Notices copied into Excel, no reconciling: Outlook to Excel are both well-known apps with ready-made connectors, so this can be a standard automation at $499.
  • Pay-by-bank payments reconciled to contract numbers against your payment provider: a custom build, fixed in writing after the prototype, from $995.
  • Watching it for you: $99 a month for monitoring, fixes and small changes, month to month.

Customer names and amounts will pass through your workflow, so on your build we'd set the platform to keep its run history only as long as you need it, and we'd agree with you how many transactions a day it must handle.

Your payments inbox could fill its own workbook.

Tell us how your payment notices arrive and where they need to go. We'll show it working on a test inbox, free, within 5 business days of receiving sample data and test access.