Informal business arrangements
An informal partnership or business arrangement
Seek proper formalization, and tell a draft, an agreement, a capital contribution and a reimbursement apart before you organize the files. Documenting the informal period doesn't, on its own, settle who holds what share or who is liable for what. Goal: organize records from the informal period and move towards formalizing it.
The problem
This use is limited to documenting the informal period of a business that already moves money and whose terms were agreed by message.
Tell a draft apart from an agreement, and a capital contribution apart from a reimbursement. Seek proper formalization; whether a partnership exists, who holds what share and who is liable depend on the facts, the documents and the law that applies where you operate.
Many partnerships start this way: trust, urgency and conversations on a phone. Contributions are made by bank transfer, tasks and profits are split by message, and nobody stops to formalize anything. When the business takes off, or when it goes wrong, the conversations have been lost to phone changes and deleted groups, and each partner remembers the deal differently.
The right path is to formalize. This use case is for documenting the informal period until that happens.
What to preserve
Exports of the communications, proof of contributions and relevant documents.
Goal: organize records from the informal period and move towards formalizing it.
Main file: drafts, messages and receipts labelled by purpose.
When to capture: at the milestones of the agreement and of each transfer.
Supporting sources: the business's documents and professional advice on formalizing it.
Limit of this scenario: on its own, the Record does not establish that a partnership exists, anyone's share or anyone's liability.
Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.
A chat export can keep the available sequence in which the terms were discussed, without guaranteeing it is complete. Link each receipt to the parties and the context, telling contributions, reimbursements and other transfers apart; a transfer on its own doesn't define its purpose. Profit-split spreadsheets, proposals and draft agreements that circulated belong here too.
How Provenia documents this scenario
Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.
Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.
Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.
Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.
In this scenario, use drafts, messages and receipts labelled by purpose as your reference material and check it against the business's documents and professional advice on formalizing it. The timestamp on a hash does not confirm that a partnership exists, anyone's share or anyone's liability.
Step by step
- Seek proper formalization, and tell a draft, an agreement, a capital contribution and a reimbursement apart before you organize the files. Documenting the informal period doesn't, on its own, settle who holds what share or who is liable for what.
- Tell a draft apart from an agreement, and a capital contribution apart from a reimbursement. Seek proper formalization; whether a partnership exists, who holds what share and who is liable depend on the facts, the documents and the law that applies where you operate.
- Preserve drafts, messages and receipts labelled by purpose exactly as it is; don't edit the file you register.
- Link the material to the business's documents and professional advice on formalizing it; describe its origin and when it was captured as declared information.
- Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.
What the Record shows and what it does not
A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish that a partnership exists, anyone's share or anyone's liability. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
What can this Record be used to check?
Whether the file you kept matches the registered hash and, where there is a valid timestamp, that the hash is tied to the UTC date and time shown. On its own, it does not establish that a partnership exists, anyone's share or anyone's liability.
Does the Record define each partner's share and liability?
No. Whether a partnership exists, each partner's share and who is liable depend on the facts, the documents and the law that applies where you operate; a Record doesn't settle that. Tell drafts, agreements, contributions, reimbursements and formalization apart, and get advice from a qualified local professional.
Which date is certified?
Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.
Official references
Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.
- RFC 3161 — Time-Stamp Protocol (IETF)https://datatracker.ietf.org/doc/html/rfc3161
Start with three free credits
Seek proper formalization, and tell a draft, an agreement, a capital contribution and a reimbursement apart before you organize the files. Documenting the informal period doesn't, on its own, settle who holds what share or who is liable for what.
Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.
Already have an account? Log in.