The staff declaration, and bank debit problems your residents report

This article explains the staff declaration and the consent choice on the Launch settings step, every message your residents can meet on the pages where they sign, set up, change or cancel a bank debit agreement, the messages that appear once agreements are live and debits are being collected, and the messages that look alarming but need nothing from you. It is written for property managers, building staff and board members.

Two things to know before you start reading.

1. Names, unit numbers, dates and row numbers inside the quoted messages are examples. Your screen shows the real ones for your property.
2. The resident-facing messages are shown to your residents, not to you. Knowing what each one means lets you tell the person on the phone exactly what to do next.

If your message is not in this article, the full "Find your problem fast" table at the top of Bank debit problems and what they mean routes every message in the set to the article that explains it.

Problems with the staff declaration and the consent choice

On the Launch settings step, a batch with bank debit rows must answer one question: "How will people agree to bank debits?" You choose once for the whole batch and it cannot be split row by row. The two options are "Send each person the agreement to sign" and "I already hold signed agreements (staff declaration)".

The declaration is serious. If you choose it, no resident signs anything in URBI, URBI holds no resident signature, and if a resident disputes a debit with their bank, the property is responsible and must produce the signed agreement and written approval. The declaration is recorded with your name, the time and your device. Only choose it when you genuinely hold signed paper agreements and written approval for every person in the batch.

When you choose the declaration, a card titled "Signed paper agreements" opens. It reads: "Residents hold signed paper agreements and were told about the first debit on . This is recorded with your name, the time and your device." You fill in two dates, Date residents were told (notice date) and First debit date, and then confirm by typing your full name. The rules on those two dates are explained in Problems with the notice date and the first debit date.

A batch with a declaration works differently from one where people sign. Launch settings hides the start period choice, the toggle for starting bank debits on the fee start date, and the communication date. The fee start date is locked to the first debit date. Nothing waits on the Send card for you to send: each resident gets one setup email automatically when the import commits, and the first bill carries no invoice email.

The declaration window, with the responsibility line and the name field that turns Submit on.

"Could not record the declaration. Try again."

What it means. You typed your name and pressed Submit declaration, and it was not recorded. No declaration exists and the consent path is unchanged.

Why it happened. The save failed with no reason given.

What to do. Press Submit declaration again. If it fails twice, close the window, reload the import, and make the declaration again.

"This batch changed since you declared it. Confirm the declaration again before you can commit."

What it means. Your declaration covered a specific set of bank debit rows. That set has changed, so your declaration no longer matches what you would be committing. You are being asked to declare again over the new set. This is deliberate, because you are taking personal responsibility for exactly the rows you declared.

Why it happened. Bank debit rows were added, removed or skipped after the declaration was made.

What to do.

1. Look through the bank debit rows so you know what you are now declaring.
2. Open the declaration again from the consent options.
3. Type your full name and press Submit declaration.

"3 of 40 rows cannot be declared and will be skipped for the declaration. The other 37 go ahead."

What it means. Some of the bank debit rows cannot be covered by a declaration, so they are left out of it. The rest are covered and go ahead. The numbers in the message are your real counts.

Why it happened. Those rows have a conflict that a declaration cannot override. The refusals are explained in Bank debit rows that are refused or need confirming.

What to do. Look at the rows marked as refused in the review table. If you want them as bank debits, deal with each conflict first. The other rows go ahead as they are, and your fee and lease rows commit either way.

"Could not load the bank debit consent choice."

What it means. The screen could not read which consent path this batch is on, so it cannot show you the options.

Why it happened. The read failed.

What to do. Press Retry in the block where the options should be.

"Could not save the bank debit consent choice. Try again."

What it means. Your choice of consent path was not saved. The batch still has no consent path, so it cannot be committed yet.

Why it happened. The save failed or timed out.

What to do. Pick the option again. If you are choosing the declaration path, the declaration window opens again and you type your name again.

"Messages for this batch are being sent. Try again once the send finishes."

What it means. The consent path cannot change right now, because emails for this batch are going out at this moment.

Why it happened. The batch is in the middle of a send.

What to do. Wait for the send to finish, then set the consent path.

"This batch has no PAD rows"

What it means. A consent path was being saved for a batch that has no bank debit rows at all. No consent is needed, because nobody is being debited.

Why it happened. The consent choice was submitted on a batch with no bank debit rows, usually because the rows were discarded in another tab.

What to do. Nothing. Carry on and commit the batch. If you did expect bank debit rows, reload the import and check whether they are still staged.

"Every PAD row must have a resolved unit before consent is saved"

What it means. At least one bank debit row is not yet tied to a unit. Consent cannot be recorded over rows whose unit is unknown.

Why it happened. A bank debit row has no resolved unit, the same condition that shows as "Needs review" on the staged list.

What to do.

1. Go back to the Review step.
2. Find the rows tagged "Needs review".
3. Correct the unit label in your file, or the payer name if you filled one in, and upload those rows again.
4. Return to Launch settings and choose the consent path.

"Saving the PAD consent timed out. Refresh before trying again."

What it means. Your choice may or may not have been saved. The screen stopped waiting before it knew.

Why it happened. The save took longer than the screen's waiting time.

What to do.

1. Reload the import.
2. Open Launch settings and look at the consent block.
3. If the option is already selected, you are done. If not, choose it again.

"Failed to save PAD consent"

What it means. An internal step of saving the consent path failed, so nothing was saved.

Why it happened. A read or a write did not complete. A related wording is "Failed to fetch PAD rows".

What to do. Choose the option again. If it fails repeatedly, contact your URBI administrator.

"Choose how people will agree to bank debits first"

What it means. This is the tooltip on the toggle "Start bank debits on the fee start date". The toggle is disabled until a consent path is chosen, because the two settings work together. The toggle is for batches where people sign. If you choose the declaration, the toggle is hidden and the fee start date is locked to the first debit date.

Why it happened. No consent path has been chosen yet.

What to do. Choose a consent path, then set the toggle if it is shown. When the toggle is off, the first debit lines up with each person's own sign date instead.

"Bank debit consent path"

What it means. This entry appears in the amber "Still need" list beside the disabled Continue button on Launch settings. Continue is the button that commits the batch, so the batch cannot be committed until this is answered.

Why it happened. The batch has bank debit rows and no consent path.

What to do. Choose one of the two options in the "How will people agree to bank debits?" block.

"Choose how people will agree to bank debits before committing this batch."

What it means. You reached the commit and the batch still has no consent path, so nothing was committed.

Why it happened. The commit found no consent path while bank debit rows exist. The same condition, written per row, reads "Choose how payers give consent before committing."

What to do. Go back to Launch settings, choose a consent path, then commit again.

"This batch has no completed bypass declaration."

What it means. The batch is set to the staff declaration path, but no declaration was actually recorded, so the rows have nothing authorising them.

Why it happened. The declaration window was cancelled, or the declaration failed to save.

What to do. Go back to Launch settings, open the declaration, type your full name, and press Submit declaration. Then commit again.

"The bypass declaration for this batch could not be matched to its recorded rows. Attest again before committing."

What it means. URBI keeps a record of exactly which rows your declaration covered, and it can no longer line that record up with the batch's rows. It will not commit rows your declaration cannot be tied to.

Why it happened. The recorded declaration cannot be matched to the batch's current rows. The closely related message "The bank debit rows changed after the bypass declaration was made. Attest again before committing." means rows were added or removed after you declared.

What to do.

1. Review the bank debit rows as they stand now.
2. Make the declaration again over that set.
3. Commit again.

Problems with the notice date and the first debit date

These come from the two date fields on the "Signed paper agreements" card. The calendar greys out any date that cannot be chosen, so most of these never reach you. The rules are:

• The notice date, "Date residents were told (notice date)", is today or earlier, and before the first debit date.
• There are at least 10 days between the notice date and the first debit date.
• The first debit date is a Canadian business day. If it falls after the 28th, it must be the last day of the month. Its bank file must not have started building yet.

"The notice date cannot be after today."

What it means. The notice date you entered is in the future. The card records the date residents were already told, and that cannot be a date that has not happened yet.

Why it happened. The notice date is later than today.

What to do. Enter the real date residents were told. It is today or earlier.

"The notice date must be before the first debit date."

What it means. The first debit date is not later than the notice date.

Why it happened. The two dates are the wrong way round, or the same.

What to do. Choose a first debit date after the notice date.

"6 days between the notice and the first debit. The notice needs at least 10 days."

What it means. Residents must be told at least 10 days before the first debit. With the dates you chose, there are fewer. The card also says "Choose a first debit date at least 10 days after the notice date." and "Earliest first debit date for a notice on 1 December 2026: 11 December 2026." Staff cannot get past this rule on this screen.

Why it happened. The first debit date is less than 10 days after the notice date.

What to do.

1. Pick a first debit date on or after the earliest date the card shows.
2. Only change the notice date if it is wrong. The date is recorded with your name, so never move it just to get past the rule.
3. If you need a shorter notice, contact your URBI administrator. Only URBI can allow a shorter notice, once. After that, everyone sees "URBI allowed a shorter notice."

"That first debit date can no longer be chosen. Its bank file build has started, or it is not a Canadian business day. Pick a later date."

What it means. The first debit date you picked cannot be used.

Why it happened. One of these is true. The date is not a Canadian business day: weekends and Canadian bank holidays are not, and neither is any date after the 28th that is not the last day of its month. Or the bank file for that date has started building. The bank file for each debit date is built at 7:00 AM Toronto time on that date, Monday to Friday, so a date that is today may already be too late.

What to do. Pick a later date. The helper under the field says "Canadian business days only. The bank file for this date is built on at 7:00 AM Toronto time." A charge due on a weekend or holiday is collected on the next business day.

The commit has its own check on the same date. It has to happen at least 30 minutes before the 7:00 AM build. See "The bank file for 16 November 2026 starts building at 7:00 AM Toronto time" in Bank debit rows that are refused or need confirming.

Problems your resident reports from the sign page

This whole section applies only to batches where each person signs. A batch with a staff declaration has no sign page and no sign links.

On the path where each person signs, every payer gets an email with a link that expires in 14 days. The link no longer opens the agreement by itself: they sign in first with the email the request was sent to, using an 8-digit code. These are the things they may call you about.

"Sign in to continue"

What it means. The resident is at the sign-in step. This is normal and not a fault. The page says "For your security, this agreement opens only after you sign in. Enter the email your bank debit request was sent to and we will email you an 8-digit code."

Why it happened. The person is not signed in yet.

What to do. Tell them to use the same email address the bank debit request was sent to, then enter the 8-digit code that arrives. A different email address will not open this agreement.

"This link has expired"

What it means. The sign link is past its expiry and can no longer be used. The page tells them "For your security, expired links can't be used to sign. Contact the management team that sent this link and ask them to send you a new one."

Why it happened. More than 14 days passed, or the link's expiry date was reached.

What to do. Send a fresh link from the Send card using Remind unsigned. Expired links are replaced with fresh 14-day links when you do. Remind unsigned is only for batches where people sign.

"This agreement belongs to someone else"

What it means. The person is signed in with one email, and the agreement was sent to a different one. URBI will not let one person sign another person's agreement.

Why it happened. The signed-in account is not the agreement's owner. This often happens in a household where two people share a device.

What to do. Tell them to press Sign out and sign back in with the exact email the link was sent to. If they no longer use that address, the address on their record needs correcting and a new link needs sending.

"We could not load this agreement"

What it means. The page could not fetch the agreement. Nothing is wrong with the agreement itself as far as this message goes.

Why it happened. The fetch failed. A second wording is "We could not load this PAD agreement."

What to do. Ask them to press Try again. If it keeps failing, send them a new link.

"The PAD agreement details were incomplete."

What it means. The agreement loaded but not all of it arrived, so the page will not show a partial agreement for signing.

Why it happened. The response could not be read into a complete agreement.

What to do. Send the person a new link from the Send card, using Remind unsigned. If the new link does the same, contact your URBI administrator.

"The first payment date changed since this page loaded, so nothing was signed. Here is the new one: ... Review it and sign again."

What it means. The first payment date moved while the person had the page open, so URBI stopped and signed nothing. This protects them from agreeing to a date that is no longer true.

Why it happened. The projected first payment date changed between the page loading and the person pressing Sign & Continue. It commonly happens when a page is left open overnight.

What to do. Tell them to read the new date shown in the message and press Sign & Continue again. Nothing was signed and nothing was debited.

"We could not sign your PAD agreement. Please try again."

What it means. The signature did not go through. No agreement is signed and no debit is scheduled.

Why it happened. The signing request failed with no reason given.

What to do. Ask them to press Sign & Continue again. If it fails repeatedly, send a fresh link.

"You already signed"

What it means. This is good news, not a fault. The agreement was already signed, so the page shows the signed state again on a repeat visit, with "No further action is needed for your property. Your confirmation email contains your agreement details. You can close this page."

Why it happened. The person opened the link a second time.

What to do. Nothing. They can close the page. Their confirmation email holds their agreement details.

"This is not the 1 May 2026 date shown before you signed, because the first payment date depends on the day the agreement is signed. 1 June 2026 is your real first payment date."

What it means. The date quoted before signing was a projection that assumed they signed by a certain day. They signed later, so the real first payment date is the later one shown.

Why it happened. The real first debit date differs from the projection quoted before signing.

What to do. Reassure them that the date in this message is the correct one, and that the earlier date was conditional. The page had already warned that "If you sign later, that charge is paid another way and bank debits start the following month."

Problems residents report when setting up, changing or cancelling on their own

These pages are used by residents who set themselves up after a set-up invitation, and by residents changing or cancelling an agreement they already hold. You cannot fix most of these from your own screen, but knowing what each one means lets you tell the person what to do.

"We could not start the secure bank connection."

What it means. The secure bank connection would not open, so they could not choose their bank. Nothing was set up and nothing was charged.

Why it happened. The request to start the bank connection failed.

What to do. Ask them to try again. This message appears both when setting up and when changing an account.

"The secure bank connection session is no longer valid."

What it means. Their bank connection session ran out before they finished, usually because they left it open too long.

Why it happened. The secure session expired.

What to do. Ask them to press Open Plaid Link again and work through the bank connection without a long pause.

"Select one bank account in Plaid to continue."

What it means. Exactly one bank account must be chosen. They chose none, or several.

Why it happened. Zero or several accounts came back from the bank connection.

What to do. Ask them to run the connection again and tick exactly one account, the chequing account they want the debits to come from.

"We could not verify the selected bank account."

What it means. The account they chose could not be verified, so it cannot be used for debits.

Why it happened. The verification step failed. A related wording is "Plaid did not return the verified account handle and masked details.", which means the bank connection sent back an incomplete answer.

What to do. Ask them to try again. If it keeps failing with the same account, they may need to choose a different account or contact their bank.

"No billing account is available for bank enrollment."

What it means. There is nothing for this person to enrol against, so the set-up cannot start.

Why it happened. The person has no eligible billing account. Two near-identical wordings exist: "No eligible billing account is available for enrollment." and "No eligible locations are available for PAD enrollment."

What to do. This one is for you to fix, not them. Check that the person is linked to the unit as its payer and that a billing account exists for it. Once that is right, ask them to open the set-up link again.

"Connect and verify a bank account before signing."

What it means. They tried to sign the agreement before connecting a bank account, so there is nothing for the agreement to draw from.

Why it happened. The sign step was reached with no verified account.

What to do. Ask them to go back to the Bank step, connect and verify an account, then sign.

"We could not complete your PAD enrollment."

What it means. The final step of setting up failed. They are not enrolled and no debits will be taken.

Why it happened. The enrolment request failed.

What to do. Ask them to try again from the start of the set-up. If it fails twice, contact your URBI administrator.

"Choose CIBC or Simplii Financial for institution number 010."

What it means. They typed their bank details by hand, and that institution number is shared by more than one bank, so the exact bank must be picked from the list.

Why it happened. The bank name was ambiguous or missing. A related wording is "Choose or enter a bank name."

What to do. Ask them to pick their bank from the list rather than typing it.

"Enter valid bank account details."

What it means. The account details they typed did not pass the checks, so nothing was saved.

Why it happened. The manually typed digits failed validation.

What to do. Ask them to check the numbers against a void cheque, and to remember that pre-authorized debits must come from a chequing account, not a savings account. The page says so: "Use your chequing account, not savings".

"Connect and verify the new bank account before signing."

What it means. They are changing which account their debits come from, and tried to authorize the change before connecting the new account.

Why it happened. No verified new account existed when they pressed to sign.

What to do. Ask them to connect and verify the new account first, then authorize the change.

"Type your full legal name to authorize this amendment."

What it means. The name field is empty. Changing the bank account on a live agreement needs their typed name, which stands as their signature.

Why it happened. They pressed to authorize with a blank name field.

What to do. Ask them to type their full legal name, then authorize.

"We could not update your PAD bank account."

What it means. The change of bank account did not save. Their existing agreement and their existing account are unchanged, so debits continue from the old account.

Why it happened. The change request failed.

What to do. Ask them to try again, and to check afterwards which account is shown on their agreement.

"Any debit already scheduled in a file built before this change will still be withdrawn from your old bank ending in 1234; your next debit on 1 June 2026 will use your new bank ending in 6789."

What it means. This is a warning, not an error, and it matters for money. Their account change worked, but one debit was already prepared before the change and will still come out of the old account.

Why it happened. A debit was already in a built file when the account change was authorized.

What to do. Tell them to keep enough money in the old account for that one debit. Every debit after it uses the new account.

"Select at least one billing account to continue."

What it means. They pressed to cancel without choosing which account to cancel, so nothing was cancelled.

Why it happened. No billing account was selected.

What to do. Ask them to tick the accounts they mean, then continue. Cancelling applies only to the accounts they tick.

"Could not cancel automatic payments."

What it means. The cancellation did not go through. Their automatic payments are still running.

Why it happened. The cancellation request failed.

What to do. Ask them to try again and to confirm afterwards that the cancellation shows. Remind them that cancellation is permanent and that restarting later needs a brand-new agreement, and that it requires 30 days' written notice.

"No billing accounts are available for this action."

What it means. There is nothing they can select for the action they chose, so the screen has nothing to show.

Why it happened. Nothing selectable exists for that action.

What to do. Check on your side that the person is still linked to a unit with a billing account, then ask them to open the page again.

Problems after the agreements are live

Once agreements exist, debits are collected in files and matched against your bank statement. These messages come from those later screens.

"This debit is already being processed by the bank and can no longer be skipped."

What it means. The debit has already been sent to the bank. It cannot be stopped now.

Why it happened. The debit was already inside a submitted file when you pressed to skip it. A debit can be skipped only until the bank file for its date has been built, which happens at 7:00 AM Toronto time on the debit date.

What to do. Let the debit settle, then put the money back the normal way, with a refund or a credit to the resident's account. Tell the resident to expect the debit so they are not caught out.

"Could not verify whether this debit is already being processed. Please try again."

What it means. URBI could not tell whether the debit had already gone to the bank, so it did nothing rather than guess.

Why it happened. The check failed.

What to do. Try again. Check the debit's state afterwards before assuming either outcome.

"This debit is not currently stopped, so there is nothing to restore."

What it means. You pressed to restore a debit that was never skipped. Nothing changed.

Why it happened. Restore was pressed on a debit that is not in a skipped state.

What to do. Nothing. The debit is already set to go ahead.

"Could not skip this debit"

What it means. The skip did not save. The debit is still scheduled.

Why it happened. The write failed. Three related wordings behave the same way: "Could not restore this debit", "Could not record skipping this debit" and "Could not record restoring this debit".

What to do. Try again, then reload and confirm the debit's state before moving on. Do not assume a skip worked without seeing it.

"Cancelling the PAD debit request timed out"

What it means. The cancellation may or may not have gone through. The screen stopped waiting before it knew.

Why it happened. The cancellation did not settle in time.

What to do. Reload the screen and check the debit's state before trying again, so you do not cancel twice or leave it running.

"Autopay cannot be turned on for an invoice that is void, written off, or already paid."

What it means. That invoice is in a state where an automatic payment makes no sense, so the toggle refused.

Why it happened. The invoice is void, written off, or already paid.

What to do. Nothing for that invoice. If money is genuinely still owed, the amount needs to be raised on a new invoice.

"Only a file requiring manual resubmission can be resubmitted"

What it means. The debit file you are looking at is not in a state that can be resubmitted.

Why it happened. The file is not waiting for manual resubmission. A related wording is "This file has no pending payments to resubmit", which means the file has nothing left to send.

What to do. Nothing. Check the file's state before trying again.

"The PAD file and bank line cannot be matched. Check their amounts, properties, and reconciliation status."

What it means. The debit file and the bank statement line you are trying to match do not line up, so URBI will not tie them together.

Why it happened. The amounts, the property, or the reconciliation status do not agree.

What to do.

1. Compare the two amounts to the cent.
2. Check both belong to the same property.
3. Check neither one has already been reconciled against something else.

"The PAD file is not currently matched to a bank line."

What it means. You pressed to unmatch a file that was not matched to anything.

Why it happened. Unmatch was pressed on an unmatched file.

What to do. Nothing. The file is already unmatched.

"Manual PAD enrollment is available only for Canadian properties"

What it means. Enrolling someone by hand is not available at this property, for the same reason the bulk path is not: bank debit is Canada only.

Why it happened. The property is not Canadian.

What to do. If the country is recorded incorrectly, correct it on the property. Otherwise this is not available here.

"Selected billing accounts and units must belong to one property"

What it means. The accounts and units you picked are not all from the same property, so the enrolment was refused.

Why it happened. The selection spans more than one property, or names records URBI cannot find. Two related wordings are "One or more selected billing accounts were not found" and "One or more selected units were not found".

What to do. Clear the selection and pick again, staying within one property.

"Manual PAD enrollment timed out. Please try again."

What it means. The enrolment may or may not have completed. The screen stopped waiting before it knew.

Why it happened. The enrolment did not settle in time. The closely related "Manual PAD enrollment failed. Please try again." means it definitely did not complete.

What to do. Reload and check whether the person is now enrolled before trying again, so you do not enrol them twice.

"Bank-debit file not found"

What it means. The record you opened does not exist, or does not belong to the property you are currently in.

Why it happened. The named record could not be found on this property. Four related wordings exist: "Bank-debit payment not found", "Bank-debit rail not found", "PAD enrollment not found" and "PAD file not found".

What to do. Reload the page. If the record still does not appear, check that you are in the right property.

"PAD enrollment property mismatch"

What it means. The record belongs to a different property from the one you are working in, so it cannot be opened or changed from here.

Why it happened. A property boundary was crossed. Related wordings are "PAD enrollment property could not be resolved", "Property scope mismatch", "Property does not match authorized property" and "Document does not belong to this property".

What to do. Switch to the property the record belongs to and open it there.

Messages that look like a problem but are not

These turn up in the same places as the errors above and often prompt a worried call. None of them needs anything from you.

"Not scheduled"

What it means. The First debit date column has no date to show for this row yet.

Why it happened. The row has no first debit date, because the date is set when the agreement is signed, or, on a batch with a staff declaration, when you choose the first debit date in the declaration.

What to do. Nothing. The date fills in once the agreement is signed or declared.

"If signed by 20 April 2026, first payment 1 May 2026"

What it means. This is a conditional date, not a promise. It tells you what the first payment date will be if the person signs by the date shown.

Why it happened. The row's first debit date is a projection and a sign-by date exists.

What to do. Nothing. The real date is set at the moment of signing, and the person is told the real date on screen and by email.

"Replaces an earlier agreement"

What it means. This row's agreement takes over from an earlier one for the same person, using the property's current agreement wording. A second chip may read "Uses the payer's replacement agreement from this property's active agreement template".

Why it happened. An earlier agreement exists for that payer.

What to do. Nothing. This is information only.

"This bank debit agreement was confirmed. It does not replace or change any other agreement."

What it means. Your tick was recorded. The row will go ahead, and nothing belonging to any other agreement was touched.

Why it happened. You confirmed the row.

What to do. Nothing.

"First bill created for 12 residents, ready for the first debit on 15 December 2026. Each invoice is due on the first debit date and is collected by that day's bank file. No invoice email was sent."

What it means. This is the result of committing a batch where you declared signed paper agreements. Each resident was billed for the first debit now. The invoice is dated and due on the first debit date, and the bank file built at 7:00 AM Toronto time on that date collects it. A payer is billed whether or not they have an URBI account. There is no invoice email for this first bill.

Why it happened. This is the normal outcome of committing a declared batch.

What to do. Nothing.

"Setup emails sent automatically to 12 residents. One email each, with the bank, the monthly amount, the debit day and the first debit date."

What it means. Each resident whose row was billed received one setup email, with the subject "Your bank payments are set up: ". It says no action is required, and lists the bank, the account ending, the monthly amount, the debit day and the first debit date, with a "View your bank payments" button.

Why it happened. The email goes out automatically when the import commits, not when you press Send. On a declared batch it is sent once. A sent batch never sends again.

What to do. Nothing. There is no communication date to set and no send to schedule.

"3 still unsigned"

What it means. A counter on the bank debit table showing how many agreements have not been signed yet. It is a running tally, not a fault.

Why it happened. Agreements were created and some people have not signed.

What to do. Nothing at this step. You can chase people later from the Send card with Remind unsigned. This counter applies only to batches where people sign. A batch with a staff declaration has no unsigned agreements.

"No bank debit rows in this batch yet. Upload a bank details file above to add them."

What it means. The bank debit table is empty because no bank details have been staged on this batch.

Why it happened. No bank details file has been uploaded onto this batch.

What to do. If you want bank debits in this batch, upload a bank details file above. If you do not, ignore it and commit the fee rows as normal.

"Institution 003 · Transit 12345 · ending in 6789"

What it means. The masked bank line for a staged row. The full account number is never shown anywhere and is never kept as a file.

Why it happened. The row was staged and matched successfully.

What to do. Nothing. Check the last four digits against the resident's own details if you want extra certainty.

"Matched"

What it means. The staged bank details row was tied to a unit successfully. This is the tag you want to see on every row.

Why it happened. The row resolved to a unit.

What to do. Nothing.

"The bank details file was discarded and nothing was kept."

What it means. Your discard worked. Every staged bank detail on this batch was removed from URBI's records, not hidden from view.

Why it happened. You pressed Discard file and it succeeded.

What to do. Upload a corrected file when you are ready.

"Saved to this unit's PAD Agreements folder. Staff only."

What it means. The signed paper agreement you attached was filed against that unit, where only staff can see it.

Why it happened. The attachment succeeded.

What to do. Nothing.

Related articles

• Bank debit problems and what they mean
• Bank debit rows that are refused or need confirming
• Uploading fees, leases and bank debit agreements in bulk: overview
• What you need before you start
• Preparing your bank details spreadsheet