Auditors — how much of your week goes to tying exceptions back to the actual source doc by hand?
Not an auditor myself, I write software for accounting workflows, and I keep hitting the same wall I can't size properly.
The tools I've seen will tell you a transaction looks risky, and then the person still has to open the ledger, find it, and match it by hand to the invoice or receipt to confirm it's real. The flagging is automated; the proving isn't.
Trying to figure out if that manual proving step is genuinely where the hours go, or if I've fixated on something minor:
- Is the tie-back to the underlying document a real time sink, or already handled by what you use?
- When something's flagged, do you trust an auto-generated trail, or is doing the tie-out yourself part of how you sign off?
- Does testing the whole population instead of a sample actually matter to you, or does sampling cover you fine?
u/corporate_retard — 1 day ago