Internal Audit Support in a PSU Context

The chief internal auditor of a Navratna in Ranchi asked for an agent that would 'do the quarterly IA'. The vendor demo opened a chat window, ingested last year's observation register, and produced a paragraph that sounded like a para. The CVO, who had not been invited, asked a smaller question: who will sign the observation if the model is wrong about a related-party invoice? Nobody had a name.

This guide is for compliance leads, IA cells and company secretaries in Central Public Sector Enterprises. It is not a promise that software will replace an IA charter. It is a map of what an agent may retrieve, what it may draft, and what still has to be a named officer under the company's audit manual, the CVC's expectations of a CVO, and the Digital Personal Data Protection Act, 2023 where personal data sits in the packet.

Internal audit in a PSU is not a private-sector SOX theatre and it is not CAG. CAG is constitutional. IA is a board instrument, usually reporting through the Audit Committee, overlapping with vigilance, statutory audit and sometimes the chief risk officer. An agent that blurs those four desks will be treated as a control failure even if the retrieval quality is high.

Not legal advice. Read your IA charter, the CVC manuals your CVO actually cites, DPE guidelines that apply to your CPSE, CERT-In log floors, and counsel. This is a field file, not a statute.

What IA is allowed to automate — and what it is not

Automate retrieval. Circulars, standing orders, previous paras, vendor master extracts, GeM invoice PDFs, and the department's own closed observations are high-volume and low-discretion if the corpus is tagged. An agent that returns the 2018 CVC circular on tenders with a hash and a page pin is a clerk. That is the useful job.

Do not automate the observation. The sentence 'the indent was split to stay under the DGM's power' is a finding. Findings require a human who can be examined. The India AI Governance Guidelines of November 2025 talk about People First and accountability as sutras. They are not a CVC circular and they are not a substitute for the officer who initials the draft para.

Do not let the agent write the management reply. Replies are negotiated, political, and often wrong in useful ways. A generated reply that concedes a fact the plant later wants to contest is a gift to the next auditor.

DPDP still applies to vendor KYC packs, employee disciplinary files, and any citizen-adjacent grievance the IA cell samples. An IA agent that embeds those packets into a vendor-hosted vector store is processing personal data. Write fiduciary and processor. Write a training ban. Write an export the company owns.

Three desks, three jobs. Do not let one chat window wear all three hats.

Desk	What an agent may do	What still needs a named officer
Internal audit	Retrieve corpus, sample packets, draft working-paper notes	Issue the observation, grade the residual risk, close the para
Vigilance / CVO	Surface prior CVC citations and the Integrity Pact text	Register a complaint, decide a regular inquiry, write the CVO note
Statutory / CAG interface	Reconstruct the four-sentence packet for a named file	Sign the statement that the packet is complete

The working paper the agent must leave

Every retrieval used to support a draft observation needs a working paper the IA cell owns after the vendor leaves. Minimum fields: workflow id, model and prompt hash, document identifiers and page pins, the sampling rule, the draft sentence, the officer who accepted or rejected the draft, and the time. CERT-In's 28 April 2022 directions already expect specified ICT logs for 180 days in Indian jurisdiction. That floor is not a licence to delete the administrative working paper at day 181.

If the vendor's console summarises conversations after ninety days, you do not have a working paper. You have a demo. Internal audit that cannot replay last quarter's sample will be treated as not having sampled.

• Pin the circular, not the model's memory of the circular.
• Store the packet on the company's file store, not only in the GPU node's disk.
• Separate the IA tenant from the production plant agent. Shared embeddings across vigilance and operations are how a para leaks into a shop-floor chat.
• Record overrides. An officer who discards a draft is doing the job. Do not punish the discard rate.

Sampling without becoming the data-science wing

IA cells that ask for 'AI-driven 100 percent testing' are buying a slogan. One hundred percent of invoices can be retrieved. One hundred percent cannot be professionally judged in a quarter. Write the sampling rule the charter already uses. Let the agent apply it mechanically: every invoice over a threshold, every related party, a random 5 percent of the rest. Then a human reads the exceptions.

If the rule cannot be written in a sentence, the model is choosing the sample. That is a scope decision. Scope is not a tool call.

How this meets the CVO and the Audit Committee

The CVO will not grade your model card. They will ask whether a complaint about the same vendor last year was in the retrieval set. Put prior vigilance outcomes in a purpose-tagged corpus the IA agent can see only on a ticket. Do not dump the CVO's open files into the same index the plant helpdesk uses.

The Audit Committee wants residual risk, not token counts. One slide: workflows live, packets reconstructable, personal-data purposes written, vendor training banned, next quarter's sample already drawn. If any cell is red, say so. A green dashboard that hides an unlogged override is worse than an amber one.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

We will be faster if the model writes the para.

You will be faster until the first wrong para. Speed of drafting is not the constraint in a PSU IA cell. The constraint is courage, evidence and a named officer. Keep the draft. Do not skip the initial.

Our SI already has an 'audit copilot' SKU.

Ask for the working-paper export on a dark VM, the purpose tags, the training ban, and whether vigilance files share an index with the plant chatbot. If those four answers are slides, it is a SKU. If they are a packet, score it.

CAG will want the same tool.

Do not invent a CAG AI circular. CAG reconstructs cases. Give them a packet. Do not offer them your IA chatbot as if it were the company's books.

Logging everything creates DPDP risk.

True, and it is an argument for purpose, retention and access, not for silence. An unlogged finding that names a vendor employee is still personal data. It is also an unaccountable finding.

A four-week playbook for the IA cell

Run this before you issue an indent. If week two fails, you do not have a tool problem. You have a charter problem.

1. Week 1: list live IA workflows. For each, write what the agent may retrieve and what a named auditor must still sign. Get the CIA and the CVO to initial the list so the desks do not collide.
2. Week 2: pick three closed observations. Rebuild the packet from systems you own. If you need the vendor on the call, the packet is not yours.
3. Week 3: classify the corpus. Personal data, vigilance-sensitive, commercial-in-confidence, public circulars. Separate indexes. Write the DPDP purpose for anything that identifies a person.
4. Week 4: tabletop with internal audit playing the Audit Committee. One member names a para. The CIA has twenty minutes. Missing fields become change tickets, not slides.

How this shows up in the file

Subject: Agent support to internal audit — retrieval only, named sign-off retained.

This company will use an agent to retrieve circulars, prior paras and sampled packets for the internal-audit cell. Observations, risk grades, management replies and vigilance decisions remain with named officers under the IA charter. Each draft will leave a company-owned packet: workflow, model hash, retrieval set, sampling rule, officer action.

Vendor consoles are supporting papers. They are not the working paper. Personal data in IA files will carry a purpose tag and will not train a vendor model. This note is an internal aid. It is not legal advice.

This article is informational field guidance for Indian public sector undertakings and their vendors, not legal, audit, labour, energy-regulatory, banking-regulatory or procurement advice. Confirm the live circular, DPE guideline, CVC instruction, sector regulator text, purchase manual and your counsel before you file it.