◆ C#

Perform month-end and quarter-end tasks

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 close for the payment processing service, ensuring all transactions from…+
Run the month-end close for the payment processing service, ensuring all transactions from yesterday are reconciled and the general ledger is updated. Then, kick off the quarter-end report generation for the fraud detection system, making sure it pulls data up to midnight on September 30th and is ready for review by the finance team.
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 run the month-end close, make sure the reconciliation process accounts for the recent…+
Before I run the month-end close, make sure the reconciliation process accounts for the recent change in how we handle chargebacks, and flag any accounts that show unusual activity so I can investigate them before the books are locked.
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 payment gateway just reported a discrepancy between our transaction count and theirs for…+
The payment gateway just reported a discrepancy between our transaction count and theirs for September 29th.
The payment gateway just reported a discrepancy between our transaction count and theirs for September 29th, and I'm worried it will hold up the month-end close. The finance team needs this done by 5 PM today, and I can't tell if it's a data sync issue or something deeper. What's the most likely cause, and what's the fastest way to diagnose and resolve it without involving the external vendor unless absolutely necessary?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI always seem to be scrambling to fix reconciliation issues right before month-end, losing…+
I always seem to be scrambling to fix reconciliation issues right before month-end.
I always seem to be scrambling to fix reconciliation issues right before month-end, losing hours that push other critical tasks. It feels like I'm always reacting instead of preventing. What habit should I change to catch these discrepancies earlier, so month-end is less of a fire drill and more predictable?
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.