Why an amount or a date was refused

Wealthru checks every amount and every date before it saves anything to your books. If an entry comes back refused, this explains what the message means and what to do about it. These checks exist because a wrong figure in your books is much harder to fix later than a refused entry now.

"Amount must be at most $20,000,000.00"

Every money field in Wealthru accepts up to $20,000,000.00. That is the ceiling for a single entry: a rent charge, a payment, an expense, a deposit, a valuation, a mortgage, anything with a dollar amount.

Almost every time you see this, it is a typing slip, usually a stray zero or a decimal point in the wrong place. Check the amount and try again.

If you genuinely need to record something larger than $20 million as one entry, split it into the real underlying items. That is better bookkeeping anyway, because a single twenty-million-dollar line has no audit trail behind it.

"Amount must be at least $0.01"

A money entry has to move some money. Zero is not an amount, and a negative one is a different thing entirely: to reverse money you already recorded, void or archive the original rather than entering a negative figure. See How rent charges are created each month for voiding a charge, and Archive and restore a property, lease, or tenant for an expense.

"must be a plausible date"

A date has to be a real day, and it has to fall inside a sensible window for the field you are filling in. Three things get caught:

• A day that does not exist. 30 February and 31 June are the common ones. Wealthru used to accept these and store the next real day instead, which meant your record was quietly dated wrong. It now refuses them, so pick the day you meant.
• A year that is a typo. 0202 instead of 2020 is the usual shape.
• A date outside the window for that field. The window depends on what the field is for, which is why the same date can be fine in one place and refused in another. See below.

"A payment date cannot be in the future"

Dates that decide when money hit your books can never be in the future. That covers a payment's received date, a deposit's received date, an owner payout, and a refund. Money that has not arrived yet is not money you can record, and dating a receipt forward would move income into a period that has not happened, which puts your year-end out.

Backdating is fine and often correct. If you are entering rent a tenant paid last month, put last month's date on it. The only limits are that it cannot be in the future, and it cannot land in a period you have already closed.

Dates that reach a long way back or forward

Some fields are meant to hold old or distant dates and accept them happily:

• when a property was bought, and when a mortgage started
• when an appliance was acquired, and when its warranty expires
• an insurance policy's effective and expiry dates
• a tenancy's start and end dates

A property bought in 1985 and a 25-year warranty are ordinary things to record, so these fields go back to 1900 and forward fifty years. Day-to-day fields like a charge due date are tighter.

"That charge was voided, so a payment cannot be attached to it"

You voided a rent charge, and the page you are recording the payment from was opened before that happened, so it still lists the charge. Voiding a charge reverses it in your books, so money can no longer be attached to it.

Refresh the page and then either:

• pick the charge the payment actually covers, or
• record the payment without choosing a month. It lands as a credit on the tenancy and you can attribute it to a month later from the payment's row. See How rent charges are created each month for what voiding a charge does to your books.

"That deposit was already recorded" or "That expense was already saved"

You tapped save twice, or retried after the connection dropped. Wealthru recognised the second attempt as the same one and returned the entry it already made, so nothing was doubled.

This now covers every money entry you can make by hand: rent payments, prorated charges, rent backfills, deposits, expenses, payment plans, refunds to a tenant, capital assets, and paying a tenant their deposit interest.

Two details worth knowing:

• Do not change the amount before retrying. If a retry carries a different amount or category, Wealthru refuses it rather than guessing, because it cannot tell whether you meant to correct the first entry or add a second one. Refresh the page, check what actually saved, and go from there.
• Two genuinely separate entries still both save. Recording two $500 deposits on the same tenancy on the same day works normally. The protection only covers a retry of the *same* attempt.

"Could not reach the server. Check your connection, then try again."

The connection dropped before Wealthru could answer, so the form does not know whether the entry saved. It hands the button back to you rather than leaving it stuck on "Saving", and your retry carries the same attempt, which is what makes it safe to just tap again. If the first attempt did save, the retry shows you that entry instead of adding a second one.

Settling a deposit, returning one, or reversing a refund

These three work differently, and the outcome is the same. They change an entry that already exists rather than creating a new one, so Wealthru does not need to recognise your retry at all:

• Settle or return a deposit. If it was already settled, you see the same settlement again. The money goes back to the tenant once.
• Reverse a refund. If it was already reversed, you get a message saying only an applied refund can be reversed. That reads like an error, and it means the reversal you asked for has already happened. Refresh the page to see it.

If you still cannot save

Check the amount and the date one more time, then refresh the page. A refused entry never leaves a partial record behind, so nothing is half-saved and there is nothing to clean up before trying again.