The following table summarizes the available creditor parameters. They are detailed in the document that lists the application parameters.
| Name | Description |
|---|---|
| Mandate creation | |
| Mandate generation on payment | Defines if SPS’ database can be managed from the payment instructions sent from the creditor to SPS.<br/>If activated, the mandate database is updated if:<br/>- The mandate on the payment order is unknown, then the mandate will be created in the database from the information available on the order; <br/>- The mandate is known to SPS, but there are differences between SPS’ mandate and the order. SPS’ mandate is updated according to the new order.<br/> If activated and if the debtor bank account in the transaction file is invalid,the mandate is created in pending status and the transaction is rejected.<br/> If disabled, SPS will not update the database from the payment orders. |
| Type of created mandates | If “Mandate generation on payment” is active, the creditor chooses if the newly-created mandates are considered as pre-SEPA migrated, New SEPA mandates mandates or as Existing SEPA mandates. If the mandates are considered migrated, migration rules are applied (automatic signature date computation for example). If the mandates are considered existing, the first sdd sent by SPS will be a recurrent and not a first. |
| Automatic UMR generation | Allows SPS to generate an UMR when it is not included on the mandate creation form.<br/> If activated, SPS will compute an UMR from a predefined model if the UMR is missing. <br/>If disabled, SPS will not generate an UMR and the mandate creation will be rejected. |
| Web GUI UMR generation mode | Allows choosing between 3 UMR generation modes:<br/>- Generator Model by default: UMR automatic generation is activated but the user can choose to disable it;<br/> - Generator Model mandatory: the UMR will be generated automatically;<br/> - Manual filling: the user will have to input an UMR manually. |
| UMR template | UMR pattern to be used. Selection and setup is done on the organization |
| Default language for mandate | Default language for mandate creation (compatible with Worldline files (csv, xml), web services, Poor Pain008), several cases are possible:<br/>- Option activated and language not specified in file/WS: the selected language in the option<br/>- Option activated and language specified in file/WS: the specified language in the file/WS <br/>- Option deactivated and language not specified in file/WS: if the option is activated in a parent organization, it will be the default language of the parent organization. Else it will be the English. <br/>- Option deactivated and language specified in file/WS: the specified language in the file/WS |
| For mandate creation in domestic file format, use the date of the day as signature date | Activated to use date of the day as signature date, in case a mandate is created from a domestic file format. Unactivated implies that the mandate will be created as incomplete. |
| Authorize the creation of mandates having the same UIR | Indicate whether the creation of a mandate with an UIR already used by an existing mandate is authorized |
| Authorize the creation of mandates with an incorrect Debtor account | On the mandate Creation/Modification page, if the debtor account information is wrong (BIC+IBAN or BBAN), and if the option is activated at Organization level, the mandate will be created/edited with pending status, If the option is not activated, the behavior is unchanged; the request will be rejected |
| Control to have the debtor address mandatory for the countries not in EEA | Debtor address becomes mandatory to activate Mandate when debtor or creditor bank account is from a non EEA country or territory. |
| Mandate validation | |
| Manual SPS creation | Decides whether a mandate created by a user on the GUI must be validated by another user before it can be used to process payments.<br/> If activated, the mandate is created and set to “Awaiting creditor validation”. Only another user with sufficient privileges can validate the mandate.<br/> If disabled, the mandate will not be set to “Awaiting creditor validation”. |
| Web service creation | Decides whether a mandate created through a web service must be validated to become active.<br/> If activated, the mandate is created with the “Awaiting creditor validation” status. If disabled, the mandate will not be set to “Awaiting creditor validation”. |
| File transfer creation | Sets if a mandate created by file transfer must be validated before becoming active.<br/> If actived, the created mandate is created with an “Awaiting creditor validation” status.<br/> If disabled, the mandate will not be created with an “Awaiting creditor validation” status. |
| File upload creation | Defines if a mandate created by file upload must be validated before becoming active.<br/> If activated, the created mandate is generated with an “Awaiting creditor validation” status.<br/> If disabled, the mandate will not be created with an “Awaiting creditor validation” status. |
| Mandate Migration | |
| Mandate Migration | If enabled, sends a notification to the debtor when a mandate is migrated to the SEPA format. |
| SDD validation | |
| Manual SPS creation | If activated, an SDD created by GUI will require validation by an authorized user.<br/> If disabled, the SDD will not require validation. |
| Web service creation | If activated, an SDD created through a web service will require validation by an authorized user.<br/> If disabled, the SDD will not require validation. |
| File transfer creation | If activated, an SDD created using a file transfer will require validation by an authorized user.<br/> If disabled, the SDD will not require validation. |
| File upload creation | If activated, an SDD created by file upload will require validation by an authorized user.<br/> If disabled, the SDD will not require validation. |
| SCT validation | |
| Manual SPS creation | If activated, an SCT created by GUI will require validation by an authorized user.<br/> If disabled, the SCT will not require validation. |
| Web service creation | If activated, an SCT created through a web service will require validation by an authorized user.<br/> If disabled, the SCT will not require validation. |
| File transfer creation | If activated, an SCT created using a file transfer will require validation by an authorized user. <br/>If disabled, the SCT will not require validation. |
| File upload creation | If activated, an SCT created by file upload will require validation by an authorized user. <br/>If disabled, the SCT will not require validation. |
| Pre-notification | |
| SDD created by file or WS | If activated, SPS will automatically send prenotifications for payments created by file transfer or web service.<br/> This parameter does not affect transactions created by schedules for which the creditor must define, for each schedule, if a prenotification should be issued. |
| Delay until pre-notification (days) | Sets the number of days before an SDD’s due date from which the prenotification can be issued. The issuing date is computed as follows: (due date) – (maximum number of days before issuing).<br/> If the issuing date is set after the current date, no prenotification is issued for the SDD. The prenotification will be sent on the set day.<br/> If the issuing date matches the current date, the prenotification will be sent the day of the creation of the SDD. <br/>If the issuing day is before the current date, the delivery of the prenotification depends on the next parameter. |
| Pre-notification after delay | Defines if the prenotification is delivered to the debtor if the prenotification delay has passed. |
| PDF generation | |
| Use detailed mode for PDF generation | If activated, SPS will use a detailed template with optional fields while generating a PDF mandate.<br/> If disabled, SPS will use the simplified template (without any optional fields) |
| SDD management | |
| Due date computing | SPS will automatically compute new due dates if the current ones are erroneous. Payment orders received by SPS that have an incorrect due date will see that date modified automatically. The same will happen for a transaction whose status switches from “Waiting” to “Created” while having an invalid due date <br/>Caution: In case of validation active, the due date won’t be recomputed during a Collection generation even if the recalculation option is enabled. |
| Authorize a SDD FIRST and RCUR at the same date | Indicate if a SDD FIRST and RCUR can have the same due date |
| Web GUI SDD’s end to end ID generation mode | Define the SDD’s end to end ID generation mode on Web GUI (Default model, model mandatory, manual input) |
| Model to use for payment schedule or web interface / Model to use if a reference is provided / Model to use if no reference is provided | SDD’s end to end ID pattern to use. |
| Make UIR different from Belgium domiciliation | If checked, the UIR and the domiciliation provided in the Dom80 files will be different; if not, it will be the same. |
| Use the specific SDD template for La Banque De France (OC240 only) | If checked will use the specific SDD template overriding any rules set about other SDD templates |
| SCT management | |
| Authorize SCT issuing | If activated, SPS will be able to process a partial or complete refund on an SDD after the legal deadline has passed.<br/> If disabled, SPS will not be able to issue refunds. |
| Due date computing | Enables the mandate manager to modify due dates upon payment request reception or upon status changes |
| Authorized the creation of SCT by importing Dom80 files | Indicates whether the application is allowed to make refunds via SCT |
| Model to use if a reference is provided | SCT's EndToEndID pattern to be used. Selection and setup is done in the organization's parameters |
| Model to use if no reference is provided | SCT's EndToEndID pattern to be used. Selection and setup is done in the organization's parameters |
| Web GUI SCT's end to end ID generation mode | Defines the SCT's end to end ID generation mode on Web GUI (Default model, model mandatory, Manual input) |
| Payment plans | |
| SDD generation | Sets a number of days after which SDDs generated from payment schedules are no longer computed by SPS. |
| SDD preview | Number of days after which SDDs generated from payment schedules are not previewed on the payment schedule details page. Even if the “SDD preview” value exceeds the “SDD generation” value, no SDD will be created on the database. |
| Rejected payments | |
| Automatic SDD re-issuing | Defines if SPS must re-issue payments that were rejected due to the debtor’s insufficient funds.<br/> If enabled, SPS will automatically compute a new SDD according to the parameters below. <br/>If disabled, SPS will not compute a new SDD. |
| Maximum re-issuing number | Sets the maximum number of times SPS will try to re-issue the SDD. |
| Days before re-issuing | Defines the number of working days SPS must wait upon reception of a rejected payment before trying to re-issue it. |
| Third party database | |
| Use third party database | If enabled, creates a third party database to allow auto completion of a third party’s information on the GUI. <br/>The database can be populated using XML files. |
| Creditor organization logo | |
| Creditor organization logo | Allows the user to upload a logo that will be used while generating PDF mandates. |
| Bank statements generation | |
| Generate bank statements | Sets if SPS must generate a daily report of unpaid transactions. |
| Output format | List of the output format for your bank statements (CFONB240, NOMRA19, CBI, DTAUSOUT, CODA) |
| Transactions to include | Type of transactions to include in the file (all type or only r-transactions) |
| Origin of transactions | List of file from which the transactions will originate (CAMT053, CAMT054, PAIN002) |
| Block empty file generation | If checked, generation won’t produce empty file (CFONB240, NORMA19, CBI, DTAUSOUT, CODA) |
| File recipient | If the previous option is activated, the creditor can choose the name of the recipient. The name is limited to 24 characters and will be integrated into a CFONB240 file in the header and footer at offsets 43 to 66. |
| SPS “libelle 1” field | In case of CFONB240, the user can customize the field “libelle 1”, the default value is “originalEndToEndId” |
| SPS “libelle 2” field | In case of CFONB240, the user can customize the field “libelle 2”, the default value is “uir” |
| Publishing | |
| Publishing color | Indicates if the publishing service must print out documents in color or in black and white. |
| Sending of debtor notification | |
| Automatic migration notification | Indicate if the application send a notification to the debtor when a mandate is migrated |
| Automatic reminder notification | Indicate if the application send a notification reminding the debtor to complete and sign a mandate |
| Automatic notification on a mandate’s debtor informations changes | Indicate if the application sends a notification when changing a debtor information within a mandate |
| Automatic notification on a mandate’s UMR changes | Indicate if the application sends a notification when changing the UMR of a mandate |
| Remote completion | |
| Remote completion retention | Number of days left for the creditor to complete the mandate |
| File Integration | |
| File Integration Report Format | Sets the file integration report format (CSV or XML), The IBAN information present in File Integration Reports for Transactions, Mandates, Collections, Creditors and Third Parties is never masked whatever the user’s role. |
| Report Version | Indicates which version o the integration report will be used |
| Report transfer type | Indicates if the integration report will be sent by Email, file transfer, or both |
| Filter report with rejects only | Filter the file integration report by putting only the rejected operations in it |
| Retain Rejected Transactions | Activate if creditor wish to retain the rejected transactions in the imported domestic transactions file |
| Web Service | |
| Web Service Version | Indicates which version of the web service will be used |
| Domestic Identification Modification Advice (CAI) Generation | |
| Domestic CAI Generation | If checked, authorize the generation of a Domestic CAI Format |
| Output format | List of the output format for the Identification Modification Advice (CFONB240) |
| Origin of transactions | List of the type of file from which the transaction will originate (ACMT022) |
| File recipient | Name of the file's recipient (24 char max) |
| SPS “libelle 1” field | The value to put in the "libelle 1" field of the generated CFONB |
| Block Empty File Generation | If checked, empty generation will not be possible. |
| Language for notifications | |
| Creditor language | Indicates the template's language to use for notifications to the creditor |
| New Alerts | |
| Automatic subscription to new alerts | Automatic subscription to new alerts if checked |
| Event reports | |
| Report version | Indicates which version of the report will be used |