Test the add-on before integrating it
An add-on acquisition brings a ledger you did not build, a vendor master you have not cleaned and users whose access nobody has reviewed. Integrating it first and testing it later means its problems move into the platform's books. We run a short, fixed set of tests on the add-on's data in the first weeks after closing, before the systems are merged.
DOJ's compliance program guidance asks specifically how a company handles due diligence and integration after an acquisition, and its 2026 enforcement policy rewards companies that find and disclose problems early. Our summary of DOJ's 2026 Corporate Enforcement Policy explains the incentives.
First-month tests for a new add-on
- Manual journal entries by time, author, approver and proximity to period end.
- Vendors that share a bank account, address or tax ID with an employee or with another vendor.
- Vendor bank-detail changes in the last twelve months, and the payments that followed them.
- Payments to agents, consultants and intermediaries in higher-risk jurisdictions.
- User access in the accounting system, the bank portals and payroll, compared with job roles.
Full-Ledger Analytics runs these tests over every transaction, and every flag is reviewed by a person before it reaches a report.
One format for every company
Operating partners read many reporting packs. We deliver findings in the same structure for each company, ranked by consequence, each with an owner and a date, so the sponsor can compare companies and track progress between board meetings. The same register, kept current, becomes part of the evidence a buyer's diligence team will ask for at exit: what was found, when, and what changed. Once the fixes are in, continuous controls monitoring keeps the same tests running weekly. Our list of ten automated tests shows what that looks like in practice.