Reminder Process Overview
Reminder Actions | Action Description |
---|---|
Soft block - Block card usage | Card usage on the account level is blocked. In case of full incoming payment, the block is removed automatically. |
Charge a reminder fee | 2 different reminder fees can be set. |
Create a reminder file | The issuer can send an official reminder letter to the cardholder. |
Trigger a push notification | The issuer can forward the information via SMS, e-mail, paper letter or through the app. |
Reminder Actions | Action Description |
---|---|
Account status change: Account in collection | Account status is changed. |
Block interest posting | Interest is not posted on the next billing cycle end. |
Stop invoicing | Account is removed from the statement generation. |
Hard block - Block card usage | Card usage on the account level is blocked. Requires a manual block lifting. |
Cards No Renewal | Cards will not be renewed whilst the account is in collection status |
Event | Actions |
---|---|
Reminder 1 | Notify the cardholder on passed due date right after. - Trigger a push notification |
Reminder 2 | Notify the cardholder on upcoming reminder. - Trigger a push notification |
Reminder 3 | Hard/strong reminder. - Create a reminder file - Soft block card usage - Charge a fee |
Reminder 4 | Notify the cardholder on the second hard/strong reminder in case of no payment. - Trigger a push notification |
Reminder 5 | Second hard/strong reminder. - Create a reminder file - Charge a fee |
Reminder 6 | Warning, collection notice will be sent in case of no payment. - Trigger a push notification |
Reminder 7 | Collection notice - Create a reminder file |
Send to Collection | Send to collection - Account status change: Account in collection - Block interest posting - Stop invoicing - Hard block - Block card usage - Card no renewal |
Reminder event | Values | Definition |
---|---|---|
"reminder1TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"reminder2TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"reminder3TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"reminder4TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"reminder5TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"reminder6TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"reminder7TriggerDate" | YYYY-MM-DD | Date when the reminder event has been/will be triggered |
"collectionTriggerDate" | YYYY-MM-DD | Date when the collection event has been/will be triggered |
"disableReminderProcess" | True False | "False" when it’s enabled"True" when the reminder processes has been stopped. This is final status so the status cannot be set back to "False" |
"reminderStatus" | "WAIT" "REMINDER1_SENT" "REMINDER2_SENT" "REMINDER3_SENT" "REMINDER4_SENT" "REMINDER5_SENT" "REMINDER6_SENT" "REMINDER7_SENT" "SENT_TO_COLLECTION" "STOPPED" "DONE" | This status will be empty when there are now overdue invoices. Once invoice has been reached overdue on the delinquency date the status will be "WAIT" .After that it will state the most recently sent reminder or collection event. If reminder process has been manually stopped it will show in "STOPPED" status. See further information in the exception handling section.Reminder status will marked as "DONE" when payment is received to clear the process. Similarly it will marked as “done” if the next reminder event stays under threshold. Please see classifiers section for more information. After the last reminder event for the process has been triggered the final status will be always set as "DONE" on the following day. |
"accountCardBlocks" SOFT_BLOCK HARD_BLOCK | "FALSE" “TRUE" | "FALSE" status is shown when the cards can be used.Once the "SOFT_BLOCK" is set to "TRUE" then the cards are blocked on the account level.At the time of collection sending “hard block" is set to "TRUE" |
Action | How |
---|---|
Under investigation | "underInvestigation" to be set “true” through Update a credit account API Account under investigation will be ignored in the reminder process. |
Set the minimum-to-pay percentage to 0 | "minimumToPay" "percentage" to 0 through Update a credit account API |
Block interest posting | "interestPostingEnabled" to “false” through Update a credit account API |
Block / Unblock cards | Card blocks on the account level can be manually lifted by changing the "accountCardBlocks" values from “SOFT_BLOCK” or “HARD_BLOCK” into “false” at the Update Account API or vise versa, blocks can be manually set back on “true” from there. |
Stop the reminder & collection process | “disableReminderProcess" to “true” through Update a credit account reminder data API |
Change the reminder dates | "reminder1TriggerDate" in “YYYY-MM-DD format through Update a credit account reminder data API |
Classifier Name | Code | Values Name/Code | Description | API/MyEnfuce |
---|---|---|---|---|
Reminder Process Status | REM_CL_STATUS | - Reminder 1 / 1 - Reminder 2 / 2 - Reminder 3 / 3 - Reminder 4 / 4 - Reminder 5 / 5 - Reminder 6 / 6 - Reminder 7 / 7 - Collection / COLL - None / N - Stopped / S | Reminder 1 classifier will be triggered along the event to be visible on the next morning’s DWH file. Reminder classifier will be set as ‘None’ when the past due balances are paid, even if the account would be in collection. ‘Stopped’ is final status that can be manually set. | Reminder trigger dates are visible in the Get Account API It is possible to amend the threshold times and stop the reminder process in Update a Credit Account Reminder data API |
Account Card Block (Soft block) | INV_CARD_BLOCK | - No / N - Yes / Y | If set to ‘Yes’ then all cards for the account are blocked for the transactions. This will be automatically lifted when overdue balance has been paid. | Card statuses are visible in the Get Account API Cards can be manually blocked/unblocked in Update a Credit Account API |
Card Hardblock | CARD_HARDBLOCK | - No / N - Yes / Y | If set to ‘Yes’ then all cards for the account are blocked for the transactions. This will not be automatically lifted by the system | Card statuses are visible in the Get Account API Cards can be manually blocked/unblocked in Update a Credit Account API |
CL. Under Threshold | CL_THRESH | - None / N - Yes / Y | In case the overdue balance is under the threshold for the next reminder event to be triggered the system will set the under threshold classifier into ‘Yes’ for the day and clears on the next day. | N/A |
Delinquency Level | DLQ_LEVEL | No Debts / 0 Due / 1 Past Due 0-30 / 2 Past Due 31-60 / 3 Past Due 61-90 / 4 Past Due 91-120 / 5 Past Due 121-150 / 6 Past Due 151-180 / 7 Past Due 181-210 / 8 Past Due 211-240 / 9 | Delinquency level is shadowing the aging of the balances in 30 days past due slots. | N/A |
Block Interest Posting | BLOCK_INT_POSTING | No / N Yes / Y | Revolving or overdue Interests will not be posted in case the block interest posting has been set to ‘Yes’. | Visible in the Get Account API Possible to update in Update a credit account API |
Under Investigation | UNDER_INVESTIGATION | No / N Yes / Y | When under investigation has been set to ‘Yes’ the reminder process for the account will be stopped for the time being. | Visible in the Get Account API Possible to update with Update a credit account API |
Section | Field Name | Details | Values |
---|---|---|---|
file | fileDate | File creation date | YYYY-MM-DD |
file | fileId | Running number sequence (file split) | 1… |
file | institutionId | Issuer number | 111111 |
file | institutionName | Issuer name | Company Ltd |
file | NumberOfRecords | Number of records in the file | 1…99 |
file | receiver | Receiver where the file will be sent | Issuer |
records / record→ | recordId | Record sequence number in the file (max 99) | 0000001… |
record / account→ | accountNumber | Customer account number | |
account | accountName | Customer name (Commercial or Private) | Company ltd or John Smith |
addInfo | type - value | Date plan configuration code | FUNCTIONAL_DATES - FLTACCPRIV01 |
addInfo | type - value | GL plan configuration code | GL_PLAN - FLTACCPRIV01 |
addInfo | type - value | Tariff plan configuration code | TARIFF_PLAN - CRDACCPRIV01 |
account | productName | Product name | Product name configured in Enfuce payment platform - Prepaid, debit, credit, fleet etc. |
account | productCode | Product code | CREDIT |
account | status | Status of the account | 00 |
← / record / account | |||
record / balances → | amount, type | Balance type with amount | TOTAL_BALANCE |
balances | amount, type | Balance type with amount | TOTAL_DUE DUE PAST_DUE OVD_01 OVD_02 TOTAL_BALANCE OPENING_BALANCE |
← / record / balances | |||
record | billingDate | Billing date | YYYY-MM-DD |
record | billingPeriodEndDate | Billing period end date | YYYY-MM-DD |
record | billingPeriodStartDate | Billing period start date | YYYY-MM-DD |
record / client → | addInfos / AddInfo | type / value | |
client | clientNumber | Issuer number | |
client | companyName | Issuer name | Company Ltd |
client | Issuer email address | company@mail.fi | |
client | locale | Client country location | fi_FI en_GB sv_SE no_NO is_IS |
← record / client | |||
record | creditLimit | Account credit limit | 0.0 |
← record / deliveryAddress | addressLine1 | Street address | Street 1 |
deliveryAddress | city | City | Helsinki |
deliveryAddress | countryCode | ISO alpha-3 code | FIN |
deliveryAddress | countryName | Country name in letters | Finland |
deliveryAddress | zipCode | Postal code | 00100 |
deliveryAddress | addressLine2 | Street address / P.O. box | Box 100 |
← record / deliveryAddress | |||
record | dueDate | Invoice due date | YYYY-MM-DD |
interestRates / interestRate → | code | Interest rate code | INT_OVD |
interestRate | effectiveDate | Start date | YYYY-MM-DD |
interestRate | name | Interest name | Interest Rate - Overdue MTP |
interestRate | value | Interest rate percentage | 00.00 |
← interestRates / interestRate | |||
fees / fee -> | code | REM1_FEE REM2_FEE | |
effectiveDate | Posting date | YYYY-MM-DD | |
name | Fee name | Reminder 1 Fee Reminder 2 Fee | |
feeBase | Set fee value | 0.0 | |
← fees / fee | |||
record | minimumToPayPercentage | Minimum percent to be paid | 100 |
record | paymentTerm | Payment terms | PAY_TERM - 1…31 |
record | recordId | Record sequence number in the file | 0000001 |
record | referenceNumber | Payment reference number | 001234567890011 |
← records / record | |||
← file |