Invoice and payment follow-up
A commercial janitorial company that invoices office buildings monthly. One property-management client's invoice slips past terms. The owner is excellent at keeping buildings spotless and terrible at asking for money — not from weakness, but because the same person doing the asking has to preserve the relationship. So the invoice ages, and the work it paid for recedes into the past.
What does this demonstration show?
This demonstration follows one past-due janitorial invoice from first reminder to payment received. Deptly starts with a friendly note to the accounts-payable contact, fixes a missing PO number without making the client ask twice, confirms the corrected invoice landed, and verifies the payment actually arrived — because a promise to pay is not closure. Amounts, payment plans, and disputes always stay with the owner.
The workflow, step by step
Real product behavior with example names and details. The notes beside each step explain what is happening — including where Deptly asks instead of acting.
Day 1 past due
Deptly
The invoice for last month's janitorial service is now one day past terms. Cadence starts after your two-day grace window.
Deptly watches the invoicing tool the company already uses; past-due status is the trigger. Nothing is sent yet — the owner's cadence starts with a grace window, because most late invoices are oversights, not refusals.
Day 3
Deptly
Hi — a friendly note that the invoice for last month's service may have slipped through. Happy to resend the PDF or the payment link, whichever is easier for your system.
The first touch assumes good faith and goes to the accounts-payable contact — not the building manager the crews work with day to day. The tone is the owner's; the relationship stays untouched.
Day 5
Property manager (AP)
Can you resend it with the PO number on it? Our system rejected it without one.
An unexpected reply, and the workflow adapts: this isn't a refusal, it's a fixable paperwork problem. Recognizing the difference is most of the job.
30 minutes later
Deptly
Of course — here's the corrected invoice with the PO number from our service agreement. Same amount, same terms.
Deptly pulls the PO number from the contract records and fixes the paperwork itself — adding a reference to an invoice is an approved routine. Changing the amount never would be.
Day 9
Deptly
Just confirming the corrected invoice made it into your system okay — anything else needed from our side?
The follow-up keeps gentle momentum without pressure. Every message so far has been helpful rather than demanding — the cadence escalates in firmness only per the owner's rules, and never past them without approval.
Day 12
Property manager (AP)
Approved on our end — payment is scheduled for Friday.
A promise to pay is progress, not closure. The workflow stays open and watches for the money — this is exactly the point where manual follow-up usually stops and shouldn't.
Day 15
Deptly
Payment received and matched to the invoice in the books. Loop closed.
Deptly verifies the payment actually arrived and reconciles it in the invoicing tool. Closure is money in the account and matched in the books — not a scheduled promise.
Friday
DinboxOwner brief
The past-due invoice is paid and matched — resolved with a PO correction and three friendly touches. You never had to make the awkward call.
The brief also notes the standing rule: any invoice that reaches the end of the cadence, or any client who disputes a charge, comes to the owner before a single firm word is sent. Collections-style language is never used without approval.
What the owner brief says
You don't watch this workflow run. It rolls up into your weekly brief alongside everything else that was handled — what closed on its own, and the few things waiting on you.
A full sample brief lives on the proof and examples page.
Your weekly brief
deptly · weekly summary
- The past-due janitorial invoice is paid and matched in the books — the delay was a missing PO number, fixed the same day it was raised.
- Three touches total, all to the AP contact, all in your tone; the building manager relationship was never part of the conversation.
- Nothing was escalated: no dispute, no payment-plan request, and the cadence never reached the stage that needs your approval.
- One other invoice enters the cadence next week when its grace window ends; the rest of the month's invoices are current.
Example — how this workflow appears in your weekly brief
Verified closure
The invoice was paid in full and matched in the books — closure verified by the payment landing, not by a promise — and the client relationship came through without a single awkward conversation for the owner.
Closure means the loop is confirmed done — not that a message was merely sent. That standard, and everything behind it, is explained on trust and control.
The boundary this workflow ran inside
The steps above where Deptly asked instead of acting are the point, not a limitation. Every workflow runs within rules you approve — anything outside them waits for you.
Deptly handles
- Routine steps like the ones above — replies, follow-ups, reminders, status updates, scheduling holds
- Logging every action so the weekly brief writes itself
- Chasing the open loop until it verifiably closes
Deptly asks first
- Anything that touches price, scope, or an exception to your rules
- Messages that fall outside the wording you approved
- Situations the rules don't cover — flagged to you, not guessed at
Always human
- Pricing, hiring, and how the work gets done
- Sensitive customer conversations
- Final say on anything Deptly flags
How those rules get set up in your first weeks is on how it works.
See this loop in context
- The capability behind this demonstration: Get Paid & Finish the Back Office
- Deptly for cleaning, restoration & exterior maintenance
- Deptly for landscaping, tree & heavy property services
- Deptly for home services & emergency trades
- Deptly for boutique legal services
- See everything Deptly handles
- All proof and examples
Questions owners ask
The workflow runs on the invoicing tool you already use — QuickBooks, a field-service suite, or whatever generates your invoices. Named systems are examples, not guaranteed integrations; what connects and how is confirmed during discovery before anything goes live.
The tone is yours, the messages assume good faith, and reminders go to the accounts-payable contact rather than the person your crews work with. The cadence gets firmer only per your rules and never crosses into collections-style language without your explicit approval.
Disputes are never argued by Deptly. The moment a client contests a charge, the thread comes to you with the full history — the invoice, the service records, the conversation — so you decide how to handle it with everything in front of you.
Payment received and matched in your books. A promise to pay, a scheduled payment, or an approved invoice keeps the loop open and watched — the workflow closes only when the money verifiably arrives, because that's the part that actually pays your crews.
Routine reminders inside your cadence run on their own, as do paperwork fixes like adding a PO number. Changing an amount, offering a payment plan, sending final-notice language, writing anything off, or responding to a dispute always comes to you first — money decisions stay human.
Your workflows next
What would this look like in your business?
Answer a few questions about where work waits in your week and get an honest read on which loop Deptly should close first.