# Review overdue-invoice reminders Canonical page: https://agents.paretoid.com/workflows/review-overdue-invoice-reminders/ Category: Operations & Reporting Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Separate unpaid invoices from paid, disputed, paused, and payment-plan exceptions. Status: Proposed / not tested. The public discussion supports the problem; the method source supports only the documented features. No outcome from this adapted recipe has been verified. Verification: The linked sources support the complaint and documented method components. We have not run this recipe or verified its results. The example below is synthetic, not a customer result. ## The problem Separate unpaid invoices from paid, disputed, paused, and payment-plan exceptions. Why it matters: An outdated payment snapshot can trigger a reminder for an invoice already paid or under review. Checking holds, disputes, and payment plans first helps billing staff avoid inappropriate follow-ups. ## Sources and evidence - pain: [Pain evidence: Handling Unpaid Client Invoices](https://www.reddit.com/r/LawFirm/comments/1qtc2o6/handling_unpaid_client_invoices/) Handling Unpaid Client Invoices, 2026-02-01, older. OP reports unpaid invoices despite a payment policy. WHY WON’T THEY PAY, 2025-04-09, separately describes overdue balances despite reminders. - pain: [Pain evidence: WHY WON’T THEY PAY](https://www.reddit.com/r/LawFirm/comments/1jvg690) Additional pain account; self-reported, not independently verified. - method: [Method: Clio bill reminders](https://help.clio.com/hc/en-us/articles/9285345945243-Bill-Reminders) Clio bill reminders documents automated schedules for approved unpaid bills, with client-wide scope and issue-date scheduling. Active operating-account payment plans can pause reminders; trust-account payment plans do not automatically do so. Source checked: October 15, 2026. Pain reports are self-reported and identities are unverified. Method documentation supports components, not a tested end-to-end workflow. ## Suggested approach Start when: Approved cadence reached 1. check unpaid status, dispute/hold and payment-plan flags 2. Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes. 3. The responsible staff member checks the draft against the source records and approves any separate action. ## What you need - Clio Manage billing/report permissions and a defined currency, bill scope and cutoff. - Approved reminder policy and authoritative dispute, hold, payment-plan, pause and reminder-history records. - Firm-approved Excel; optional Copilot entitlement and tenant approval for the exact minimized data. Native Excel analysis can be done manually if Copilot is absent. - Keep raw exports and identifying source pointers in a separate restricted location. The AI workbook contains only approved alias-based tables and visible policy/scope text, never raw client records on another tab. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-checked proposed route; source collection and human approval required - Accounts receivable includes approved outstanding bills, not drafts. It does not supply every reminder-control field. - No reminder is eligible until latest payments and holds are checked; a stale balance or unknown pause state blocks sending. Access and setup: - Actual account access, plan and source-data completeness have not been tested. ### 1. Obtain the named report, with its real scope Tool: Clio Manage; optional Manage AI report link Location: Diamond/gem > AI Launchpad > Ask a question; or Reports > Classic reports > Reports > Billing > Accounts receivable If Manage AI is available, ask for the named report with the exact period, then open its report link. Otherwise use the native Reports menu shown. Set the actual filters, choose CSV under Output format and generate. Keep the original headers, filter settings, generation time and control totals. Use the actual Balance, Status, Invoice number and Due date, distinguishing invoice rows from interest/subtotal rows. Do not calculate amount due from the report Amount field alone. Prompt: ```text Open the Accounts receivable report for [APPROVED PERIOD AND SCOPE]. Return its report link; do not change records or infer missing data. ``` Expected output: Native Accounts receivable CSV and a saved scope/control note. The kit schema is a later staff mapping. Next step: Inspect the actual report and source items before creating a separate deidentified workbook. Check before continuing: Report/AI availability varies by plan and permissions. A returned link is not an arbitrary data-query result; verify the report name and filters. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/9290078155803-Clio-Manage-Reports-Presets-and-History https://help.clio.com/hc/en-us/articles/29658606211483-Manage-AI-Generate-Reports-and-Monitor-Performance https://help.clio.com/hc/en-us/articles/14330519112987-Clio-Manage-Billing-Reports ### 2. Map the observed records to the starter input Tool: Excel and authorized staff Location: Separate analysis workbook > Home > Format as Table Map invoices.csv: invoice_id from the actual invoice reference; client_alias/matter_alias from the restricted crosswalk; outstanding_amount from verified invoice Balance; due_date/status from source. Inspect the original bill for issue_date and currency. Read current payment plan and the firm’s actual dispute/hold/pause/reminder records locally, then fill paid_status,dispute_flag,hold_flag,payment_plan_type,manual_pause,last_reminder_date only when verified. Paste approved-reminder-policy.txt into Policy and cutoff/unknown semantics into Scope. Create named tables for Invoices. Put the policy and review scope in visible worksheets or paste them into the next prompt. Expected output: Invoices table with source-backed controls; unknown is not false. Next step: Check the mapping against each original source before using AI. Check before continuing: Aliases and missing policy fields are staff-created; do not relabel a native export as the kit schema. Unknown stays blank/unknown, not false or zero. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ### 3. Review the bounded evidence with Copilot Tool: Excel Copilot, optional Location: Approved analysis workbook > Copilot icon at lower right > Chat only Use Chat only and submit the prompt. Without Copilot: apply the approved reminder rules, checking every control field and invoice balance. Prompt: ```text Using Invoices, Policy and Scope, return invoice_id, observed outstanding amount/currency, eligibility=review/hold/not_due/unknown, exact policy rule, missing evidence and row citations. Exclude paid, disputed, held, paused or incompatible payment-plan items under Policy. Unknown control/history blocks a send recommendation. Draft neutral reminder text only for staff-verified eligible rows using supplied facts. Do not add interest, fees, threats, deadlines or payment instructions; do not send or edit. ``` Expected output: Billing-review queue and conditional drafts. Next step: Copy the draft exception list to the reviewer; retain row references. Check before continuing: Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel https://support.microsoft.com/en-us/excel/copilot/frequently-asked-questions-about-copilot-in-excel ### 4. Approve the review result Tool: Responsible staff reviewer Location: Reviewed local worksheet Billing staff refresh the actual invoice/payment state immediately before approving a draft. The responsible lawyer reviews disputes/holds and approves exact recipients and wording through the firm’s communication process. Expected output: Approved draft or explicit hold, with evidence of final balance check. Next step: Any external message, source change, payment or deletion requires its own authorized process. Check before continuing: No automatic reminder or charge. Report arithmetic is not collection authority. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ## What you will get reminder-review.csv: invoice_id, client_alias, queue_status, payment_check_required, policy_rule_id, evidence_rows, placeholder_draft. No live changes. ## Human review and limits Billing staff reconcile current payments before sending; lawyer handles disputes and representation decisions. Test paid-since-export and trust-payment-plan edge cases. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved. ## Original prepared-input schema invoices.csv: invoice_id, client_alias, matter_alias, issue_date, due_date, currency, outstanding_amount, paid_status, dispute_flag, hold_flag, payment_plan_type, manual_pause, last_reminder_date. approved-reminder-policy.txt. Synthetic example input: ```text INV1: overdue but paid INV2: trust-account payment plan INV3: outstanding, no dispute or hold ``` Expected synthetic output: ```text INV1: exclude INV2: manual payment-plan review INV3: candidate reminder, recheck current payment first ``` Failure check: Billing staff reconcile current payments before sending; lawyer handles disputes and representation decisions. Test paid-since-export and trust-payment-plan edge cases. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/a13-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/a13/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/a13/README.txt) — Required inputs, file use, review steps and limits - [Invoices blank CSV](https://agents.paretoid.com/assets/starter-kits/a13/invoices-template.csv) — Blank input headers for invoices.csv - [Invoices synthetic example](https://agents.paretoid.com/assets/starter-kits/a13/invoices-example.csv) — Synthetic test records for invoices.csv - [Approved reminder policy template](https://agents.paretoid.com/assets/starter-kits/a13/approved-reminder-policy-template.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Approved reminder policy example](https://agents.paretoid.com/assets/starter-kits/a13/approved-reminder-policy-example.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a13/expected-results.txt) — Compare a pilot result with the planted exceptions ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Review this deidentified overdue-invoice table against our approved reminder policy. Exclude paid, disputed, held and manually paused items. Surface payment plans and multiple matters for the same client for review. Draft a neutral reminder with invoice placeholders only. Do not add interest, threaten collections, suspend representation, change terms or send. INPUTS invoices.csv: invoice_id, client_alias, matter_alias, issue_date, due_date, currency, outstanding_amount, paid_status, dispute_flag, hold_flag, payment_plan_type, manual_pause, last_reminder_date. approved-reminder-policy.txt. OUTPUT reminder-review.csv: invoice_id, client_alias, queue_status, payment_check_required, policy_rule_id, evidence_rows, placeholder_draft Use only the supplied synthetic or firm-approved inputs. Cite source row or page IDs for each finding. Keep unknowns unresolved. Return a draft for the responsible staff reviewer. Do not send messages, connect accounts, change records, move money, or make legal decisions. Keep source files unchanged. If an input or permission is missing, list what is needed and stop that check. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.