T5, T3 and T5008 at Tax Time: How to Sort a Client's Investment-Income Slips Into One Clean PDF (Locally)

Short answer: A client's investment-income slips — T5 (interest & dividends), T3 (trust income) and T5008 (securities transactions) — arrive on different dates: T5 and T5008 by the end of February, T3 by the end of March. So the bundle comes in piecemeal, with stragglers into April. The clean way to handle it is to drop every scan and PDF into a local tool that classifies each slip, orders a mixed T5/T3/T5008 set to a consistent convention, and exports one merged PDF — all on your own machine, so SINs never leave it. PDF Insight does exactly this, on-device.

General information, not tax or legal advice. Filing deadlines and slip due dates can change and depend on the taxpayer's and trust's specific facts. Confirm dates with CRA guidance and your own professional judgment for each engagement.

The task no one writes about: assembling the bundle

Plenty of pages define these slips for investors, and plenty of vendors will sell you a cloud portal. Almost none cover the actual mechanical job an accountant does every spring: taking a shoebox of mixed investment-income slips — some emailed, some scanned, some downloaded from a broker — and turning them into one correctly ordered PDF you can review, reconcile and file from. That's the job this guide is about.

Know the three slips (and what each drives)

The overlap is what makes them easy to mis-file: a T3 and a T5008 can both feed capital gains, and a single brokerage account can generate all three. Sorting by slip type first keeps the reconciliation clean.

Why the bundle arrives piecemeal

The staggered due dates are the whole reason this is annoying:

• T5 and T5008 — end of February. These generally have to reach the recipient by the last day of February, so they show up first.
• T3 — end of March. T3 slips are due 90 days after the trust's tax year end; for most calendar-year trusts that's around March 31. Complex multi-tiered funds are the ones most likely to be late.

Practically, that means you'll assemble a client's file at least twice: an initial pass in early March with the T5s and T5008s, then a second pass once the T3s land — sometimes into April. Any workflow that forces you to re-sort the whole stack by hand each time is where the hours leak.

A clean four-step sort

1. Collect everything into one client folder. Broker downloads, emailed PDFs, phone photos of paper slips — one place.
2. Classify by slip type. Group T5s, T3s and T5008s so like sits with like. Multiple accounts multiply the count fast; a household of two with three accounts each can easily hit a dozen slips.
3. Order to a consistent convention. Pick one and stick to it firm-wide — e.g. T5 → T3 → T5008, then alphabetical by issuer within each type. Consistency is what makes the reviewer's job fast next year too.
4. Merge into one ordered PDF, and re-run when stragglers arrive. When the late T3 shows up, drop it in and regenerate rather than re-sorting by hand.

This is exactly the loop PDF Insight automates. You point it at the folder; it reads each page with on-device OCR, classifies each slip as a T5, T3 or T5008, orders them to your convention, and exports a single merged PDF — roughly 100 seconds for an 11-document bundle on a 16GB Mac. Add the late T3 and re-run in seconds. It's bilingual EN/FR, so French-labelled slips sort correctly too.

Auto-fill My Return doesn't get you off the hook

CRA's Auto-fill My Return (AFR) is a genuine time-saver, but it isn't a substitute for the actual bundle. Slips only populate as issuers file them, and T3s in particular often lag — so if you pull AFR in early March and file, you can easily miss a late trust slip and end up amending. The reliable practice is to reconcile AFR against a clean, ordered set of the slips the client actually received. That reconciliation is far faster when the slips are already sorted and merged than when they're scattered across email and downloads.

Why do this locally

Investment slips carry SINs, account numbers and full holdings — some of the most sensitive data you touch. Cloud portals and "AI" upload features move that data to a third party's servers, which you then have to account for under PIPEDA and your CPA confidentiality duties. A local-first tool sidesteps that entirely: the files are read, classified and merged on your own machine and never uploaded. It's the same wedge that separates on-device processing from TaxDome, SmartVault and Dext — you remove the disclosure instead of managing it. (For the full argument, see Is it safe to use AI on client tax documents?)