A supplier payment block is a status flag applied to an invoice or to a supplier account that prevents any payment from being released until the underlying issue is documented and cleared.
A supplier payment block operates at two levels. An invoice level block stops a single document, usually because a match failed or a required approval is missing. A supplier level block stops every invoice on that account, and is used for compliance holds, disputed relationships, or unverified bank details.
Five triggers account for most blocks:
- a supplier price variance above the agreed matching tolerance
- a quantity billed higher than the quantity actually received
- a missing goods receipt on a purchase order invoice
- a bank detail change not confirmed through a second channel
- a hit from duplicate invoice detection on an invoice already recorded
The structural weakness of payment blocks is asymmetry. Blocks are set automatically by the system and released manually by a person. When release depends on a buyer answering an email, the blocked queue grows quietly and produces the two costs the block was meant to prevent: late payment penalties and a forfeited early payment discount.
Phacet treats each block as a case with a documented reason and a named owner rather than a flag in a queue. The invoice is compared against its purchase order, its receipt and the supplier price book, and the specific discrepancy is routed to the person who can resolve it, so release happens before the next payment run rather than after it.
