Documents on a relationship

Every relationship carries two kinds of paperwork: what the relationship itself produced (the agreement, an addendum, the fee schedule) and the counterparty's own corporate documents (its certificate of incorporation, licence, registers). Both live on the party page in the Relationships section, with placeholders for what is expected of that role, so the gaps are visible before an auditor asks.

Before you start

• Anyone who can view KYB records can read the documents. Uploading needs document-upload rights; adding document rows and editing fields needs the Contributor, Editor, or Workspace Admin role; requesting documents from the party needs the right to create collection links.
• Accepted files are the same as for the KYB record: PDF, PNG, JPEG, WebP, and TIFF, up to 25 MB.

The party page

Open Relationships in the sidebar and click the party. The page has no tab strip: the relationship details sit at the top (the entity, the role, the account reference, the Since and Until dates), and below them each relationship shows two document sections:

• Relationship documents: what the relationship produced. The platform ships six types in the Relationship category of the document catalogue: Agreement / contract, Addendum / amendment, Account opening letter, Service level agreement, Termination notice, and Fee schedule / pricing letter. You can also add a document under a title of your own.
• Counterparty KYB documents: the party's own paperwork, drawn from the ordinary document catalogue: certificate of incorporation, licence or registration, register of directors, AML policy, and so on.

Each section is headed with a count such as 2 of 3 expected on file. A party with several relationships shows the two sections once per relationship.

Expected placeholders

When a relationship is created, or its role changes, ComplyWise adds an empty row for every document expected of that role, on both sides. A placeholder reads Expected for a PSP · not yet received, carries a Required or Optional chip, and offers two ways to fill it:

• Upload opens the document drawer so you can add the file yourself.
• Request from party mints a collection link scoped to this party's documents. Send it to your contact: they open it in a browser and upload straight into these rows, without an account. The link is shown once, next to the button, with a Copy action; it is open to whoever holds it, so send it directly to the person you expect to use it.

Placeholders are never removed automatically, even if the expected set changes later, so a document that has already arrived is never lost. Which documents are expected per role is set in Workspace Settings; see below.

Add a document that was not expected

Use Add relationship document or Add KYB document at the foot of the section. Pick a type from the catalogue (relationship types on the first, every other type on the second) or type a title of your own; a typed title shows a Custom chip. The new row behaves exactly like a placeholder: upload into it, or request it from the party.

Working with a document

Click a row to open the same document drawer the KYB Manager uses: the preview, versions, the data fields, verification and review, Mark N/A, and snooze all work here, so nothing needs a detour through the entity's record. A document reached from the library, clause search, or an audit item opens on the party page in its drawer.

Relationship documents are facts you hold rather than evidence to verify, so no review steps run on them once uploaded; instead, ComplyWise reads their terms for you (see Terms summary below). Counterparty KYB documents follow the verification recipe of their type, as they would anywhere else.

Documents on a relationship never count toward the entity's own KYB readiness. The entity's score covers the entity's own checklist; a counterparty's paperwork is tracked here, against the relationship.

Terms summary

When a file lands in a Relationship documents row, whether through the drawer, by dropping it onto the row, or from your contact uploading through a Request-from-party link, ComplyWise reads the whole document in passes and shows a read-only Terms summary in the drawer: a short paragraph on what the document is, then three groups of values.

• Key dates: Effective date, Signed (the effective date when no separate signing date is printed), Initial term, End date, Renewal, Termination notice.
• Fees: Fee structure, Settlement.
• Law and parties: Governing law and courts, Entities named, Account / merchant reference, Signatories, Status.

Each value shows the page it was read from; hover over it to see the sentence it was taken from. A field the document does not contain reads not stated. There is nothing to accept: a signed document is a fact.

Two of the dates flow into the document's own fields: the end date becomes the document's expiry, so the expiry alerts you already receive cover agreement renewals, and the effective date becomes its issue date. A date someone has already typed is left alone.

The status line under the summary reads Read on <date> · N passes over M of T pages · K AI credits. If a newer version has been uploaded since the read, a note says so.

The summary offers two actions:

• Edit only corrects a misread value. A correction is kept even when the document is read again, and the value shows a corrected chip.
• Read again re-reads the current version (it uses AI credits); your corrections are kept.

Reads use the workspace's AI credits: 1 credit per pass, times the model's multiplier. They need the Legal AI module to be enabled on the workspace; if it is not, the summary says so and nothing is charged.

Counterparty KYB documents are not read this way; they keep their type's verification recipe.

Set what is expected per role

Workspace Admins decide the expected set in Workspace Settings › Relationship documents. The table has one row per role (PSP, EMI and Bank share a row while their sets are identical; Customer, Downline, Supplier, Partner, and Other have their own), each showing the relationship-side and the KYB-side lists with (required) marked, and a chip reading Inherited from platform or Customised.

1. Click Edit on a role.
2. On either side, Add from the catalogue, switch each item between Required and Optional, reorder, or remove it.
3. Save appears only once something changed. Saving the shared PSP · EMI · Bank row applies the set to all three roles.

A role you customise replaces the platform set for that role; roles you leave alone keep inheriting the platform default, including later changes to it. Reset to platform default (in the same dialog, on a customised role) removes your own set on both sides and puts the inherited one back; documents already on file, and placeholders already on existing relationships, stay where they are.

As shipped, the platform defaults are:

Platform staff maintain these defaults under Platform settings › Document library › Relationship documents.

Relationship types and the entity checklist

Relationship document types form their own Relationship category in the document catalogue. They describe a dealing between two parties, not the entity itself, so they cannot be added to an entity's checklist template; they appear only on relationships.

The Notes rail

The right-hand rail on the party page holds the party's notes and stays in view as you scroll: onboarding history, open points, who your contact is. Select text to make it bold, italic, or underlined, or turn it into a bulleted or numbered list; headings and images are not supported, and pasted formatting beyond that is dropped with a note saying so. Save appears only while the text differs from what is saved.

Related articles

• Add a relationship: recording the relationship the documents hang off
• The Relationships register: parties, groups, and the party page
• Request documents from a counterparty: how collection links work
• Document statuses: what each status chip means