Reference · built on requestOperator by FibricProperty & tenants

Deposit Return

Combines move-out inspection findings, ledger balances, and the deadline you set, and proposes an itemized deposit disposition.

Request accessPricing ↗

About

Deposit Return is an operator job for the days between a move-out and the deposit statement. It reads move-out dates and lease ledgers from Buildium, Entrata, or AppFolio, the move-out inspection as recorded in Entrata or as an UpKeep or Limble task with its checklist and comments, the parts, labor, and invoices on the repair tasks that followed, and the deposit payment where it was collected through Stripe. It reads the deadline rule and the deduction categories you set per jurisdiction.

For each move-out it proposes an itemized disposition: deposit held, each deduction with the finding and the cost behind it, the ledger balance, and the amount to return. The property manager approves it, changes a line, or waits for evidence. On approval the deductions are proposed as lease charges so the ledger matches the statement.

This is a reference listing. It documents what Fibric would read from Deposit Return and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Move-outs and lease end dates: Buildium move outs and leases; Entrata getLeases filtered by move-out date; AppFolio occupancies
  • Ledger balances: Buildium lease transactions and outstanding balances; Entrata getLeaseArTransactions; AppFolio tenant ledgers and open charges
  • Move-out inspection findings: Entrata getInspections; an UpKeep work order with its form-template checklist; a Limble task with instructions and comments
  • Repair cost per finding: Limble task parts, labor, and invoices; UpKeep work orders and parts
  • The deposit as paid and any refund already issued, from Stripe charges and refunds, where deposits are collected there
  • The deadline rule, the deduction categories, and the normal-wear list you set per jurisdiction, in the operator's configuration

Proposed actions

  • Target capability: propose an itemized disposition per lease: deposit held, each deduction with the finding and cost behind it, balance owed, and return amount
  • Target capability: propose the deadline date per move-out from your rule, and a list of dispositions still unapproved as it approaches
  • Target capability: propose the ledger entries once approved: one charge per deduction on the lease through Buildium lease transactions or an AppFolio charge
  • Target capability: propose a hold where evidence is missing: an inspection with no findings, or a repair task not yet costed, naming what is needed

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Build the statement from Buildium and UpKeep

    A Buildium move out is matched to the UpKeep work order that carried the move-out checklist. Findings with a completed repair work order get their cost; the operator proposes the disposition and the lease charges.

    With Buildium, UpKeep

  • Cost deductions from Limble task invoices

    Each finding on the Limble move-out task is tied to the repair task that followed, and its parts, labor, and invoice total become the deduction. The Entrata ledger supplies the balance owed.

    With Limble CMMS, Entrata

  • Match the deposit to a Stripe charge

    Where the deposit was paid through Stripe, the charge and any refund are read and shown beside the ledger. A refund already issued reduces the return amount on the proposed statement.

    With Stripe, Buildium

  • Keep a deadline list

    Every open move-out carries the deadline your rule gives it. Dispositions not yet approved are proposed as a list, oldest deadline first, with what each one is waiting on.

    With AppFolio Property Manager, UpKeep

Requirements

  • A property connector holding leases, move-outs, and ledgers: Buildium, Entrata, or AppFolio
  • A source of inspection findings: Entrata inspections, or a move-out task in UpKeep or Limble with a checklist
  • A deadline rule and deduction categories per jurisdiction, entered in the configuration
  • Optional: Limble or UpKeep task costs to price deductions, and Stripe to match the deposit as paid
Authentication
Has no login of its own. Ledgers, inspections, task costs, and payments are read, and statements and charges proposed, through the connectors you bind and their permissions.

Limits

  • Deadlines and deduction categories are rules you configure per state or city. The operator does not read statute
  • Normal wear is a judgment. The operator lists each finding and its cost; the manager decides what is deducted
  • It proposes the statement and the ledger charges. It does not send money; the refund is paid through your property system or bank
  • A finding with no costed task behind it is listed as pending and cannot be priced

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Deposit Return ↗

Questions and answers

What does the manager sign off on?
The itemized statement for one lease: deposit held, each deduction with its finding and cost, the balance, and the return amount. Approve, change or remove a line, or hold for evidence. Ledger charges follow only after approval.
What record backs the statement?
The inspection and tasks read, the costs used and where each came from, the rule applied and the deadline it produced, the statement as approved with name and time, and each ledger charge as the property system created it, with its reversal.
Does it pay the refund?
No. It proposes the statement and the ledger entries. The return itself is issued the way you issue it today, through the property system or your bank. Stripe is read only, to match the deposit as paid.
Ask about Deposit Return

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy