For deals involving foreign government officials, record three FCPA and FEPA points in the deal file: coverage, accurate books, and official requests. Quarter-end review is when questions about those deals tend to surface. A reviewer may ask why a consultant was paid, who an agent works for, or why a discount went to a particular buyer. If the answer lives only in memory or in a chat thread, it will be hard to defend. If it sits in the deal file with a date on it, the conversation is much shorter.
This post covers three rules that belong in that file: two from the U.S. Foreign Corrupt Practices Act (FCPA) and one from the Foreign Extortion Prevention Technical Corrections Act (FEPA), a separate statute. It is written for revenue leaders, not lawyers. It is not legal advice, and it does not replace review by your company's counsel. Think of it as a checklist of facts you should be able to produce on request.
The starting point is the statute itself. The U.S. Department of Justice cites the "Foreign Corrupt Practices Act of 1977, as amended, 15 U.S.C. §§ 78dd-1, et seq." and says the law was enacted for the purpose of "making it unlawful for certain classes of persons and entities to make payments to foreign government officials to assist in obtaining or retaining business" (DOJ, FCPA Unit). Because the law targets payments to foreign officials made to win or keep business, any deal with that element deserves its own file.
Rule 1: Record whether the law covers your company and your activity
The first rule is about scope. Before you can say whether the FCPA applies to a deal, you need to know which entities it covers and where the relevant conduct happened. The DOJ describes coverage in two parts. The first concerns who is covered: "Since 1977, the anti-bribery provisions of the FCPA have applied to all U.S. persons and certain foreign issuers of securities." (DOJ)
The second concerns location. "With the enactment of certain amendments in 1998, the anti-bribery provisions of the FCPA now also apply to foreign firms and persons who cause, directly or through agents, an act in furtherance of such a corrupt payment to take place within the territory of the United States." (DOJ)
That means a company with no U.S. headquarters can still be within reach if a step toward a corrupt payment took place on U.S. soil. A deal file should therefore answer three plain questions:
- What is our company's status: a U.S. person, a foreign issuer of securities, or neither?
- Where did each key step happen: the pitch, the approval, the payment, or the signing?
- Did any step toward a payment, such as an approval, a transfer, or a message, happen within the United States?
You do not need to answer the legal question yourself. You do need to write down the facts, including dates and names. Counsel can work with facts far more easily when someone recorded them at the time, and a reconstruction written weeks later is rarely as reliable.
Coverage is a question of facts, not labels. A company that is not a U.S. person may still have people in the United States who act for it, and the place where a step happened can matter as much as the company's home country. Write down roles and locations, and do not assume that a foreign deal is outside the statute simply because the contract is signed abroad.
Rule 2: Keep books and records that match the deal
The second rule is about accuracy. The FCPA includes accounting provisions that were "designed to operate in tandem with the anti-bribery provisions." The DOJ summarizes them as requiring covered corporations "(a) make and keep books and records that accurately and fairly reflect the transactions of the corporation and (b) devise and maintain an adequate system of internal accounting controls." (DOJ)
For a revenue leader, the practical meaning is straightforward. The books have to tell the same story as the deal file. If a commission, rebate, travel cost, gift, or consulting fee is connected to a foreign official's decision, the book entry should describe what it really was. A vague label such as "marketing services" that hides the purpose is hard to defend.
Before close, check these items:
- Every payment tied to the deal has an invoice, contract, or written approval that matches its amount and recipient.
- Every third party paid on the deal is named in the file, with the reason for the engagement and the person who approved it.
- Discounts, credits, and side arrangements sit in the same record as the main contract, not in a separate email thread.
- Any exception to the normal approval path is written down, with the name of the person who granted it.
The second half of that requirement is about controls, not just entries. For a revenue leader, that means the path from a deal to a payment should have checkpoints: someone other than the requester approves the payment, the amount is checked against the contract, and the approval is stored with the deal. You do not need to design the control system yourself, but you should be able to show that one exists and that it was followed on this deal.
Notice the phrase "corporations covered by the provisions." The accounting requirements apply to covered corporations, so the coverage facts from Rule 1 still matter here. Even when you are unsure about coverage, a file where every entry is accurate is the one you most want to hand to counsel.
Rule 3: Document every request from a foreign official
The third rule is the one that is easiest to overlook, because it concerns a request that comes from the other side of the table. The DOJ states that the Foreign Extortion Prevention Technical Corrections Act, 18 U.S.C. § 1352 (“FEPA”), was enacted in July 2024 and criminalizes the “demand side” of foreign bribery. (DOJ)
The penalty provision is specific: "A violation of FEPA is punishable by up to 15 years’ imprisonment and a maximum fine of $250,000 or three times the monetary equivalent of the thing of value demanded by the foreign official." (DOJ)
The same page notes that "unlike portions of the FCPA, FEPA does not provide any civil remedies or grant enforcement authority to the U.S." (DOJ) For a revenue leader, the lesson is that a demand from an official is never just a negotiation point. It is a fact that belongs in the file, with an escalation path attached.
A request can be subtle. It may arrive as a suggested consultant, a gift, a favor for a relative, or a hint that a faster approval is available. Record it the same way whatever its form. The file should include:
- The date, the person who made the request, and the exact words or written message.
- What was asked for, whether money, a gift, a favor, a job for a relative, or a faster approval.
- Who on your team heard it, and what each person said in response.
- The escalation: who was told, when, and what counsel advised.
- The outcome, including confirmation that the request was declined, if it was.
A recorded refusal is far more useful than one that lives only in someone's memory. It shows the reviewer what happened, when it happened, and who handled it. Do not treat the record as a formality.
A worked example
Consider a hypothetical deal. A regional sales lead is negotiating a supply contract with a company whose largest shareholder is a government agency. The buyer's procurement manager suggests using a local consultant who, the manager says, can speed up the internal approvals. The sales lead agrees to meet the consultant and asks for a fee estimate.
Now apply the three rules. Under Rule 1, the file records the company's status, where the meetings and approvals took place, and whether any step passed through the United States. Under Rule 2, the consultant's fee appears in the books with a description that matches the actual service, along with a contract and an approval from someone above the sales lead. Under Rule 3, if the consultant or the manager later hints that a faster approval depends on a personal payment, that hint is logged the same day, with the names of everyone who heard it and the escalation to counsel.
Notice what the example does not require. The sales lead does not need to decide whether the consultant is covered by the statute, and does not need to judge the ministry relationship alone. The lead needs to make sure the facts are written down, the payment is recorded accurately, and the question goes to counsel before the fee is paid. A reviewer who sees that trail can follow the reasoning, even if the answer is still open.
Questions reviewers will ask
Reviewers tend to ask the same questions. Having answers ready makes the review shorter and calmer:
- Who is the company, legally, for purposes of this deal?
- Where did the key steps happen, and did any of them touch the United States?
- Who received money or value connected to the deal, and why?
- Do the books describe each of those payments accurately?
- Did any foreign official ask for something, and what happened next?
- Who approved each exception, and is that approval in the file?
If you can answer each question by pointing to a dated entry, you are in good shape. If you cannot, the gap is the thing to fix before close, not after.
Assemble the file before the review
Make these three rules a routine part of your close process rather than a scramble. A workable setup is one folder for each foreign-official deal, with a short index at the top. The index lists the coverage facts from Rule 1, the payments and third parties from Rule 2, and any official requests from Rule 3, each with a date and a pointer to the supporting document.
Some habits make the file easier to defend:
- Write entries when things happen, not at quarter close. A note added in the moment carries more weight than a summary written later.
- Never edit an old entry to match a new understanding. Add a dated note that clarifies or corrects it, and leave the original in place.
- Keep approvals with the deal. If a sign-off happened in a chat app, export it or summarize it with its date, and store it in the folder.
- Name an owner for each section, so a reviewer knows whom to ask about a given entry.
- Run a short check before close. Look for missing invoices, unnamed third parties, and open escalations.
The file is a business record, and people who did not work on the deal may read it. Write each entry so a reader outside the room can follow it. Plain sentences beat shorthand. "Consultant X, approved by Y on this date, for a market access study" is far better than "Consultant X handled it." For another example of a record written for a reader, see the forecast handoff guide.
Timing the work
Timing matters because the file is only as good as its last entry. Work backward from the quarter-end review date and decide which items need to be complete by then: the coverage notes, the payment approvals, the official-request log, and the list of open questions for counsel. Give each item an owner and a date that falls well before the review, so that any gap has room to be fixed.
Avoid the temptation to clean up the file the week of the review. Last-minute edits are visible, and they can make a reviewer wonder what else changed. A file that was built steadily, with dated entries and visible corrections, usually reads as more credible than one that looks polished overnight. For a related record of date changes, see the close date change log.
Common mistakes to avoid
Most problems in a deal file are not dramatic. They are small gaps that add up. Four show up often:
- Relying on a verbal assurance. A promise from a partner that a third party is clean is not a record. Ask for the due diligence in writing and put it in the file.
- Vague descriptions. Terms like "consulting," "support," or "miscellaneous" invite questions. Describe the service, the deliverable, and the person who received it.
- Side conversations. Deal terms agreed in a text message or a hallway conversation often never reach the file. Summarize them the same day and attach them.
- Silence after a hint. When an official's request is ignored rather than refused and recorded, the file looks as if nothing happened. Write down the refusal and the escalation even when the request went nowhere.
When a rule is unclear
Some facts will not fit neatly. A distributor may have a relative who works for a ministry. A payment may pass through a bank in another country. A customer may be partly state-owned. Your job is not to decide these questions alone. Your job is to flag them, describe the facts in plain words, and send them to counsel with the file. A flagged, documented question is far better than an unflagged assumption.
If a deal is close to its date and a question is still open, say so in the review. Reviewers handle an open question with a documented plan much better than a surprise found after signing.
The short version
Before quarter close, your deal file should answer three questions. Does the FCPA reach our company, given our status and any steps that touched the United States? Do our books and records describe each foreign-official-related payment accurately, with controls we can show? Have we written down every request from an official, with the response and the escalation?
The statute is specific in some places and general in others. The DOJ's pages give you the statute, the accounting requirements, and the FEPA penalties. The rest of the file is the discipline of recording facts as they happen. Start with the three rules above, check them against your own deals, and bring counsel in early on anything you cannot answer yourself.