# Integrating GoPaperless into existing software

For ISVs and integration teams adding documents, approvals and signing to existing software. Four approaches—Portal API, Universal External Signing, Universal Internal Signing and Document Gateway—are selected by workflow ownership and signer experience.

## Problem

Manual signing or results disconnected from the correct version can separate documents from CRM/ERP/DMS cases. Establish the system of record and how completion is verified.

## Scope

- Portal API automates tasks managed in the Portal.
- External Signing uses invitations independent of the application session; Internal Signing redirects and returns.
- Document Gateway embeds document interaction while the Backend verifies results.

## Boundaries

Odoo, SAP, Dynamics 365 and FileNet are integration examples, not evidence of packaged connectors. Returning to the application does not prove signing completion.

## Prerequisites

- Choose a sample case and creation, approval, signing and retention roles.
- Obtain the applicable API, sandbox, states and notification contract.

## Pilot

Run one source-system case through verified completion. Test cancellation, expiry, duplicate/late notifications and recovery; measure integration effort and eligible-case completion.

## Source document

https://docs.mobile-id.vn/Proposals/MobileID_GoPaperless_Integration_Proposal_V4%201.pdf

V4; 51 pages; Vietnamese PDF.

Observed source version; confirm implementation scope.
- Software use cases: 3
- Four integration approaches: 9
- Partner system examples: 17
- Reference architecture: 23
- Pilot scope: 27
- Reference flows and contracts: 40