One workspace for every
regulated customer you sell to.

Onboarding overview and target readiness

Two panels that answer the only three questions that matter before go-live: what is blocking this customer, who owns it, and what is due next. Target readiness then scores you against the supplier requirements that institution has published itself.

• Pull the onboarding overview from the customer's internal requests, customer requirements, contracts and obligations, rather than from a status someone typed in.
• Score readiness against a library built from published supplier and third-party requirement documents: 33 financial institutions and 34 source documents, including EU DORA as its own baseline.
• Show each requirement as ready, review due, evidence required, expired or missing.
• Turn every gap into a next action with a supply method: upload evidence, enter a fact, connect a source or assign an internal request.
• Flag when an approved source change may affect a readiness target you already met.

Scope: Readiness is preparatory guidance based on published supplier information. It is not the questionnaire your customer will send, and it does not predict one.

Browser assistant for the customer's own portal

Many institutions will not accept a document — they want the answers typed into their own portal. The MatchAudit browser assistant works inside supported SAP Ariba and Coupa questionnaire pages: it reads the visible question, asks MatchAudit for an approved answer, and offers it next to the field with its source and confidence.

• Detect supported question fields on the portal page and offer a 'Find approved answer' action beside each one.
• Return a suggestion only from approved records your workspace is authorized to use, shown with the customer name, the source document or fact, its provenance and a confidence score.
• Insert the value only after you press confirm — including matching the answer to the portal's own dropdown options, and refusing when it is not one of them.
• Block insertion when the underlying source is past its review date, so a stale answer cannot be pasted into a live assessment.
• Read only the visible field label and options you ask about. It never receives portal credentials, never presses the final submission control, and requests no access to unrelated sites.
• Pair to one customer relationship with a revocable 30-day connection token issued in the dashboard, with every suggestion request logged.

Scope: A Manifest V3 extension for Chrome, supporting SAP Ariba and Coupa question fields today. It is paired and installed with our help rather than downloaded from a public store, and it suggests — a person confirms every insertion and submits the portal form.

Events, incidents, reports and internal coordination

The operational half of the relationship after go-live: typed lifecycle events matched to approved obligations, incidents, customer contacts, the reports you owe, and the internal requests that unblock all of it.

• Record typed events such as a changed processing location, a materially changed service, an approaching contract renewal or an approaching termination notice, and match them to the obligations they trigger.
• Prepare incident responses and customer communications that remain preparation-only until a person acts on them.
• Generate a frozen operational report draft, review it, and approve it before any export for external use.
• Assign missing information to a colleague, track who it is waiting on, keep the discussion and attach reusable evidence to the answer.

Scope: MatchAudit does not send reports automatically. Nothing leaves the workspace without an approval.

Connected source systems

Read-only connections to Vanta, OneTrust and ServiceNow that bring information you already maintain into the same review flow.

• Map selected Vanta controls, tests or document metadata into reusable facts.
• Map selected OneTrust records the same way, one mapped object and field at a time.
• Read one selected ServiceNow Incident field at a time through a restricted REST auth scope.
• Send every changed value for human approval, keeping the object, field and date it came from.
• Disconnect at any time: credentials are revoked, and facts already approved plus the sync history are retained.