Understanding PAD error codes
When an automatic withdrawal (PAD, pre-authorized debit) is processed in Plexflow, it can sometimes be declined or returned by the financial institution. These returns come with an error code that lets you identify the exact cause.
👉 Understanding these codes will help you know why a transaction failed and what follow-up to do with the tenant.
Why can a PAD fail?
Pre-authorized debit (PAD) is an automated process: when a collection date is reached, a request is sent to the tenant’s bank.
The manager does not intervene directly in this process. The final confirmation always depends on the bank’s return.
The most frequent reasons for failure are:
- Insufficient funds at the time of the withdrawal
- Invalid/incorrect account number
- Payment stop
- Frozen account
- Incorrect payer/payee name
Frequent comments
“There was money in the account”
The balance must be available exactly at the time of processing by the bank.
- If the funds were present later in the day, the debit will still have failed.
- Sometimes, the money is indeed present, but other factors can block the transaction: Funds not cleared (code 908): the funds are on hold (e.g. a cheque recently deposited). Frozen account (code 911): the bank prevents any movement for a legal or administrative reason.
“I have proof that the bank withdrew the funds”
It is important to distinguish the collection attempt, which can appear on the account, from a collection that actually succeeded.
“You did not do the collection at midnight”
The collection is not done at midnight sharp, but during the banking day.
The exact time depends on interbank processing systems and can vary by institution.
đź’ˇ Complete list of codes and examples
Code | Meaning | Concrete example |
|---|---|---|
900 | Validation rejection | The tenant’s bank account has not yet been verified, or a required field is missing; the withdrawal is declined as soon as it is sent. |
901 | Insufficient funds | The tenant does not have enough funds on the day of the $1,200 debit; the bank rejects the operation. |
902 | Account not found | The institution or transit number entered does not correspond to any existing account. |
903 | Payment stop | The tenant asked their bank to block any debit from the manager; the withdrawal is returned. |
905 | Account closed | The tenant closed their account the previous week; the debit comes back as “account closed”. |
907 | No debit permitted | The tenant’s account does not allow pre-authorized debits (restricted bank settings). |
908 | Funds not cleared | A recent deposit is still on hold; the apparent balance is sufficient, but the funds are not available. |
910 | Payer or payee deceased | The bank reports the death of the account holder; the debits are returned. |
911 | Frozen account | The account is frozen by the bank (e.g. a compliance measure); no movement is authorized. |
912 | Invalid or incorrect account number | A digit in the account number was reversed at entry; bank validation fails. |
914 | Incorrect payer or payee name | The name recorded in the PAD agreement does not match the name on the bank account. |
915 | Refused or no agreement | The tenant never signed a PAD authorization for this account, or contested the authorization. |
916 | Agreement non-compliance (P) | The withdrawal does not comply with the terms of the agreement (e.g. a different amount/date without the required notice). |
917 | Agreement revoked | The tenant revoked their PAD authorization with the manager or the bank; the debit is returned. |
đź’¬ All fees are subject to change without notice.
🎓 Did you know…
Plexflow now offers free training to help you get more out of the platform.
👉 Access the training
đź’ˇ An excellent way to save time and use Plexflow to its full potential.
Updated on: 12/11/2026
Thank you!