Certyneo Webhooks: Automate Accounting Close in Your ERP

When a document is signed electronically via Certyneo, what happens next in your accounting chain? For most businesses, the answer is still too often: nothing automatic. An employee manually downloads the signed PDF, sends it by email to the accounting firm, who re-enters it into their management software. This fragmented process generates errors, delays, and a loss of traceability incompatible with the requirements of a reliable financial statement. Certyneo webhooks address this issue precisely: they automatically trigger actions in your third-party systems — ERP, accounting software, document management — as soon as a signature event occurs. This article explains in detail how to configure and exploit these webhooks to streamline your accounting cycle end-to-end.

What is a webhook and why it's essential for accounting

The webhook principle explained simply

A webhook is a real-time HTTP notification mechanism: instead of regularly asking an API "has something changed?" (the so-called polling approach), the sending application — here Certyneo — sends an HTTP POST request to a URL of your choice as soon as a specific event occurs. In accounting, this means that the moment a purchase order, supplier contract, or expense report is electronically signed, your ERP can be instantly notified, without human intervention.

Unlike a simple CSV export or a monthly report, the webhook guarantees near-real-time data synchronization. For an accounting firm managing monthly or quarterly closings, this granularity is decisive: supporting documents are available in the system immediately upon signature, not at the end of the month during a laborious catch-up.

Certyneo events that trigger accounting close

Certyneo exposes several types of events via webhooks, directly exploitable in an accounting context:

• `envelope.completed`: all parties have signed the document — this is the main trigger for injecting a supporting document into your ERP.
• `envelope.declined`: a signer has refused — useful for alerting the accounting department of a disputed invoice.
• `envelope.expired`: the signature deadline has passed — allows you to restart a procedure and avoid a gap in accounting.
• `signer.signed`: partial signature by a party — relevant for multi-signer contracts (e.g., commercial lease requiring signature from both landlord and tenant).

Each JSON payload sent by Certyneo contains essential metadata: document identifier, qualified timestamp, signer names, secure URL to download the signed PDF and audit trail. This structured data is directly exploitable by an ERP or accounting software.

Step-by-step configuration of Certyneo webhooks for an ERP

Create and register a webhook endpoint

Configuring a Certyneo webhook is done from the dashboard, Settings > Integrations > Webhooks section. Here are the key steps:

1. Define the destination URL: this is the endpoint exposed by your ERP or integration middleware (e.g., a dedicated endpoint in SAP, Sage, Cegid, or an iPaaS tool like n8n, Make, or Zapier).
2. Select the events to listen to: for accounting close, prioritize at least `envelope.completed` and `envelope.declined`.
3. Configure the HMAC signature secret: Certyneo signs each payload with a secret key that you define. Your endpoint must verify this signature to guarantee the authenticity of notifications — a non-negotiable security step.
4. Test with simulation mode: Certyneo allows you to send a test payload without creating a real document. Verify that your endpoint responds correctly with an HTTP 200.

Map payload data to your chart of accounts

Once the endpoint is operational, you must map the fields of the Certyneo payload to the fields expected by your ERP. Here is an example of mapping logic for a supplier contract:

```json { "event": "envelope.completed", "envelope_id": "env_01HX...", "completed_at": "2026-05-26T14:32:00Z", "document_url": "https://app.certyneo.com/documents/signed/...", "metadata": { "type": "supplier_contract", "amount_ex_tax": 12500, "accounting_account": "607", "supplier_id": "F-2891" } } ```

The `metadata` field is freely configurable when creating the envelope via the Certyneo API. This is key to enriching each signature with the business data necessary for automatic accounting: account number, cost center, fiscal year, etc. To explore the technical integration possibilities further, consult the Certyneo help center which lists the full API documentation.

Handle rejections and automatic retries

A webhook can fail if your endpoint is temporarily unavailable. Certyneo implements an exponential retry policy: if there is no HTTP 2xx response, the system retries at increasing intervals (5 min, 30 min, 2 h, 24 h) over a 72-hour window. Beyond that, the webhook is marked as failed and an alert is raised in the dashboard.

For accounting, this resilience is crucial: a supporting document not received in the ERP can generate a balance sheet discrepancy. It is therefore recommended to complement the webhook mechanism with a daily reconciliation job that queries the Certyneo API to list envelopes completed in the last 24 hours and verify their presence in the accounting system.

Integration with major ERPs and accounting software

Native connection with Cegid, Sage, and Pennylane

Several publishers of popular accounting software in France offer connectors or REST APIs compatible with Certyneo webhooks. Here are the most common integration patterns:

Cegid XRP Flex: exposes a REST API allowing the creation of accounting entries and attachment of files. The `envelope.completed` webhook triggers a POST call to the Cegid API to create the entry and attach the signed PDF as a digital supporting document.

Sage 100cloud / Sage 50: the recommended approach is through a lightweight middleware (Python or Node.js script hosted serverless) that receives the Certyneo webhook, downloads the document via the secure URL, and deposits it in Sage's automatic import folder.

Pennylane: cloud-native solution whose API directly accepts documents as attachments with their accounting metadata. The webhook-Pennylane integration is particularly suited for accounting firms managing documents for multiple clients — a use case we detail in the scenarios section.

For teams evaluating different solutions before migrating to Certyneo, the comparison of electronic signature solutions offers a detailed view of integration capabilities by platform.

Use an iPaaS like Make or n8n for non-developers

If your organization does not have a dedicated technical team, no-code/low-code automation platforms (Make, n8n, Zapier) are an effective alternative. The principle is simple:

1. Create a scenario with a webhook trigger on Make or n8n — the generated URL serves as your Certyneo endpoint.
2. Configure the following actions: download the signed document, parse metadata, send to Google Drive / SharePoint, create a row in a tracking spreadsheet, notify the accounting manager via Slack.
3. Optionally, trigger an API call to your accounting software to create the entry.

This approach allows you to achieve a high level of automation in less than a day, without writing a single line of code. It is particularly relevant for SMEs or accounting firms wishing to automate document collection for their clients without mobilizing a developer.

Security and audit best practices for accounting webhooks

HMAC signature verification and endpoint security

In an accounting context, the reliability of data received via webhook is critical. An attacker who succeeded in injecting false `envelope.completed` events could corrupt your accounting. Three security measures are necessary:

• HMAC-SHA256 verification: each Certyneo request includes an `X-Certyneo-Signature` header. Your endpoint must recalculate the signature with your secret key and compare — reject any request whose signature does not match.
• JSON schema validation: before any processing, validate the structure and data types of the received payload. A `amount_ex_tax` field with a `null` or negative value should trigger an alert, not an erroneous accounting entry.
• Immutable logging: preserve each received payload in a timestamped, non-modifiable log for at least 10 years, in accordance with document retention obligations (Article L123-22 of the French Commercial Code).

Traceability and audit trail for the accounting firm

One of the major advantages of the webhook approach is the end-to-end traceability it generates. Certyneo produces for each signed document an audit trail (audit trail) compliant with eIDAS requirements, including the qualified timestamp, the IP addresses of the signers, and the certificates used.

By combining this audit trail with the webhook payload, your ERP can store not only the supporting document but also the proof of its legal validity. For an auditor or accounting firm, this dual layer — document + proof — significantly simplifies verification during an audit or review. The electronic signature in business details the signature levels and their probative value in different business contexts.

To calculate the return on investment of this automation before you launch, the Certyneo ROI calculator allows you to precisely estimate time and cost savings based on your volume of signed documents.

Legal framework applicable to webhooks and digital accounting

The automation of the accounting chain via electronic signature webhooks falls within a specific regulatory framework that must be understood.

eIDAS Regulation No. 910/2014 (and its eIDAS 2.0 revision): the European regulation on electronic identification and trust services establishes the legal value of electronic signatures. Article 25 provides that an electronic signature cannot be denied legal effect solely because it is in electronic form. Qualified signatures (QES) benefit from a presumption of reliability equivalent to a handwritten signature. For accounting documents, the appropriate signature level depends on the nature of the document: a simple invoice may use an advanced signature (AES), while a capital lease contract or an electronic notarial deed requires a qualified signature.

French Civil Code, Articles 1366 and 1367: Article 1366 recognizes electronic writing as evidence in the same way as paper writing, provided that the person from whom it originates can be duly identified and that it is established and preserved in conditions to guarantee its integrity. Article 1367 defines electronic signature as the use of a reliable process for identification guaranteeing the link with the act to which it is attached. The Certyneo webhook, by transmitting the audit trail with each signed document, meets this requirement for identification and integrity.

Article L123-22 of the French Commercial Code: accounting documents and supporting documents must be retained for ten years. Documents received via webhook and stored in an ERP must therefore be subject to a compliant retention policy, including immutability and long-term readability of formats (PDF/A recommended by ISO 19005 standard).

GDPR No. 2016/679: webhook payloads contain personal data (signer names, email addresses, timestamps related to individuals). Your endpoint and your ERP are recipients of this data — you are responsible as a processor or joint processor depending on the contractual terms with Certyneo. The DPA (Data Processing Agreement) must be formalized. The data transmitted must be minimized to what is strictly necessary for the accounting purpose.

NIS2 Directive (2022/2555): for companies falling within the NIS2 scope (essential service operators, important entities), the security of API interfaces and webhooks is a mandatory network security measure. HMAC verification, TLS 1.3 minimum encryption, and logging of access are required.

ETSI EN 319 132 Standard: defines the XAdES format for advanced electronic signatures. Signatures produced by Certyneo comply with these ETSI standards, guaranteeing their interoperability with archiving systems with probative value compliant with the French general security reference (RGS).

Concrete use cases

Scenario 1: An accounting firm managing 40 client files

An accounting firm of about ten employees manages engagement letters, SEPA mandates, and annual accounts for 40 client companies. Before integrating Certyneo webhooks, each signed document was manually retrieved by a file manager, renamed according to a naming convention, then deposited in the client folder of the accounting production software. This process represented approximately 15 to 20 minutes per document, or several hours per week during closing periods.

After configuring an `envelope.completed` webhook connected to their document management tool via Make, the firm automated this entire chain: as soon as a document is signed, the signed PDF is automatically filed in the corresponding client folder with the correct filename, a notification is sent to the relevant manager, and a row is created in the document receipt tracking spreadsheet. The estimated time savings is around 70 to 80% on this task, or about 6 to 8 hours recovered per week during closing periods — a figure consistent with benchmarks published by the French Order of Accountants in its reports on digital transformation of firms.

Scenario 2: An industrial SME with a Sage ERP and 300 annual supplier contracts

An SME in the industrial sector signs approximately 300 supplier contracts per year (standing orders, amendments, confidentiality agreements). Each signed contract must be attached to a supplier record in Sage 100cloud and archived as proof of commitment. Without automation, the purchasing department transmitted signed contracts by email to the accounting department with an average delay of 3 to 5 business days.

After deploying a Node.js middleware receiving Certyneo webhooks and calling the Sage API, the attachment delay fell to a few seconds. Off-balance-sheet commitments are now recorded in real time, which improved the reliability of interim statements presented to the CFO. The project was completed in less than two weeks by an internal developer, leveraging the webhook documentation in the Certyneo help center.

Scenario 3: A group of companies managing complex intercompany flows

A group consisting of a dozen subsidiaries uses Certyneo to sign its intercompany treasury agreements and intra-group service contracts. Accounting consolidation requires that each signed agreement be simultaneously recorded in the system of both the issuing subsidiary and the receiving subsidiary, with the same document identifier to facilitate elimination of reciprocal flows.

By configuring a single webhook that notifies the endpoints of both concerned subsidiaries in parallel (identified via the envelope metadata), the group eliminated consolidation discrepancies related to missing or misreferenced documents. The consolidated closing period was reduced by an average of 2 days, which represents a significant gain for a group finance department that closes quarterly. Teams considering migration from another solution can consult the migration guide to Certyneo to assess technical feasibility.

Conclusion

Certyneo webhooks are a powerful automation lever for any party wishing to integrate electronic signature at the core of their accounting process. By eliminating manual steps between signing a document and recording it in the ERP or accounting software, they reduce delays, data entry errors, and the risk of missing documents during a closing or audit. Whether it's an accounting firm, an SME, or a multi-entity group, webhook configuration is accessible — with or without a developer — and the return on investment is measurable within the first few weeks of use.

To learn more, consult the Certyneo help center to access complete documentation of the API and webhooks. Ready to automate your accounting close? Create your Certyneo account for free and connect your first signed documents to your ERP today.