The controller at fictional North Pier Studio asks for customer, vendor, and G/L setup before the first order. Use the numbered requests. Done means the requested cards exist with correct classifications and the duplicate-review vendor is blocked.
North Pier's controller needs a small set of master records before operations begin. The request names the record numbers as well as their labels. Those numbers let the reviewer distinguish an intended edit from a change to a similar card.
Complete the setup and retain the earlier choices as you move between pages. The final recommendation asks which evidence establishes readiness. A list with the right names is insufficient when the account categories or blocks differ. This case stays within company master data; tenant creation, permission assignments, tax registration, and data migration require controls outside the browser model.