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

For operations and finance managers at Canadian lenders

Back-office automation for Canadian lenders

We schedule the daily hand-offs your staff do by hand. What we build alerts someone when a run fails and keeps a dated log an auditor can check.

From $499 for simple hand-offs; SFTP, PGP and payment matching from $995.

After the call, a free working prototype within 5 business days of receiving sample data and test access. Sample data or a test setup only, never live customer data.

Run sheet

A Canadian consumer lender's schedule

WhenWhat runs on scheduleStatus
Daily Customer file sent to the card processor by key-based SFTP, each transfer confirmed by a separate watchdog. We built this.
Each
morning
Screening batch pulled from SharePoint, PGP-encrypted and sent by SFTP. We built this and its encryption service.
Later Screening results collected, decrypted and filed in SharePoint as a readable CSV. A member of the lender's team built this on our service.
Every
minute
Payment emails picked up and added to the loan system's daily workbook. Built by a member of the lender's team; our part is the payment provider connection.
Live in production at one lender. A tick means live. None of these steps uses AI.

AI Agency Canada builds scheduled loan servicing back-office automations for Canadian consumer lenders and finance companies (instalment loans, auto finance, alternative lending) that move work between SharePoint, Outlook, the loan management system and partners' SFTP servers. Based in Ontario, working with lenders anywhere in Canada, by phone or video.

Does your back office still run on someone remembering?

If you run operations or finance at a lender, some of this will sound familiar.

  • The customer file goes to the card processor once a week, when someone has time to log in to the SFTP server.
  • The screening batch has to be encrypted before it's uploaded, and one person knows how.
  • Payment notices are keyed into the loan workbook one email at a time, and a contract number gets typed wrong.
  • The customer portal shows balances from the last time someone did the upload.
  • When someone asks whether a file went on a given day, the answer is an inbox search.

Your staff aren't the problem. The manual hand-off is. Every file that moves only because a person moved it can be late, wrong or forgotten, and you're the one who answers for it. A lender's customer records and compliance files shouldn't depend on someone remembering a weekly upload.

Leave it as it is and the risks stay put: the upload that waits until someone is back from holiday, a payment entered twice or against the wrong contract, and no record to show when a partner or an auditor asks.

Has anyone done this for a Canadian lender?

Yes. These four are live in production at a Canadian consumer lender, which we don't name. All four come from that one lender, and each card says exactly which part was ours: we'd rather show you real work with honest credit than pad the list. None of them uses AI. Fixed rules are what you want for payments and compliance files.

No. 1 Live in production

Daily customer file to the card-payment processor

Our part
We built it.
Runs
Daily
Replaced
A weekly manual upload.
Now
The daily customer-records export goes from SharePoint to the processor over key-based SFTP. Each transfer is confirmed by a separate watchdog, with an error alert on any failed run.
Tools
n8n, SharePoint, SFTP with SSH keys

Read the SFTP transfer case

No. 2 Live in production

Encrypted sanctions (AML) screening batch

Our part
The encryption service and the morning send. A member of the lender's team built the results workflow.
Runs
Each morning; results collected later
Now
The customer screening batch is pulled from SharePoint, PGP-encrypted and sent by SFTP. Results come back, are decrypted, flattened from XML into a readable CSV and filed in SharePoint.
Tools
n8n, a small encryption service for PGP, SFTP, SharePoint

Read the screening batch case

No. 3 Live in production

Customer-portal balances from the loan system

Our part
We contributed, working with the lender's team.
Runs
On a schedule
Replaced
A weekly manual upload.
Now
The loan system's account export reaches the customer login portal through a scheduled secure upload that the site imports.
Tools
Power Automate, SharePoint, WordPress

Read the portal sync case

No. 4 Live in production

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

Our part
The connection to the payment provider's API and the read-only transaction lookups. The flow itself was built by a member of the lender's team.
Runs
Every minute
Now
Payment emails are picked up, pay-by-bank emails are matched to the payment provider's API for the contract number, duplicates are skipped, and rows go into the daily workbook for the loan-management system.
Tools
n8n, Outlook, SharePoint, Excel, Microsoft Graph

Read the payment email case

Who builds it, and why should you trust them with your files?

Scott Holmes, founder of AI Agency Canada
Scott Holmes, founder

You shouldn't have to check every morning that the file went.

Scott Holmes, an Ontario-based AI automation builder, designs and builds our automations, and you talk to him directly.

  • Of the four examples: we built the card-processor SFTP transfer; we built the screening batch's encryption service and morning send; we contributed to the portal upload; and the payment-email flow was built by a member of the lender's team, using our connection to the payment provider's API.
  • Each case page says which part we built and what the automation doesn't do.
  • Designed with PIPEDA and Quebec Law 25 in mind. We claim no certifications.

How we keep the risk down on every build: we test the hardest connection in the first week, ask for partner test access on day one, and give every hand-off its own check, because some systems never confirm that a file arrived.

How do we start?

Three steps. The first two are free.

  1. Book a 30-minute call

    Name the hand-off you'd stop first. We ask what your partner requires: SFTP, keys, PGP, file format, schedule.

  2. Get a free working prototype

    Within 5 business days (terms), on sample data or a test setup, never live customer data. You keep a written summary and the fixed price for the full build.

  3. Approve the price, and it runs

    We build it in your accounts with alerts, a separate check and a run log. Typically live in about 2 weeks once partner access is in place.

No obligation after the prototype. The prototype itself stays with us. Limited to 4 prototypes a month.

Book a free 30-minute call

What does it cost?

Published prices, in Canadian dollars. Custom work is fixed in writing before we start.

What you getPrice
Standard automationOne well-known app to another through a ready-made Zapier, Make or n8n connector, such as Outlook to Excel. One simple AI step included if it helps. Documentation and 2 weeks of support. $499
Custom buildSFTP with keys, PGP encryption, loan-system files, matching to a payment provider. Fixed in writing after the free prototype. Typically live in about 2 weeks. from $995
Each extra app connectedSystems with no connector and custom software are quoted separately, in writing, after the prototype. $499
Monthly supportHosting, monitoring, fixes and small changes. Month to month, cancel anytime. $99a month
Call and working prototype30-minute call, then one workflow working on sample data within 5 business days (terms). $0

See what's included, what isn't, and how each example would be priced

What changes once it's running?

  • Every dayYour partner gets a fresh file, not a weekly one.
  • MorningThe screening batch leaves on schedule, and the results come back later, decrypted and filed.
  • All dayPayment notices reach today's workbook within a minute or two of arriving, and nobody keys them.
  • When it failsAn alert the same day, and a separate watchdog that confirms the file arrived.

You stop being the person who checks. When a partner or an auditor asks whether a file went on a given day, you open the run history and the dated file in SharePoint and show them.

Questions to ask before you start

How do you send files to a partner's SFTP server, and what if a transfer fails?

With key-based SFTP, the way card processors and screening services ask for it, and PGP encryption where they require it. Every transfer gets an error alert on any failed run and a separate watchdog that confirms it happened, as in our card-processor example, because a sending tool can report success even when the other end never received the file. Read the SFTP case.

Can you automate our AML sanctions screening uploads?

Yes. For a Canadian consumer lender we built the PGP encryption and decryption service and the morning send: each morning the customer screening batch is pulled from SharePoint, unzipped, encrypted and uploaded by SFTP. A member of the lender's team built the results workflow on top of our service; it later collects the results, decrypts them, flattens the XML into a readable CSV and files it in SharePoint. The automation moves and converts files. The screening service does the screening, and your analysts review the results. Read the screening case.

Can you automate e-transfer payment emails into our loan workbook?

Yes. In a live example at a lender we work with, customer payment emails (e-transfer and pay-by-bank) are picked up every minute, 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, duplicates are skipped, and new rows go into a daily Excel workbook for the loan-management system. That flow was built by a member of the lender's team. Our part was the connection to the payment provider's API and the read-only transaction lookups. Read the payment email case.

Where does our customer data go? Is this PIPEDA compliant?

We design with PIPEDA and Quebec Law 25 in mind and claim no certifications. Your automations are built in your own Microsoft 365 and automation accounts. Before we build, we write down every place customer data will pass through, including short stops such as an encryption service, so it can go in your privacy records, and we set run history to be kept only as long as you need it.

Do you use AI for this?

Only where it helps. None of the four lender automations on this site uses AI. They follow fixed rules, which is what you want for payments and compliance files. We add an AI step only where a fixed rule can't do the job, such as reading text with no set layout, and we tell you which steps use it before you pay.

How long does it take, and what does it cost?

The free prototype is ready within 5 business days (see the terms). A build is typically live in about 2 weeks once access is in place. Partner test access can take weeks or months, so we ask for test credentials on day one. A standard automation is $499. SFTP, PGP, loan-system files and payment matching are custom work, fixed in writing after the prototype, from $995. Monthly support is $99 a month, month to month. Prices are in Canadian dollars. Full price list.

Pick the hand-off you'd stop first. We'll prototype it free.

A 30-minute call, then a working prototype within 5 business days (terms). If it isn't worth building, you'll hear that too.