Why rush invoices deserve their own sample stratum
Rush and emergency invoices often bypass the quiet controls that look healthy in a random sample. Here is how we weight them in a financial audit.
A random sample across all invoices can make an application look orderly. Rush invoices — those flagged for same-day payment, marketing events, or plant downtime — are where approval paths shorten and evidence thins.
In a financial audit of invoice processing applications, we usually carve rush items into their own stratum. Even a modest count of rush invoices can carry outsized statement risk if they skip three-way match or land with a single approver who also releases payments.
Ask AP for the configuration that defines “rush,” not only the informal habit. Some applications use a reason code; others rely on a payment term override. Document both before you pull the sample. Then test whether the reason code still appears on the payment proposal your treasury team sees.
If your internal audit plan treats all invoices as one population, consider a short control walkthrough focused on rush handling before the next full engagement.