|
| 1 | +--- |
| 2 | +extends: _layouts.user_guide |
| 3 | +section: content |
| 4 | +locale: en |
| 5 | +--- |
| 6 | + |
| 7 | +# e-invoices |
| 8 | + |
| 9 | +## Introduction |
| 10 | +e-invoicing is rapidly being adopted in many jurisdictions. Invoice Ninja has supported UBL format invoices for some time and now we also support a range of e-invoice formats including direct delivery of e-invoices over the PEPPOL network. |
| 11 | + |
| 12 | +## e-invoice standards |
| 13 | +The list of supported e-invoice formats include: |
| 14 | + |
| 15 | +- Facturae (Spain) |
| 16 | +- FatturaPA (Italy) |
| 17 | +- FACT1 (Romania) |
| 18 | +- Zugferd - XRechung (Germany) |
| 19 | +- EN16931 (Generic) |
| 20 | +- PEPPOL (Universal - Cross industry / border) |
| 21 | + |
| 22 | +## How does it work? |
| 23 | +All of the supported e-invoice standards can be downloaded directly after creating a standard invoice in Invoice Ninja. In some jurisdictions you are able to forward the e-invoice directly to your customer, however in some regions (ie, Italy) the invoice is sent through the government and then forwarded onto the customer. This introduces a number of complexities including both parties being registered with the government body (SDI for Italy). If you are in one of these jurisdictions, you will need to start the process (if you have not already) in acquiring a government routing ID. |
| 24 | + |
| 25 | +Invoice Ninja will be rolling out a PEPPOL access point which will be available for both self hosted and hosted users to route their e-invoices through the PEPPOL network. |
| 26 | + |
| 27 | +## How do I get started? |
| 28 | + |
| 29 | +### All users |
| 30 | +Each particular jurisdiction has a specific set of fields which MUST be populated in order for an e-invoice to be validated. For example, in Germany a Payment Means field is required within the e-invoice. What is this? This is the sending parties paymnet details, ie IBAN + financial account meta data such as bank, FIB etc. Without this data the e-invoice cannot be generated or sent. As you onboard through the application you will have the opportunity to validate your data to ensure delivery of your e-invoices. |
| 31 | + |
| 32 | +### Hosted users |
| 33 | +We will be sending out notifications to our hosted users for the steps required for onboarding in their particular region. |
| 34 | + |
| 35 | +### Self hosted users |
| 36 | +Self Hosted users will be proxying their e-invoices through our hosted platform. What does this mean? In order to send your e-invoices you'll need to register your service with Invoice Ninja and we will create your legal entity id for you. Your system will then route e-invoices through our system as required. For security and data privacy, the service will only ever proxy the data that is sent, we will never store the data that is sent. |
| 37 | + |
| 38 | +## How do I prepare my Invoice Ninja installation to support e-invoicing? |
| 39 | +There are a few important considerations with e-invoicing. |
| 40 | + |
| 41 | +1. All taxes must be applied at the line level. Total taxes are not supported with e-invoicing |
| 42 | +2. If you do not charge VAT/TAX on your invoices, you still need to apply a tax code/reason ie. Cross Border exemption, seller with no VAT number etc |
| 43 | +3. After an invoice has been "sent" it can never be modified, instead if there are changes that need to be applied you must create a new Invoice/Credit with the changes |
| 44 | + |
| 45 | +## Can I receive e-invoices? |
| 46 | +Yes, in an upcoming version we will also support the delivery of e-invoicing via the peppol network directly into your company. |
| 47 | + |
| 48 | +(Self hosted users will receive these via WebHook) |
| 49 | + |
| 50 | +## Getting started checklist |
| 51 | + |
| 52 | +### Hosted Users |
| 53 | + - Register with your government body if e-invoices are to be routed via government portal. |
| 54 | + - Enable e-invoicing (Settings > E Invoice - select e invoice type => PEPPOL) |
| 55 | + - Enable e-invoicing (Settings > E Invoice - select e invoice type => PEPPOL) |
| 56 | + - Ensure your company details pass validation (Settings > E-Invoicing - Validation) |
| 57 | + - Generate and send e-invoices! |
| 58 | + |
| 59 | +### Self Hosted Users |
| 60 | + - Register with your government body if e-invoices are to be routed via government portal. |
| 61 | + - Register your entity with Invoice Ninja. |
| 62 | + - Ensure your company details pass validation (Settings > E-Invoicing - Validation) |
| 63 | + - Enable e-invoicing (Settings > E Invoice - select e invoice type => PEPPOL) |
| 64 | + - Generate and send e-invoices! |
| 65 | + |
| 66 | +## Code lists / values |
| 67 | + |
| 68 | +<a id="payment-means-codelist"></a> |
| 69 | +<details> |
| 70 | +<summary>Payment Means Codelist</summary> |
| 71 | + |
| 72 | +1 - Instrument not defined<br> |
| 73 | +2 - Automated clearing house credit<br> |
| 74 | +3 - Automated clearing house debit <br> |
| 75 | +4 - ACH demand debit reversal <br> |
| 76 | +5 - ACH demand credit reversal <br> |
| 77 | +6 - ACH demand credit <br> |
| 78 | +7 - ACH demand debit <br> |
| 79 | +8 - Hold <br> |
| 80 | +9 - National or regional clearing <br> |
| 81 | +10 - In cash <br> |
| 82 | +11 - ACH savings credit reversal <br> |
| 83 | +12 - ACH savings debit reversal <br> |
| 84 | +13 - ACH savings credit <br> |
| 85 | +14 - ACH savings debit <br> |
| 86 | +15 - Bookentry credit <br> |
| 87 | +16 - Bookentry debit <br> |
| 88 | +17 - ACH demand cash concentration/disbursement (CCD) credit <br> |
| 89 | +18 - ACH demand cash concentration/disbursement (CCD) debit <br> |
| 90 | +19 - ACH demand corporate trade payment (CTP) credit <br> |
| 91 | +20 - Cheque <br> |
| 92 | +21 - Banker\'s draft <br> |
| 93 | +22 - Certified banker\'s draft <br> |
| 94 | +23 - Bank cheque (issued by a banking or similar establishment) <br> |
| 95 | +24 - Bill of exchange awaiting acceptance <br> |
| 96 | +25 - Certified cheque <br> |
| 97 | +26 - Local cheque <br> |
| 98 | +27 - ACH demand corporate trade payment (CTP) debit <br> |
| 99 | +28 - ACH demand corporate trade exchange (CTX) credit <br> |
| 100 | +29 - ACH demand corporate trade exchange (CTX) debit <br> |
| 101 | +30 - Credit transfer <br> |
| 102 | +31 - Debit transfer <br> |
| 103 | +32 - ACH demand cash concentration/disbursement plus (CCD+) credit <br> |
| 104 | +33 - ACH demand cash concentration/disbursement plus (CCD+) debit <br> |
| 105 | +34 - ACH prearranged payment and deposit (PPD) <br> |
| 106 | +35 - ACH savings cash concentration/disbursement (CCD) credit <br> |
| 107 | +36 - ACH savings cash concentration/disbursement (CCD) debit <br> |
| 108 | +37 - ACH savings corporate trade payment (CTP) credit <br> |
| 109 | +38 - ACH savings corporate trade payment (CTP) debit <br> |
| 110 | +39 - ACH savings corporate trade exchange (CTX) credit <br> |
| 111 | +40 - ACH savings corporate trade exchange (CTX) debit <br> |
| 112 | +41 - ACH savings cash concentration/disbursement plus (CCD+) credit <br> |
| 113 | +42 - Payment to bank account <br> |
| 114 | +43 - ACH savings cash concentration/disbursement plus (CCD+) debit <br> |
| 115 | +44 - Accepted bill of exchange <br> |
| 116 | +45 - Referenced home-banking credit transfer <br> |
| 117 | +46 - Interbank debit transfer <br> |
| 118 | +47 - Home-banking debit transfer <br> |
| 119 | +48 - Bank card <br> |
| 120 | +49 - Direct debit <br> |
| 121 | +50 - Payment by postgiro <br> |
| 122 | +51 - FR, norme 6 97-Telereglement CFONB (French Organisation for Banking Standards) - Option A <br> |
| 123 | +52 - Urgent commercial payment <br> |
| 124 | +53 - Urgent Treasury Payment <br> |
| 125 | +60 - Promissory note <br> |
| 126 | +61 - Promissory note signed by the debtor <br> |
| 127 | +62 - Promissory note signed by the debtor and endorsed by a bank <br> |
| 128 | +63 - Promissory note signed by the debtor and endorsed by a third party <br> |
| 129 | +64 - Promissory note signed by a bank <br> |
| 130 | +65 - Promissory note signed by a bank and endorsed by another bank <br> |
| 131 | +66 - Promissory note signed by a third party <br> |
| 132 | +67 - Promissory note signed by a third party and endorsed by a bank <br> |
| 133 | +70 - Bill drawn by the creditor on the debtor <br> |
| 134 | +74 - Bill drawn by the creditor on a bank <br> |
| 135 | +75 - Bill drawn by the creditor, endorsed by another bank <br> |
| 136 | +76 - Bill drawn by the creditor on a bank and endorsed by a third party <br> |
| 137 | +77 - Bill drawn by the creditor on a third party <br> |
| 138 | +78 - Bill drawn by creditor on third party, accepted and endorsed by bank <br> |
| 139 | +91 - Not transferable banker\'s draft <br> |
| 140 | +92 - Not transferable local cheque <br> |
| 141 | +93 - Reference giro <br> |
| 142 | +94 - Urgent giro <br> |
| 143 | +95 - Free format giro <br> |
| 144 | +96 - Requested method for payment was not used <br> |
| 145 | +97 - Clearing between partners <br> |
| 146 | +ZZZ - Mutually defined <br> |
| 147 | + |
| 148 | +</details> |
| 149 | + |
| 150 | +## Jurisdiction specific requirements |
| 151 | + |
| 152 | +### AT - Austria |
| 153 | + |
| 154 | +#### CustomerAssignedAccountID - Mandatory for GOV clients |
| 155 | +If you are sending an e-invoice to a government body, then you must include in the object |
| 156 | + |
| 157 | +AccountingSupplierParty > CustomerAssignedAccountID |
| 158 | + |
| 159 | +This is the ID of the department within the government that the e-invoice will be routed to |
| 160 | + |
| 161 | +### BE - Belgium |
| 162 | +No additional requirements, when your legal entity id is created this is automatically sync'd with HERMES |
| 163 | + |
| 164 | +### CH - Switzerland |
| 165 | + |
| 166 | +#### Payment Means - Mandatory |
| 167 | +The payment means contains information on how the seller wishes to be paid. Use the [Payment Means](#payment-means-codelist) you must have at least ONE payment means that is a Credit Transfer type |
| 168 | + |
| 169 | +```php |
| 170 | + <cac:PaymentMeans> |
| 171 | + <cbc:PaymentMeansCode>30</cbc:PaymentMeansCode> <!-- code from payment means code list Credit Transfer--> |
| 172 | + <cac:PayeeFinancialAccount> |
| 173 | + <cbc:ID>DE89370400440532013000</cbc:ID> <!-- IBAN CODE --> |
| 174 | + <cac:FinancialInstitutionBranch> |
| 175 | + <cbc:ID>DEUTDEMMXXX</cbc:ID> <!-- BIC CODE --> |
| 176 | + </cac:FinancialInstitutionBranch> |
| 177 | + </cac:PayeeFinancialAccount> |
| 178 | + </cac:PaymentMeans> |
| 179 | +``` |
| 180 | + |
| 181 | +### DE - Germany |
| 182 | + |
| 183 | +#### Payment Means - Mandatory |
| 184 | +The payment means contains information on how the seller wishes to be paid. Use the [Payment Means](#payment-means-codelist) list to determine the correct code required. For example, to display your bank account details the following would be required |
| 185 | + |
| 186 | +```php |
| 187 | + <cac:PaymentMeans> |
| 188 | + <cbc:PaymentMeansCode>30</cbc:PaymentMeansCode> <!-- code from payment means code list Credit Transfer--> |
| 189 | + <cac:PayeeFinancialAccount> |
| 190 | + <cbc:ID>DE89370400440532013000</cbc:ID> <!-- IBAN CODE --> |
| 191 | + <cac:FinancialInstitutionBranch> |
| 192 | + <cbc:ID>DEUTDEMMXXX</cbc:ID> <!-- BIC CODE --> |
| 193 | + </cac:FinancialInstitutionBranch> |
| 194 | + </cac:PayeeFinancialAccount> |
| 195 | + </cac:PaymentMeans> |
| 196 | +``` |
| 197 | + |
| 198 | +### ES - Spain |
| 199 | + |
| 200 | +*** Government registration required *** |
| 201 | + |
| 202 | +#### Payment Means - Mandatory |
| 203 | +The payment means contains information on how the seller wishes to be paid. Use the [Payment Means](#payment-means-codelist) you must have at least ONE payment means that is a Credit Transfer type |
| 204 | + |
| 205 | +```php |
| 206 | + <cac:PaymentMeans> |
| 207 | + <cbc:PaymentMeansCode>30</cbc:PaymentMeansCode> <!-- code from payment means code list Credit Transfer--> |
| 208 | + <cac:PayeeFinancialAccount> |
| 209 | + <cbc:ID>DE89370400440532013000</cbc:ID> <!-- IBAN CODE --> |
| 210 | + <cac:FinancialInstitutionBranch> |
| 211 | + <cbc:ID>DEUTDEMMXXX</cbc:ID> <!-- BIC CODE --> |
| 212 | + </cac:FinancialInstitutionBranch> |
| 213 | + </cac:PayeeFinancialAccount> |
| 214 | + </cac:PaymentMeans> |
| 215 | +``` |
| 216 | + |
| 217 | +#### Due Date - Mandatory |
| 218 | +The invoice MUST have a due date set. |
| 219 | + |
| 220 | +#### Government bound e-invoices |
| 221 | +If sending to a Spanish government body the property |
| 222 | + |
| 223 | +AccountingCustomerParty > PublicIdentifiers |
| 224 | + |
| 225 | +Must be set |
| 226 | + |
| 227 | +### FI - Finland |
| 228 | +No special requirements |
| 229 | + |
| 230 | +### FR - France |
| 231 | +The SIRET / 0009 identifier of the final recipient is to be included in the invoice.accountingCustomerParty.publicIdentifiers array. |
| 232 | + |
| 233 | +### IT - Italy |
| 234 | +No special requirements |
| 235 | + |
| 236 | +### NL - Netherlands |
| 237 | +When sending to government bodies the following property must be configured |
| 238 | + |
| 239 | +accountingSupplierParty > party > contact >email |
| 240 | + |
| 241 | +### PL -Poland |
| 242 | + |
| 243 | +*** Government registration required *** |
| 244 | + |
| 245 | +### RO -Romania |
| 246 | + |
| 247 | +*** Government registration required *** |
| 248 | + |
| 249 | +#### Special codes for county |
| 250 | +The county field for a Romania address must use the ISO3166-2:RO codes, e.g. "RO-AB, RO-AR". Don’t omit the country prefix! |
| 251 | + |
| 252 | +#### Special codes for city |
| 253 | +The city field for county RO-B must be SECTOR1 - SECTOR6. |
| 254 | + |
| 255 | +### SE - Sweden |
| 256 | +Receiver needs to be registered with Svefaktura to receive the e-invoice |
| 257 | + |
| 258 | +<x-next url=/en/invoices>Invoices</x-next> |
0 commit comments