EFT information

You cannot override the parameters per company.

Access and processing

ASP

You can move data paths higher up in the folder hierarchy than is defined in the EFT system data path field.

Use user access table only

Used by some EFT systems to find out to which companies they have access to create payments.

Transfer automatic deduction when paying

Checks for automatic deduction (Agreement giro/Autogiro) when payments is done. Used by some EFT systems.

Override file, no backup

The files that are produced for the bank will be overridden each time and it is not possible to save a backup file. Used by some EFT systems.

Display and reports

Show single transaction grid

You get a simplified version of the transaction summary when paying and importing. Only the sum per account and currency is shown, and not single transactions. If you have large volumes of data the routine goes faster if you select this field.

Split reports, one account per page

Detailed reports with page break for each new account appear.

Formats

Show imports with no files

The banks without available files will shown in grey. If you have not selected this field, only the banks with available files will be shown. If you have a lot of imports it is easier not to select this field.

Select all accessible imports as standard

All available imports (imports with available files) will be chosen initially. The default is "No". The user must then actively select which imports he/she wants to select.

Select all exported transactions as standard

All transactions in an export/payment transfer will appear as selected. This applies to preview of transactions in some external EFT systems.

Select all imported transactions as standard

All transactions in an import/payment transfer will appear as selected. This applies to preview of transactions in some external EFT systems.

The selections in this dialog box affect Business NXT and Visma Payment (BabelBank)/Visma.net AutoPay/other external EFT systems. The selections in this dialog box apply to all companies in the system database.

Payment suggestion

Estimated transfer date is payment date for all transactions

All transactions, regardless of the payment date, will be assigned the same payment date that you used in the Create payment suggestion processing.

Set extra text on payment post

You will be able to transfer text (40 characters) on an open post in the Additional text field. This has been implemented for the 96 - Liinos and 99 - Z Data Converter bank systems. Only Telepay (NO), Postal giro and Bankgiro (SE) can use this function.

No debit balance

Some EFT systems will test whether the payments per supplier exceed the total amount owed, and rejects this supplier and transactions that will create a debit balance for the supplier will not be paid.

Net credit notes towards invoices

Posting

Generate batch/vouchers for settlement from EFT system

Automatically create batch/vouchers when receiving settled payments from the EFT system. Recommendation is to have this setting selected. If not selected the Create account batch processing in the Payment line table can be ran manually at a later stage.

Automatically update batch for outgoing payments from Visma.net AutoPay

After return data for payments are received from Visma.net AutoPay, the Update batch processing will start automatically.

Update all settled payments in a single batch

When selected, one common batch with voucher lines is created for the settlements of outgoing payments received in the same status change report from Visma.net AutoPay. If this option is not selected, separate batches will be created for each <OriginalPaymentBatch> section in the status change report.

Incoming payments

Automatically update batch for incoming payments from Visma.net AutoPay

After incoming payments are received from Visma.net AutoPay, the Update batch processing will start automatically.

Use value date on Visma.net AutoPay incoming payments

When selected, the bank's "Value date" is used for the Value date field in the Voucher table, instead of the bank's "Booking date". With this the user can configure what suites best for optimizing their bank reconciliation.

Create voucher lines if charges from incoming payments from Visma.net AutoPay

When selected, charges will be posted when importing incoming payments from Visma.net AutoPay. Charges will be posted if they are specified in the <ChargesDeducted> tag in the import file. Alternatively, charges will posted if the value in the <PaidCurrencyAmount> is higher than amount in the <ReceivedAmount> tag (meaning the customer has paid more than we have received), the difference will be considered as charges (currency must be identical for both amounts).

Create bank posting for each incoming payment from Visma.net AutoPay

When selected, a separate bank voucher will be created for each incoming payment when importing from Visma.net AutoPay.

Ignore the group value when creating bank posting for incoming payments from Visma.net AutoPay

In the XML file for incoming payments from Visma.net AutoPay (VIP file) there is a tag named <Group>. Import of the incoming payments creates bank vouchers, with grouping based on payment date and <Group> values. When this setting is selected, the <Group> tag is not taken into account when creating bank vouchers.

Do not match CID payment when paid amount is larger than outstanding amount

Relevant for incoming payments which has a CID code, and where the paid amount is larger than open entry's outstanding amount (e.g. when the payer has used same CID code for payment of multiple invoices).

When this setting is selected, the Cross reference and Credit account fields will not be filled out on the voucher. The batch will then have a difference, making it easier for the user to see that something needs manual handling (e.g. matching of open entries).

Check for double payment by CID in customer transactions

When incoming payments are imported, but no match is found in the Open customer entry table, an activation of this parameter will result in an additional search for the CID code in the Customer transaction table. If the CID code is found; the customer no. is added to the voucher line and the batch will balance. In addition the text "Warning - double payment?" will be added to the Additional text field.

Do not check reminders in Customer document when matching payments

When selected, the content in Customer document tables will not be used for matching of incoming payments from Visma.net AutoPay.

Sweden

Accept negative payments

Negative amounts will also be processed. This check box is also present under Accounting processing field in the Company information table. By using this selection in the Bank partner table, you can set different processing for each bank partner.

Note:

For negative payments you are meant to transfer larger amounts of credit notes than invoices. This is selected when it is permitted to send this to the bank for monitoring, so that with the next invoice the bank reduces the payment amount with the remaining credit note value. This is only used when paying to Swedish banks.

Always use Post giro if exists

Post account is used in EFT processing. This applies for Sweden and is only used by some external EFT systems.

Numeric cost codes

The cost codes "OUR" and "BEN" will be replaced by numerical values that are used in Sweden.

Allow uploading payments with 0-amounts

When selected, the Create payment suggestion processing will create payment lines also for suppliers where the sum of the transactions is zero (e.g. one invoice with amount 2000 and one credit note with amount 2000). Check that your bank accept zero-payments, this is accepted by several banks in Sweden.

Denmark

Joint Transactions

Some EFT systems produces a joint transaction for the bank. If you use this parameter you cannot retrieve return data to match the payments. This field is only used in some external EFT systems.

Short message to receiver

The recipient receives a short message. This field is only used by some EFT systems.

Bank reconciliation

Update general ledger transactions with reconciliation amount

When selected, new transaction in the General ledger transaction table with Account no. = the bank partner's GL bank account will be assigned values in the Reconciliation rest amount fields. This makes it possible to later reconcile the transactions against the Account statement transaction table.

Match transactions even if amounts are different

Enables the possibility to match transactions with different amounts when running the Manual reconciliation processing.

Reconciling single transactions before multiple transactions

When selected, the 4 - Single transactions on same date reconciliation algorithm will be executed before the 2 - Multiple general ledger transactions on same date and 3 - Multiple account statement transactions on same date algorithms.

Reconcile using value date

Bank reconciliation based on principle Value date instead of Voucher date. When enabling Reconcile using value date, the algorithms will look into the value date instead of voucher date when executing the processes. Also, when running the bank reconciliation statement report, the value in the field Balance according to general ledger is calculated based on the value date for the transactions.

AutoInvoice

Do not send CID to AutoInvoice

When selected, no CID will be sent to AutoInvoice.

Miscellaneous

Use database connection for ZData

This field is not in use in this table.

Payments for active company only

You cannot export data from other clients than the client from whom the export was started.

Process active settling only for payments

You can only process the selected payment line for the company where Upload data or Download data was started from.

Update bank account/organisation no. from EFT system

You get updated bank account and organisation numbers of customers who are paying by OCR. Not all formats support this. It depends on the information in the file that comes from the bank.

Get currency exchange rate when creating payments

You will be able to get exchange rates from the bank, and update the Currency and Currency rate tables with updated exchange rates from the bank. Not all bank formats are supported at present.

Set to "Cancelled" for payments not transferred

Some EFT systems sets the Paym. line status field in the Payment line table to 4 - Cancelled in the lines that have status 1 - Estimate after you have run the Upload data processing in the Payment table. It is the EFT system that performs the cancellation of the open entries for everything that is rejected before you send data to the bank.

Set "Cancelled" on payments that are refused

Some external EFT systems will set the Paym. line status field in the Payment line table to 4 - Cancelled in the lines that are being cancelled by the control routines in the EFT system, while suggestions that you selected manually so that they will not be transferred remain as Paym. line status equal 1 - Estimate, and will be ready for paying the next time the EFT system is started.

Domestic payments to foreign countries (payment method 43/TBIO)

Foreign transactions will be sent over and processed as domestic transactions in the recipient country. This depends on what is offered by the bank that you use for the payments.

No exchange rate on processed payments

This field is not in use.

Accounting

Duty/Fees included in amount

Fees will be included in the total amount.

Fees per record

Fees and duties will be recorded per supplier and payment.

Do not post duty and fees

Fees and duties will not be posted with the payment. Select this field when you have a separate agreement with the bank that fees and duties are debited separately.

Taxes and fees in foreign currency

Fees and duties are in a currency other than default currency. Then the account currency is used for the fees.

Use bank reference, domestic

The bank reference will be used to gather the posting in the general ledger account for bank postings on domestic payments.

Use bank reference in foreign countries

The bank reference is used to gather posting in the general ledger account for bank postings in foreign payments.

Telepay

Only one invoice per transaction

Some EFT systems will only produces transactions for the bank. If you use this parameter, several payments will not be batched for the same account.

The selections in this dialog box affect Business NXT and Visma Payment (BabelBank)/Visma.net AutoPay/other external EFT systems. The selections in this dialog box apply to all companies in the system database.

Payment suggestion

Estimated transfer date is payment date for all transactions

All transactions, regardless of the payment date, will be assigned the same payment date that you used in the Create payment suggestion processing.

Set extra text on payment post

You will be able to transfer text (40 characters) on an open post in the Additional text field. This has been implemented for the 96 - Liinos and 99 - Z Data Converter bank systems. Only Telepay (NO), Postal giro and Bankgiro (SE) can use this function.

No debit balance

Some EFT systems will test whether the payments per supplier exceed the total amount owed, and rejects this supplier and transactions that will create a debit balance for the supplier will not be paid.

Net credit notes towards invoices

Posting

Generate batch/vouchers for settlement from EFT system

Automatically create batch/vouchers when receiving settled payments from the EFT system. Recommendation is to have this setting selected. If not selected the Create account batch processing in the Payment line table can be ran manually at a later stage.

Automatically update batch for outgoing payments from Visma.net AutoPay

After return data for payments are received from Visma.net AutoPay, the Update batch processing will start automatically.

Update all settled payments in a single batch

When selected, one common batch with voucher lines is created for the settlements of outgoing payments received in the same status change report from Visma.net AutoPay. If this option is not selected, separate batches will be created for each <OriginalPaymentBatch> section in the status change report.

Incoming payments

Automatically update batch for incoming payments from Visma.net AutoPay

After incoming payments are received from Visma.net AutoPay, the Update batch processing will start automatically.

Use value date on Visma.net AutoPay incoming payments

When selected, the bank's "Value date" is used for the Value date field in the Voucher table, instead of the bank's "Booking date". With this the user can configure what suites best for optimizing their bank reconciliation.

Create voucher lines if charges from incoming payments from Visma.net AutoPay

When selected, charges will be posted when importing incoming payments from Visma.net AutoPay. Charges will be posted if they are specified in the <ChargesDeducted> tag in the import file. Alternatively, charges will posted if the value in the <PaidCurrencyAmount> is higher than amount in the <ReceivedAmount> tag (meaning the customer has paid more than we have received), the difference will be considered as charges (currency must be identical for both amounts).

Create bank posting for each incoming payment from Visma.net AutoPay

When selected, a separate bank voucher will be created for each incoming payment when importing from Visma.net AutoPay.

Ignore the group value when creating bank posting for incoming payments from Visma.net AutoPay

In the XML file for incoming payments from Visma.net AutoPay (VIP file) there is a tag named <Group>. Import of the incoming payments creates bank vouchers, with grouping based on payment date and <Group> values. When this setting is selected, the <Group> tag is not taken into account when creating bank vouchers.

Do not match CID payment when paid amount is larger than outstanding amount

Relevant for incoming payments which has a CID code, and where the paid amount is larger than open entry's outstanding amount (e.g. when the payer has used same CID code for payment of multiple invoices).

When this setting is selected, the Cross reference and Credit account fields will not be filled out on the voucher. The batch will then have a difference, making it easier for the user to see that something needs manual handling (e.g. matching of open entries).

Check for double payment by CID in customer transactions

When incoming payments are imported, but no match is found in the Open customer entry table, an activation of this parameter will result in an additional search for the CID code in the Customer transaction table. If the CID code is found; the customer no. is added to the voucher line and the batch will balance. In addition the text "Warning - double payment?" will be added to the Additional text field.

Do not check reminders in Customer document when matching payments

When selected, the content in Customer document tables will not be used for matching of incoming payments from Visma.net AutoPay.

Sweden

Accept negative payments

Negative amounts will also be processed. This check box is also present under Accounting processing field in the Company information table. By using this selection in the Bank partner table, you can set different processing for each bank partner.

Note:

For negative payments you are meant to transfer larger amounts of credit notes than invoices. This is selected when it is permitted to send this to the bank for monitoring, so that with the next invoice the bank reduces the payment amount with the remaining credit note value. This is only used when paying to Swedish banks.

Always use Post giro if exists

Post account is used in EFT processing. This applies for Sweden and is only used by some external EFT systems.

Numeric cost codes

The cost codes "OUR" and "BEN" will be replaced by numerical values that are used in Sweden.

Allow uploading payments with 0-amounts

When selected, the Create payment suggestion processing will create payment lines also for suppliers where the sum of the transactions is zero (e.g. one invoice with amount 2000 and one credit note with amount 2000). Check that your bank accept zero-payments, this is accepted by several banks in Sweden.

Denmark

Joint Transactions

Some EFT systems produces a joint transaction for the bank. If you use this parameter you cannot retrieve return data to match the payments. This field is only used in some external EFT systems.

Short message to receiver

The recipient receives a short message. This field is only used by some EFT systems.

Bank reconciliation

Update general ledger transactions with reconciliation amount

When selected, new transaction in the General ledger transaction table with Account no. = the bank partner's GL bank account will be assigned values in the Reconciliation rest amount fields. This makes it possible to later reconcile the transactions against the Account statement transaction table.

Match transactions even if amounts are different

Enables the possibility to match transactions with different amounts when running the Manual reconciliation processing.

Reconciling single transactions before multiple transactions

When selected, the 4 - Single transactions on same date reconciliation algorithm will be executed before the 2 - Multiple general ledger transactions on same date and 3 - Multiple account statement transactions on same date algorithms.

Reconcile using value date

Bank reconciliation based on principle Value date instead of Voucher date. When enabling Reconcile using value date, the algorithms will look into the value date instead of voucher date when executing the processes. Also, when running the bank reconciliation statement report, the value in the field Balance according to general ledger is calculated based on the value date for the transactions.

AutoInvoice

Do not send CID to AutoInvoice

When selected, no CID will be sent to AutoInvoice.

Miscellaneous

Use database connection for ZData

This field is not in use in this table.

Payments for active company only

You cannot export data from other clients than the client from whom the export was started.

Process active settling only for payments

You can only process the selected payment line for the company where Upload data or Download data was started from.

Update bank account/organisation no. from EFT system

You get updated bank account and organisation numbers of customers who are paying by OCR. Not all formats support this. It depends on the information in the file that comes from the bank.

Get currency exchange rate when creating payments

You will be able to get exchange rates from the bank, and update the Currency and Currency rate tables with updated exchange rates from the bank. Not all bank formats are supported at present.

Set to "Cancelled" for payments not transferred

Some EFT systems sets the Paym. line status field in the Payment line table to 4 - Cancelled in the lines that have status 1 - Estimate after you have run the Upload data processing in the Payment table. It is the EFT system that performs the cancellation of the open entries for everything that is rejected before you send data to the bank.

Set "Cancelled" on payments that are refused

Some external EFT systems will set the Paym. line status field in the Payment line table to 4 - Cancelled in the lines that are being cancelled by the control routines in the EFT system, while suggestions that you selected manually so that they will not be transferred remain as Paym. line status equal 1 - Estimate, and will be ready for paying the next time the EFT system is started.

Domestic payments to foreign countries (payment method 43/TBIO)

Foreign transactions will be sent over and processed as domestic transactions in the recipient country. This depends on what is offered by the bank that you use for the payments.

No exchange rate on processed payments

This field is not in use.

Accounting

Duty/Fees included in amount

Fees will be included in the total amount.

Fees per record

Fees and duties will be recorded per supplier and payment.

Do not post duty and fees

Fees and duties will not be posted with the payment. Select this field when you have a separate agreement with the bank that fees and duties are debited separately.

Taxes and fees in foreign currency

Fees and duties are in a currency other than default currency. Then the account currency is used for the fees.

Use bank reference, domestic

The bank reference will be used to gather the posting in the general ledger account for bank postings on domestic payments.

Use bank reference in foreign countries

The bank reference is used to gather posting in the general ledger account for bank postings in foreign payments.

Telepay

Only one invoice per transaction

Some EFT systems will only produces transactions for the bank. If you use this parameter, several payments will not be batched for the same account.

If you select ASP under Bank-processing in the EFT information table, the user cannot go lower in the folder structure than that which is defined in this field.

The BankX database contains all BankX data. If the Reconciliation database name field has already been filled in when the base was created, the database gets this name.

Installation of Visma Payment (BabelBank) will fill in this field.

You get the following information from the events log in ConvertX:

• Time: This field shows you the date and time.
• Type: This field shows you if it is an import or an export.
• Event history: This field shows you if it is an import, export or validation.
• User: In this field you see the user's name.

In this field you can enter rules for free text-reconciliation. Please refer to the EFT system documentation for the syntax.

Blank/0 in the field gives extended logging "off", and a different numerical value to 0 gives extended logging "on".

CID code generating

No leading zeros in customer/supp. no.

The customer/supplier number parts in the CID codes will not be completed with leading zeros when the number of digits is less than that stated in the CID cust./suppl. chars. field. This is normally used together with the Length digit check box in Swedish payment transfer.

Length digit

A length digit will be included before the check digit which shows the last digit in the total number of characters in the CID code (including the length digit and check digit). (The length digit is also included in the check digit calculation.) This is used in Swedish postal giros, among other things.

Finnish CID calculation

Modulus 10 check digits will be replaced by the algorithm for Solo reference payments. This is used in Finland.

Invoice no. first

The default CID code will be generated with the invoice number first. The order will then be as follows:

Invoice reference + Factoring ID + Customer number + Control digits.

The system will then produce a reversed CID code in connection with invoice printing and on importing OCR files. This enables the CID code to be imported in other accounting systems which expect an OCR with invoice number + customer number or receive OCR produced from accounting systems which have the invoice number before the customer number.

Note:

You must not use this parameter together with No leading zeros in customer/supp. no.

This field is also included in the Factoring company table and is activated when using Def. Factoring companys/CID code def.

Use customer no. as CID

You will only get the customer number and check digit in the CID code when you print invoices, interest notes and reminders.

Use Invoice no. as CID

You will only get the invoice number and check digit in the CID code when you print invoices, interest notes and reminders.

Payment suggestion

Payment if giro no.

Create payments only for transaction where Bank account or Postal giro is specified in Associate table, or Bank account is specified on the Open supplier entry.

Use bank partner from supplier/customer

Used as default value for the corresponding field in the Create payment suggestion processing dialog.

Processing when importing from EFT system

Prepayment

Some external EFT system processes OCR transactions for a specified series of advance payments that do not have open entries, but only advance orders that have not been invoiced. The order will be looked up and the suspension on the advance payment will be lifted when this payment is updated. You will find more about advance payments in the section about Advance payment.

Update bank account

Some EFT systems updates the bank account/postal giro for suppliers/customers if the format contains sufficient information to find suppliers/customers with an advanced search.

Generate batch/vouchers for settlement

The batch is created by the EFT system when the settlement is returned, and you cannot use the Create account batch processing in the Payment line table.

Control EFT system at payment

Control CID when importing

The CID code will be checked during data import.

Control if invoice no. is in the CID field

This field is used when the CID code field does not contain a complete CID code. This is common for payments from Sweden.

Only show CID sum

Only the sum per account is shown on the CID report.

Look up in open entries table

Search in open customer entries

Used by some EFT systems. Search for transactions will be done in the Open customer entry table.

Search in customer transactions

Used by some EFT systems. Search for transactions will be done in the Customer transaction table.

Search in open supplier entries

Used by some EFT systems. Search for transactions will be done in the Open supplier entry table.

Search in supplier transactions

Used by some EFT systems. Search for transactions will be done in the Supplier transaction table.

Matching rules

Invoice no. = one invoice

A search will be performed for invoice numbers in the invoice number field or the CID field in the file, and a row will be entered with the amount that has been paid.

Transaction info = Sum invoice

A search will be performed for invoice numbers from the text field in the file, and rows will be entered for the invoice numbers that are found. The outstanding amount will be entered as a separate row without a reference.

Customer no. + Amount = One invoice

A search will be performed for invoice numbers based on customer number in the customer number field or the CID field in the file. This rule will only add a row if the amount paid is equal to an open entry.

Transaction info + Customer no. + Amount = Sum Invoice

A search will be performed for all available invoices for customer numbers found in the text field in the field, and all the invoices will then be settled with the amount that has been paid.

Account no. + Amount = Sum Invoice

A search will be performed for all customers which have specified account numbers and open entries. The EFT system will then begin to settle the invoices that are found from the oldest invoice onwards.

Posting

Bank transaction per date

The bank transactions will be posted per date.

Bank transaction per Archive reference/batch

The bank transactions will be posted per archive reference/batch.

Bank transaction per transaction reference

The bank transactions will be posted per transaction reference.

Post rest amount in own customer record when invoice reference is missing

The outstanding amount will be posted if no references are found. If you have not selected this field, the outstanding amount will be settled against open entries according to the oldest date first.

Post difference record per processed record

Difference record per payment with a payment difference is produced.

Use open entries table for difference record

This field is not in use.

Use Cross reference table when paying

The Cross reference field is not used on the voucher line, but the Cross reference table is used instead when you are creating payments.

Use cross reference table when receiving payments

The Cross reference field is not used on the voucher line, but the Cross reference table is used instead when you retrieve OCR data.

This field specifies into which field in BankX you will import the information. You must specify the SQL field name, not user-defined or original texts. If you enter an invalid field name, the import from Visma Business will take much longer than usual. When you save the table, the information is saved in the BankX.xml file.

This was created to avoid giving rights to the program directory that cannot be done on terminal servers etc.

When using the DBISAM database, the field will contain a file path to the Database directory. The database contains all the profiles in ConvertX. If the EFT system database name field has already been filled in when the base was created, the database gets this name.

This field specifies into which field in BankX you will import the information. You must specify the SQL field name, not user-defined or original texts. If you enter an invalid field name, the import from Visma Business will take much longer than usual. When you save the table, the information is saved in the BankX.xml file.

This field specifies into which field in BankX you will import the information. You must specify the SQL field name, not user-defined or original texts. If you enter an invalid field name, the import from Visma Business will take much longer than usual. When you save the table, the information is saved in the BankX.xml file.

This field specifies into which field in BankX you will import the information. You must specify the SQL field name, not user-defined or original texts. If you enter an invalid field name, the import from Visma Business will take much longer than usual. When you save the table, the information is saved in the BankX.xml file.

This field is used to omit customers who will not be automatically reconciled. For example CustNo 12345.

It decides the formatting for long text. The text is wrapped on the specified keyword.

It decides the formatting for long text. The text is wrapped on the specified keyword.