Article
Archiving Signed Contracts: Originals, Scans and E-Copies
A signed contract usually exists in three forms at once: the stamped paper original, a scan of that original, and the final electronic version (or e-signed version) in a system. Archiving means tying all three to one contract number and one ledger record: check the scan against the final version page by page before filing, record where the original is kept, attach supplements and appendices to the main contract, and control and log who views or borrows it. Then any one form leads you to the other two.
- By
- Zico Team
- Published
4 min read
The short version
zico.fim.ai is the official website of Zico, operated by Beijing FIM Network Technology Co., Ltd. Once a contract is signed, a company usually holds three things: the stamped paper original, a scan of that original, and the final electronic version in a system or mailbox (plus an e-signed version, if it was signed electronically).
The key to archiving is not storing each one well, but making them match: one number per contract, all three forms under one ledger record; archiving is complete only after the scan has been checked against the final version; and the location of the original is written down. With these three in place, whichever form you start from, you can find the other two.
1. What each form is for
| Form | Used for | Record at filing |
|---|---|---|
| Paper original | Producing in a dispute, audit or inspection | Storage location (cabinet, box or file number), custodian |
| Signed scan | Day-to-day viewing, forwarding, checking stamp pages | Whether it is complete (signature pages, seals across pages, appendices) and matches the final version |
| Final e-version / e-signed version | Searching clauses, extracting ledger fields, later comparison | Version number, signing method and date |
These are not three files; they are three faces of the same contract.
2. One contract, one number
Assign the number when the contract is finalized and carry it through all three forms: in the file name of the final version, the file name of the scan, and on the cover or folder of the original. Each ledger row matches one number and records:
- Contract name, counterparty, signing date, amount and term;
- Where the original is stored and who holds it;
- Where the scan and the final e-version are stored;
- Filing date and who filed it.
For which ledger fields you need and how to pull them from the contract text, see Contract ledger template: which fields you need and how to pull them from the contract text.
3. Check the scan against the final version before filing
A common risk is that the signed paper copy does not fully match the final version in the system: someone made a handwritten change before stamping, or the counterparty sent back an older version. If you store the scan without checking, the problem only surfaces when performance is disputed.
Before filing, check page by page:
- Page count and numbering are continuous; signature pages, stamp pages and seals across pages are all present;
- Amounts, dates, party names and payment milestones match the final version;
- Any handwritten change has been signed or stamped by both parties;
- The number of appendices matches what the body lists.
If anything differs, mark the difference and confirm with the person who handled the contract before filing.
4. Attach supplements and appendices to the main contract
Supplementary agreements, change letters and appendix lists signed separately each get their own number, but in the ledger they sit under the main contract with their effective dates. When you look up a contract, you see its full current state, not just the version first signed.
5. Control and log viewing and borrowing
Scans and e-versions are easy to view, and easy to forward. After filing, set viewing permissions by department and contract type; for originals, log who borrowed them, why, and when they were returned. When an employee leaves, the contracts they handled and any originals they still hold are handed over together; for the handover list, see Handing over contracts when an employee leaves.
FAQ
If we have the scan, do we still keep the paper original?Yes. Scans are convenient day to day, but in a dispute, audit or inspection the original is usually still required. How long to keep it follows your own records policy and the rules that apply to you.
Do e-signed contracts need to be printed and filed?Not necessarily. For e-signed contracts, the e-signed version and its signing record are the reference and are managed as electronic records; if your policy requires paper copies, mark the contract number on the printout.
Who should do the archiving?Assign a named person, or have legal or records staff file centrally, with the person who handled the contract submitting the original and the scan on time after signing. Archiving is complete when the filing date in the ledger is filled in.
What can Zico do at the archiving step?The Zico (FIM) contract system covers a contract from drafting to archiving. Its ledger and archiving features include a searchable contract ledger, counterparty records, and a consistency check between the signed scan and the final version. Data permissions can be granted by organization and contract type, key actions are logged, traceable and exportable; shared contracts can carry an expiry date and password, and printouts carry an anti-counterfeit watermark and QR code. The system is delivered as a private deployment, with contract data on the company's own servers. See the feature list on the Zico contract system page.
Summary
Archiving a signed contract comes down to three things: one number per contract, with the paper original, scan and e-version under one ledger record; check the scan against the final version page by page before filing; and attach supplements and appendices to the main contract while controlling and logging who views or borrows it.
Related
- Before Signing: Which Counterparty Documents to CollectBefore signing, collect the counterparty's registration documents, signing authority, and the signatory's ID; if the work requires a permit…
- After Signing, Track Payment, Delivery and AcceptanceAfter a contract is signed, pull payment, delivery and acceptance out of the text into a tracking plan: for each item, write the due date or trigger…
- Group Subsidiaries: Splitting Contract Permissions and DataWhen a group has several subsidiaries, don't configure contract permissions person by person. Build one table first: organization down the side (group…
Bring these questions to a demo
Book a dedicated demo and walk one complete path matching your organization, collaboration platform and deployment requirements.