Front-End Load vs. Back-End Load: What's the Difference?
A mutual fund’s sales charge can be taken out at two very different points in the life of an investment, and which point applies can make a real difference in the total amount paid.
The short answer
A front-end load is a sales charge deducted immediately when shares are purchased, which reduces the amount that actually gets invested from day one. A back-end load, sometimes called a contingent deferred sales charge, is instead deducted when shares are sold, and it typically shrinks the longer the shares are held, occasionally disappearing altogether after several years. Both exist to compensate whoever facilitated the sale; they differ mainly in timing, and often in total size as well.
How a front-end load works
With a front-end load, the charge comes off the top of the initial investment before the remainder goes to work in the fund. Suppose, as an illustration only, an investor puts in a set amount and a portion of it is deducted as the sales charge — the rest is what actually gets invested. Larger purchases sometimes qualify for a breakpoint discount that reduces the percentage charged as the invested amount crosses certain thresholds, which can make front-end loads relatively more efficient for bigger, longer-term investments.
How a back-end load works
A back-end load flips the timing: the full amount is invested upfront, and the charge only applies if and when the shares are sold, generally within a set number of years of purchase. These charges commonly start at a certain percentage and step down each year the shares are held, reaching zero after enough time has passed. This structure is closely related to how level-load share classes are priced over the life of an investment, where the ongoing annual cost, rather than a single charge, does most of the work.
Why the expected holding period matters so much
Because a front-end load is charged once regardless of how long the shares are ultimately held, its cost is fixed at the time of purchase. A back-end load, by contrast, can be avoided almost entirely if the shares are held long enough to outlast the declining schedule. This is why how long an investment is expected to be held plays such a direct role in comparing the two structures — a short holding period can make a back-end load riskier to end up paying, while a front-end load’s cost is known from the start either way.
Where to find the exact numbers
The precise percentages, breakpoint thresholds, and decline schedules for any given fund’s loads are laid out in its prospectus fee table, and they vary by fund company and by share class, so there is no universal number that applies across the board.
The bottom line
Front-end and back-end loads are two different ways of billing for the same basic service: compensating whoever facilitated getting the money into the fund. Neither structure is automatically cheaper — the answer depends on the specific percentages involved and how long the investment is actually expected to stay put.