Sage 50 error "Cannot get start balance for This Year or Last Year
Sage 50 cannot pull the opening balances for this year or last year for the operation you just attempted, often during an export, report, or conversion.
“Cannot get start balance for This Year or Last Year in this method.” is Sage 50’s way of saying that whatever you just attempted needs the opening balances for the current fiscal year or the prior one, and the program could not retrieve them. Despite the wording, this is not about a bank reconciliation start balance. It is about year-start account balances, and it tends to appear when data is being pulled out of the file: a comparative report, an export, or a conversion to another accounting product. Sage 50 is the product formerly sold as Peachtree in the US and Simply Accounting in Canada.
What the message actually means
Each time a fiscal year is closed, Sage 50 carries forward a set of opening balances into the new year. When a report, export, or conversion asks for “This Year” or “Last Year” figures, the program first fetches those stored year-start numbers. The phrase “in this method” refers to how the program was fetching them, not to anything you did wrong. If the stored balances are missing, incomplete, or inconsistent, the fetch fails and you see this message instead of numbers. In plain terms: the file cannot answer a question about where your accounts stood at the start of this year or last year.
Why it happens
- A fiscal year was never properly closed, so no opening balances were carried forward.
- A year-end close was interrupted or performed out of order, leaving partial year-start data.
- The data holding year-start figures is inconsistent or damaged.
- The operation itself does not support reading balances across those periods, which is common with export and conversion tools that read Sage 50 data from outside the program.
What to check first
Make a fresh backup before changing anything. Then confirm your fiscal year setup: that the current year and the prior year are both defined, and that year-end was completed for the year before last. If you have a backup from before the most recent year-end close, try the same operation on that backup; if it works there, the problem is with the most recent close rather than the whole file. Also try the same report or export for a single year instead of a two-year comparison, since that avoids asking for one of the balances that is failing.
If it appeared during a conversion
This message is a common stumbling block when moving Sage 50 data to QuickBooks, because a conversion needs opening balances to build the destination company correctly. If the tool cannot read them, the conversion stalls even though day-to-day accounting inside Sage 50 looks fine. Our engineers handle this by extracting the balances directly from the data and rebuilding them in the target file, as part of our Sage 50 to QuickBooks conversion service; we do the same for the Canadian edition.
When the file needs attention
If the message appears on ordinary reports inside Sage 50, not only during an export, the year-start data itself is likely damaged or incomplete. That is not something a reinstall or a settings change fixes; the data has to be repaired. Our engineers do this kind of Sage 50 database repair regularly, and we can tell you whether yours is a repair case or a conversion case.
The useful next step is a free evaluation of the file before you retry anything. We will examine the year-start data, tell you what is missing, and provide a no-obligation quote, so you know whether this is a settings issue or a repair before anyone touches your books.