Getting the signed PDF back to Salesforce is the part that usually falls to a person. Here it does not. The moment the last signature lands, the sealed PDF posts to the record that sent it, the certificate of completion is stored beside it, and the signed date, signer and status write back to fields you can report on.
Three things happen at completion, in this order, without anyone pressing anything.
The send carries the record id that started it. When the document completes, the file posts to Files on that exact record, whether the send began on an Opportunity, an Account, a Contract, a Quote or an object your admin built.
Files arrive as template name, record name and completion date, so a Files list reads like an index instead of a pile. Set your own pattern on the template if your filing convention is different.
The certificate of completion posts as a second file on the same record, carrying signer identity, email, timestamps, device and the full event history. The evidence never travels separately from the agreement.
A file on a record is useful. Values in fields are reportable. On completion the app writes the facts of the signature to fields you choose, and your admin maps them once.
| Written value | Type | What it gives you |
|---|---|---|
| Signature_Status__c | picklist | Sent, viewed, signed, completed or expired, so a list view shows the whole pipeline of paper. |
| Signed_Date__c | date/time | The moment the final signature landed, which is what renewal and expiry maths runs off. |
| Signed_By__c | text | The named signatory as they signed, printed the same way on the certificate. |
| Signer_Email__c | The address the link was opened from, for matching against the contact on the record. | |
| Countersigned_By__c | text | Who signed for your side, so internal approval is visible without opening the PDF. |
| Document_Name__c | text | The file name as it was stored, so a report row links straight to the right file. |
| Certificate_Id__c | text | The identifier of the certificate of completion, for audit and diligence requests. |
| Time_To_Sign__c | number | Hours between send and completion, which is the number that makes cycle time a chart. |
Once signature facts live in fields, they behave like every other Salesforce number. Reports, dashboards, list views and forecasting all reach them with no extra tooling.
Filing is only useful if it respects the model your org already has. The app follows your objects, your retention rules and your sharing settings.
Point the send action at Opportunity, Account, Contract, Quote, Case, or a custom object such as Onboarding, Grant, Property or Placement. The file returns to that object, the fields write back to that object, and the related list appears on that page layout. Junction objects and lookup relationships are supported, so a signed PDF can land on a parent record while the fields update on the child.
Choose whether the file attaches to the record that sent it or to a related parent, so filing follows how your team searches.
Sealed PDFs and certificates stay available for as long as your plan is open, and they sit inside your org where your own retention policy governs them.
Access follows the record. Profiles, permission sets and sharing rules decide who opens the file, exactly as they do for every other attachment.
Pull the agreement and its certificate together for audit, diligence or your own archive. Nothing is locked in a format you cannot read.
The seal validates on its own, aligned with ESIGN, UETA and eIDAS. Detail sits on the legality page.
Start free, install the app, and watch the next completed agreement arrive on its own record. Seats are $12 per user per month billed annually.