Find fraud risk before it costs you

We analyze the full ledger, assess your fraud exposure and close the payment routes criminals use most.

Engraving of a ledger seen as farmland from above, crossed by a trail of magenta footprints.
Every entry leaves a footprint.

The median fraud runs a year

The Association of Certified Fraud Examiners' Occupational Fraud 2026 report puts the median duration of an occupational fraud at 12 months and estimates that organizations lose 5% of revenue to fraud each year. Most of the cases it studied trace back to absent controls, overridden controls or missing management review. Those are conditions you can test for long before anyone confesses or a bank calls.

Outside the company, the payment is the target. The AFP's 2026 Payments Fraud and Control Survey found that 76% of organizations experienced attempted or actual payments fraud in 2025, with business email compromise the most common route in.

This pillar works in both directions. We test the ledger for the marks internal fraud leaves, assess where the company is exposed, and harden the payment process against people outside it. Every analytic flag is reviewed by a person before it reaches a report.

What we offer here

Each offering has a fixed scope and a named set of deliverables. Most clients start with one and add others later.

  • Engraving of a fishing net full of coins and receipts with one magenta fish caught among them.

    A two-to-four-week diagnostic that runs a library of explainable tests and outlier models over every transaction in the period, then reports only the flags an analyst has reviewed.

  • Engraving of a townhouse cutaway showing its plumbing, with a magenta drop forming at one hidden joint.

    A four-week diagnostic that identifies how fraud could happen in your business, scores each scheme, maps it to the controls that should stop it, and tests the riskiest ones against your data.

  • Engraving of a featureless mask in profile at an antique telephone whose cord is cut, the cut end in magenta.

    A six-to-eight-week project that redesigns how payment instructions are verified and released, cleans the vendor master, configures bank controls and drills your team against realistic attacks.

These conditions invite fraud

  • Nobody reviews manual journal entries

    Entries keyed and posted by the same person, with no review before close, are the most direct route to moving results or hiding a payment.

  • Vendor bank details change by email

    If a PDF on letterhead is enough to redirect payments, the next invoice can go to a criminal's account and nobody will know until the vendor calls.

  • No one has asked how fraud would happen here

    Without a fraud risk assessment, controls defend against the risks someone happened to remember, not the ones that fit your business.

  • A UK link or a DOJ question is on the horizon

    UK operations, UK customers or a prosecutor's inquiry raise a direct question about whether your fraud prevention procedures are documented and reasonable.

The ledger is tested before interviews

Trace. We map who can create vendors, change bank details, post journal entries and release payments, and which systems hold each record.

Test. We run a library of explainable tests over every transaction in the period, plus statistical outlier models, then confirm the flags that matter with walkthroughs and document reviews. No flag goes into a report until a forensic data analyst has looked at the underlying records.

Disclose. Findings are ranked by consequence and written in plain language. Where a flag could point to misconduct, we raise it only with the person you named at scoping, typically the CFO, audit committee chair or general counsel, and never with the people involved.

Teach. Finance staff learn what the tests look for and how to respond to an alert, and the payment team practices the verification steps before they are needed.

Inside schemes hide in routine entries

Fraud by insiders rarely looks unusual one transaction at a time. It looks unusual in aggregate, which is why we test the whole population rather than a sample. Tests are tuned to your approval limits and calendar first, so a payment run every Friday at 18:00 does not flood the list. Each result is a short list for a person to check, not a verdict.

Billing schemes surface in vendor data

A shell vendor that shares a bank account or a street address with an employee. A real vendor whose invoices arrive in round amounts just under the approval limit. A vendor whose bank details changed four days before its largest payment of the year. Each of these is a test in our library, and each produces a short list that an analyst can check against contracts and receiving records.

Some entries move results, not cash

Not every irregular entry is theft. Some move costs between periods to meet a covenant or a bonus target. We look for entries posted on weekends or late at night, entries keyed and approved by the same user, reversals just after period-end and gaps in entry sequences. The Sunday-night entries scenario shows how that pattern can look in practice.

Payroll and expense fraud repeats itself

Pay rate changes outside the normal cycle, off-cycle runs, employees who share a bank account, and receipts that repeat across claims. Generated receipts now look real, so our tests compare claims with card data and travel dates rather than trusting the image.

Outside fraud targets the payment

Business email compromise and its newer forms, cloned voices and deepfake video calls, all aim at one moment: the instruction to pay, or to change where payment goes. FinCEN warned financial institutions about fraud using deepfake media in alert FIN-2024-Alert004 in November 2024. In the widely reported Arup case that year, roughly $25 million was sent after a video call with fake executives.

Banks are tightening their side as well. Nacha's fraud monitoring rules, which reached every business that originates ACH payments in June 2026, require risk-based processes for spotting entries authorized under false pretenses, such as a payment to an impersonated vendor. The single control that matters most is a callback to a number already on file, made by someone who did not receive the request. Our payment fraud defense work builds that protocol and tests it with drills.

Finding it first changes the outcome

Since March 2026, the Department of Justice's department-wide Corporate Enforcement Policy has offered a presumption of declination to companies that voluntarily self-disclose misconduct, cooperate and remediate. A company can only disclose what it has found. ACFE's 2026 report finds that tips detect the largest share of frauds, so analytics and a working reporting channel complement each other rather than compete. The explainer on DOJ's 2026 Corporate Enforcement Policy sets out the terms.

What people ask before hiring us

Is this a fraud investigation?

No. This work finds risk and the patterns that point to it. If an analytic flag suggests that a specific person has committed fraud, we pause, tell the contact you named at scoping, and recommend that you involve counsel before anything else happens. Any investigation that follows should be set up through counsel.

Will the analytics produce a flood of false positives?

Rules are tuned to your business before the first full run, using your approval limits, your working calendar and your payment schedule. Every flag is reviewed by an analyst, and the report shows only exceptions that survived that review, with the reason each one matters.

Do we need to buy software?

No. We run the analytics in our own access-logged environment from read-only access or exports. If you want the tests to keep running after a diagnostic, they can move into a continuous controls monitoring subscription.

What happens to our data afterward?

Client data is deleted 90 days after the engagement closes unless you ask otherwise in writing. It is never used to train external AI models.

Related work and reading

  • Continuous Controls Monitoring

    Automated tests on your ledger, bank and access data every week or month, each exception reviewed by a person and routed to a named owner, run as a subscription after a six-week setup.

  • Segregation of Duties & Approval Design

    A six-to-eight-week project that maps every user's access against their duties, removes conflicting rights, redesigns the approval matrix and adds compensating controls where the team is too small to split.

  • Training Programs

    Half-day sessions to six-week cohorts for managers, staff and boards, built on your policies, your approval limits and anonymized examples from your own ledger.

Tell us what you are seeing

A first conversation is a scoping call: what worries you, what you need to show, and to whom. You leave it with a view on where to start, whether or not you hire us.

Writehello@financeethics.com
Call(307) 365-5252
Office7124 Commons Dr, Cheyenne, WY 82009
HoursMonday to Friday, 9:00 to 17:00 Mountain Time