① Guide · Precisely (Syncsort) audit response
A Precisely audit lands on products you may still call Syncsort, against capacity figures you may never have validated. The finding arrives as settled fact. It is an opening position. Here is the buyer side response, from the notice to the settlement.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Syncsort (Precisely) brought its mainframe portfolio under the Precisely brand after the 2020 rename, but the products and the contracts behind them often still read Syncsort. Syncsort MFX, the high performance sort, copy and join engine, is commonly licensed against mainframe capacity. The Ironstream family, which streams mainframe and IBM i operations and security data into platforms used for SOX, NYDFS and DORA compliance, can turn on instances and the systems being streamed from. Connect and the Assure resilience products carry their own metrics. An audit can touch any of them, and the naming gap between Syncsort paper and Precisely claims is part of what the audit relies on.
The recurring pattern, common to most vendor audits, is a claim built from the vendor's reading of your deployment and presented as fact. It is not fact until you have validated the capacity figure and reconstructed your entitlement from the original contracts. That validation is the entire game.
The first 48 hours and beyond
| Stage | The vendor wants | What you do |
|---|---|---|
| Notice | Fast access to raw system data | Acknowledge; confirm scope and contractual audit rights in writing |
| Data request | Unfiltered deployment and capacity data | Agree scope first; share only what the contract requires |
| Entitlement | To work from its own record | Reconstruct entitlement from original Syncsort and Precisely contracts |
| Finding | To present a number as an invoice | Validate capacity and counts; treat the finding as an opening position |
| Settlement | To close at the claimed figure | Negotiate down and write caps and clean audit language into the close |
The routine reductions
An audit settlement is the worst possible moment to discover your contract has no audit cap, no capacity definition, and no exit. It is also the best possible moment to fix all three. Closing a finding is a negotiation, and the same conversation that reduces the claim can write in the protections that prevent the next one: a defined capacity basis for MFX, clean audit language, entitlement clarity across the Syncsort and Precisely record, and caps on future escalation. This is the discipline of our mainframe audit defense work, where the response and the renewal are run as one engagement.
Syncsort became Precisely in 2020, but the products, MFX, Ironstream, Connect and Assure, and the contracts behind them often still read Syncsort. That naming gap is what an audit relies on. Reconcile entitlement under the original paper first.
For capacity licensed products like MFX, the mainframe capacity and whether deployment matches entitlement. For Ironstream, instances, environments, or systems streamed from. The claim is built on the vendor's reading until you validate it yourself.
Slow the clock and control the data. Acknowledge, confirm scope and audit rights in writing, and decline raw data until scope is agreed. Then reconstruct entitlement and validate any capacity figure before responding. See the first 48 hours of an audit.
Commonly, yes. Findings are opening positions, not invoices. Misread capacity, inherited entitlements, products counted where unused, and shelfware are routine reductions, and the settlement is a chance to write in caps and clean audit language.
The full portfolio, metrics, and renewal behavior in one place.