Inbound document exchange
Inbound exchange helps you review documents received from an external operator or connected source. It is a review queue, not automatic approval: identify the sender, context, and next action before importing anything.
Where to find it
Conceptual guidance, not a UI screenshot or state evidence.
Open Documents → Inbound exchange at /documents/exchange/inbound. The queue shows candidates waiting for review. An empty queue and no search results are valid states.
The screen shows up to 50 candidates at a time. Search, the count, and actions therefore cover only the loaded page. Refresh after processing a batch, use bulk rematching, or ask an administrator for access to the next page of older records.
Open a candidate from the list. Available actions depend on the connection, permissions, counterparty, legal entity, and the material itself.
Review a candidate
Conceptual guidance, not a UI screenshot or state evidence.
- Check the file, sender, counterparty, and suggested context.
- Read the summary and reason when available.
- Choose the action supported by the facts: link to an existing document, create a document, import artifacts, or ignore.
- Confirm the resulting link, version, access, and owner.
Ignoring removes a candidate from the work queue; it does not mean the source material was deleted at the provider. Record the reason and follow your retention policy.
Link or create
Conceptual guidance, not a UI screenshot or state evidence.
Link to an existing card when counterparty, subject, and version match. Check for duplicates before creating a second card. Create a document only when the material is new and has a clear client, opportunity, task, or project context. Assign an owner and next step immediately.
Rematch in bulk
Conceptual guidance, not a UI screenshot or state evidence.
Bulk rematching works on stored candidates and re-resolves their counterparty inside the portal. It requires a configured connection and selected legal entity and is bounded to 100 candidates per run. The UI enables automatic local-document creation and available-artifact import for eligible matches, so the result separately reports created documents and import failures.
If the provider returns only metadata or an unreadable artifact, importing that file ends with a clear unavailable-artifact message; it does not mean the source document was deleted. Keep the identifier and request the file from the provider again.
The result includes statistics and can be incomplete when a provider or document limit is reached. Keep the warning, refresh the queue, and process the next batch. Run a separate connection sync when you need to fetch new provider materials.
Errors and safety
Conceptual guidance, not a UI screenshot or state evidence.
- Check for an existing document before retrying, to avoid duplicates.
- Never put connection tokens, client addresses, or contract contents in public comments or shared material.
- A connection error does not prove that a document is absent; record it and check the provider state.
- If an action is unavailable, check the permission, legal entity, source, and connection status.
- For significant documents, compare the provider original and current version before signing or sending.
Provider connection
Conceptual guidance, not a UI screenshot or state evidence.
The exact actions and limits depend on the connected provider. See the provider-specific setup, such as SBIS exchange, and do not assume a provider is active until an administrator has tested it.
Manager review
Conceptual guidance, not a UI screenshot or state evidence.
Regularly review old queue entries, repeated documents, incomplete bulk operations, and candidates without an owner. Every candidate should end with a clear decision: link, create, import, or record a justified ignore action.
Related pages
Conceptual guidance, not a UI screenshot or state evidence.