Considerations for using Force Zero Proof

If you set Force Zero Proof in GL Settings to By debit/credit or By [Prefix A, B or C]:

• General Ledger checks the total debits and credits to ensure that they are in proof.
• If a file is out of proof, Sage copies all records from the import and writes them to the rejected file.

Out of balance

An out-of-balance situation results if:

• The original import file is out of proof.
• Rejected transactions records force the file out of balance during the verification process.

An out-of-balance message prints on the first page of the journal. It includes the total debits/credits and the difference.

If rejections force the file out of balance, the journal's second page lists the rejected transactions with the error messages. The line numbers on the journal correspond to the records in the rejected records file.

See information about false rejections when you use No for the Force Zero Proof setting during imports.

Considerations for using Excel to create import files

• Save Excel files as .txt files to import into General Ledger. Make sure the encoding type is ANSI.
• Import treats positive amounts in the credit field as credits. Using the negative sign attached to the credit results in importing a debit amount.
• If you get a non-printable character error, save the file as a .csv first, then rename to .txt. The CSV file must be the CSV (Comma Delimited) type, not the CSV UTF-8 type.
• If you get an error/rejection for an unknown record type identifier, review the file. If it shows lines of commas, the defined print area is too large. Resize it to fit the data. Click and drag in Excel to select the area you want to include. From the Page Layout menu tab, select Print Area, Set Print Area.
• Format the amounts as numbers without commas.