The need
Getting a payment agreement out the door took five separate steps.
Someone calculates the schedule. Someone prepares the document. An attorney has to approve it, then it goes out, and then somebody follows up. When each of those lives in its own file or email thread, finding the latest version or the next due date is one more job on top of the real one.
Payment is the app I built for DHN so all of that stays in one place, from the figures behind an agreement to the reminder that goes out next.
What I built
Everything about an agreement
happens in one place.
Payment works out plans, stipulations, and payoffs from the case’s ledger figures, fees, costs, and dates. Staff edit the wording right next to those numbers and export a PDF or Word file when it’s ready.
Attorneys get an approval link by email and decide from there. The decision is saved with the document, so staff can follow the agreement through delivery and keep the proof with the file.
My wider work with DHNPayment / Agreement workflow
Calculate & prepare
Payment plans, stipulations, or payoffs
Current document + linked revisions
Attorney approval
Review by email. Decision recorded.
Follow through on delivery
Keep the approval and supporting proof with the file.
- Payment datesDue-date reminders
- Returned paperworkDocument-return reminders
Sent notices remain in the record.
The decisions behind the build
Three things I made sure
it keeps track of.
Every earlier version stays attached.
When the wording or the figures change, the previous version stays linked to the current one. Staff can see what changed without digging through old files.
The attorney’s approval is on the record.
Each approval link is signed and expires on its own. The decision is stored with the document, so there is a record to point to all the way through delivery.
Follow-up runs on a schedule.
Due-date and document-return reminders sit with the agreement, along with a log of the notices already sent. Staff can see what’s coming up and what has already gone out.