The need
Getting a payment agreement out the door took five separate steps.
Staff had to calculate a payment schedule, prepare the agreement, get an attorney’s approval, send it, and follow up. The figures and documents were spread across files and email threads, making it hard to find the current version or check the next due date.
I built Payment to handle those steps together.
What I built
Staff prepare the agreement.
Attorneys approve it by email.
Staff enter the case’s ledger figures, fees, costs, and dates to work out a payment plan, stipulation, or payoff. They can edit the agreement beside those numbers and export it as a PDF or Word document.
The attorney receives an approval link by email. Once the document is approved, staff can send it and keep the approval and delivery records with the agreement.
More of my work for DHNPayment / Agreement workflow
Calculate & prepare
Payment plans, stipulations, or payoffs
Current document + linked revisions
Attorney approval
Review by email. Decision recorded.
Send the agreement
Save the approval and delivery records with the agreement.
- Payment datesDue-date reminders
- Returned paperworkDocument-return reminders
Staff can see which notices have been sent.
The decisions behind the build
Keeping versions, approvals,
and reminders with the agreement.
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.
Approval links are signed and expire. The attorney’s decision is saved with the document and remains available after it’s sent.
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.