Wire Fraud · Federal Charges
Can Automated Emails Support Separate Wire Counts?
An automated message can support a separate wire-fraud count, but the transmission, its purpose, and the defendant’s intent still require proof.
By Heath Hyde · East Texas and statewide
Eligible to Practice in Texas
Attorney at Law
Bar Card Number: 00796807
TX License Date: 11/01/1996
214 Connally St Ste A
Sulphur Spgs, TX 75482-2612
Short answer: Yes, it can. Automation does not take a transmission outside the wire-fraud statute. But the number of emails alone does not prove that every count is valid. For each charged wire, the government still has to prove the scheme, an interstate or foreign transmission, the wire’s role in carrying out the scheme, and the defendant’s intent.
An order example
A customer places an online order. The company’s software sends a confirmation, then a shipping notice. Months later, an indictment calls the order part of a fraud and charges each email as its own count. This example is hypothetical.
| Charged message | What the government might argue | What the defense may point to |
|---|---|---|
| The order confirmation sent on the day of purchase. | It reassured the buyer and kept the payment in place. | It went out automatically before anyone reviewed the order. |
| A shipping notice falsely saying the order is on its way. | It helped induce a second payment the seller knew would not be filled. | The notice was routine, and the sale had already ended. |
| A third copy of the shipping notice found in an email archive. | It is another wire. | It is a record of the same transmission, not a new one. |
A message does not need to ask for money to matter. Whether it furthered the scheme depends on the facts.

What the statute asks
Section 1343 of Title 18 covers schemes to obtain money or property by fraud and wire communications sent to carry them out. Separate qualifying transmissions can support separate counts, even when they relate to one scheme.
| Part of the charge | Question to ask about each count |
|---|---|
| The scheme | What scheme does the indictment describe? |
| The transmission | Did this message travel in interstate or foreign commerce? |
| The wire’s purpose | What did this message do to carry out the scheme? |
| Intent | What did this defendant know and intend? |
A system log is evidence to examine. It is not a substitute for proving these points.
Build a record for each count
Start with the date, recipient and description in the indictment. Then find the message in the source system, keep its original time zone and note any conversion.
| Record | What it may help establish |
|---|---|
| The indictment. | The communication the count identifies. |
| Message ID, headers and routing. | The message and the path it took. |
| Delivery or bounce records. | What the system recorded about delivery. |
| Template history and deployment logs. | The version that was active on the date sent. |
| Trigger rules and configuration. | How the process generated the message. |
One email can show up in an inbox, an archive and a discovery export. Count the transmissions the evidence shows, not the files. Two messages built from the same template may still be separate transmissions. A current screenshot of that template may not show what a recipient saw months earlier.
Who knew what?
A system can send a message without anyone pressing a button. In United States v. Richards, the Fifth Circuit explained that a defendant need not personally make or direct the communication. The test it applied was whether the use of the wires was reasonably foreseeable. Richards involved wire transfers and faxes in an investment scheme, not automated email, so its reasoning has to be applied to the facts of the charged case.
| Evidence | What it can show | What it cannot show alone |
|---|---|---|
| Configuration history. | Who built the automation and when a version went live. | What a particular person knew. |
| Employment records. | The person’s job at the company. | Knowing participation in a fraud. |
| Message logs. | That the system sent the message. | That the defendant meant it to further a scheme. |
Authenticating a record
Federal Rule of Evidence 901 covers authentication. Rules 902(13) and (14) cover certain certified electronic records.
| An authenticated record can show | It does not show on its own |
|---|---|
| What a system produced or sent. | That the message was true. |
| When the system recorded the event. | That the defendant knew its contents. |
| Which account or template was involved. | The remaining elements of the offense. |
Common questions
| Question | Short answer |
|---|---|
| Can one scheme give rise to more than one count? | Yes. Each separate qualifying transmission may support a count, and each still needs proof. |
| Are archived copies separate wires? | Not necessarily. Compare identifiers, routing and source records first. |
| Does automation establish fraudulent intent? | No. How a system works and what a person knew are separate questions. |
Sources
This article provides general information, not legal advice. The law and its application depend on the facts and the law in effect on the relevant date. Consult a lawyer about a specific matter.
Wire Fraud Defense · Texas and Federal Financial Crimes Defense



