Why do I keep missing approvals and duplicate invoices?

You move through a stack of invoices. You approve, code, pay. Somewhere in that motion, a duplicate slides past you. Or an approval that should stop you doesn't. You find out later, when someone else catches it. Or worse, no one does. This is not because you do not know the rules. You know what a duplicate looks like. You know which approvals matter. The failure happens in the moment you choose speed over the check. You tell yourself you will catch it on the next pass. You rarely do. Nothing here will give you a new system to memorize. It will give you a smaller, harder habit: the pause before you click approve. That pause is yours to take or skip. Choose to take it.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

A little to learn

1:1 with AureliusWith others (a Pod)

Mostly you & the coach

A little with peers

You already know what a duplicate or a bad approval looks like; the gap is attention and habit under pressure, which coaching builds better than instruction.

How the two dials adapt to you →

What’s really going on

You are not missing these because you lack a checklist. You are missing them because you let speed replace attention. Choose to stop before every approval. Ask: has this vendor billed this amount before? Does this have the right signature? That pause catches most of it.

🔒 What you’ll build togetherUnlock by starting

A moveBefore you approve any invoice, say the vendor name, amount, and date out loud. Then search for that exact match in the last 90 days.

A moveSplit your inbox into two piles: checked and unchecked. Never let them touch.

A movePick one fixed time each day for a second check on every approval. Same time, every day, no exceptions.

A moveWhen the stack feels too long to pause, that feeling is the warning — not the stack. Choose the pause anyway.

A moveEach week, pull three invoices at random. Trace each one back to its origin. Make this nonnegotiable.

What changes unlock by starting

You catch duplicates before they are paid, not after.
Your approval pace slows slightly, and your error rate drops sharply.
You stop depending on others to catch what you missed.
You become known as the checkpoint, not the bottleneck.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.