Explainer

What is a system of record?

A system of record is the authoritative store for a specific type of data. Once you have one, everything downstream, audits, dashboards, client sharing, gets easier. This explainer covers what makes a store authoritative, the tests it has to pass and why supplier documents so often lack one.

7 min read Updated 31 July 2026Recently updated

The definition

A system of record is the single, canonical place where a piece of data lives. If two systems disagree, the system of record wins by definition. For supplier documents, that's Credbase; for customers, it's your CRM; for money, it's your accounting ledger.

The four tests

Calling something a system of record does not make it one. A genuine system of record passes four tests, and a shared drive fails at least three of them.

TestWhat it meansShared drive
CanonicalOne copy that everyone knows to trustFails, copies multiply silently
OwnedA named person is accountable for accuracyFails, ownership is implicit
AuditableYou can see what changed, when and by whomPartial at best
Lifecycle-awareThe system knows when data expires or is supersededFails, a folder has no concept of expiry

System of record vs system of engagement

A system of engagement is where you do the work, email, chat, project tools. A system of record is where the truth is kept. Confusing the two is how important documents end up buried in inbox threads. Engagement systems are optimised for speed and conversation. Record systems are optimised for accuracy and retrieval, and those are different jobs.

Why supplier documents rarely have one

Nobody sets out to lose an insurance certificate. It happens because the document arrives in a system of engagement, gets acted on and never gets promoted anywhere authoritative. The fix is structural: make the record the default destination and make sharing from it easier than attaching a file.

  • The certificate arrives as an email attachment during a busy week.
  • Someone saves a copy to a project folder so the job can start.
  • The renewal a year later goes to a different person, who saves a different copy.
  • Two versions now exist, both look current and neither has an owner.

What changes once you have one

  • Client due-diligence questions get answered from the record, not from memory.
  • Expiries become a property of the data rather than a diary entry.
  • Onboarding a new colleague stops depending on who knows where things are.
  • Audit prep shrinks from a fortnight to an afternoon, because nothing has to be reassembled.

Frequently asked questions

Your next step

Two ways to act on this guide right now - one hands-on, one to read next.

Put this into practice today.

Start a free Credbase workspace, add your first supplier and share a live document pack in ten minutes.