Skip to content
Register

Features

Peppol e-invoicing through a configured Storecove access point

Invoice Crowd builds the structured invoice, hands it to Storecove, and records each attempt in a transmission log: pending, pending confirmation, submitted, rejected, failed or delivered. Supplier invoices that arrive over Peppol come back as unposted draft bills for review. The feature ships switched off and is enabled per business profile during controlled onboarding, not on every account.

Try Invoice Crowd See pricing
  • Storecove access point
  • Received bills arrive as drafts
  • Off by default, enabled per profile

Last updated:

The Peppol dashboard in Invoice Crowd showing sent invoice, received bill and error counts above a list of recent Peppol transmissions.

What is inside

Send through your own access point, and keep the evidence

Peppol here is deliberately narrow. You configure your own Storecove access point on a business profile, send standard sales invoices through it, and get supplier invoices back as unposted draft bills. Every attempt, outbound and inbound, is recorded in the transmission log.

Turning it on

Off until you configure it

Configuring the Storecove access point on a business profile in Invoice Crowd, with the participant ID, legal entity ID and webhook tenant ID filled in.

Two switches, and neither starts on

Peppol is fail-closed at two levels. A platform switch is off by default, and each business profile carries its own Storecove configuration: your seller participant ID, a Storecove API key, the numeric legal-entity ID and the exact webhook tenant ID. Nothing sends until both are on. Missing configuration is treated as do not send, never as consent.

  • The platform switch is off by default
  • Your own Storecove account, key and legal-entity ID
  • Enabled per business profile during onboarding

Invoice Crowd builds it, Storecove delivers it

The split of work decides what each side can promise. Invoice Crowd validates the invoice, the participants, the tax categories, the totals and the payment account, then builds the structured submission and a fixed submission reference. Storecove converts it to the applicable Peppol document, performs the network and scheme validation, routes it to the recipient and returns delivery events. Invoice Crowd records status, evidence hashes and timestamps against the invoice.

  • Storecove is the only provider you can select
  • Pagero and Unimaze are not supported
  • Conversion and network validation happen at the access point

Sending an invoice

Submitted is not delivered

Reviewing the Peppol transmission log in Invoice Crowd, where every attempt is recorded with its direction, sender, receiver and status.

Send, log the attempt, then wait for evidence

Pressing Send via Peppol saves any unsaved editor state, then validates the invoice locally against the business profile, the participants, the buyer reference, the currency, the totals and the tax categories. A failure there returns a safe rejection and nothing leaves the app. Otherwise a pending attempt is logged before the request leaves. An ambiguous connection result stays pending confirmation, and you retry the same contents under the same submission reference.

  • Submitted means accepted by the access point, not delivered
  • Delivered needs an authenticated webhook and matching sending evidence
  • A rejected invoice is not resent until you change it

Every line resolves to one Peppol tax category

Categories, exemption reasons and reason codes are stored on the tax itself, and each invoice line copies them when the invoice is saved, so a tax you set up once carries its Peppol meaning forward. Ordinary VAT is carried on each taxed line, and on a document-level discount where there is one, with the authoritative amounts in the tax subtotals. Anything ambiguous is rejected before sending rather than reinterpreted in transit.

  • One tax per line, or one invoice-level tax on every line
  • A zero rate needs its category chosen explicitly
  • Exempt and reverse charge each need a reason or reason code

What comes back

Nothing posts itself

An inbound Peppol transmission logged in Invoice Crowd after a supplier invoice arrived and was imported as a draft bill.

A supplier invoice becomes one draft bill

The webhook tenant ID has to resolve to exactly one enabled business profile before anything is fetched, and the document is retrieved with that profile's own encrypted API key. Invoice Crowd validates ownership, direction, document type, currency, supplier identity, dates, lines, tax and discount arithmetic and the payable total, then creates one vendor, found or created by Peppol ID, and one unposted draft bill linked to its inbound log row.

  • Never posts accounting, never marks a bill paid
  • Never overwrites an existing document
  • The same document arriving twice does not create two bills

A narrow supported path, deliberately

This is a controlled-onboarding integration rather than a general Peppol compliance product. Outbound covers the standard sales invoice only. Once an attempt is pending, submitted or delivered, the invoice is locked against editor saves, so correcting a transmitted invoice means issuing a corrective document rather than changing the evidence. Country and tax coverage depend on the Storecove service and account you configure, on your jurisdiction and on your accountant's sign-off.

  • Enabled deliberately, not through a signup flow
  • Failed and rejected attempts can be corrected and sent again
  • Invoice Crowd makes no independent certification claim

Built in

The rest of the Peppol path

The configuration details you meet on the way in, the tax rules that decide whether an invoice can be sent, and the boundaries worth reading before you plan a rollout.

  • Credentials stay hidden

    Your Storecove API key is stored encrypted and never returned by the app. Saving the form with the secret blank keeps the existing value.

  • Webhook secret

    A custom secret header, set identically in Invoice Crowd and in Storecove, is compared in constant time before processing. Never put it in a URL.

  • Customer Peppol IDs

    Simple identifiers go in as scheme:id. Compound schemes such as FR:SIRENE need the separate Scheme ID and Endpoint ID fields instead.

  • Buyer reference

    The Peppol buyer reference is its own field, supplied by your customer. Your internal document reference is never sent in its place.

  • Test the connection

    A test-connection action checks the current business profile against the configured Storecove legal entity. A separate flag records whether those credentials are sandbox ones.

  • Ambiguous tax is refused

    Rejected before send: a line with no tax category, two categories on one line, or some lines taxed per line while others use a global tax.

  • Shipping needs a line

    A positive standalone shipping charge is refused, because the shipping field carries no Peppol tax category. Add shipping as a taxed invoice line instead.

  • Discount after tax

    A document discount your invoice calculated after line tax is refused rather than reinterpreted in transit, because it would change what the numbers mean.

  • Sales invoices only

    Credit notes, orders, self-billing, prepayments and attachments are not sent. Estimates, recurring templates, subscriptions, Payment Links, bills, purchase orders and vendor credits are rejected.

  • No participant discovery

    Invoice Crowd does not search the Peppol directory or check what a recipient can receive. You enter the customer's identifier yourself.

  • Inbound failures flagged

    A document that fails validation is never partly imported. It stays in the log for manual review, and a transient retrieval failure creates nothing.

  • What the log keeps

    Hashes, identifiers, status metadata and timestamps. Provider messages, addresses, document content, credentials and secrets are never written, and there is no document viewer.

Questions

Peppol E-Invoicing, answered

Which Peppol access point does Invoice Crowd use?

Invoice Crowd submits and receives Peppol documents through Storecove, which is the only supported access point provider. Storecove converts the submitted structured invoice to the applicable Peppol document, performs network and scheme validation, routes it to the recipient and returns delivery events. Pagero and Unimaze are not supported and cannot be selected. You supply your own Storecove account, API key and legal-entity ID.

Is Peppol e-invoicing available on every Invoice Crowd account?

No. Peppol e-invoicing in Invoice Crowd is available for controlled onboarding rather than as a self-serve feature. It is fail-closed at two levels: a platform switch that is off by default, and a per-business-profile configuration that needs your Storecove participant ID, API key, numeric legal-entity ID and webhook tenant ID. Both have to be enabled deliberately before any invoice can be sent.

What is the difference between a submitted and a delivered Peppol invoice?

In Invoice Crowd, submitted means the access point accepted the request and returned a valid document GUID. Delivered is a later and stricter state: it requires an authenticated success webhook plus retrieval of the matching Peppol sending evidence for the same GUID on the Peppol network. Delivered is terminal and monotonic, so a late failure event cannot downgrade an invoice that already reached it.

Can an invoice be edited after it has been sent over Peppol?

No. Once a Peppol attempt is pending, submitted or delivered, Invoice Crowd locks that invoice against editor saves so the transmitted evidence and the stored document cannot drift apart. Corrections are made by issuing a separate corrective document. Attempts that failed or were definitively rejected can be corrected and submitted again, and resending an unchanged rejected invoice resolves to its existing attempt rather than creating a second one.

What happens to supplier invoices that arrive over Peppol?

A supplier invoice received over Peppol is imported once as a single unposted draft bill in Invoice Crowd, with the vendor found or created by Peppol ID. The import never posts accounting, never marks a bill paid and never overwrites an existing document. Provider GUID and reference uniqueness prevent duplicate bills, and a document that fails validation is flagged for manual review instead of being partially imported.

Does Invoice Crowd send Peppol credit notes?

No. Only a standard sales invoice is supported for outbound Peppol delivery today. Credit notes, orders, self-billing documents, prepayments and attachments are outside the supported path, and estimates, recurring templates, subscriptions, Payment Links, bills, purchase orders and vendor credits are rejected before any provider request is made. Correcting a transmitted invoice is handled by issuing a corrective document rather than by sending a Peppol credit note.

Ask about Peppol before you plan a rollout

Peppol is enabled per business profile during onboarding rather than from a signup flow. Bring your Storecove account and the countries you invoice, and check what the supported path covers.

  • No card required to start
  • Your data stays yours
  • Cancel anytime
Try Invoice Crowd Compare plans