Business Email Compromise: Documents Required
By Advocate Panchanand Shaw, Bar Council of West Bengal · Published 19 Nov 2026 · Corporate & Compliance
A company's file is complete when three propositions each have a document behind them: that the domain and mailbox were the company's, that the instruction which moved the money was not, and that the money left on a date it can pin down. Everything below serves one of those three, and a folder of screenshots serves none of them.
What a company's bundle has to prove
Corporate fraud files fail for a reason that has nothing to do with the merits: the company proves the loss but not the mailbox, or proves the mailbox but not the authority of the person who signed the complaint. Three propositions have to be documented separately, and each has its own set of papers.
The table is the whole checklist in the order a cyber cell will read it. The sections after it take each group, say who issues the paper, and say what to do when it does not exist.
| Document | Who issues it | What it proves |
|---|---|---|
| Certificate of incorporation, PAN and GST registration | Registrar of Companies, Income-tax Department, GST portal | That the complainant entity exists and is the entity that lost the money |
| Board resolution and letter of authority | The company, under its articles | That the signatory may complain and instruct counsel |
| Domain registration invoice and registrar record | Domain registrar or reseller | That the mail domain belongs to the company |
| Mail tenant record and subscription invoice | Mail provider, or the IT administrator | That the compromised mailbox sat inside the company's tenant |
| Raw headers of the fraudulent message | The mail administrator, exported from the mailbox | Where the message came from, and that the display name was not the sender |
| Audit log of mailbox access and rule changes | Mail provider's admin console, or the mail server | When the intruder was inside, and what was altered |
| The genuine invoice and the altered one | The vendor, and the intruder respectively | That the bank details were changed without the vendor's authority |
| Vendor's written confirmation | The vendor, on letterhead | That no request to change bank details was ever made by it |
| Bank statement and payment confirmation | The remitting bank | The debit, the date, the beneficiary and the reference |
| Certificate for the electronic records | The person in charge of the record, usually the IT head | That the exports are true copies of what the systems hold |
The corporate authority set comes first
The officer at the counter is entitled to ask who is speaking for the company, and the answer is a document rather than a designation. The set is short: the certificate of incorporation or, for a firm, its registration; the PAN of the entity; the GST registration where the transaction was a business supply; and a board resolution authorising a named person to lodge the complaint, to pursue the hold and to instruct advocates.
The resolution should be drafted for the purpose rather than borrowed from another file. It needs to name the transaction, name the signatory, and authorise the specific acts, because a resolution that authorises one director to file a suit does not authorise him to sign a police complaint. Where the resolution is passed by circulation, attach the signed copy with the date, and where the articles require a particular quorum, note it on the face of the resolution.
Along with it go the signatory's own identity and address proof, his appointment letter or DIN where he is a director, and a letter of authority if someone other than a director, such as the chief financial officer or the company secretary, will attend the counters. An LLP adds its LLP agreement and the designation of the partner signing. None of this is onerous, but all of it is checked, and a file returned for want of authority loses the days that matter most.
Proving the domain and the mailbox were the company's
This is the group companies most often omit, and without it the complaint describes a fraud against an unnamed mailbox. Four papers establish the point, and the first two are usually obtainable the same afternoon.
- The invoice or renewal receipt from the domain registrar for the domain in question, showing the company as the registrant.
- The registrar's or a public WHOIS record for the domain, showing the registrant organisation, the creation date and the name servers.
- The mail tenant record from the provider's admin console, showing the domain as a verified domain and the compromised mailbox as a user within it.
- The subscription invoice for the mail service, which ties the tenant to the company's payment instrument.
Where the domain is held through an agency or a reseller, the invoice may carry the agency's name rather than the company's, and the WHOIS record may be redacted for privacy. Ask the reseller for a registrant confirmation on letterhead, and attach the company's own payment record. Where the mail is hosted on a company server rather than a cloud tenant, the equivalent documents are the server's configuration record showing the domain, and the administrator's certificate identifying the server and the mailbox store.
The reason this group matters procedurally is narrow and decisive. A requisition to a foreign mail provider has to identify the tenant and the account precisely, and a provider will not search on a guess. A bundle that names the tenant, the domain and the mailbox is a bundle that can be acted on.
Headers and logs, not screenshots
A screenshot of an email shows what somebody's screen displayed. The raw header shows what the mail system actually received, and the difference is usually the whole case.
The header set to export is small: the full received chain from the top of the message down to the mailbox, the return path, the message identifier, the reply-to address, the authentication results for the sending domain, and the originating internet address. A display name that carries the vendor's name, sitting on a return path at a different domain, is the fraud in one line, and it is a line no screenshot contains. Export the message as a file rather than printing it, and keep the exported file, not only a copy of it.
The audit log is the second half, and it answers what the header cannot. Ask the administrator for the sign-in log covering the period of access, showing the addresses and locations from which the mailbox was opened, the events that created or changed mailbox rules, the events that added a forwarding address or a delegate, and any change to the registered authentication methods. Most cloud mail consoles export this as a dated file with an event identifier per row, and that export should be taken before anyone cleans the mailbox, because retention in the console is measured in days for some categories and months for others.
Where the compromise began in the vendor's own mail system, the same two exports are needed from the vendor, and the request for them should be in writing on the first day. A company that asks on the twentieth day is asking a vendor to produce logs that its console has already aged out.
The two invoices, and the vendor's written denial
The documentary core of a business email compromise is a pair: the invoice the vendor actually issued, and the invoice the company paid. Laid side by side they show one difference, which is the account into which the money was to be paid, and that difference is the offence.
Supporting the pair are the purchase order or contract under which the payment fell due, the mail thread in which the instruction to pay into the new account was given, and the internal approval that authorised the payment. That last document matters more than finance departments expect, because it shows the company acted on the instruction in the ordinary course rather than carelessly, and it identifies the employee who could speak to it.
The vendor's written confirmation is the document that converts a commercial disagreement into a fraud, and it should be asked for in terms. What is needed is a letter on the vendor's letterhead stating that it did not change its bank details, did not send the altered invoice, and did not authorise anyone to do so on its behalf. Where the vendor's own mailbox was compromised, add its complaint or FIR copy and its audit log export, since the two files then corroborate each other.
If the vendor will not give the letter, its silence is itself a fact to place before the investigating officer, and the request with its acknowledgement should be attached. A vendor that has been paid twice is sometimes reluctant to confirm anything, which is a reason to ask early rather than a reason not to ask.
The money trail, and what the remitting bank must certify
The bank documents are the ones the cyber cell acts on, and the standard to aim at is the one the hold requires: an identifiable credit into an identifiable account.
- The statement for the paying account, sealed at the branch or downloaded with the bank's digital signature, for the period covering the debit.
- The payment confirmation or advice, showing the value date, the amount, the beneficiary name, the account and the branch identifier.
- The unique transaction reference for a domestic transfer, taken from the advice rather than from memory.
- For a payment abroad, the remittance message copy, which the authorised dealer bank holds and will give the customer on request, together with the correspondent bank's details.
- The bank's own fraud-desk complaint reference and the date it was given, which fixes notice.
Ask for the beneficiary particulars in full. Statements sometimes truncate the account or show only the name, and the requisition to the receiving bank needs more. Where the paying bank will not release the remittance message, the investigating officer can requisition it, and the request should say what is wanted rather than asking for the file.
The certificate for the company's electronic records
Every export in the bundle is a copy of an electronic record, and copies are admitted on the strength of a certificate. Under s. 63 of the Bharatiya Sakshya Adhiniyam 2023 the certificate is signed by the person in charge of the computer or the record, identifies the record, describes the manner of its production, and gives the particulars the section requires.
In a company that person is the IT head or the company secretary, not the lawyer and not the director who signs the complaint, because the certificate speaks to custody and to the system. Where there are several exports from different systems, take one certificate for each, since a single certificate covering a mailbox export and a bank download will be signed by someone who controls neither in full. Include the hash value of each exported file where it can be generated, and record in the certificate how it was generated.
The practical effect is worth stating plainly. A certificate that matches the export, with the file name, the date range and the hash, is rarely challenged. A certificate signed by someone who has never seen the console invites the one question the company cannot answer at that stage. The form and the way it is used are set out in the guide to a certificate under s. 63(4) of the Bharatiya Sakshya Adhiniyam, and the standards for metadata extraction are described in the note on metadata extraction and admissibility.
When a document does not exist: the substitutes
Corporate files have gaps that cannot be filled by explanation, and each has an accepted substitute. The order below runs from the preferred paper to the last resort.
- Registrant confirmation from the reseller on letterhead in place of a WHOIS record redacted for privacy, with the company's payment record attached.
- Tenant verification record and subscription invoice in place of an admin console export the provider will not release to the customer.
- Message file exported from the recipient's mailbox in place of the sender's copy, where the message was deleted from the company's own mailbox.
- Event list exported from the admin console in place of a full audit log, where retention has already aged the detail out.
- Vendor's letter and its own complaint in place of the vendor's audit logs, where the vendor's provider will not release them.
- Bank's payment advice in place of the remittance message, until the authorised dealer bank produces the copy.
What has no substitute is the board resolution. A complaint signed without authority is returned on the day it is presented, and the delay runs from there.
What to do next
Take the exports before anyone tidies the mailbox: the message file with full headers, the audit log for the period of access, and the list of rules and delegates as they stood. Then the authority set, the domain and tenant papers, the invoice pair, the vendor's letter, and the bank documents, each in three copies with the transaction reference on the first page. A bundle assembled in that order is one a cyber cell can act on without a second visit. The chambers of Advocate Panchanand Shaw, before the Calcutta High Court and the district courts of West Bengal, review company bundles and draft the certificate, the resolution and the complaint that go with them. To have a bundle checked, write through the contact page, and see also what to preserve in the first forty-eight hours.
Need help with a cyber crime matter?
Tell me what happened and I will tell you what to file, where, and by when. First conversation is free.
Call +91-9007000603 WhatsAppFrequently asked questions
Is a screenshot of the fraudulent email enough for the cyber cell?
No, and it is the commonest reason a company file stalls. A screenshot shows a display name, which anyone can set. The raw header shows the return path, the received chain and the authentication results, and the audit log shows when the mailbox was opened. Export the message as a file and take the certificate that covers it.
Who should sign the certificate for a company's electronic records?
The person in charge of the record, which in practice is the IT head or the company secretary who controls the mail tenant. Not the advocate, and not the director who signs the complaint, unless that director also administers the system. Where exports come from different systems, take a separate certificate for each rather than one covering all.
What if the domain record is in the hosting agency's name?
Ask the agency for a registrant confirmation on its letterhead, stating that the domain is held for the company, and attach the company's own payment record for the domain and the mail subscription. Where the agency will not confirm, the tenant record from the mail provider and the subscription invoice usually establish control well enough for a requisition.
Can the company rely on the vendor's own complaint instead of its own FIR?
No. The vendor's complaint is evidence in your file, not a substitute for it. Your entity lost its own money and must be the informant on its own FIR, with its own board resolution and its own transaction reference. The two complaints corroborate each other, and the investigating officers can share the requisitions between them.
Does the bank statement have to be a sealed copy?
A sealed statement is accepted everywhere and should be obtained when there is time. A download with the bank's digital signature is accepted in most counters and can be verified by the branch. What the file cannot carry is a screenshot of net banking, which proves neither the balance nor the source.
Information for general guidance only and not legal advice. Provisions cited follow the Information Technology Act 2000, the Bharatiya Nyaya Sanhita 2023 and the Bharatiya Nagarik Suraksha Sanhita 2023.
Related articles
Cyber crime lawyer in your city · Bank account freeze help · Contact