AP/AR cycles for global startups: when to formalize
The signals that say ad-hoc AP/AR has aged into something a finance team needs to actually operate.
Early-stage AP/AR is run from a shared inbox, a Bill.com or Mercury account, and the founder's memory. It works until it does not. Knowing where the line is matters because crossing it without noticing turns finance into a perpetual fire.
Five signals AP/AR has outgrown ad-hoc
- More than three vendors are on retainer with recurring monthly bills.
- More than two customers are on multi-month payment terms.
- Any one vendor or customer accounts for over 10% of monthly cash movement.
- The founder has been pinged twice in a month about a late payment they did not know about.
- The team has missed an early-pay discount or hit a late-pay penalty in the last quarter.
What formalization looks like
A formal AP/AR cycle is not enterprise software. It is a process with named ownership: one person who runs AP, a defined payment cadence, a defined approval threshold, an aging review every two weeks, and a hand-off to the close cycle at month-end. Tools follow process — Bill.com, Ramp, Brex, Mercury, or just a shared spreadsheet works at small scale. The breakthrough is the process discipline, not the tool.
For most companies, this transition happens around the 50–80 person mark or when monthly AP volume passes $100k. Companies that miss the transition keep paying vendors out of the founder's calendar instead of a process.