SAGE LINE 100/1000 STD Format (PNM Format)

Introduction

This format corresponds to the format that can be imported via the "SAGE Format" import menu.
This article describes the configuration elements necessary to set up an export of accounting entries for expense reports in SAGE PNM extension format.

The generated file is intended to be imported into the Sage accounting software line 100 or 1000.

 

 

Name of the connector to activate

Sage line 100/1000

 

 

Format description from SAGE

 

  • File position
  • No header lines
  • Date format: DDMMYY
  • Numeric format: 2 decimal places, period separator, right-aligned.

 

 

 

Questions to ask yourself during implementation:

  1. What is the journal code?
  2. Do we need to generate the lines for analytical accounting? If so, what analytical information needs to be retrieved?
  3. Should the central account (collective account) be exported in addition to the third-party account?
  4. Should a company code be displayed in the file header? Generally necessary in the case of multi-company accounting.

 

 

1 - What is the journal code?
 

 

This is usually the NDF or ACH code

 

In the toolbox (access restricted to Eurécia), select the log code retrieval source:

  • Free text field: direct entry into the toolbox. Disadvantage: the client will not have the ability to update it if necessary.
  • Code of the department or structure filtered during the export of expenses (only 1 journal code for the same exported file)
  • Company record journal code: "SETTINGS" tab of the company record. Advantage: The client has the ability to update it if needed.

 

2 - Do we need to generate the lines for analytical accounting?

 

If so, you must check the "Analytical accounting management" box.

What analytical information needs to be retrieved?

  • This is generally one of the following pieces of information:
    • Employee record field "Analytical Code": key {CAU}
    • Employee record field "Analytical Code 2": key {CAU2}
    • Account code of the analytical axis assigned to the expense: key {CAAX} The X is to be replaced by the number of the analytical axis.
    • Account grouping code for the analytical axis assigned to the expense: key {CRAX} The X is to be replaced by the number of the analytical axis.

The analytical information designated by the key between {} generally populates field 6 of the analytical line. (Use this by default as it usually meets the need)

The analytical information designated by the key between {} less frequently feeds into field 20 of the analytical line.

If it is necessary to populate the analytical plan, the information must be entered in the "Associated analytical plan" field below:

 

 

 

It is rarely necessary to generate more than one analytical line per charge line.

In this case, the following analytical configurations will need to be populated (up to a maximum of 7 analytical lines). 



 

 

 

3 - Should the central account (collective account) be exported in addition to the third-party account?

 

If so, you must enable the setting below to ensure that the central account and the third-party account are correctly positioned in the exported file:



The data will be positioned in the file as follows:

 

Third-party accounts and centralizing accounts are located in the "Employment" tab of the employee record:



If we do not wish to export the central account but only the third-party account, the data will be positioned as follows and there will be nothing after the character "X":

 

 

 

4 - Should a company code be displayed in the file header?

 

This is generally necessary in the case of multi-company accounting.

 

It is possible to retrieve the information from one of these 3 sources.

  • "Company" points to the code field below, located in the "Settings" tab of the company record:

 

  • "Department" retrieves the department code filtered during export (only 1 log code for the same exported file)
  • "Code Structure" retrieves the code of the filtered structure during export (only 1 log code for the same exported file)

 

Note: If this file header is absent or present in an unwanted way, SAGE generates the following error message:

 

Additional points:

 

1 - Writing label:

 

We can set the following default keys {DESCR} {NOM} {PRENOM} in the fields below in the toolbox: 

 

 

This will export the description of the expense report followed by the employee's first and last name, and this generally meets the need except in special cases.

If this wording is not suitable, it will be possible to modify it using the keys available in this link:

https://help.eurecia.com/hc/fr/articles/360000030217-Configurer-le-libell%C3%A9-et-la-description-dans-l-export-personnalis%C3%A9-des-notes-de-frais

 

 

2 - Part type:

 

In the "Part Type" field, enter "OD" by default:

 

3 - Decimal separator :

 

Use a period as the decimal separator

 


 

 

 

 

4 - VAT Profile:

 

In SAGE 1000, it is sometimes necessary to display the VAT profile associated with the expense account in position 200 of the file. In this case, the file length will be 250 characters instead of 200 characters.

The following toolbox setting enables it:

 

The "Additional code" field from the VAT configuration in the expense type will be retrieved:

 

 

 

5 - Part No. Prefix:

Allows you to specify a prefix before the expense report number that appears in field 7 (entry reference) in position 39.

 

Was this article helpful?

0 out of 0 found this helpful

Comments

Article is closed for comments.