Questions welcome.
Clarity included.
Straightforward answers about the platform, your existing systems and the way your documents move.
The platform
What does Docnaut connect?
Docnaut connects enterprise systems with Peppol, tax authorities, government platforms and business partners through a shared integration layer.
Does it replace our ERP?
No. Docnaut works with your existing ERP landscape, centralizing document transformation, validation, routing and monitoring.
Your ecosystem
Can we keep our existing EDI?
Yes. Docnaut connects traditional EDI processes with modern e-invoicing and compliance requirements, helping preserve existing exchanges.
Can we use one platform across markets?
Docnaut provides a centralized architecture for country-specific formats and compliance workflows. The team can review the precise markets and requirements for your project.
Does Docnaut support Peppol?
Yes. Docnaut supports standardized document exchange with Peppol networks and trading partners, including UBL documents.
Which ERP systems can we connect?
Docnaut supports SAP ECC, SAP S/4HANA, Microsoft Dynamics, Oracle, NetSuite, Sage, IFS and other enterprise systems.
Getting started & operations
How do teams track status?
Centralized monitoring provides document status, processing history and audit trails across the lifecycle.
Where should our project discussion start?
Share your ERP landscape, target markets, document formats and exchange requirements with the team. These details help frame an integration discussion.
Planning your project
How is a project priced?
A useful proposal depends on the systems, legal entities, countries, document types and expected volumes in scope. Share these details with the team so implementation and ongoing service requirements can be assessed together.
How long does implementation take?
Timing depends on interface readiness, mapping complexity, destination requirements and access to test documents and environments. Agree milestones, dependencies and acceptance criteria after the initial assessment rather than assuming one timetable fits every project.
Can we start with one flow or country?
Discuss a phased scope with the team. A clearly defined first flow can help validate interfaces, document rules and operational ownership before considering additional entities, networks or markets. The wider rollout should be planned against the requirements of each destination.
What should we review for security and data handling?
Include access roles, authentication, document sensitivity, data handling, retention requirements and operational responsibilities in the project discussion. Ask the team for the documentation and contractual information your organization needs before approving production use.
What if a document fails validation or delivery?
Review the document reference, processing stage and available status information. Your operational process should define who corrects source data, who investigates connectivity issues and how a corrected document is resubmitted. Agree these responsibilities during implementation.
How do we request technical support?
Use the contact form and select Technical Support, or email [email protected]. Include a document reference, relevant time and a concise description. Availability, escalation procedures and service commitments should follow your agreed support arrangements.
Big possibilities.
One simple conversation.
Let’s explore the connections your business needs next.
