Organisational context

Organisational context is what your company tells Ressura about itself that is not a document. Which legal entities you run, when your financial year ends, who can approve a payment and up to what amount, or a note such as "that rate was renegotiated in March". It is held on your company, separate from the Data Room, and every module reads it before checking anything.

Entries and their scope

Context is a list of entries. Each entry answers one question and carries the name of the person who added it and the date. An entry is scoped to the whole company, to one module, or to one subject such as a single supplier.

A value that is an amount, a percentage or a number also carries the date it took effect. A Control uses the value in force on the document's date, and a change adds a new dated entry rather than overwriting the old one.

How context is gathered

Ressura asks for as little as possible. Nothing is asked at sign-up except your role in the company. When you first open a module it asks at most two questions, and only for a value it cannot work without; today only Tax & Compliance asks any. Everything else has a default the module names in its findings, such as "assuming a 30-day dispute window; tell me if yours differs", or is asked only when a check needs it.

Entries arrive in four ways:

• Answering a question. A needs-information finding asks you for a value, and your answer becomes an entry.
• Rejecting a finding. When you reject a finding you give the reason, and the reason becomes an entry scoped as you choose. See Findings and Dispositions.
• Confirming a proposal. When an agreement or a notice is added, the module may propose entries it read there, as cards you confirm.
• Telling Ask Ressura. You can add, change or remove an entry in conversation, through a card you confirm. See Ask Ressura.

Who may change it

Any member may add an entry within their scope, and admins may edit or remove one. Every add, change, move and removal is recorded in the activity ledger with its author. Fraud Watch reads that record, because a context change that makes an exception stop firing is itself worth a second look.

Context governance

An admin chooses how changes take effect, in one company-wide setting:

• Auto-accept, the default. A change takes effect at once and is recorded with its author and date.
• Admin approval required. A change pends until an admin approves it. Until then it is a pending context change, and the check keeps using the old value.

The setting applies to every add, change, move and delete, including entries created from a rejection.

Read next

The Data Room holds the documents that context is read alongside, and Procure-to-Pay lists the questions that module may ask you.