Agree the job before selecting the tools
Start with following up invoices already issued by the business. Write down which customers, currencies, countries and invoice types are included, and what the process excludes. Invoice creation, supplier payments, tax filing, payment processing and legal collection are different jobs. Naming these boundaries avoids a sales conversation becoming accidental permission to change accounts or contact customers. Your team should be able to explain the scope in a few clear sentences.
For each decision, name a responsible person and a cover arrangement. Separate approval of a reminder draft from approval of a credit, revised payment terms or changed payment instructions. If an outside provider is involved, record the agreed responsibility and access rather than assuming a service name establishes it. Discuss your accounting system and main difficulty with Procora without sending passwords, bank credentials or customer-sensitive documents.
Make the data and the contact route usable
Review a small sample containing an open invoice, a part payment, a credit and a dispute. Check invoice references, due dates and remaining balances against the approved source. Identify how recently it was updated and how differences are resolved. A connection logo or a successful login does not prove that the exact records needed are available. Agree what happens when access fails, a payment is unallocated or information is older than the team's accepted limit.
Check who should receive invoice correspondence, which address sends it and who monitors replies. Map reminders already sent by the accounting system, colleagues and any existing supplier. Decide who owns each invoice so one process does not request payment just after another promises to review it. The same review should check approved invoice copies and links, the recipient's access and the correct language; keep country, language and currency as separate choices.
Plan the ordinary case and the point where it stops
Review the wording before discussing timing. Use the checked balance and due date, a clear reply route and payment instructions already approved by the business. Set reasonable intervals, working-day handling, a maximum ordinary sequence and an owner review. Repeating a message indefinitely is not a complete process. If someone asks for different terms, the next step is an authorised review, not an automatic acceptance hidden inside a friendly reply.
Define a response for missing documents, a disputed amount, bounced email, a promised payment date and a customer who says paid. Each needs a task, owner and review date. Keep the disputed balance visible while deciding whether ordinary reminders should pause. An awaiting-verification state must preserve the amount owed until the approved source confirms and allocates the payment. Write down who can pause the entire process and who reviews queued messages before it restarts.
Test without customers, then review the evidence
Use fictional records to test ordinary and difficult paths before any operational approval. A draft must stay a draft; a simulated payment must be labelled and kept away from customer records. Check that partial payments leave the correct remainder, credits are separated from cash and a dispute is not counted twice. Check the pause control and deliberately test missing or stale information. A successful happy-path demonstration is not enough to establish readiness for live sending.
Choose the first review date before starting. Useful review items include dated open balances, ageing, unresolved replies, owner tasks and verified payment allocations. Note what improved, what remains unclear and what should stay paused. Do not label an invoice balance as new revenue or a payment promise as collected cash. The checklist below can be printed for a team discussion; ticked items are local to this page and are not an approval record or a saved setup.
Opens your browser's print dialogue for this checklist. No PDF is supplied. Ticks are local, are not saved and do not approve or activate a service.
Invoice-follow-up setup checklist
For planning and team review · Procora Invoice Follow-up is planned
Business: ____________________ Owner: ____________________ Review date: ____________________
Prepare scope, records, contacts, approval rules, exceptions, testing and pause controls. Use a printable HTML checklist without uploading financial records.
A tick records your review here, not an operational approval. Confirm scope, source access and sending authority separately before any live customer follow-up.