Compliance
Definition
Compliance
Compliance is the state of meeting the rules that bind an organisation — statute, regulation, contract and internal policy alike. It is a condition, not a department, which is why a company can staff a compliance team and still fail to be compliant.
The distinction decides how the work is measured. A program is the apparatus built to produce compliance. Whether it produces it is a separate question, and the one regulators actually ask.
Outsourcing raises the stakes because obligations do not transfer with the work. A buyer who moves a process offshore still answers for it, under rules written in its own jurisdiction.
Key takeaways
- Compliance is an outcome; a compliance program is the machinery built to reach it.
- Accountability stays with the buyer even when delivery moves to a provider.
- Regulators test whether a program works in practice, not whether it exists on paper.
- Most outsourcing compliance work concentrates in data protection and labour law.
How it works
Compliance runs as a loop: identify every obligation, map each one to a control, test whether the control holds, fix what fails, and keep a record good enough to show someone who was not there.

The obligation map is the part most organisations skip. Without it, controls accumulate around whatever was audited last rather than around what the business is actually required to do.
Testing is what separates a program from a policy library. A control that has never been sampled is an assumption, and assumptions are what turn up in enforcement findings.
Record-keeping is the part that feels like overhead until it is the only thing that helps you. The question an investigator asks is not what your policy said but what you did, when, and who decided it.
That is why findings matter more than clean results. A program that has never recorded a failure is usually a program that has never looked properly, and experienced regulators read it exactly that way.
Regulators judge the outcome rather than the paperwork. The United States Department of Justice instructs prosecutors to assess a compliance program’s adequacy and effectiveness at two points in time — when the conduct occurred and when the charging decision is made.
Data protection is the obligation that bites hardest in outsourcing. The General Data Protection Regulation requires that a controller use only processors providing sufficient guarantees of appropriate technical and organisational measures.
That requirement is why due diligence on a provider is a compliance activity, not a procurement formality. The same logic governs any cross-border data transfer between a buyer and an offshore delivery site.
| Obligation type | Where it comes from | Who answers for it |
|---|---|---|
| Statutory | Law in the buyer’s jurisdiction | The buyer, always |
| Regulatory | A sector regulator’s rules | The buyer, via the provider |
| Contractual | The client agreement itself | Whichever party signed |
| Internal policy | The company’s own standards | The named control owner |
Examples
Compliance looks different in every sector, but the obligations that reach an outsourced team cluster in a few places. These four are the ones that shape day-to-day delivery work.
A US healthcare client sends claims processing to a Philippine provider. Patient data brings HIPAA obligations with it, so access controls, training records and breach reporting are written into the delivery contract before a single claim is touched.
A European retailer runs customer support offshore. Under GDPR the retailer remains the controller, so it has to evidence that its provider’s safeguards are adequate — and keep evidencing it, not prove it once at signature.
A financial services firm offshores KYC review. The regulator’s expectations follow the work, so the provider’s analysts are trained, sampled and documented to the same standard the firm would apply in-house.
An Australian employer hires through an offshore staffing provider. Two labour regimes now apply at once — the client’s obligations to its own workforce, and Philippine employment law covering the people actually doing the work.
The pattern repeats across all four. A compliance program exists to close the gap between where an obligation is written and where the work is actually done.

Firms that would rather buy the discipline than build it use compliance outsourcing, which contracts monitoring, testing and reporting to a specialist while the regulated firm keeps accountability.
Related terms
Compliance sits beside an operating model, a design practice and two roles that are routinely confused with each other. Each entry below draws a line this page deliberately does not cross.
- Governance Risk Compliance: one operating model joining three jobs that used to run separately.
- Compliance Program Design: the work of building the system that produces compliance.
- Compliance Officer: the senior owner accountable for the program.
- Compliance Analyst: the role that maps obligations to controls and tests them.
- Compliance Outsourcing: buying regulatory work from an outside specialist.
- Cross-Border Data Transfer: moving personal data between jurisdictions under a lawful mechanism.
FAQ
Is compliance the same as a compliance program?
No. Compliance is the state of meeting your obligations; the program is the apparatus built to get you there and prove you got there.
Can compliance be outsourced?
The work can; the accountability cannot. A provider can run monitoring, testing and reporting, but the regulated firm still answers to the regulator.
What makes a program credible to a regulator?
Evidence that it was tested and acted on. Regulators look for sampling records, findings, remediation and consequences rather than a policy document and an org chart.
How does offshoring change the obligations?
It does not change them, it adds a layer. The buyer’s own rules still apply, and the provider’s jurisdiction may add data, labour and tax requirements on top.
What belongs in the contract rather than the policy?
Anything you would need to enforce. Access controls, breach notification timings, audit rights and training standards all work better as contractual obligations than as expectations stated in a policy the provider never signed.
Where should a first-time buyer start?
With a written obligation map, because every control and every contract clause should trace back to a specific rule.
Start at Outsource Accelerator if you are mapping those obligations for the first time.







Independent




