Admin remembers “it expires around September.” Sales remembers “we stamped two copies.” Legal remembers “there is an addendum.” When the three memories do not match, the client is already shipping on old terms, or the seal already sat on a void draft. The ledger’s job is to put those three sentences on one row.
| Number | Counterparty | Term | Seal | Status | Reminder |
|---|---|---|---|---|---|
| HT-24018 | East China dealer | Through 2027-03 | Stamped ×2 | In force | — |
| HT-23091 | Equipment service | 2026-09-30 | Stamped ×1 | Pending renewal | To-do 30 days before expiry |
| HT-25006 | New-client intent | — | Not requested | In approval | No stamp without approval |
| HT-22044 | Former supplier | Ended | History ×3 | Read-only archive | Do not stamp again |
Expiry is not tribal knowledge because the reminder is a to-do, not a notebook
Renewals, auto-renewals and termination notices all have legal or commercial clocks. Written in an admin notebook, they vanish on leave. Written in the ledger, a to-do is created before expiry and the responsible role can be chased. A pile of “final” emails cannot do this job—see The risk when contracts and policies live in email. An audit also checks whether number and seal are one chain—see What role OA plays in audit and compliance.
Seals are not tribal knowledge because the ticket comes before the stamp
The request states contract number, copies, perforated pages and whether the seal leaves the site. The stamp happens after approval. Return is checked off. Rush jobs still happen. Exceptions are backfilled the same day with a trail—not a permanent “stamp first, talk later.” When sales, delivery and finance share contracts, see how to split fields in Sales, delivery, and finance share contracts: how to split the back office. If the system is a filing cabinet you scan after the fact, expiry reminders never appear—see Filing cabinet vs. work entry: two ways to treat the system.
Phase one does not need full contract-lifecycle software. List live contracts, expiry to-dos, and bind seals to numbers, and departments will open it every day: sales checks terms, admin checks the seal, finance matches the billing entity. DaXi starts with the contract type you already get wrong. To stand up the ledger, say who holds contracts today on the Management systems service page. Benefit overview: Visible efficiency a management system can deliver.
A ledger is not a warehouse of scans
Upload every PDF while the number still lives in admin’s head, and expiry still slips. Fields at minimum: counterparty, start and end, auto-renew yes/no, seal count, whether the invoice title matches. Miss any one, and finance and sales still search their own inboxes. On access, not everyone downloads the full attachment pack. Export is its own column—see How clear permissions cut disputes and leaks. In a sample, the ledger is the index of the evidence chain—see What role OA plays in audit and compliance. Collect live contracts first. History can be read-only archive. You do not have to migrate every old email in phase one. Reminders in to-dos are what turn a spreadsheet into work. Rush seals can be exceptions, but they must be backfilled that night or the ledger splits back into email within a week.
Invoice title not matching the contract party is the row finance catches first. Make it required and sales will fix it before the seal, instead of fighting on invoice day. Departments open the ledger to avoid that fight.