For institutional buyers, net-30 is not a courtesy. It’s the mechanical reality of how AP (accounts payable) processes work. A buyer-side workflow typically looks like:
- Day 0: Service delivered, invoice generated
- Day 1-5: Invoice received and matched to PO (purchase order)
- Day 5-15: Invoice approved by relevant department head
- Day 15-25: AP processes payment in the next check run
- Day 25-30: Payment issued (ACH or check)
For the buyer, paying faster than net-30 is mostly impossible without expedited-payment processes that AP discourages. Asking AP for exceptions creates friction that hurts the relationship.
For vendors and interpreters, net-30 means:
- Cash flow must accommodate a 30-day lag between work delivered and payment received
- Net-30 is the floor; net-45 and net-60 are common at large hospital systems and most government entities
- Invoicing precision matters: an invoice missing a PO number, a service date, or an interpreter ID often gets kicked back, restarting the 30-day clock
Platforms that aggregate institutional billing (one invoice covering all assignments per organization per month) typically improve collection speed because they reduce the per-invoice administrative overhead on AP. Individual interpreters invoicing institutional buyers directly should expect longer collection times and price accordingly.
For interpreters working through a platform, net-30 from the buyer is decoupled from interpreter payout: the platform typically pays the interpreter on a faster cycle (often within days of session attestation) and absorbs the cash-flow lag itself.