Identify discrepancies and risks

Identify discrepancies and risks — real work, not an imagined feature: named inside 16 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

16career tasks name it
4prompt heights

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 found numbers that don't agree between the closing trial balance and the statutory report. Send…
I found numbers that don't agree between the closing trial balance and the statutory report. Send the reconciliations and a short cover note to Marco in audit and to Anika in finance, ask Marco to confirm which adjustments came from his schedules and ask Anika to sign off that the statutory classification is correct, with a Thursday close-of-business deadline — check that every figure in the reconciliation links to a source before sending.

Improve — make it easier to accept

+
Before I hand this to the external auditor, make the discrepancies obvious and reduce their review…
Before I hand this to the external auditor, make the discrepancies obvious and reduce their review time — show the total variance at the top, group unreconciled items by account and amount, highlight anything over 10,000 rupees in orange, and add a one-line explanation for each material variance so a reviewer can decide in three seconds what needs follow-up.

Decide — diagnose the stuck moment

+
I matched the trial balance to the statutory report and hit a 47,321 deficit I can't trace. The…

I compared the trial balance totals and the statutory report and found a 47,321 mismatch.

I matched the trial balance to the statutory report and hit a 47,321 deficit I can't trace. The team members are Marco in audit who prepared the closing adjustments and Anika in finance who signs the statutory numbers. I am afraid I will miss a recurring booking error and the auditors will flag it, but I don't know which ledgers have been altered post-close. What's the most defensible next step to find the source quickly and to preserve audit trails?

Become — change the pattern

+
Across several closes we keep finding small but repeated variances between our trial balance and…

Recurring unexplained variances between internal ledgers and statutory reports.

Across several closes we keep finding small but repeated variances between our trial balance and statutory reports that cost us rework and audit queries. We lose time re-tracing journal origins and lose credibility with auditors. Which habit should I change in month-end close so these mismatches stop happening: change who posts adjustments, require a one-line justification and source cell for every adjusting journal, or enforce a pre-signoff tie-out checklist with named owners? Recommend the single change that reduces rework most quickly.

Where the evidence lives

Who was seen doing this, and what people really ask.

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.