Topic
Sage 50
Sage 50 (US Peachtree and Canadian Simply Accounting) conversions, editions, and downgrades. 36 guides and 425 answers on this topic.
Sage 50 FIFO error: "cannot change the historical Opening Quantity or Opening Value
Sage 50 locks inventory opening balances once a FIFO item has any transaction, preventing edits to quantity or value.
AnswerSage 50Sage 50 has lost contact with the current Sage Drive company
Sage 50 cannot reach the cloud-hosted copy of your company file, usually due to a sync, network, or upload interruption.
AnswerSage 50Sage 50 unable to locate a supported version of Crystal Reports
Sage 50 cannot find a compatible Crystal Reports runtime, which blocks forms and report printing until the runtime is restored or reinstalled.
AnswerSage 50Sage 50 was unable to reconcile those transactions
Sage 50 is rejecting a reconciliation attempt because one or more transactions are damaged, locked, or internally inconsistent.
AnswerSage 50Sage 50: "The fiscal year cannot be changed after your company is created
Sage 50 locks your fiscal-year structure once the company file exists, so you cannot edit it through settings afterward.
AnswerSage 50Sage 50: "The transaction line inventory item is not valid
Sage 50 cannot match an inventory item on a transaction line to a valid item record, blocking the entry from posting or saving.
AnswerSage 50Simply Accounting "Internet access is required for this command
The message means Sage 50 needs an online connection to validate your licence or sync cloud data, not that your file is damaged.
AnswerSage 50SmartPosting service encountered an error while posting transactions
Sage 50's background posting engine failed to commit transactions for the last opened company, usually pointing to data corruption in the company file.
AnswerSage 50SmartPosting will remain stopped for the company that caused the error
Sage 50's background posting service hit a data problem in one company file and has disabled background posting for that file.
AnswerConversionThe conversion log reports what could not be converted to Sage 50
Sage 50 finished importing your data but skipped records it could not map, and the log lists each item that did not make it across.
AnswerSage 50The cost record number of the transaction line is not valid" — Sage 50 error
Sage 50 is rejecting a transaction because an internal cost-tracking reference on a line item is corrupted or points to a missing record.
AnswerSage 50The job record number of the transaction line is not valid" in Sage 50
Sage 50 is reporting that a transaction references a job record that no longer exists or is internally inconsistent, indicating data corruption.