WORKED EXAMPLE · FICTIONAL DETAILS
A payment reminder is different from an invoice tracker
A reminder answers “what should I ask next?” An invoice record documents a request for payment. A bank or payment record helps confirm receipt. These jobs overlap, but they are not interchangeable.
Use the right source for each fact
Take the amount, currency and due date from your actual agreement and issued invoice. Take received-payment status from the appropriate financial records. Use a follow-up workspace to record who you are waiting on and when you will contact them. A client promise is useful context, not settled revenue.
A worked example
A fictional consultant has an invoice for an agreed project milestone due on 18 November 2026. On 19 November they plan a manual check-in. If the client says payment is scheduled for 21 November, record that as a promise while preserving the original due date. Only mark the payment received after checking the relevant records.
Keep currencies and unknowns clear
Do not add unrelated currencies into one total or convert them using an invented exchange rate. If the amount is not known, leave it unknown rather than entering zero as a fact. Separate disputed items from confirmed amounts. A recorded open amount is neither a forecast nor money recovered by the product.
What PakkaFollow does
The reviewed product stores follow-up stages, recorded amounts, dates and user-entered updates, with export controls. It does not issue tax invoices, collect client payments, reconcile a bank feed or replace accounting software. Paid workspace availability remains subject to the subscription release gates.
Editable message example
Check names, dates, amounts and permissions. Send through your usual channel only when you choose.
Request a status update
Hi Sam, I’m checking on the milestone payment due on 18 November. Could you confirm its current status and whether you need the invoice reference again?