产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $799.00 USD
- ERPNext 版本
- —
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Peppol Access Point Connector
Send and receive EN 16931 / Peppol BIS Billing 3.0 documents over the Peppol network straight from ERPNext. ECOSIRE builds, installs, and supports the connector for your v15/v16 environment on a build-to-order basis — no marketplace download.
$799.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Maps ERPNext `Sales Invoice` and credit notes to Peppol BIS Billing 3.0 UBL 2.1 output
EN 16931 business-rule and Schematron validation runs before any document is transmitted, with a stored validation report
SMP/SML participant lookup resolves the recipient's Access Point and capabilities by participant identifier
AS4 send/receive handoff to your chosen certified Access Point provider (BYO or ECOSIRE-recommended)
Dedicated `Peppol Document` DocType storing payload, message ID, direction, transmission status, and errors
`Peppol Settings` single DocType for participant ID, endpoint scheme, credentials, and default profile per company
`on_submit` / `on_cancel` doc-event hooks in `hooks.py` queue transmission when an invoice is submitted
Scheduler event polls the Access Point for inbound documents and drafts `Purchase Invoice` records from received UBL
PINT and country-specific CIUS profiles configured per company (national layers on top of BIS)
Whitelisted REST API methods to trigger send, re-validate, and query transmission status programmatically
Client script adds a `Send to Peppol` button and live transmission-status indicator on the invoice form
Role profiles and DocType permissions restrict who can transmit or view raw Peppol payloads
Background job queue with retry and error logging for failed transmissions, surfaced in the Frappe error log
Compatible with ERPNext and Frappe v15 and v16, packaged as a standard installable Frappe app
关于此产品
EU and international firms are increasingly obliged to exchange invoices as structured EN 16931 documents over the Peppol network rather than as PDFs or emails. ERPNext core can produce a print-format invoice and a generic e-invoicing export, but it has no concept of a Peppol participant, no SMP/SML lookup, no Access Point transport, and no BIS Billing 3.0 UBL that will pass Schematron validation at the receiver. Teams end up bridging the gap with a manual portal, a third-party SaaS with per-document fees, or a spreadsheet export — none of which keep the audit trail inside ERPNext where finance actually works.
为什么选择 Peppol Access Point Connector
Maps ERPNext `Sales Invoice` and credit notes to Peppol BIS Billing 3.0 UBL 2.1 output
EN 16931 business-rule and Schematron validation runs before any document is transmitted, with a stored validation report
SMP/SML participant lookup resolves the recipient's Access Point and capabilities by participant identifier
AS4 send/receive handoff to your chosen certified Access Point provider (BYO or ECOSIRE-recommended)
Dedicated `Peppol Document` DocType storing payload, message ID, direction, transmission status, and errors
`Peppol Settings` single DocType for participant ID, endpoint scheme, credentials, and default profile per company
ECOSIRE builds a proper Frappe application (its own module, DocTypes, and hooks.py) that turns your ERPNext into a first-class Peppol endpoint. We map Sales Invoice (and, where in scope, credit notes and Purchase Invoice) to Peppol BIS Billing 3.0 UBL, run EN 16931 business-rule and Schematron validation before anything leaves the system, resolve the recipient's Access Point through SMP/SML participant lookup, and hand the signed payload to your chosen Access Point over AS4. A dedicated Peppol Document DocType stores the outbound/inbound payload, transmission status, message ID, and validation report, so every exchange is traceable from the invoice it belongs to.
Technically, submission is wired through on_submit doc events in hooks.py so an invoice can be queued to Peppol the moment it is submitted, with a Peppol Settings single DocType holding your participant ID, Access Point credentials, endpoint scheme, and default profile. A scheduler event polls the Access Point for inbound documents and creates draft Purchase Invoice or Peppol Document records from received UBL, mapping supplier, tax, and line data back into ERPNext. Whitelisted methods exposed over the Frappe REST API let you trigger send, re-validate, or fetch transmission status programmatically, and client scripts add a "Send to Peppol" action plus a live status indicator on the invoice form. Country-specific and PINT profiles (e.g. national CIUS layers on top of BIS) are configured per company, and role profiles / permissions restrict who can transmit or view raw payloads. It targets ERPNext and Frappe v15 and v16.
Because this is build-to-order, it starts with a scoping call, not a download. We confirm your target countries and Peppol profiles, your Access Point provider (or advise on one), the document types in scope, and your ERPNext version, then quote a fixed build. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable source for your version, installation and configuration on your environment, UAT on a staging bench with a rollback plan, documentation, a training session, and a post-go-live support window. The git repository is handed over so the code is yours to keep and extend.
你得到什么
- Installable source code for your ERPNext/Frappe version (v15 or v16), packaged as a standard app
- Installation and configuration on your environment, including `Peppol Settings` and Access Point credentials
- UAT on a staging bench with a documented test plan and a rollback plan before go-live
- Technical documentation: DocType schema, hooks, whitelisted API methods, and profile configuration
- User guide plus a live training session for finance and operations users
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover so the code is yours to keep, audit, and extend
- Mapping specification for your in-scope document types and country/PINT profiles
这是给谁的
EU finance controller facing a Peppol mandate
Needs outbound and inbound invoices to move as compliant EN 16931 documents over Peppol without leaving ERPNext, with a clear audit trail and validation before send.
Cross-border seller with multiple country profiles
Sells into several EU markets and needs BIS Billing 3.0 plus the correct national CIUS/PINT profile applied per company and per recipient, configured once and enforced automatically.
ERPNext systems integrator or IT lead
Wants a properly built Frappe app with real DocTypes, doc-event hooks, and whitelisted API methods they can maintain and extend, not a black-box SaaS bridge or brittle export script.
Shared-service or group finance team
Processes AR/AP centrally and needs inbound Peppol documents auto-drafted into ERPNext, with role-based control over who can transmit and view raw payloads.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Peppol Access Point Connector 应用程序 ZIP。
将应用程序添加到您的工作台
将 ZIP 解压到您的 bench 的 apps 文件夹中，或者使用解压缩的应用程序的路径运行“bench get-app”。
安装在您的网站上
运行 `bench --site SITE_NAME install-app APP_NAME`，然后运行 `bench migrate` 以安装 Peppol Access Point Connector 并应用其架构。
激活您的许可证
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
Peppol Access Point Connector 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Delivery model | Build-to-order for your version, 2–4 weeks from scope | In-house project, timeline depends on your team | Instant download, generic to all installs | |
| Peppol BIS 3.0 / EN 16931 output | Built and validated for your in-scope documents | Must be built and maintained yourself | Often partial or one-profile only | |
| Validation before send | EN 16931 + Schematron with stored report | Only if you implement it | Varies; sometimes none | |
| SMP/SML participant lookup | Included, resolves recipient Access Point | Build and maintain yourself | Sometimes included | |
| Inbound receive into ERPNext | Scheduler polls AP, drafts Purchase Invoices | Extra scope to build | Often send-only | |
| Country / PINT profiles | Configured per company for your markets | Your responsibility to add | Limited profile coverage | |
| Code ownership | Git repo handed over, yours to extend | You own it fully | Vendor-locked, no source | |
| Support and updates | Post-go-live window + optional retainer | Your team maintains it | Generic support, mandate lag |
关于Peppol Access Point Connector的常见问题
+Is this a ready-made download from the Frappe marketplace?
No. This is build-to-order. ECOSIRE builds the connector for your specific ERPNext version, target countries, Peppol profiles, and Access Point provider, then installs and supports it. It is not an off-the-shelf marketplace download.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. Timing depends on the number of document types, country/PINT profiles, and your Access Point setup. We agree the exact timeline at the end of the scoping call before any build starts.
+Do you provide the Peppol Access Point itself?
The connector handles document generation, EN 16931 validation, SMP/SML lookup, and the send/receive handoff, but transmission runs through a certified Access Point provider over AS4. You can bring your own Access Point, or we can recommend and help you onboard one as part of the engagement.
+Which ERPNext versions are supported?
We build against ERPNext and Frappe v15 and v16. The app follows standard Frappe conventions — its own module, DocTypes, `hooks.py` doc events, scheduler events, and whitelisted API methods — so it fits cleanly into your bench and upgrade path.
+How do updates and support work after go-live?
Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the git repository, your team can maintain and extend the code directly, and ECOSIRE can quote ongoing support or profile updates (for new country mandates) separately.
+Can it receive inbound documents, not just send?
Yes. A scheduler event polls your Access Point for inbound Peppol documents and drafts `Purchase Invoice` or `Peppol Document` records from the received UBL, mapping supplier, tax, and line data back into ERPNext for review and posting.
+What happens if a document fails validation?
Documents are validated against EN 16931 business rules and Schematron before transmission. A failure is logged with a readable validation report on the `Peppol Document` record and the invoice is never sent, so non-compliant documents are caught inside ERPNext rather than rejected downstream.
申请报价
Peppol Access Point Connector
Send and receive EN 16931 / Peppol BIS Billing 3.0 documents over the Peppol network straight from ERPNext. ECOSIRE builds, installs, and supports the connector for your v15/v16 environment on a build-to-order basis — no marketplace download.
- Maps ERPNext `Sales Invoice` and credit notes to Peppol BIS Billing 3.0 UBL 2.1 output
- EN 16931 business-rule and Schematron validation runs before any document is transmitted, with a stored validation report
- SMP/SML participant lookup resolves the recipient's Access Point and capabilities by participant identifier
- AS4 send/receive handoff to your chosen certified Access Point provider (BYO or ECOSIRE-recommended)