4 ms·

For me the real pain was paying vendors or freelancers. They all had to be input as an additional vendor, which is reasonable, but there were dozens of fields w

For me the real pain was paying vendors or freelancers. They all had to be input as an additional vendor, which is reasonable, but there were dozens of fields within each vendor, many of which were esoteric in they're labeling (likely a fault of implementation on our side). Then I would get a rejection via email that a particular field wasn't filled out (why wasn't it a required field?), and it was often hard to find where to input that field -- very unintuitive. I think I even had to go through a company admin once to add an associated email address to a vendor. Beyond that, just the philosophy of creating a "purchase order" to pay a UX researcher who did 10 hours of work over three months seemed goofy -- purchase order is what I think of when doing something like ordering printer paper, not getting an invoice paid.

rad_gruchalski 4y ago
> purchase order is what I think of when doing something like ordering printer paper, not getting an invoice paid How can you pay an invoice for a service / item you haven’t purchased? If you buy a service from a supplier, you raise a po, you pay an invoice based on the po. As a supplier, I always ask for a po.
- ghaff 4y ago
  And there's often also an approved vendor process as well. Big companies are mostly not OK with just expensing some random new supplier. And yeah, there's a lot of paperwork but maybe you're hiring this gal because she's your sister. Maybe she's really good. Or maybe you're just funneling some money to a family member. As companies scale up they need controls for a lot of things even if they're legit 95% of the time. And, again, not a software issue. It's a perhaps necessary bigco process issue.