Post, sorted

Scanned post should not need a person to work out whose it is twice. Each letter is matched to a client as it arrives, filed in a click, named the way you would name it, and sent to whoever has to act.

Post is the least glamorous problem in a practice and one of the most persistent. Somebody opens it, somebody works out whose it is, somebody scans it, somebody files it under a name that made sense at the time, and somebody emails the manager who needed to see it. Often that is the same somebody, doing the same thinking twice.

It arrives already matched

Scanned post comes into AccountingFlow matched to a client. You are confirming a match rather than performing a search, which is a much smaller job — and it means a backlog can be cleared in one pass instead of one letter at a time.

Filed the way you would file it

Filing names the document the way your firm names documents, so the client file stays navigable. Assign it, title it and notify the right person from the same screen, with the attachment going along with the notification — the preparer, the reviewer or the partner, whoever actually has to act.

Letters that are not jobs

Plenty of post needs marking as sent to the client, or as spam, and nothing more. That happens from the row itself, so the queue reflects reality instead of filling with items nobody will action.

And the quiet nudge

Post left unactioned for three days nudges the preparer. Once — because an alert that repeats is an alert people learn to ignore.