Use the Sage 50 payroll transactions function to enquire on and amend financial transactions created from XML files imported from Sage 50 Payroll.

You should use it to check all header and detail line values before you post the journal, especially the Site and Account Codes that have been transcribed from Sage 50 Payroll values.

When you have reviewed the transaction you can:
  • Post it as an automatic journal 
  • Delete it, correct the transcription tables and import it again.

Splitting large files

Sage X3 can only accept transactions with a maximum of 9,999 lines. If the Sage 50 XML X3 Import Conversion Tool processes a file with more than 5,000 lines it will split the output into two, or more, XML files to be transcribed into separate Sage X3 transactions. The files produced will have a '-n' suffix so, for example a Sage 50 Payroll file with 3,000 lines would result in a single file with a file identifier such as 20140701151617, whereas a Sage 50 Payroll file with 9,000 lines would result in two files with identifiers such as 20140701151617-1 and 20140701151617-2.

Because these import transactions have been created from the same Sage 50 Payroll file, you should post all the journals, created from related transaction files, at the same time.

 5,000 is the default number of lines, it can be configured in the Sage 50 XML X3 Import Conversion Tool, please refer to the accompanying PDFs for guidance and instructions.

Prerequisites

See also Refer to documentation Implementation

Screen management

There are two selection lists in the list panel; one includes only unposted transactions and the other includes all imported payroll transactions.

Header

The header displays details of the imported file and the transaction created from it, the fields are read-only and cannot be amended.

Tab Summary

The summary tab displays details of the imported file and the transaction created from it. All fields with values from Sage 50 Payroll are read-only.

Tab Detail

The detail tab displays all the detail lines from the imported file. Values contained in the imported file cannot be amended, but those created during the import can be corrected if required.

Reports

By default, the following reports are associated with this function :

Bullet point  S-MURANA : Spanish payroll analysis

This can be changed using a different setup.

Specific buttons

Post

The Post action is only available if:

  • The Debit and Credit totals agree;
  • The journal has not already been posted;
  • You have saved any changes made.


When you have reviewed the details of the imported transaction and made any necessary changes click Post; a popup window will be displayed asking you to confirm your intention, click Yes to continue.

Delete

Use the Delete action to remove the transaction without posting it. This will, for example, let you add or correct transcription values using the Sage 50 import transcribe function and then import the XML file again.

Validation

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

A problem was encountered, record not deleted
If the Supervisor encounters a problem, such as a locked record or corrupt data, when deleting a transaction the deletion is abandoned and nothing is deleted. You will have to investigate and correct the cause before trying to delete the transaction again.

Journal posting not permitted, transaction does not balance
The most likely cause of a transaction with debits and credits that don't balance is a split imported XML file with no offset account. If the Sage 50 XML X3 Import Conversion Tool has split a file and the Site used does not have an offset account you will need to:
  • delete all the transactions created by the import;
  • use the Sage 50 import transcribe function to add an offset account to the Site's configuration;
  • import the XML file again.

Tables used

See also Refer to documentation Implementation