Collections follow-up: every question

1. How you work today for your version, wk Dec 7

What we heard on our call on Nov 6, about how your team chases late payments today. Correct anything that's changed. Confirm each line, or write what's different.

1. About 160 invoices are past due on a Monday. (Our call on Nov 6)
2. Your 10 largest accounts get no reminder until you've said so. (Our call on Nov 6)

2. Who's involved for deep dives, wk Nov 30

At the deep dives we meet the people who chase payments today, each for about 45 minutes. Confirm each line, or write what's different.

• Owns it: Ewart Pillay, AR lead. Approves: Ewart Pillay, AR lead. Decides: Ingrid Vasskog, controller.
• Also: AR clerk (name to come), joins the deep dives.
• Also: Sales manager (name to come), not at the deep dives.

3. When reminders go for your version, wk Dec 7

When each reminder goes out, counted in days from the due date. Confirm each line, or write what's different.

• Day 7 after the due date: first reminder, by email.
• Day 14 after the due date: second reminder, by email.
• Day 21 after the due date: third reminder, by email.
• Day 28 after the due date: a call from your ar team.

4. Rules and exceptions for your version, wk Dec 7

What your version does with the accounts that need care. Confirm each line, or write what's different.

1. Reminders go from your AR inbox. (What we assumed)
2. Which accounts should never get a reminder?
3. When should an account stop getting new orders? (usually your controller)

5. Your files for build and test, Dec 14 to Jan 22

Your written rules and a few past examples, so we build and test on your real work. Send them as they are; our NDA covers them.

1. Your credit and collections policy, if it's written down.
2. An aged receivables report from the last month-end.
3. Ten reminder emails your team has sent.