DocuSign vs. PandaDoc: which has an audit trail at close?
Today, only DocuSign — through Loopfour. Loopfour's DocuSign integration implements a dedicated getAuditEvents action; its PandaDoc integration doesn't have an equivalent action yet. That's a gap in Loopfour's current PandaDoc integration, not a PandaDoc API limitation — PandaDoc's own API added a document audit-trail endpoint that Loopfour simply doesn't call yet.
Part of the finance integrations guide.
| DocuSign, via Loopfour | getAuditEvents action calls DocuSign's listAuditEvents endpoint |
|---|---|
| PandaDoc, via Loopfour | No audit-trail action implemented in Loopfour's integration today |
| PandaDoc's own API | Has a GET /documents/{document_id}/audit-trail endpoint — the capability exists, Loopfour just doesn't wire it up yet |
| What this means for close | Pulling a contract's audit trail for close-period documentation works out of the box for DocuSign, requires a manual PandaDoc lookup for now |
| Access requirement | PandaDoc's audit-trail endpoint is restricted to authorized workspace administrators |
The real answer is about Loopfour's integration, not the vendors
It's tempting to read this as a DocuSign-vs-PandaDoc capability gap, but it isn't one. DocuSign's eSignature API has offered a listAuditEvents endpoint for years, and PandaDoc's Public API v2 has since added an equivalent GET /documents/{document_id}/audit-trail endpoint that returns comparable data — user actions, timestamps, and event types for a document's full history. Both vendors can answer "who did what, and when" for a signed document. The actual difference is which of the two Loopfour has implemented: getAuditEvents exists in the DocuSign integration's action set; nothing equivalent exists yet in the PandaDoc integration.
Why this matters at month-end close specifically
An auditor or controller closing a period that includes a newly signed contract often needs more than the final signed PDF — evidence of when it was sent, when each party viewed it, and when it was actually signed, to support cutoff and revenue-recognition timing questions. For a DocuSign-signed contract, a Loopfour workflow can pull that evidence programmatically as part of the close checklist. For a PandaDoc-signed contract today, the same evidence exists on PandaDoc's side — a workspace administrator can retrieve it from PandaDoc directly — but it isn't yet something a Loopfour workflow can fetch automatically.
What to do about it today
For a PandaDoc-signed contract that needs audit-trail evidence at close, retrieve it directly through PandaDoc's own interface or API (a workspace admin can call GET /documents/{document_id}/audit-trail) rather than expecting it to show up automatically in a Loopfour workflow. If audit-trail evidence is a recurring close requirement across both e-signature tools, that's a real, well-scoped integration gap worth raising — the endpoint already exists on PandaDoc's side, so closing this gap is a matter of Loopfour implementing the call, not waiting on PandaDoc to build anything new.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Field mapping
Audit-trail capability: vendor API vs. Loopfour's current integration
| Vendor's own API | Loopfour's integration today | |
|---|---|---|
| DocuSign | listAuditEvents endpoint | Implemented (getAuditEvents) |
| PandaDoc | GET /documents/{document_id}/audit-trail endpoint | Not implemented |
Frequently Asked Questions
Sources
Related
Topic
Month-End Close
Month-end close is the set of accounting tasks a company runs after a calendar month ends to turn raw transactions into a finished, trustworthy set of financial statements: reconciling subledgers, boo…
Read moreTopic
Integrations
Every finance automation vendor publishes an integrations page: a grid of logos, a claim of "seamless" connectivity, and not much else. That page answers a marketing question — does this vendor touch…
Read moreDiagnostic
Does a DocuSign envelope carry contract-value data for revenue recognition?
No, not as a structured field. A DocuSign envelope exposes signer-facing tabs and free-form custom fields, but neither is a line-item or deal-value object — tabs collect data a signer enters or reviews, and custom fields store metadata as arbitrary strings. There is no built-in field a revenue-recognition workflow can read as "contract value."
Read moreDiagnostic
Can a PandaDoc proposal's pricing table become the AR invoice basis?
Structurally, yes. A PandaDoc pricing table stores typed rows with name, price, quantity, tax, and fee fields — real data an AR workflow can read directly, unlike a DocuSign envelope's free-text fields. The catch is timing and accuracy: the invoice basis should come from the signed document's final pricing table, not a draft version that changed during negotiation.
Read more