Payment entry transactions

Single code identifying the payment transaction.

Common description for the transaction.

This access code is used to restrict access to data by a user or group of users.

Only users with this access code in their profile can use this transaction.

If several transactions are available, you can choose the transaction you want to use to open the function. If only one transaction is available, the default entry screen opens.

Select the payment sign.

If you select Expense or Revenue, this field does not display in the payment header screen in the payment entry. The payment transaction is always an expense, issued check for example, or always a receipt, check receipt for example.

If you select Unspecified, you make the selection in the payment header as Expense or Revenue. This makes it possible to create only one payment transaction used for both receipt and expenses as in a cash entry for example.

Requiring payment authorization only applies to expenses or unspecified types, and when the Remittances and Bank file checkboxes are selected. Use the PAYAPP - Payment authorization parameter (TRS chapter, AUZ group) to grant users the ability to approve payments.

Select Bank for a bank register and Cash for a cash register.

You can then select the appropriate Sign: Revenue or Expense.

Defines the payment attribute submitted by default upon entry of a payment for this transaction.
This payment attribute is usually set up with Payment sense for the accounting sense.

The Interbanking code is used by all banks to indicate the bank operation type on the lines of the bank statements that are sent to their customers.

This code refers to the miscellaneous table 306.
The accounting journals also have an interbank code. It is used to facilitate sorting and selecting and to control the bank reconciliation between the postings in a bank account with the lines in the bank statements.

This code can be transmitted to the posting documents via the automatic payment journals.

Enter the exchange rate type to be used to perform the currency conversions which are being entered or whose payments are being posted.

Select this checkbox to apply the invoice rate on a payment line if:

• The invoice currency is equal to the payment currency.
• The bank currency is equal to the company currency or to the invoice currency, which is equal to the payment currency.
  

If these conditions are met, it implies that the exchange rate applied to convert the invoice or open item from its currency to the company currency (or main general ledger currency) is the same as the rate found in the journal entry of the invoice.

This converted amount is then stored in the related payment line when the payment is created or saved. It is used during the first payment posting step and it results in no exchange rate variance journal reported in the company currency (the main general ledger currency) for the related invoice.

This amount is also applied to the line on other ledgers of the company when these ledgers are held in the same currency as the main general ledger, thanks to automatic journal entry setup.

When one of these conditions is not met:

• The rate used to convert the invoice from its transaction currency to the main general ledger currency is the exchange rate on the posting date. An exchange rate variance journal entry for the main general ledger is likely to be generated.
• The rate used to convert the invoice from its transaction currency to the other ledgers’ currency (when different from the main general ledger currency) is the exchange rate on the posting date. An exchange rate variance journal entry for these other ledgers could be generated.

When posting a payment with several invoices where invoice rate application has been applied, it implies that several rates can co-exist within the same journal entry. In this case, the accounting journal entry displays a blank exchange rate and suggests an exchange rate as an inlay on the screen.

If you select this checkbox:

• The grouping code is forced to payment or due date according to the posting stages.
• The automatic propositions generated are grouped by due date item, with an open item per payment or a due date by payment.
• The accounting date retained for the bank posting entry of the payment is equal to the payment due date when this is entered upon receipt. When using a remittance advice note, you can confirm the choice made at cash receipt. Or you can modify this so that it is a receipt with a discount and you can enter the accounting date.

This field only displays when the KSP - Spanish localization activity code is activated.
It means that all payments made by this transaction must be considered as cash payments.

This field requires the KSW – Swiss localization activity code to be active.

Use this field to select the generated file type:

• Normal: No specific file type. Use this setting if no payment file is created.
• EZAG: Payment files are created in the EZAG format (specific format of the Swiss Postfinance).
• DAT: Payment files are created in the DTA format (specific format of the Swiss banks/Swiss interbank clearing SIC).
• ISO: Payment files are created in the ISO 20022 format.

This grid is used to specify the payment modes that will be considered for the Automatic payment proposal.

Only the open items with a payment method linked to one in the grid are likely to be paid automatically.

No help linked to this field.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This field is displayed automatically on the payment entry. It corresponds to the company which is linked to the site specified in the payment header.

It is possible to enter an internal reference for the payment document.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

The user can enter a description for information. This description will be taken by default in the line texts at the payment entry (if the line text field has been selected).

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This field is linked to Miscellaneous Table 3.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

Select this checkbox if the Bank ID number field is to be displayed in the payment entry transaction.

The Bank ID number usually defaults from the payment address code. If the payment entry transaction is for a direct debit, the Bank ID number is obtained by default from the mandate entered in the header payment (see the How to manage SEPA mandates in AR processes in Sage X3 document in the 'How to', 'Financials' area of the Sage X3 Online help center).

This checkbox is used to make the corresponding field mandatory on payment entry.

Field to specify the bank name. The paying bank is initialized from the payment address code.
If the VII (international bank transfer) activity code is active, activating these fields is also used to make accessible other paying bank references for the intermediate banks.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory on payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory on payment entry.

Select this checkbox to directly enter a currency rate at payment entry. This action overrides the default payment currency in the Currency rates table.

This checkbox is disabled if the Invoice rate application checkbox on the General tab is selected.

If you select this checkbox, the Invoice rate application field on the General tab is disabled.

Select this checkbox to make entering a currency rate at the payment entry mandatory.

Defines the presence of the bank amount field. This field features the payment amount expressed in the bank account currency.
If this field is not present, the amount will be calculated automatically.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

Specifies the number of columns that will be frozen on the left
when scrolling the posting entry grid.

Conditions the management of the entry lots (Entry lot tab and header fields) in the payment entry.

This field displays if the PROBALCTL - Progressive balance control (TRS chapter, PAY group) parameter is set to Yes It is enabled if the Entry batch checkbox is selected.
It is used to define the balance control for the entry batch. Additional fields on the Entry batch tab are added for the balance control of the batch.

Activating balance control requires the following settings.

On the General tab:

• Bank or Cash: Select Bank.
• Sign: Select Unspecified.

On the Entry tab:

• Select Bank and the associated Mandatory checkbox.

On the Steps tab, Bank posting block:

• Select Posting. No other steps should be selected.
  

This field is available if Bank or Cash is selected for the Bank or Cash field on the General tab for a Polish or South African legislation.

For Bank: Select N/A or Bank register. If you select N/A, the payment can only be created through Payment/Receipt entry (GESPAY). To create payment from the Bank register (GESBCREG), select Bank register.

For Cash: Select N/A or Cash register. If you select N/A, the payment can only be created through Payment/Receipt entry (GESPAY). To create payment from the Cash register (GESBCREG), select Cash register.

This grid is comprised of optional fields that may have been added upon installation. It is used to activate or de-activate these fields in the payment entry screen.

This checkbox is used to make the corresponding field mandatory upon payment entry.

This checkbox is used to make the corresponding field mandatory upon payment entry.

Specifies if the payment mode must be considered by the automatic payment proposal function.

Enter the report code to identify which payment types to include. This code is used for printing reports relating to checks, drafts, and remittances.

For bank or cash register entry types, use the following codes:

PLKP for cash in

PLKW for cash out

Specifies if the print associated with the code above is a compulsory step before payment or note validation.

Specifies if an automatic bank assignment phase is possible for this type of payment. If this phase is not retained, the bank must be entered manually for each payment.

Specifies whether an approval stage is necessary before the first payment validation. This approval consists manually assigning a flag specifying that the validation is possible.

Select this checkbox if authorization is required for payments.

Specify if the remittance must be subjected to an intermediate posting before being posted to the bank (for example, for posting notes payable/receivable on collection or discount).

Specify if notes payable/receivable posting phase is required for this payment transaction. The notes payable/receivable posting consists individually validating payments on an account different from the bank account.

Use this field to indicate if the payment type is linked to a Notes P/R field on the BP record.

The Notes P/R fields (1, 2, etc.) correspond to a group or portfolio of customer notes payable/receivable that are not due.

These notes can then be subject to a risk closing phase in a dedicated function.

Select this checkbox if payments need to be regrouped onto deposit notes before bank posting.

When payment authorization is required, this checkbox must be selected.

Specify if payments must be grouped as paying bank notes before bank posting (issued notes payable/receivable).

Select this checkbox if an electronic transmission of the deposit slip is possible with the bank (transfers, LOC, etc.).

For paying banks, select this checkbox to trace imported and exported files in payments and paying bank notes monitoring.

When payment authorization is required, this checkbox must be selected.

For France it is the ETEBAC file. Specify the name of the file to be generated, if the transaction only generates this type of file. Otherwise leave the field blank for the file to be selected at the electronic deposit stage.

This checkbox -when selected- is used to generate bank files with the SEPA format for the current payment entry transaction.
Generating such a file is only possible if the option is activated.

This field is used to select the pivot text file sent from Sage X3 to Sage Connect for conversion into XML.

The nature of the payment identifies the bank file formats that can be generated by the payment transaction. According to the bank establishment or the national/international character of the payment, the file format is different. The nature of the payment is used to associate a payment transaction with a group of possible bank files.

This field is required if the transaction generates a bank file.

Select this checkbox to split bank files from one remittance group by payment method.

File splitting depends on the bank file format and must be evaluated for each type.

This option is not available when EDI files are created.

Select this checkbox to split bank files from one remittance group by currency.

File splitting depends on the bank file format and must be evaluated for each type. For example, splitting by currency can be applied if a specific format supports multi-currency in general but requires separate files per currency.

Select this checkbox to split bank files from one remittance group by due date.

File splitting depends on the bank file format and must be evaluated for each type.

Used to mention the generating fact for taking into account the payments of a transaction in the payment export file, towards the cash management software (see documentation Payment export to Sage cash management).
The possible values are (local menu 2673):

• None: The payments posted to the transaction are not considered in the export.
• Draft management posting/Intermediate posting/Bank posting: Payments are considered for the export whenever the posting phase that has been completed corresponds to the generating fact.
  In case of accounting cancellation, the cancellation is also transmitted from the moment that it took place after the generating fact.

This field points to the miscellaneous table 325 and it represents a grouping/splitting criterion for the payments upon generation of the payment export file(s).
For example, from the moment two transactions have the same grouping file code, the payments taken into consideration by the export will be regrouped in a same file whose code will contain the grouping code as the first component of its name.

Code of the field of the payment export file whose content can be set up.
This code corresponds to identifying the field in the cash management software:

• local menu 2671, for the interface to the Sage Concept Cash Management software
• local menu 2674, for the interface to the Sage 1000 Cash Management software
• local menu 2686, for the interface to the Sage FRP Treasury software

This formula can be entered with the help of the formula assistant.

By default, various accessible tables are proposed: 

• Payment tables (PAYMENTH, PAYMENTD)
• The payment transaction table (TABPAYTYP)
• The payment slip table (PAYFRM)
• Annex tables (TABCUR, BANK, BPARTNER)

And the main screens:

• The journal entry screens (GACCENT0, GACCENT1, GACCENT2)
• The analytical distribution screens (VENTILE and VENTILE2)