Reference · built on requestOperator by FibricProperty & tenants

Delinquency Notice

Rent ledgers matched to payments and your grace rules, with a late notice, a fee, a payment plan, or a hold proposed per account.

Request accessPricing ↗

About

Rent is due, the ledger shows a balance, and a payment may be on its way. Delinquency Notice reads all of that before anyone writes to a resident. It reads lease ledgers and outstanding balances from Buildium, delinquent charges per occupancy from AppFolio Property Manager, and lease AR transactions from Entrata. It reads the payments that have settled in Stripe, and the grace days and fee terms you set.

When a balance is past its grace day and no payment is in flight, it proposes one path: a late notice by email or SMS, a late fee on the ledger, a payment plan, or a hold that pauses notices while a person talks to the resident. You approve the path. Nothing is charged, posted, or sent until you do.

This is a reference listing. It documents what Fibric would read from Delinquency Notice 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

  • Lease transactions, charges, and outstanding balances in Buildium through /v1/leases, and lease AR transactions and invoices in Entrata through getLeaseArTransactions
  • Open charges, delinquent charges, and recurring charges per occupancy in AppFolio Property Manager
  • Charges, refunds, and balance transactions in Stripe, and the events Stripe sends when a payment succeeds or fails, matched to the resident
  • Grace days, late fee amounts, and notice steps as you configure them per property or lease type
  • Notices already sent and their delivery events: delivered, bounce, and dropped from SendGrid, and bounces and suppressions from Postmark
  • Notes and lease activities recording a dispute, a promise to pay, or an agreed plan

Proposed actions

  • Target capability: propose a late notice by email through SendGrid or Postmark, or by SMS through Twilio, naming the balance, due date, and grace day
  • Target capability: propose a late fee as a lease charge in Buildium, or a charge on the occupancy in AppFolio Property Manager
  • Target capability: propose a payment plan as a lease note plus the recurring charges that match it, for a person to confirm with the resident
  • Target capability: propose a hold on the account: no further notices or fees while a dispute, a plan, or a pending payment is open
  • Target capability: propose the formal notice text your jurisdiction requires, for a person to review and serve

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

What you can build

  • Send the first late notice on the day after grace

    AppFolio Property Manager lists a delinquent charge. Grace has passed and Stripe shows no charge for the resident. The operator proposes a SendGrid notice with the balance and due date for your approval.

    With AppFolio Property Manager, Stripe, Twilio SendGrid

  • Cancel a notice when the payment lands

    A Stripe charge succeeds after the notice was drafted. The operator withdraws the proposal, and proposes a note on the Buildium lease recording the payment date instead.

    With Stripe, Buildium

  • Text before the fee posts

    The day before a late fee would post, the operator proposes a Twilio SMS naming the amount and the date. If the resident replies, the fee proposal is held for a person.

    With Twilio, Entrata

  • Hold an account while a plan is agreed

    A note on the Entrata lease records a promise to pay. The operator proposes a hold: no notices or fees until the plan date, then a Postmark reminder if the balance remains.

    With Entrata, Postmark

Requirements

  • A property connector with lease ledgers: Buildium, AppFolio Property Manager, or Entrata
  • A payment connector where residents pay outside the property system, such as Stripe, so a settled payment cancels a notice
  • A messaging connector for notices: Twilio SendGrid, Postmark, or Twilio
  • Your rules: grace days, fee amounts, the notice sequence, and which accounts a person must handle
Authentication
It reads ledgers and payments and drafts notices through the property, payment, and messaging connectors you attach, with the scopes you grant each one; it holds no account credentials itself.

Limits

  • It moves no money. It never charges a card, pulls a bank payment, or refunds. Fees are ledger entries you approve.
  • A payment the property system has not yet posted looks unpaid. The proposal shows the last payment date and any Stripe charge it found.
  • Statutory notice forms, service methods, and deadlines differ by place. It drafts to the template you give it and a person serves it.
  • One notice per balance per step. A bounce brings back one proposal with the other channel, not a stream of resends.

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 Delinquency Notice ↗

Questions and answers

What decision is put in front of me for a late account?
One path per account: notice, fee, plan, or hold. You see the ledger balance, the charges behind it, the last payment and any Stripe charge found, the grace rule applied, and the exact notice text. Approve, pick another path, or edit the text.
What is recorded after I approve?
A receipt per account: the balance and transactions cited, the path chosen, who approved, the message id and delivery event from SendGrid, Postmark, or Twilio, the ledger charge id if a fee was posted, and how to reverse the charge.
Does it ever post a fee or send a notice without me?
No, and it has no way to. Every notice, fee, plan, and hold waits for approval, and each is applied once. If the rules do not match an account, or a dispute note exists, it proposes nothing and lists the account for a person.
Ask about Delinquency Notice

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