A committed commercial promise can turn operational detail into a lasting system choice.
The pressure is to meet a precise obligation without embedding fragile exceptions into the billing model.
Who you’d be doing this for
“If the invoice doesn’t match our tax and entity rules, it doesn’t enter the payment queue.”
Kabir Thakur · Procurement Operations Director
Owns invoice acceptance and vendor compliance for a multinational design organization.
What is at stake
A signed enterprise deal requires new regulated invoicing before the next renewal, and configuration locks soon. You have to settle tax handling, invoice format, and credits while some tax exceptions are still unverified.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- enterprise commitment vs. configuration flexibility
- tax defensibility vs. operational scale
- automated classification vs. human verification
- customer-specific acceptance vs. standardized billing
- deadline certainty vs. exception completeness
Why Figma
At Figma, the tension can matter when enterprise collaboration work must fit into varied procurement and compliance environments.
Written with these in mind
Not your kind of problem? 11 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.