Closeout

Signed on site. Verifiable from the office.

The customer signs the project confirmation on a phone or tablet: address, occupant, start and description of the job. Your own documents too: privacy notice, tenant information, permission to enter. Krahasso produces a PDF and records who signed, when, and with which checksum. Also which of your people was present.

  • Project confirmation and your own documents, signed on site
  • SHA-256 checksum of the signed PDF, recomputable from the office
  • The signatory receives their copy as an email attachment

30-day money-back guarantee. No credit card.

Project confirmation P-2041
Signed at handover
Musterstrasse 5, 10115 Berlin · 28 Sep 2026
Signatory
B. Bauer (client)
Signed at
28.09.2026, 16:12
Checksum
sha256:4f2a9c… e81d
Simple electronic signature under eIDAS. Verifiable from the office, revocable with a reason.

Sign it. Record it. Check it later.

On site the project confirmation shows on the device and is signed. Krahasso creates a PDF and stores the checksum alongside it. If they want one, the signatory gets their copy. Back in the office you recompute it and see the document is still the same one. That holds for the project confirmation and for your own documents.

Signing

Signed with a finger. On a phone or tablet.

The customer sees the document on the device and signs with a finger. Name and role sit underneath, from tenant through property manager to loss adjuster. The signature is stored in the app first and uploaded afterwards. So your technician carries on in a basement with no signal. The document itself is fetched beforehand, while there is still a connection.

Your own documents

Written once. Filled in on every job.

Privacy notice. Tenant information. Permission to enter. You write your wording once in the office. On the job, tenant, address and project number are already in it. Your technician asks for none of it again on site. No carbon copy left behind in the van. They show the document, the customer reads and signs. The first signature fixes the text. Later changes to your template leave signed copies alone.

For information only

Not everything needs a signature. It still needs a record.

Some documents only inform. For each one you choose: sign, confirm receipt, or send only. It goes out as a PDF by email, straight from the job. Krahasso records which address it went to, and when. If the client asks later, you show the send.

Samples

Samples to start from. The wording stays yours.

Krahasso ships samples for the usual documents. You adopt one as a draft and fill the marked gaps. Only a released document can be assigned to a job. So no half-finished text reaches a tenant. The samples are a starting point and not legal advice. What your business has people sign is your business's call.

The record

Time, name, checksum. And who was there.

The timestamp from the device. The signatory's name and role. The member of your team who was present. A SHA-256 checksum of the signed PDF. From the office the checksum is recomputed and compared with the stored one. Where several people sign the same document, they all carry the same content checksum. If the property manager asks later, it is all there. In legal terms this is a simple electronic signature under eIDAS, not a certificate and not a qualified signature.

The customer's copy

The signatory gets their copy. From your business.

If the signatory leaves an email address, the signed PDF goes straight to them as an attachment. Ready to file or forward. It comes from your business, and replies come back to you. Everyone involved holds the same version.

Corrections

Signed by mistake. Revoked with a reason.

A signature taken in error is revoked with a reason. The reason is mandatory and is kept with the name and time of the revocation. Both the signature and the revocation stay in the record. A handover that stands is an invoice that goes out.

Take the next step

See it on a job of your own.

A short call where we walk through your actual workflow and show what it looks like in Krahasso.

Hosted in Germany

Servers and backups sit in German data centres. Processing under Art. 28 GDPR, with the DPA included.

E-invoicing to EN 16931

With the Commerce module: every invoice as XRechnung or ZUGFeRD, mandatory fields checked before it goes out.

Backed up daily

Backups at a second German data-centre site, kept for 31 days.

Your data stays yours

Projects, receipts and documents export to file whenever you want, including on your way to someone else.

Closeout

More in Closeout

All features
Drying protocol
Drying report
Musterstraße 5, Berlin
P-2041
14.05.2026
Client
Beispiel Versicherung AG
Claim #BV-2026-04417
Restorer
Trocknungs GmbH
Berlin, DE
Equipment deployed
DH-014
Trotec TTK 125 S
12 days
142 kWh
DH-027
Aerial AD 660
12 days
218 kWh
FAN-088
Drymatic Boost
8 days
67 kWh
Readings per visit: MP-1 Wall A
Visit 1
28.04.2026
86 → 82
Digits
Visit 2
05.05.2026
82 → 71
Digits
Visit 3
12.05.2026
71 → 62
Digits
Photographic evidence
Created on 14.05.2026
Page 1 / 6

Reports

Leak detection. Drying. Floorplan. Three reports as PDFs, from the data already in the project.

Receipts & tax
Q3 2026
Beleg_2026-09-14.pdf
read out
Supplier
Baustoffe Meyer GmbH
Date
14.09.2026
Net
842,02 €
VAT 19 %
159,98 €
Advance VAT
1.184,20 €
payable this quarter
Cash-basis
18.430,75 €
result to date
Period as a DATEV posting batch
EXTF format, with the documents if you want them

Receipts, tax & DATEV

Have receipts read out. Figures for UStVA, EÜR and the EC Sales List. Hand a period over as a DATEV posting batch.

Get started

Your first job. Set up together.

We set up your warehouse and your first project with you. On the call we work out which modules fit your business. Every number that is right on site is right in the report.

30-day money-back guarantee. No credit card.