Invoice Archive

The archive keeps a tamper-evident copy of every invoice and credit note your billing entity issues. Open it from the sidebar under Billing → Archive.

Nothing to set up — documents are archived the moment they are issued:

• Invoices — when you send one by email or mark it as sent (or mark a draft straight away as paid). That is the moment it gets its number.
• Credit notes — when you cancel an issued invoice, which issues the credit note.
• The stored copy is the PDF your client receives — identical to the emailed attachment.
• Archiving runs automatically in the background. If storing a document fails, it is retried automatically.

• Invoices and credit notes issued before automatic archiving was introduced. They are not added afterwards.
• Drafts, quotes and retainer contracts — only issued invoices and credit notes are archived.
• Re-sends. Sending an issued invoice again does not create a second copy.
• Invoices you receive from suppliers. TeeckIn does not receive invoices on your behalf, so keep those yourself.

The Archive page shows how many documents are archived and anchored, and lists them:

• Each row shows the counterparty, the number, the invoice date, the amount, the anchor status and the date it is kept until.
• Search by invoice number or counterparty.
• Open an entry to see its digests, seal and anchor, its event history, and to download the original or the readable view.

In plain words, each archived document goes through four steps:

1. 1
   Fingerprint — TeeckIn computes a SHA-256 digest of the file. Change a single byte and the fingerprint changes completely.
2. 2
   Seal — the fingerprint is signed with TeeckIn's archiving key, so anyone holding the public key can check it.
3. 3
   Batch — seals are grouped, and one combined fingerprint (a Merkle root) stands for the whole batch while still proving each document is in it.
4. 4
   Anchor — that batch fingerprint is timestamped with OpenTimestamps, which writes it into the Bitcoin blockchain. Confirmation usually takes about an hour.

Once anchored, anyone can prove that the document existed in exactly this form no later than the time of that Bitcoin block — without having to trust TeeckIn.

The anchor status of each entry tells you where it stands:

• Archived · anchoring pending — sealed and stored; the Bitcoin confirmation has not arrived yet.
• Anchored — the seal is attested by a Bitcoin block, shown with its block number.
• Anchoring problem — the anchor could not be completed. The document is still sealed and stored, and the problem has been flagged to us.

1. 1
   Go to Billing → Archive
2. 2
   Open the entry you want to check
3. 3
   In Check integrity, click Check integrity
4. 4
   Read the result: every check passed, or which one failed

TeeckIn re-reads the stored bytes, recomputes every digest and replays the proof chain:

• Original document digest
• Readable view digest
• Seal signature
• Inclusion in the timestamp batch
• Bitcoin anchor
• Event journal chain

1. 1
   On the Archive page, find Export your archive and click Export archive
2. 2
   The export is prepared in the background — we email you when it is ready
3. 3
   Click Download. The download stays available for 30 days.

The bundle holds every original and readable document, a manifest with all digests, seals and timestamp proofs, the event journal, the public keys, and instructions plus a script to check it all — no TeeckIn account required.

Each document is kept for ten years from its invoice date — not from the day it was archived. The Kept until date is shown on every entry.

• Changing plan, or moving to Free, does not shorten the retention of documents already archived or remove your access to them.
• If you close your account, a full export of the archive is generated; the archive and its export stay available for 90 days, after which they are permanently deleted with the billing entity.

• Anyone who can see the billing entity's invoices can see its archive. Running an integrity check or requesting an export needs permission to edit billing.
• Integrity checks and exports need a connection.