What installation sets up
This page describes the number series, defaults, codes and report selection entries that 365 business Banking creates at installation, and the settings you should check.
So that you can start working right after installation, 365 business Banking creates a basic setup in every company. Only empty fields are filled, or values are set once, the first time. Your own settings remain unchanged. Use this page as a checklist after an installation, reinstallation or update.
Number series
In Banking Setup, Numbering FastTab. A number series is only created if the field is empty. An existing series with the same code is reused:
| Field | Number series | Description | First number |
|---|---|---|---|
| Standing Order Nos. | SO | Standing Order No. Series | SO00001 |
| Remittance Advice Nos. | RA | Remittance Advice No. Series | RA00001 |
| End-to-End Reference Nos. | E2E | End-to-End Reference No. Series | E2E-00000001 |
| Payment Message ID Nos. | MSGID | Payment Message ID No. Series | MSG-00000001 |
| Prenotification Nos. | DDP | Direct Debit Prenotification No. Series | DDP00001 |
All series allow manual numbers and are marked as default numbers.
Defaults
Only set if still empty
| Setting | Value |
|---|---|
| Direct Debit Return On Hold Code | RLS |
| CORE Direct Debit Lead Time (Days), First CORE Direct Debit Lead Time (Days) and B2B Direct Debit Lead Time (Days) of connected bank accounts | 1 bank working day each, if all three are still 0. Can be changed on the bank account card, see Bank working days and lead times |
| Verification of Payee on Banking Setup | Verification of Payee (via finAPI), if a license is present |
Set once, the first time
| Setting | Value |
|---|---|
| Prenotification Lead Time (Days) | 14 |
| Direct Debit Mandate Validity | 36M |
| Bank Account Reconciliation Line Posting | Direct Posting |
| Create Bank Accounts | Yes |
| Direct Debit Return Invoice Action | Set On Hold |
| Direct Debit Return Fee Action | Manual or Reconciliation Rule |
| Undocumented Deduction Reason in the payment application settings | 43, if the field is empty |
| Deduction Posting Text in the payment application settings | the default posting text, if the field is empty |
These values are only preset at the first installation in a company. After that, you manage these settings yourself. A reinstallation or an update does not reset them, even if you entered a Prenotification Lead Time (Days) of 0 or an empty Direct Debit Mandate Validity.
On existing master data
- Existing customer and vendor bank accounts without a status get the status Released, so that you do not have to release each account before the first payment. New accounts get the status New, see Recipient bank accounts.
- Existing bank accounts get the Account Holder from the company information, once.
- Payment methods with the banking payment method SEPA Collective Direct Debit get the Direct Debit flag, once.
Codes and context words
| Data | Content |
|---|---|
| SEPA purpose codes | the standard purpose codes, see SEPA purpose codes |
| ZKA codes | the standard business transaction codes, see ZKA codes |
| Bank account reconciliation context words | with the type Both: ZAHLUNG, PAYMENT, RECHNUNG, RG, INV, INVOICE, RECHNUNGSNUMMER, RECHNUNGS-NR, RGNR (strong) and ZLG, PMT, RE (weak), see Context words |
| Payment application fields | for customer and vendor ledger entries, Document No., External Document No. and Payment Reference each, priority 1, see Payment application fields |
| Deduction reasons | 24 reasons from EDIFACT code list 4465, such as 43 Reason unknown and 66 Cash discount, see Deduction Reasons |
Existing entries are not changed. Missing entries are added. The payment application fields and the deduction reasons are the exceptions:
- The standard lines of the payment application fields are created only once. Lines that you deleted are not created again by a reinstallation or an update.
- The deduction reasons are created once and after that only again if the table is empty. Reasons that were deleted or renamed are therefore not created again.
Report selection
For Remittance Advice, Direct Debit Prenotification, SEPA Direct Debit Mandate and Payment Authorization, installation creates one report selection entry each that uses the supplied email layout as the email body. The entry is only created if no report is entered for the usage yet. See Report selection and email for banking documents.
Assisted setup
In Assisted Setup, the Connect group gets the entry Connect a banking provider (short title "Connect banking"). It opens the Connect Bank Account wizard. Its help link points to the Connect a bank account page of this documentation. The language of the link follows the language of the session in which the installation or update was run: German for a German session, English otherwise.
Technical settings
- Allow HttpClient Requests is switched on for the app. Without this permission, 365 business Banking cannot reach either the 365 business API or the payment service providers.
- The Banking and EBICS Connection licenses are registered, see Permissions and licenses.
- The tables for retention policies are offered, but no policy is created, see Retention policies.
- A notification on the Direct Debit Collections page that points to the cash receipt journal is registered. You can switch it off in the notification settings, see Direct debit collections.
When updating to 18.4
In addition to the installation steps, the update makes the following changes once:
- The 365 business Banking settings in the General Ledger Setup are moved to the Banking Setup, including the number series, the settings for direct debits and returned direct debits, Bank Account Reconciliation Line Posting and Create Bank Accounts. The moved values stay as they were. From now on, you maintain them only in the Banking Setup.
- Banking User Setup becomes the company bank access, including email address, phone number, password and all connected bank accounts, without signing in again, see Banking setup.
- Each bank account's previous banking provider becomes its Account Information Service and Payment Initiation Service.
- Connected SEPA bank accounts without an Account Type get the account type Checking, see Bank account card.
- Verification of Payee on the Banking Setup is set to Verification of Payee (via finAPI) if a license is present, see Verification of Payee (VoP).
- Retrieve Transactions From is set, if empty, to the date of the oldest transaction ever imported (for accounts without imported transactions, to the last statement date), and all imported transactions get their transaction fingerprint, see Combine banking services.
- The capabilities of connected bank accounts are filled in. File accounts get them the next time their ISO 20022 file setup is used, see Bank account capabilities.
- The bank accounts get the logo of their bank or their payment service provider.
- Bank accounts that receive their bank statements through EBICS or camt files are switched to Pmt. Rec. Journal Creation Per Bank Statement. Open payment reconciliation journals remain unchanged. Only transactions imported afterwards are placed in one journal per bank statement, see Retrieve bank transactions.
- A Custom Date Pattern of the Universal setup is converted into a regular expression in the Custom Date Regex field. Patterns made of
DDorD,MMorM,YYYYand separators, such asDD.MM.YYYY, are converted. If a pattern cannot be converted (for example, with a two-digit year), the field stays empty and the Universal setup is considered incomplete. In this case, enter the regular expression yourself, with the named groupsday,monthandyear. - The ZKA codes created by the installation are replaced by the standard business transaction codes of Die Deutsche Kreditwirtschaft. Codes that you created yourself with other numbers are kept. Reconciliation rules store the code the bank reports and work unchanged, see ZKA codes.
- All stored bank transactions are classified again according to the current rules. If a transaction is no longer considered a returned direct debit, the update removes the assignment to the direct debit and the application of the line in open payment reconciliation journals, so that you apply the line like any other line. Posted lines remain unchanged. A fee line that was already split off is kept; delete it yourself if needed, see Process returned direct debits.
- Bank account ledger entries that were posted through a transit account and not yet moved from the transit account are marked In Transit. Balance excl. Transit therefore takes them into account immediately, see Transit account.
- The bank account ledger entries of posted payment reconciliations get the transaction ID of their bank transaction. After the payment reconciliation is reversed, the bank transaction can therefore be reconciled again, see Reverse a posted payment reconciliation.
- Successful collections through payment service providers whose payment is already posted or whose invoice is already closed are marked as posted. Post Collected Payments therefore does not post them again, see Collect payments via payment service providers.
Check direct matching for payment service providers after the update
In companies where direct matching for payment service providers was switched on before, the update switches off Enable Transaction ID Matching and Enable Direct Purpose Matching. As a result, there can be fewer automatic matches for payment service providers after the update. If needed, switch both settings on again in the payment application settings, group Direct Matching Settings, see Direct matching for payment service providers.