The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I have the vendor invoices and the matching purchase orders ready. Send the reviewed payment batch…
Execute — do the immediate task
+I have the vendor invoices and the matching purchase orders ready. Send the reviewed payment batch to Priya in procurement and then to Omar in accounts payable for payment approval, in that order, with payment scheduled for Wednesday. Before you send, verify every invoice has a PO number, the amounts match the PO lines, and that no invoice is missing a receipt or approval signature.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I forward this payment packet to procurement, make it easy for Priya to approve — put the…
Improve — make it easier to accept
+Before I forward this payment packet to procurement, make it easy for Priya to approve — put the total payable and any early-pay discounts at the top, make the PO-to-invoice mismatches obvious with color, and flag invoices older than 30 days or missing receipts. Also list three things that would make a reviewer hesitate so Priya can resolve them quickly.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I matched invoices to POs and found two with line-item mismatches. Priya in procurement will decide…
Decide — diagnose the stuck moment
+Two vendor invoices in the batch mismatch their POs and procurement needs fast answers.
I matched invoices to POs and found two with line-item mismatches. Priya in procurement will decide whether to approve or query, and accounts payable waits for her sign-off; payment is due Wednesday. I’m unsure whether the vendor billed for legitimate change orders or we failed to update the PO. What’s the best rapid checklist I should run and the exact evidence I should send Priya so she can decide without a phone call?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep hitting PO versus invoice mismatches that stall payments and erode vendor trust. Priya…
Become — change the pattern
+Frequent PO/invoice mismatches that delay payments every cycle.
We keep hitting PO versus invoice mismatches that stall payments and erode vendor trust. Priya spends hours chasing approvals and AP delays payments. Which process habit should I change to stop mismatches — stricter PO change capture, a pre-payment QC gate, or a vendor invoice template — and how do I roll it out with minimal extra work for procurement?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Where the evidence lives
Who was seen doing this, and what people really ask.
Accountant AssistantAccountantAuditorBilling SpecialistBookkeeperChartered Accountantalso: Review financial statements
Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.