Skip to main content

Deposit readiness

Deposit readiness tracks the operational status of an expected reservation deposit. It helps Sales and Administration see whether a deposit is expected, due, supported by submitted proof, overdue, or linked to a separately recorded payment.

It is an attention and coordination tool—not the financial ledger.

Information to review

Deposit readiness may include:

  • expected deposit amount;
  • due date;
  • current readiness status;
  • proof-submitted indicator;
  • proof or document link;
  • confirmation or review date;
  • assigned owner;
  • notes; and
  • optional link to an existing payment record.

Operational statuses

The exact live labels should be verified, but staff should distinguish conditions such as:

  • expected/not yet due;
  • due today or due soon;
  • proof requested;
  • proof submitted and awaiting review;
  • overdue;
  • linked to a verified payment; and
  • no longer applicable because the reservation was released or cancelled.

Do not mark a status financially confirmed without following the Finance procedure.

Not financial reconciliation

Deposit readiness cannot create a payment, confirm a bank transfer automatically, generate a receipt, alter a balance, or replace the payment ledger. Record and verify the payment separately.

When proof is submitted

  1. Record that proof was received.
  2. Confirm it belongs to the correct buyer and reservation.
  3. Assign Finance review.
  4. Enter or confirm the reference information available.
  5. Keep buyer communication accurate: proof received and under review.
  6. Finance verifies the transaction through the approved source.
  7. Finance searches for and records the payment.
  8. Link the existing payment where supported.
  9. Update operational readiness and reservation follow-up separately.

Overdue readiness

When the expected date passes:

  • review buyer activity;
  • check whether proof or a payment was received elsewhere;
  • review the reservation expiry;
  • contact the buyer according to the approved process;
  • assign any internal Finance check;
  • record the result; and
  • decide whether extension, continued follow-up, or release is required.

Do not move the due date just to remove the overdue indicator.

Example: proof submitted but no bank reference

A fictional buyer, Tanya Training, uploads a transfer screenshot before reservation expiry, but the bank reference is missing.

  1. Deposit readiness is updated to show proof received and awaiting verification.
  2. Finance reviews the proof and requests/locates the reference.
  3. No payment is created until the transaction is verified according to policy.
  4. The reservation owner monitors the expiry and obtains any approved extension.
  5. After verification, Finance records the payment and the readiness record links to it where supported.
  6. If verification fails, the reservation outcome is handled separately.

Common mistakes

  • Treating proof-submitted as paid.
  • Entering the expected amount as a financial transaction.
  • Updating readiness without the correct reservation.
  • Allowing an overdue item to remain without owner or next action.
  • Linking the wrong payment because amount/date look similar.
  • Using readiness notes to store banking details.
  • Forgetting to update the reservation after Finance review.

Suggested training media

Screenshot space: Add a deposit-readiness list showing expected, proof-submitted, overdue, and payment-linked fictional examples. Label due date, owner, amount, status, and related reservation.
Screenshot space: Add a detail view showing proof, missing bank reference, Finance review assignment, and optional payment link.
Diagram space: Add two parallel lanes: Reservation/Deposit readiness tracks expectation and proof; Payments tracks verified transaction, receipt/reference, and balance effect.
Video space: Record a 5–7 minute Tanya Training scenario from proof receipt through Finance verification and payment linking, including the unsuccessful-verification path.