PEPPOL Service Bus deliveryOption

For sending documents it is good to know the partyId that will garanty the best delivery. The Generic/deliveryOption (Beta) you can request the best partyId to used with the salesInvoice/send. A organisation can have more than one partyID that can be used for sending documents if there are documents registered […]

PEPPOL Service Bus Hooks

Use hooks to be notified about events of the Peppol Service Bus. The Peppol Service Bus can send webhooks and email notifications to your application about events that happened in your Party. This mechanism is very useful for receiving invoices. Once an invoice has arrived you will be notified via […]

PEPPOL Service Bus Authenticiation and Authorization

The PEPPOL Service Bus API uses the OAuth2.0 Resource Owner Password Credentials Grant type. Requesting a bearer token Request: POST https://accp-identity.econnect.eu/connect/token HTTP/1.1 Accept: application/json Content-Type: application/x-www-form-urlencoded Host: accp-identity.econnect.eu Content-Length: 155 Expect: 100-continue username={userName}&password={userSecret}&scope=ap&grant_type=password&client_id={clientId}&client_secret={clientSecret} For the production environment use https://identity.econect.eu. username={userName}&password={userSecret} Specifies the user that is authorized for a specific party. […]

Walkthrough: PEPPOL Service Bus

Step 1: Get access To be able to use the PEPPOL Service Bus API you need credentials and a subscribtion key. You can ask for a key via your sales representative or via the contact page. Step 2: Get an API user If you have been identified as a valid […]

PEPPOL Service Bus Overview

The PEPPOL Service Bus provides a cloud managed connection to the PEPPOL network. Specially designed for large volumes and low latency with automatic scaling. Build with redundancy and high availability in mind. The shared cloud approach is centrally monitored for optimal utilization and predictable costs. Additional services are available, like […]

Simplerinvoicing XML Invoice with extension

<?xml version=”1.0″ encoding=”UTF-8″?> <Invoice xmlns=”urn:oasis:names:specification:ubl:schema:xsd:Invoice-2″ xmlns:cac=”urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2″ xmlns:cbc=”urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2″ xmlns:ext=”urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2″ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 http://docs.oasis-open.org/ubl/os-UBL-2.1/xsd/maindoc/UBL-Invoice-2.1.xsd”> <ext:UBLExtensions> <ext:UBLExtension> <ext:ExtensionContent> <myext:TestExtension xmlns:myext=”urn:text.example:test:ver1.0″> <myext:MyQuantity unitCode=”Fleebs” unitCodeListID=”RnM:unitCodes”>16</myext:MyQuantity> <myext:MyCurrency currencyID=”Schmeckle” unitCodeListID=”RnM:currencyCodes”>160</myext:MyCurrency> <myext:MyData mimeCode=”hive/unity”>160</myext:MyData> </myext:TestExtension> </ext:ExtensionContent> </ext:UBLExtension> </ext:UBLExtensions> <cbc:UBLVersionID>2.1</cbc:UBLVersionID> <cbc:CustomizationID>urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol4a:ver2.0:extended:urn:www.simplerinvoicing.org:si:si-ubl:ver1.2</cbc:CustomizationID> <cbc:ProfileID>urn:www.cenbii.eu:profile:bii04:ver1.0</cbc:ProfileID> <cbc:ID>I2013.03.4361</cbc:ID> <cbc:IssueDate>2013-08-06</cbc:IssueDate> <cbc:InvoiceTypeCode listID=”UNCL1001″ listAgencyID=”6″>380</cbc:InvoiceTypeCode> <cbc:DocumentCurrencyCode listID=”ISO4217″ listAgencyID=”6″>EUR</cbc:DocumentCurrencyCode> <cac:AccountingSupplierParty> <cac:Party> <cac:PartyName> <cbc:Name>Innopay B.V.</cbc:Name> </cac:PartyName> <cac:PostalAddress> <cbc:StreetName>Main street</cbc:StreetName> <cbc:CityName>Big city</cbc:CityName> […]

Simplerinvoicing XML Invoice Small

<?xml version=”1.0″ encoding=”UTF-8″?> <Invoice xmlns=”urn:oasis:names:specification:ubl:schema:xsd:Invoice-2″ xmlns:cac=”urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2″ xmlns:cbc=”urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2″ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 http://docs.oasis-open.org/ubl/os-UBL-2.1/xsd/maindoc/UBL-Invoice-2.1.xsd”> <cbc:UBLVersionID>2.1</cbc:UBLVersionID> <cbc:CustomizationID>urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol4a:ver2.0:extended:urn:www.simplerinvoicing.org:si:si-ubl:ver1.2</cbc:CustomizationID> <cbc:ProfileID>urn:www.cenbii.eu:profile:bii04:ver1.0</cbc:ProfileID> <cbc:ID>I2013.03.4361</cbc:ID> <cbc:IssueDate>2013-08-06</cbc:IssueDate> <cbc:InvoiceTypeCode listID=”UNCL1001″ listAgencyID=”6″>380</cbc:InvoiceTypeCode> <cbc:DocumentCurrencyCode listID=”ISO4217″ listAgencyID=”6″>EUR</cbc:DocumentCurrencyCode> <cac:AccountingSupplierParty> <cac:Party> <cac:PartyName> <cbc:Name>Seller B.V.</cbc:Name> </cac:PartyName> <cac:PostalAddress> <cbc:StreetName>Main street</cbc:StreetName> <cbc:CityName>Big city</cbc:CityName> <cbc:PostalZone>54321</cbc:PostalZone> <cac:Country> <cbc:IdentificationCode listAgencyID=”6″ listID=”ISO3166-1:Alpha2″>NL</cbc:IdentificationCode> </cac:Country> </cac:PostalAddress> <cac:PartyLegalEntity> <cbc:CompanyID schemeID=”NL:VAT”>3333333333</cbc:CompanyID> </cac:PartyLegalEntity> </cac:Party> </cac:AccountingSupplierParty> <cac:AccountingCustomerParty> <cac:Party> <cac:PartyName> <cbc:Name>Buyercompany VOF</cbc:Name> […]

Simplerinvoicing XML Invoice Full

<?xml version=”1.0″ encoding=”UTF-8″?> <Invoice xmlns=”urn:oasis:names:specification:ubl:schema:xsd:Invoice-2″ xmlns:cac=”urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2″ xmlns:cbc=”urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2″> <cbc:UBLVersionID>2.1</cbc:UBLVersionID> <cbc:CustomizationID>urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol4a:ver2.0:extended:urn:www.simplerinvoicing.org:si:si-ubl:ver1.2</cbc:CustomizationID> <cbc:ProfileID>urn:www.cenbii.eu:profile:bii04:ver1.0</cbc:ProfileID> <cbc:ID>TOSL108</cbc:ID> <cbc:IssueDate>2009-12-15</cbc:IssueDate> <cbc:InvoiceTypeCode listID=”UNCL1001″ listAgencyID=”6″>380</cbc:InvoiceTypeCode> <cbc:Note languageID=”en”>Ordered in our booth at the convention.</cbc:Note> <cbc:TaxPointDate>2009-11-30</cbc:TaxPointDate> <cbc:DocumentCurrencyCode listID=”ISO 4217 Alpha” listAgencyID=”6″>EUR</cbc:DocumentCurrencyCode> <cbc:AccountingCost>Project cost code 123</cbc:AccountingCost> <cac:InvoicePeriod> <cbc:StartDate>2009-11-01</cbc:StartDate> <cbc:EndDate>2009-11-30</cbc:EndDate> </cac:InvoicePeriod> <cac:OrderReference> <cbc:ID>123</cbc:ID> </cac:OrderReference> <cac:ContractDocumentReference> <cbc:ID>Contract321</cbc:ID> <cbc:DocumentType>Framework agreement</cbc:DocumentType> </cac:ContractDocumentReference> <cac:AdditionalDocumentReference> <cbc:ID>Doc1</cbc:ID> <cbc:DocumentType>Timesheet</cbc:DocumentType> <cac:Attachment> <cac:ExternalReference> […]

GetAdvisedInvoiceRecipientId

This API is used to retrieve RecipientId that is advised to use for sending documents.  The RecipientId is selected based on the fact that the RecipientId is published for recieving the specific documents in the PEPPOL network. Request fields Fieldname Description ReferenceIdSet List of RecipientId‘s. A RecipientId is a identifier prefixed with […]