Automated EOD Account Exclusion Processing

This document provides an overview of the automated process for excluding broken accounts from Mambu's End-of-Day (EOD) processing.

When an account is broken, it can cause the EOD process to fail. This disrupts customer services that rely on the EOD success webhook. To solve this, we've automated the process of identifying and excluding broken accounts from EOD processing. This new mechanism automatically detects problematic accounts and skips them, allowing the EOD to complete successfully without manual intervention. This is a crucial step towards our long-term goal of automatically "healing" broken accounts.

How it works

The automated process is triggered by specific appraisal failure exceptions that indicate a broken account.

• Initial failure: The first time an account causes an EOD failure, Mambu logs the issue and sends an EOD failure webhook to the customer, as usual.
• Automatic exclusion: On subsequent EOD runs (which retry every hour), the system checks for the logged issue. If the account is on the "broken" list, it is automatically skipped. This allows the EOD process to finish successfully, while still keeping a record of the original failure.

Frequently Asked Questions (FAQ)

How will customers know if an account has been automatically excluded?

Mambu is designed to notify customers. If a new "broken" loan account is found, the End-of-Day (EOD) process will initially fail. When this happens, customers will receive a webhook notification, just as they do now. The Mambu system will then automatically retry the EOD process within the next hour. This time, the broken account will be excluded, and the EOD will be successful.

Additionally, as soon as the Mambu EOD process fails for the first time, we will open a Salesforce case and inform customers about the specific broken account(s). This automation is in place to ensure that our teams can handle these issues efficiently without manual intervention, and your Mambu EOD process can continue.

What happens to the accounts that are excluded?

When an account is excluded, we open a Salesforce case and pass it to the respective team for further investigation. They will work to fix the issue with the account. Once the problem is resolved, the account will be included back into the Mambu EOD process as part of their standard operational procedures.

Could an infrastructure issue cause all accounts to be excluded from the EOD?

No. The Mambu EOD auto-exclusion logic is specifically built to only exclude accounts that fail due to very specific appraisal errors. These errors are caused by schedule failure exceptions like:

• NegativePrincipalForRepaymentException
• InconsistentScheduleWithLoanAmountException
• UnableToAllocateAmountAfterSeveralAttemptException

This ensures that only genuinely broken accounts are excluded, and not healthy ones affected by broader system issues.

What happens to an account while it is excluded from the EOD?

The Mambu EOD process primarily appraises an account, which means it applies interest, penalties, and other necessary calculations. While an account is excluded, these operations will not be performed. This is the same as what would happen if the account was broken anyway. However, once the account is fixed and re-included, Mambu will automatically apply all pending interest, penalties, and fees, ensuring that the account is fully up to date.