What this means
Social engineering and funds transfer fraud coverage addresses losses when criminals trick employees into sending money, changing payment details, or trusting fraudulent messages. It may be sublimited or excluded unless specifically added.
Do not assume a cyber policy automatically covers every fraudulent payment scenario.
When it shows up
This usually appears when a client wants proof that your business can meet insurance obligations before a project starts.
In practice, the requirement is rarely only about buying insurance. It is also about showing that you understand the client's risk concern, can produce the right evidence, and know which details belong with a broker, IT/security contact, operations owner, or legal reviewer before you sign.
What to look for in the contract
Look for the coverage names, limits, certificate details, timing, and any special wording that needs broker or legal review.
Exact policy names or phrases, such as cyber liability, technology E&O, or professional liability.
Per-claim, aggregate, sublimit, deductible, and any contract-specific amount.
Certificate holder, due date, endorsement wording, and delivery instructions.
How to use this guide
Treat this page as preparation for a more precise conversation. Start with the checklist, gather the evidence you already have, and split unanswered items into coverage questions for a broker and readiness questions for IT, security, or operations.
Checklist
- Ask whether social engineering is included.
- Check sublimits and verification requirements.
- Document wire approval procedures.
- Train staff on payment change requests.
Who should help with what
Most requirements become easier when the packet is split into coverage questions and technical evidence.
Ask a broker to confirm policy fit, limits, certificate wording, endorsement availability, and open quote questions.
Ask IT, security, or operations to gather control evidence, system access details, data handling facts, and unresolved readiness items.
Common mistake to avoid
The common mistake is treating dense contract wording as a yes-or-no requirement instead of breaking it into separate coverage and evidence tasks.
Questions for the right specialist
Coverage questions
- What is the funds transfer fraud limit?
- Are callback procedures required?
- Does BEC trigger cyber coverage, crime coverage, or both?
Readiness questions
- Which items belong with a broker and which require internal evidence?
- Who can confirm the facts behind the insurance application answers?
- What needs to be fixed before the business makes commitments to the client?
Build your packet
If this requirement is tied to a real client contract, use the CoverReady checklist to turn the wording into a readiness packet: coverage questions for your broker, technical evidence for IT/security, certificate needs, and items to clarify before making commitments to the client.
Start checklistCoverReady is a practical education tool. Specific insurance requirements can vary by contract, policy, carrier, state, and business facts, so bring real requirements to a licensed broker or attorney before you rely on them.