E-invoicing
Invoice Crowd creates Peppol BIS Billing 3.0 sales invoices as UBL 2.1 files, checks them locally and lets you download them for the Peppol Access Point your business chooses. An optional customer-managed Peppol.sh connection can also keep configured delivery and status context linked to the invoice.
What is implemented
Invoice Crowd owns the document it builds and the bounded checks it can prove. Your chosen Access Point owns authoritative Peppol rules, participant discovery, onboarding, network delivery and delivery evidence.
No Invoice Crowd provider account required
For a supported standard sales invoice, Invoice Crowd uses the saved business, customer, tax, payment and total data to create deterministic UBL XML. The local preflight catches bounded structural problems before download.
The downloaded XML is handed to the Access Point portal or service selected by the customer. That provider remains responsible for current network rules, participant discovery, onboarding and delivery evidence.
Customer-managed Peppol.sh Personal
Where the connection is explicitly enabled, the customer enters the API key for its own Peppol.sh Personal account and selects the exact company returned from that provider workspace. The key is encrypted and write-only in Invoice Crowd.
Connected delivery sends provider JSON plus the complete UBL attachment only when the implementation can preserve the invoice meaning. An unsupported or ambiguous document is refused rather than simplified.
Manual import, not inbound network receiving
A supplier UBL file can be uploaded manually on Bills. Invoice Crowd validates a bounded supported shape and exact receiver match, then creates an unposted draft bill for review.
The importer is deliberately conservative. Unsupported types, unsafe XML, mismatched receivers, invalid money or duplicate evidence fail without partially creating a bill.
Supported Peppol workflow
The safest rollout treats local file creation, provider delivery and jurisdiction-specific compliance as three separate evidence gates.
Outbound export is limited to standard sales invoices.
Invoice Crowd builds a structured XML document rather than treating a PDF as an e-invoice.
Local checks catch supported structural issues; they are not authoritative network validation.
The customer EAS and Endpoint ID are entered from evidence supplied by the recipient or provider.
A buyer reference is kept distinct from Invoice Crowd internal document references.
Ambiguous tax category treatment is refused rather than guessed.
A standalone positive shipping field is refused because it lacks a Peppol tax category.
A document discount calculated after tax is refused rather than reinterpreted.
A customer-managed Peppol.sh API key is encrypted and never returned in full.
The optional connection does not claim an inbound status webhook.
Manual supplier UBL import creates an unposted draft bill only.
Use a downloaded UBL file with the Access Point your business chooses or configure the optional customer-managed Peppol.sh delivery path where available.
Questions
No. Invoice Crowd can create a supported UBL invoice file and, where explicitly enabled, connect to a customer-managed Peppol.sh Personal account. The Access Point remains the network service provider.
Yes. The default file workflow does not require an Invoice Crowd provider account, provider fee, API key, legal-entity record or webhook worker. You download the UBL XML and upload it through the Access Point you choose.
No. It is a bounded local check for the supported document shape. Your Access Point and the applicable authority remain responsible for current authoritative validation, participant discovery and acceptance.
Only when the feature flags are deliberately enabled, a business can enter the API key for its own funded Peppol.sh Personal account, select the exact provider company and send a supported standard sales invoice. Provider onboarding, verification, balance and external acceptance remain the customer’s responsibility.
No. There is no inbound Peppol.sh receiver or webhook. A supplier UBL file can be uploaded manually on Bills, where a supported document creates an unposted draft for review.
Outbound export is limited to standard sales invoices. Estimates, recurring templates, subscriptions, payment links, bills, purchase orders, vendor credits, credit notes and other unsupported types cannot be exported.
No. An invoice with a Peppol submission can't be deleted. Use Void instead: the invoice keeps its number, is marked Void and is reversed in your books. Agree any correction with your customer through your Access Point process.
Confirm the invoice data, download and inspect the UBL, then have your chosen Access Point and local adviser verify the network and jurisdiction-specific requirements before production use.
