◆ C#

Perform month-end closing procedures

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun the month-end closing script for September, generate the preliminary balance sheet and…+
Run the month-end closing script for September, generate the preliminary balance sheet and income statement, and send them to Sarah in accounting by 3 PM today.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize the Q3 financial statements for the CFO, make sure the revenue recognition…+
Before I finalize the Q3 financial statements for the CFO, make sure the revenue recognition figures are clearly reconciled against the sales ledger. Flag any discrepancies over 0.5% and suggest potential reasons for them.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new general ledger system is showing a variance in the cash accounts compared to the old…+
The new general ledger system is showing a variance in the cash accounts compared to the old system, and the finance team is demanding an explanation by end of day.
The new general ledger system is showing a variance in the cash accounts compared to the old system, and the finance team is demanding an explanation by end of day. I'm afraid of signing off on numbers that aren't fully reconciled, but I don't have a clear path to identify the source of the discrepancy quickly. I can't tell them that the migration tool had known issues. What's the likely diagnosis here and the best next move?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently spend too much time manually verifying individual transactions during month-end…+
I consistently spend too much time manually verifying individual transactions during month-end close.
I consistently spend too much time manually verifying individual transactions during month-end close, especially when dealing with intercompany transfers. This always pushes me past the deadline. What habit should I change to automate more of this verification or flag issues earlier?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from C#'s own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.