Archive fields that nobody fills

Invoice processing applications often ship with dozens of archive attributes: cost center, project code, tax category, receiving reference. If half of them are optional, busy operators leave them blank. Months later, a review cannot reconstruct why an invoice was paid.

In our audits we pull a random set of archived invoices and count blank required-for-control fields — even when the application itself treats them as optional. The conversation with AP is practical: which fields genuinely support month-end and external review, and which can stay unused without consequence.

Making two or three fields mandatory usually beats a long training memo. Pair that with a weekly exception list for blanks that still slip through, and the archive becomes something a future colleague can trust.