Force post transactions to ledger
If you use the Force Listing Of Batches option, you must print batch listings for each batch you want to post. You must also print a new listing for each batch you edit. Once the check data has been posted to Bank Services when you leave the Print Checks screenthe program proceeds to the payment-posting stage. Payment posting applies all payment information to vendor accounts, and creates a Payment Posting Journal and a Check Register, which are the audit trail reports of the checks that were produced to pay vendors.
If errors are found in a batch during posting, the incorrect transactions are force post transactions to ledger posted. Instead, they are placed in a new batch that uses the next available batch number. The details of the incorrect transactions are printed in an error report which you print separately from the posting journal. If checks were printed for any of the incorrect entries, the word "Printed" appears with the transaction on force post transactions to ledger error report. Accounts Payable assigns a posting sequence number to each transaction during posting.
The same sequence number is assigned to all transactions that are posted together. Posting sequence numbers provide another force post transactions to ledger to trace posted transactions back to source documents. Accounts Payable uses a separate numbering sequence for each type of batch invoice, payment, force post transactions to ledger adjustment.
When you post a batch, its contents are transferred to the vendor accounts and you can no longer edit the transactions. You must enter adjustments or apply debit or credit notes to change any transactions you have already posted. When you import and post a batch, the original file you imported still exists in the program where you created it. Imported batches are deleted automatically only from Accounts Payable. You should also delete the batch file from the program where you created it, to avoid accidentally importing the batch twice.
CSV, which can be imported by a remote site Sage General Ledger, or transferred to another general ledger that you use. All general ledger transactions are placed in the same CSV file. Each time Accounts Payable creates transactions it will ask you whether you want to add to the file, or replace it.
If you overwrite the file, you force post transactions to ledger destroy all transactions that are already in the file. When you are ready to transfer the batch to your general ledger, copy the file to the computer or directory where your general ledger is located, and delete the original CSV file. Then make a backup copy of the CSV file.