Canada’s Real-Time Rail: are your ERP and accounts receivable ready?

Fictional illustrative scenario. Friday, 10:40 p.m., a distributor customer pays twelve invoices in one transfer with a truncated reference. If both their bank and yours support real-time payments, the money could reach your account that same evening.

Working out which invoices it belongs to may still wait until Monday morning. Meanwhile, the customer’s next order may sit on credit hold.

Payments Canada plans to launch the Real-Time Rail (RTR) in the fourth quarter of 2026. For AR teams, speed is the easy part. The real work sits between the bank, the ERP and the people who apply cash.

About 60% of Canadian businesses surveyed by Payments Canada say they are ready to use real-time payments. Source: Payments Canada, Leger study of 507 businesses, August 2026

Stated intent is not adoption. It does suggest your paying customers could change habits faster than your month-end process.

What does Canada’s Real-Time Rail change for accounts receivable?

It changes when money arrives and how much data can travel with it, not your duty to apply every dollar correctly. According to Payments Canada, the RTR is built for instant, data-rich payments, any day of the year.

In practice, for the AR team:

• receipts land in the evening, on weekends and on holidays, when nobody is watching bank statements;
• a payment can carry structured remittance data, if the payer and their bank fill it in;
• a customer who pays instantly expects to see the account updated quickly, especially when an order is waiting for credit release.

That last point gets underestimated. A payment received but not applied means a blocked order and a collections call to a customer who already paid.

Public reference points as of October 2026:

• Planned launch: Q4 2026 (Payments Canada, 2026).
• Target availability: any time of day, 365 days a year (Payments Canada, 2026).
• Intent study: 507 businesses surveyed by Leger, March 23 to April 3, 2026 (Payments Canada, 2026).

Method note: these figures come from a study published by the system’s operator, which promotes it. They measure stated interest, not actual adoption.

Can your bank deliver ISO 20022 remittance data to you?

Possibly, and that is the first question to put to them in writing. Payments Canada presents ISO 20022 as a way to carry richer remittance data that supports reconciliation automation.

Nothing forces every payer to populate those fields. What your bank keeps, shortens or drops along the way matters just as much.

Before launch, ask your financial institution:

• when it expects to offer real-time receipts, and on which business accounts;
• which formats it uses for statements and credit advices (for example camt.053 or camt.054), and through which channel;
• how often it publishes intraday statements, weekends included;
• which remittance fields it passes through in full, and which it truncates;
• how it flags a returned or rejected payment.

Log the answers with dates. A verbal assurance in a relationship meeting is not a format specification.

Can your ERP absorb 24/7 receipts without losing control?

Your ERP does not need to post in real time, but it must receive, store and defer cleanly. Many environments still import one bank statement per business day. That cadence can work at first, as long as it is a choice rather than a default.

Check with your ERP team:

• how often statements can be imported, and whether several imports a day create duplicates;
• how a Saturday or holiday transaction is dated, and which accounting period it lands in;
• which controls must pass before anything hits the general ledger: amount, customer, invoice, currency;
• where the raw remittance is kept, for audit and for disputes.

The rule we recommend: separate receipt from posting. Each payment moves through explicit statuses, for example pending, linked, reconciled, then posted.

If the customer payment amount (the deposit item) does not match the total of the targeted invoices and adjustments, the payment stays at linked, in plain view. It does not vanish into a suspense account nobody reviews before close.

How do you apply cash when the invoice reference is missing?

Treat a missing reference as a routed exception, not a speed problem. Real-time payments speed up the money. They also speed up your exceptions.

Your cash application software or ERP rules should at least provide:

• matching on a structured invoice number first, then on amount and customer when the reference is missing;
• separate handling for partial payments, overpayments and bundled payments;
• an exception queue with a readable reason code and a named owner;
• a procedure for returns and misdirected payments.

Talk to your paying customers too. Telling them which reference to enter, and in which field, is still the cheapest way to improve remittance quality.

Real-time payments do not remove your exceptions. They deliver them faster, often on a Saturday night.

Who owns a payment that arrives on a Sunday?

Someone has to before launch, or nobody will after. An always-on system does not mean your team works weekends. It does require an explicit decision on what can wait and what cannot.

• Treasury: balance monitoring and after-hours fraud alerts.
• Accounts receivable: exception queue and application on the next business day.
• Credit: a rule for releasing orders on payments received but not yet applied.
• IT and ERP: import monitoring and recovery when a load fails.

Put these rules on one page. The auditor and the on-call person will both use it.

How do you measure readiness before and after launch?

Take a baseline now, on your current receipts. Without a starting point, you cannot show that real-time payments improved anything.

• Average time from payment receipt to application.
• Share of payments applied without manual touch.
• Unapplied cash balance at month end.
• Number of exceptions without a documented reason.

Unapplied cash feeds straight into collection timelines, as we explain in our piece on how to reduce DSO by tackling unapplied cash.

Which decision checklist should you use before the RTR launch?

A short list where every item ends in a decision: ready, prepare or defer. We recommend reviewing this list with finance, treasury and IT together, because every item depends on at least two teams.

1. Real-time receipt date confirmed in writing by your bank.
2. Statement format and frequency validated with a real import test.
3. ISO 20022 remittance fields preserved all the way into the ERP.
4. Matching rules adapted to structured references and to payments with no reference.
5. Intermediate statuses between receipt and posting.
6. Documented handling of returns, overpayments and partial payments.
7. Named after-hours owners, with a written credit-release rule.
8. Baseline measured on three months of receipts.

An unchecked item will not stop your customer from paying you in real time. It only decides who on your side finds the problem, and when.

Should you wait for launch to get ready?

No. The launch is planned, not dated to the day, and each bank will follow its own onboarding schedule. The checklist work improves how you handle today’s transfers anyway.

If cash application automation is part of a broader AI agenda, our four-week AI workshop helps one business unit, with about five participants, sort use cases by problem, value, data and effort. Investment depends on scope and is confirmed after a short scoping call.

Frequently asked questions about real-time payments and accounts receivable

When will Canada’s Real-Time Rail launch?

Payments Canada plans to launch the Real-Time Rail in the fourth quarter of 2026. Actual access will depend on your financial institution, which sets its own onboarding schedule. Ask your bank in writing when your business accounts can receive real-time payments and in which format the remittance data will reach you.

Will real-time payments always include the invoice number?

No, nothing guarantees it. ISO 20022 can carry detailed, structured remittance data, but each payer and their bank decide what they actually fill in. Build matching rules for payments without a reference, and tell your customers clearly which reference to enter and in which field when they pay you.

Does my ERP need to post receipts in real time?

Not necessarily. What matters is that the ERP receives and keeps every receipt with its remittance data, then posts it after defined controls. Several imports a day can be enough at first. The key is a clear status between receipt and posting, plus an exception queue owned by a named person.

Will request to pay be available when the RTR launches?

No public source we reviewed confirms that a request to pay feature will be available at RTR launch. Businesses show interest in this feature, but no public timeline has been confirmed. Wait for your bank’s announcements before designing a collections process around that feature.