Payment Types

• Payment transaction (field PAYTYP)

Single code identifying the payment transaction.

• Legislation (field LEG)

• Description (field DESTRA)

Standard title of the current record.

• Short description (field SHOTRA)

• Group (field GFY)

• Active (field ENAFLG)

• Access code (field ACS)

Access code that is used to restrict access to data by user or group of users.
If this field is assigned, only users with this access code in their profile can use this transaction.
If several transactions are set up for a function, and the user only has access to one of them because of the access codes, the selection window is no longer suggested: the access is by direct entry. 

• Sign (field SNS)

Specifies the payment sense.

If the payment sense is defined as Expense or Receipt, the "Sense" field is not visible in the payment header screen (in payment entry). In this case, the user knows that the payment transaction is always an expense (issued cheque for example) or always a receipt (cheque receipt for example).

If the sign is not determined, the "Sign" field is entered in the payment header as Receipt or Expense. This makes it possible to create only one payment transaction used for both receipt and expenses (Cash entry for example).

• Bank or cash (field BANCSH)

This field determines whether the treasury account linked to this payment transaction is a cash management account or a bank account.

If the payment management is associated with a petty cash:

• in the payment header screen, a petty cash (and not a bank) must necessarily be entered
• only the posting stage "deposit to bank" (understood as "cash") is available.

• Default payment attribute (field DENDEF)

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.

• Interbank code (field CIB)

The Inter-banking code is a coding used by all banks to indicate the bank operation type on the lines of the bank statements that are sent to their customers.
In X3, this code refers to miscellaneous table 306.
The accounting journals also have an inter-bank code. It is use to facilitate (sort, selection) and to control the bank reconciliation (RAPBAN function) between the postings in a bank account with the lines in the bank statements.
The code entered here can be transmitted to the posting documents for the payments via the automatic payment journals.

• Rate type (field RATTYP)

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

• Invoice rate application (field RATINV)

If this check box is selected for an invoice in a currency different from the company currency, the exchange rate applied between the open item currency for the closing of the BP account (closed during the first posting step) is the same as the rate on the invoice. There is no exchange rate variance journal reported in the company currency. 

If this check box is not selected, the exchange rate applied between the open item currency and the company currency for the closing of the BP account is the exchange rate on the posting date. For an exchange rate variance, an exchange rate variance journal in company currency is generated. 

Note: This check box is also relevant for the reporting currency for which an exchange rate variance journal in the reporting currency can be generated, or not, depending on whether it is selected or not.

This exchange rate is applicable to the Bank or BP payment type attributes and uniquely for the cases where one (or more) invoice is posted. For other payment attributes or non-posted Bank or BP payment attributes, the retained exchange rate is fixed with respect to the exchange rate type previously specified.

At the same time as the application of this original invoice exchange rate, several rates can co-exist. In this case, the accounting journal displays a blank exchange rate and suggests an exchange rate as an inlay on the screen.

• Due date management (field DUDFLG)

If this flag is checked:

• 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 (a 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, it is possible to confirm the choice made at cash receipt or otherwise to modify this in order that it is a receipt with discount ; in this latter case, the accounting date can be entered.

• Endorsement (field FLGEND)

• Cash payment (field SPACSH)

This flag is displayed only when the KSP activity code is activated.
It indicates that all payments made by this transaction have to be considered as Cash Payment.

• Swiss payment type (field SWIPAYTYP)

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 will be 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.

Refer to the Swiss legislation guide on the How to tab for more details regarding payment and ISR setup.

• Business partner (field BPRTYP)

• Cash VAT (field CSHVATRGM)

• No. (field NUMLIG)

• Payment method (field PAM)

This grid is used to specify the payment modes that will be considered for the automatic payment proposal (refer to documentation on the Automatic payment proposal).
In effect, only the open items with a payment mode corresponding to one of those that have been entered will be likely to be paid automatically.

• Bank (field DACBAN)

No help linked to this field.

• Mandatory (field BANOBL)

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

• Company (field DACCPY)

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

• Reference (field DACREF)

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

• Mandatory (field REFOBL)

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

• Remittance reference (field DACFRMREF)

• Mandatory (field FRMREFOBL)

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

• Discount type (field DACFRMTYP)

• Header description (field DACDES)

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

• Mandatory (field DESOBL)

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

• Line description (field DACDESLIN)

• Mandatory (field DESLINOBL)

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

• Payment method (field DACPAM)

This field is linked to Miscellaneous Table 3.

• Source date (field DACORIDAT)

• Mandatory (field ORIDATOBL)

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

• Due date (field DACDUDDAT)

• Mandatory (field DUDDATOBL)

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

• Value date (field DACVALDAT)

• Mandatory (field VALDATOBL)

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

• Date created (field DACBILDAT)

• Mandatory (field BILDATOBL)

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

• Bank account number (field DACBID)

Click this check box if the Bank ID number field is to be displayed in the payment entry transaction.

 This field is mandatory if this payment type is used with electronic payments. You must click both this check box and the associated Mandatory check box. Electronic transmission payments have either the check box Bank file or SEPA generation in the Steps tab selected.

The Bank ID number is typically initialized from the payment address code. If the payment entry transaction is for a direct debit however, 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).

• Mandatory (field BIDOBL)

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

• Paying bank 1 (field DACPAB1)

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.

• Mandatory (field PAB1OBL)

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

• Paying bank 2 (field DACPAB2)

• Mandatory (field PAB2OBL)

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

• Drawee reference (field DACBPRREF)

• Mandatory (field BPRREFOBL)

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

• Check type (field DACCHQTYP)

• Check number (field DACCHQNUM)

• Mandatory (field CHQNUMOBL)

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

• Pay-by branch (field DACCHQBAN)

• Mandatory (field CHQBANOBL)

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

• Bank card number (field DACCRDNUM)

• Mandatory (field CRDNUMOBL)

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

• Credit card authorized (field DACCRDAUZ)

• Mandatory (field CRDAUZOBL)

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

• Purchase type (field DACPURTYP)

• Bank amount (field DACAMTBAN)

Defines or not 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.

• Mandatory (field AMTBANOBL)

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

• Bank date (field DACBANDAT)

• Mandatory (field BANDATOBL)

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

• Number of fixed columns (field NBRCOL)

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

• Entry batch (field DACPYL)

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

• Balance control (field LOTPROBALC)

If parameter PROBALCTL - Progressive balance control (chapter TRS - group PAY) is set to ‘Yes’, the balance control field is displayed. It is enabled if box "Entry batch" is activated.
It is used to define the balance control for the Entry batch. Additional fields in tab "Entry batch” tab are added for the balance control of the batch.
The activation of the balance control has an impact on:

• "Bank or Cash": Bank must be activated in tab "General".
• "Sign" must be "Unspecified" in tab "General".
• Field "Bank" must be "Mandatory" in tab "Input".
• Step "Bank Posting" must be activated. No other steps should be selected in tab "Steps".
  

• No. (field NUMLIG)

• Input (field DACSUP)

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

• Description (field LIBSUP)

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

• Mandatory (field SUPOBL)

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

• Auto proposal (field PAYPPS)

Specifies if the payment mode must be taken into account by the
automatic payment proposal function
.

• Payment report code (field CODEDT)

This code enables the reports to identify which payment types
must be taken into account. This code is used for the printing reports relating to
checks, drafts and deposit slips.

• Mandatory printing (field EDTFLG)

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

• Bank allocation (field STA4)

Specifies if an automatic bank assignment phase is
possible for this type of payment. In the event of this phase not being retained,
the bank will have to be entered manually for each payment.

• Acceptance return (field STA2)

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

• Posting (field STA8)

Specify if the deposit slip must be subjected to an intermediate posting before being posted to the bank (for instance, used for drafts received upon deposit for cash receipt or discount).

• Group entry (field AUTACE8)

• Cash journal type (field JOU8)

• Discount journal type (field JOU82)

• Posting (field STA3)

Specify if a draft management phase is necessary for this payment transaction. Draft management consists in individually validating payments on an account different from the bank account.

• Portfolio update (field UPDBIL)

Specifies if a "Draft management" field on the BP record must show movements
for this payment type. Draft management allows for instance customer drafts that are not due
to be totalled. Draft management will be devalued using a
specific
function.

• Group entry (field AUTACE3)

• Journal type (field JOU3)

• Posting (field STA9)

• Group entry (field AUTACE9)

• Payment grouping (field ACETYP91)

• Discount grouping (field ACETYP92)

• Journal type (field JOU9)

• Remittances (field STA5)

Specifies if payments need to be regrouped onto deposit notes before bank posting.

• Paying banks (field STA7)

Specifies if payments must be regrouped as paying bank notes before bank posting (case of the issued drafts).

• Bank file (field STA6)

Specifies if an electronic transmission of the deposit slip is possible wiith the bank (transfers, LOC, etc.).

For paying banks, used to trace imported and exported files in payment and paying bank note monitoring.

• Electronic medium (field FILREF6)

For France is it 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.

• EDI (field FILREF71)

• SEPA generation (field EPACDTTRF)

This box -when checked- 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.
 The SEPA term means SEPA Credit Transfer only.
 This checkbox can be accessed if the box ‘Bank file’ has not been activated.

• SEPA file (field FILREF8)

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

• Bank file group (field NATPAY)

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, a group of possible of bank files.

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

• Group entry (field AUTACE10)

• Journal type (field JOU10)

• Triggering event (field FLGCAS)

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 in no way taken into account in the export.
• Draft management posting/Intermediate posting/Bank posting: payments are taken into account 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.

• File grouping code (field FICCAS)

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 instance, from the moment that 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.

• Zone code (field CODCAS)

Code of the field of the payment export file whose content can be set up.
This code corresponds to that 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 code MUST be entered in uppercase letters.

• Formulas (field CLCFOR)

The parameterization formula can be entered with the help of the formula assistant.

By default, the various accessible tables are proposed: 

• payment tables (PAYMENTH, PAYMENTD),
• the payment transaction table (TABPAYTYP),
• the payment slip table (PAYFRM),
• annex tables (TABCUR, BANK, BPARTNER)

As well as the main screens:

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