Electronicinvoice30/Functional Documentation

Contents 1 Document sign-off 2 Document Status 3 Overview & Justification 3.1 Purpose 3.2 Scope 3.3 Justification 3.4 New definitions and acronyms 4 Users & business process description 4.1 User goals 4.2 User Roles and Personas 4.3 Business process diagram 4.4 Business scenario/s 4.4.1 Sales invoices sent as a xml file 4.4.2 Sales invoices sent as a pdf file 5 Functional requirements 5.1 Functional Requirement nº 1 - Invoice content requirements 5.2 Functional Requirement nº 2 - Facturae format e-invoice requirements 5.3 Functional Requirement nº 3 - Issuer company – Legal obligations regarding e-invoicing 5.4 Functional Requirement nº 4 - Recipient company - Legal obligations regarding e-invoicing 5.5 Functional Requirement nº 5 - Configuration 5.5.1 ID configuration 5.5.2 Electronic invoice configuration 5.6 Persona based scenarios 5.6.1 Sales invoices sent as a xml file 5.6.1.1 Sales Invoice generated for a National customer as a xml file 5.6.1.2 Negative/Credit sales invoice generated as xml file 5.6.1.3 Good Sales Invoices including several “National” VAT tax rates 5.6.1.4 Good Sales Invoices including “National” VAT + Equivalence charge 5.6.1.5 Services Sales Invoices including “National” VAT + Withholding 5.6.1.6 Shipment dates versus Invoice dates 5.6.1.7 Sales Invoice sent and signed as “Adjunto e-mail” 5.6.1.8 Sales Invoice sent as “ Usuario portal” 5.6.1.9 Sales Invoice sent as “Descarga on-line” 5.6.1.10 Sales Invoice sent as “Correo ordinario” 5.7 Assumptions & Dependencies 5.7.1 Assumptions 5.7.2 Dependencies 6 Design & Technical considerations 6.1 Design considerations 6.2 Technical constraints 6.3 Technical Requirements 7 User interface 7.1 New User Interface 7.2 User interface changes 8 License 8.1 License code description 8.2 Functionality enabled by the license code 9 Discussion items 9.1 Open discussion items 9.2 Closed discussion items 10 Appendix

Document sign-off

Role	Name	Sign-off date
Development	David Alsasua

Document Status

Date	Author or editor	Description of change	Document status	Document version
July 12nd, 2010t	Patricia San Juan	Document creation and sent for review	Final	V1

Overview & Justification

Purpose

The purpose of this document is to describe the functional specifications for a new extension module which is the “Electronic invoice” (“e-invoice”), Advance Payables & Receivables feature compatible.

An electronic invoice is an invoice which can be sent or received to the corresponding recipient or from the corresponding sender as a “file” via internet.

Electronic invoicing requirements are listed below:

1. An electronic format is required (EDIFACT, xml, html....)

2.- It has to be sent via internet from a computer to another computer (electronic transmission).

3.- The electronic format and its electronic transmission have to guarantee its integrity and authentication through a well know digital signature, therefore electronic invoice has to comply with:

• the authentication of its origin
• and the integrity of its content

therefore it can not be repudiate by the invoice recipient.

In the link below overall and relevant information about electronic invoicing feature in Spain can be found (documentation in Spanish): http://www.facturae.es

This new feature is going to be developed and delivered as a new extension module which will be part of the Spanish Professional Localization Pack version 2.0, compatible with Advance Payables & Receivables management module

This new extension module will be split in 3 modules, one will create and validate the xml file according to facturae 3.1 format, the second one will create the required OB ERP enhancements for BP and Sales Invoice features and the third one will integrate OB ERP to Camerfactura web platform via web services. For more information see technical sections below.

Scope

In scope:

The first phase of this project takes into account just “Sales/Issued Invoices” sent as a valid XML file according to facturae format and requirements to Spanish customer; in a second phase OB electronic invoicing feature will take into account “Purchase/Received Invoices” and rest of countries; therefore it is in scope what is detailed below:

• OB ERP UI enhancements => in order to get that the end-user can send “Sales/Issued Invoices or corrective invoices” as “electronic invoices” to Spanish customers, besides the end-user will know whether the invoice has been sent electronically or not.
• XML file generation according to “facturae v 3.1” format => in order to get that the end-user can send an “Issued Invoice” electronically as a valid XML file according to facturae v 3.1 format and facturae requirements.
  An existing API developed by Spanish government will be used to generate the XML file according to facturae v 3.1 format. Government API and facturae 3.1 format can be found in the links below:
  http://www.facturae.es/Descargas/Desarrollo/
  http://www.facturae.es/Descargas/Utilidades/
  

• XML file integration in “Camerfactura” Web Portal via web services => in order to get that the issued invoice sent as a valid xml file can be imported in Camerfactura Web Portal, by using Camerfactura web services; so it can be digitally signed through a valid Certificate as well as time stamped and authenticated.

As mentioned above OB ERP is going to be enhanced in order to allow electronic invoicing feature implementation but it is not going to be enhanced as an “electronic invoicing” platform; therefore OB ERP electronic invoicing feature implies an integration to an existing “Electronic Invoicing Platform” named “Camerfactura” developed by a third party “Camerfirma”. http://portal.camarafactura.es/Portal/

“Camerfactura Portal” allows the end user to:

• sign invoices by using a valid Certificate
• validate Certificates via OCSP queries
• send invoices via email
• keep tracking of the invoices sent and pending to be sent
• receive invoices
• store invoices
• visualize invoices
• time stamping
• import invoices by using either a web form or by importing an xml file generated from an application/ERP
  

Out of scope:

As mentioned above “Purchase/Received Invoices” reception as a valid xml file according to facturae format and requirements is out of scope by now. It will be implemented in a second phase. Same applies to sales and purchase invoice sent or received from Non-Spanish customers/suppliers.

It is also out of scope below listed invoice types according to facturae format:

• OR = Corrective invoice
• AA = Auto-invoices – in case of Reverse Charge scenarios
• CC&CO&CR = “Copy” of Cumulative/Original or Corrective invoices – in case of sending a clearly high-lighted “Copy” of a sent “Original” or “Cumulative” or “Corrective” invoice.
• OC = “Cumulative” invoices – in case of sending an invoice containing all transactions done with the same customer within a period of time (natural month).

It is also out of scope invoices in different languages rather than Spanish; in a second phase and depending on OB ERP translations additional languages could be taken into account.

List of further e-invoice enhancements:

• Corrective invoice feature including corrective reason (ID + name) and corrective method (ID + name)
• process to search which sales invoices are pending to be generated or generated and send as xml files as well as to search the ones already generated or generated and sent
• process to create or to create and sent several sales invoices as xml files ate the same time, regardless each xml file will only contain 1 sales invoice
• Customers creation in Camerfactura web platform by using the cor responding web services
• Get the "namespace" and "invoice template" into the XML file (namespace URI prefix as"namespace" and not "fe")

invoice template: <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href=" http://desarrollo.camarafactura.es/public/xsl/XX_cci.xsl "?> <namespace:Facturae xmlns:namespace="http://www.fact... Donde "XX" es el identificador indicado en el apartado "Administración / Configuración" (ID para plantillas). La URL es la del portal de desarrollo (en el entorno de producción habría que indicar la URL de producción).

Justification

Electronic invoicing feature will allow the end-users to send positive or negative (credit invoice) “Sales/Issued Invoices” as a valid xml file according to facturae format & requirements via internet.

This feature is not mandatory by now, just for companies which supplies Spanish government as well as big companies, but it is becoming a common business practice which we foresee it would be set as mandatory by law in a short period of time.

The applicable legislation is listed below:

Law 59/2003 and Order 962/2007 – Facturación electrónica

Order PRE/2971/2007 – Expedición de facturas por medios electrónicos

Law 56/2007 – Impulso a la sociedad de la Información (BOE 29/12)

New definitions and acronyms

E-invoice => electronic invoice

Facturae => electronic invoice xml format

Camerfactura => electronic invoice 3rd party platform

Camerfirma => electronic invoice valid certificate (digital signature certificate)

Users & business process description

User goals

Electronic invoicing feature will allow the end user to send positive or negative (credit invoices) “Sales/Issued Invoices” as “electronic invoices” which means:

1. from positive or negative “Sales/Issued Invoices” posted create a valid xml file according to facturae v 3.1 format and facturae requirements and send it to Camerfactura web platform.
2. upload valid xml files generated from OB ERP into Camerfactura Web Portal by using Camerfactura web services, therefore electronic invoices can be digitally signed through a valid Certificate, time stamped, authenticated and sent to the corresponding customer. All these steps will take place in Camerfactura web portal.
3. and store and visualize invoices in Camerfactura Web Portal for audit purpose

User Roles and Personas

The following roles are involved:

Sales staff (Mike): Mike is an employee part of the sales staff.

Mike is the one entering sales orders in the system. He must monitor that the corresponding good shipments are entered in the system by the warehouse staff once the goods leave the warehouse as he must enter in the system the corresponding sales invoices later on.

Mike should be aware of the customers which allow his company to send the sales invoices electronically to them as an xml file according to facturae format rather than by post printed as a pdf file; therefore while creating Business Partner (customers) in OB ERP, he should enter customer information accordingly so he is able to know later on and when creating sales invoices which customer allow e-invoicing and which ones not.

Accounting staff (Peter): Peter is an employee part of the accounting staff. He will check that the sales invoices are properly entered, completed and post in the system. Peter will also be in sync with sales staff in order to sent them either by post or as an xml file.

Business process diagram

Business scenario/s

Small Bazaar is an enterprise located in Spain made of several subsidiaries. Small Bazaar Holding is the parent company while, Small Bazaar Pamp and Small Bazaar Barc are two subsidiaries. Each subsidiary is modelled in OB ERP as a legal entity organization with accounting.

It is important to not that depending on whether Small Bazaar Spanish customers allow e-invoicing or not business scenarios can be split in two types as described below; but only the one related to invoices sent as xml files will be taken into account through out current specification document because invoices sent as pdf files is not a feature part of e-invoicing scope.

Sales invoices sent as a xml file

As part of Small Bazaar normal activities Mike should invoice Small Bazaar Pamp and Small Bazaar Barc Spanish customers for the goods delivered to them after monitoring that the corresponding good shipments have been entered and completed in the system once the goods have left the warehouse.

Mike should also invoice Small Bazaar Pamp and Small Bazaar Barc Spanish customers for the services provided to them.

Mike should be aware of the customer which allow his company to send the sales invoices as an xml file according to facturae format and requirements; therefore Mike should enter in OB ERP electronic invoicing related information for those customers besides “generic” information.

Once the above is done Mike must be able to enter sales invoices in OB ERP containing all required information. Mike should complete and post the sales invoices.

Once a sales invoice is posted he must press a process button to generate the e-invoice according to facturae v 3.1 format, besides he must also be able to generate and sent the e-invoice to the platform.

After that it will not be possible to un-post that invoice or even to re-activate it because it is already transferred to Camerfactura portal via web services. In case of any change required a new corrective invoice should be created, post and therefore sent as facturae.

Mike would also be able to attach the corresponding xml file as an attachement to the sales invoice document by clicking on the “attachment” menu button and selecting the xml file. See below:

Sales invoices sent as a pdf file

As part of Small Bazaar normal activities Mike should invoice Small Bazaar Pamp and Small Bazaar Barc Spanish customers for the goods delivered to them after monitoring that the corresponding good shipments have been entered and completed in the system once the goods have left the warehouse.

Mike should also invoice Small Bazaar Pamp and Small Bazaar Barc Spanish customers for the services provided to them.

Mike must be able to enter sales invoices in OB ERP containing all required information. Mike should complete and post the sales invoices (for those customers which do not allow e-invoice the new process button to create and send an xml file will not be shown in the sales invoice header window).

Once the invoice is posted he must press the “print” menu button from which he will be able to print and archive the corresponding sales invoice as a pdf format file to be sent by post later on.

He would be able to inquiry the sales invoice created by clicking on the “attachment” menu button.

Functional requirements

Functional Requirement nº 1 - Invoice content requirements

Every single invoice regardless its format have to mandatory contain the information listed below:

• Invoice number
• Invoice date
• Issuer company name (company which issued the invoice)
• Issuer company Tax id number
• Issuer company address
• Tax base amount
• Tax rate
• Tax amount
• Total invoice amount
• Operation date (in case it is different from the invoice date)

In the case of Sales invoices,we will use below listed OB ERP document types:

• As “normal” sales invoices:
  • “AR invoice”
  • “AR invoice indirect”
• As “corrective” sales invoices:
  • “Negative AR invoice”
  • “Negative AR invoice indirect”

For more information see “Persona based scenarios” section below. This requirement is covered by OB ERP default invoicing related features but corrective invoice to be implemented in a second phase of the project e-invoice.

Functional Requirement nº 2 - Facturae format e-invoice requirements

Facturae / XML format requires some “mandatory” invoice data as described below together with the suitable OB ERP value/data or constant/fixed data for the corresponding facturae section. For more information see urls below:

(Note: It is important to know that depending on the scenarios we are talking about xml format will change. Most common scenarios are covered in the current specification persona based scenarios section)

http://www.facturae.es/Documentacion/EsquemaFormato/Version3_1/

http://www.facturae.es/NR/rdonlyres/2DF1A921-9E57-4A24-85D8-14FE74E0FB31/0/Facturaev3_2.xsd

• HEADER section:
  • “Version” = fixed value => 3.1
  • “Modalidad” = list of valid values =>
    • “I” in the case of xml containing a single invoice or
    • “L” in the case of xml containing several invoices
    • In our case, “I” is the right value as Camerfactura web platform only manage xml files containing 1 single invoice.
  • “Tipo Emisor” = flist of valid values =>
    • EM = Emisor (issuer)
    • TE = Tercero (Third party)
    • RE = Recipient
    • In our case, “EM” is the right value as only issue invoices are in scope, therefore issued invoices are issued by the issuer.
  • “Lote – Identificador de Lote” => invoice id
  • “Lote – Número total facturas” => 1
  • “Lote – Importe total facturas” => invoice amount
  • “Lote – Total a pagar” => invoice amount
  • “Lote – Total a ejecturar” => invoice amount
  • “Lote – Código moneda factura” => EUR
• ISSUER section:
  • “Identificación fiscal – Tipo Persona”= list of valid values =>
    • J in case of NIF or
    • F in case of DNI
    • In our case, “J” is the right value as OB ERP is used by companies not individuals.
  • “Identificación fiscal – Residencia” = list of valid values =>
    • ”R” in the case of Spanish companies
    • “E” in the case of foreign companies or
    • “U” in case of intra community companies
    • In our case, “R” is the right value as e-invoicing feature according to facturae format and requirements only applies to Spanish companies.
  • “Identificación fiscal – Código identificación => OB company/organization Tax ID (ES+A/B+8 digits)
  • “Datos personales – Razón Social => OB Company/Organization name
  • “Datos personales – Datos domicilio” => Location data (address, postcode, Location, Region and Country)
• RECEPIENT section
  • “Identificación fiscal – Tipo Persona”= list of valid values =>
    • J in case of NIF or
    • F in case of DNI
  • “Identificación fiscal – Residencia” = list of valid values =>
    • ”R” in the case of a Spanish customer
    • “E” in the case of foreign customers
    • “U” in case of intra community customers
    • In our case, “R” is the right value as e-invoicing feature according to facturae format and requirements only applies to Spanish companies.
  • “Identificación fiscal – Código identificación => Recipient Tax ID
  • “Datos personales – Razón Social => Recipient name
  • “Datos personales – Datos domicilio” => Recipient Location data (address, postcode, Location, Region and Country)</n
• INVOICE section:
  • Invoice header
    • “Número de factura” => invoice number
    • “Tipo documento” => FC (Factura completa)
    • “Clase factura” = list of values => in our case either
      • OO Original invoice in case of positive/negative AR invoice or AR invoice indirect
  • Invoice data
    • “Fecha expedición” => invoice date
    • “Moneda factura” => EUR
    • “Moneda impuesto” => EUR
    • “Lengua” => “ESP”
  • Tax data
    • “Impuesto repercutido - Clase impuesto” = list of values => Tax type
      • (01) IVA: Impuesto sobre el valor añadido
      • (02) PSI: Impuesto sobre la producción, los servicios y la importación
      • (03) IGIC: Impuesto general indirecto de Canarias
      • (04) IRPF: Impuesto sobre la Renta de las personas físicas
      • (05) Otro
      • (06) ITPAJD: Impuesto sobre transmisiones patrimoniales y actos jurídicos documentados
      • (07) IE: Impuestos especiales
      • (08) Ra: Renta aduanas
      • (09) IGTECM: Impuesto general sobre el tráfico de empresas que se aplica en Ceuta y Melilla
      • (10) IECDPCAC: Impuesto especial sobre los combustibles derivados del petróleo en la Comunidad Autonoma Canaria
      • (11) IIIMAB: Impuesto sobre las instalaciones que inciden sobre el medio ambiente en la Baleares
      • (12) ICIO: Impuesto sobre las construcciones, instalaciones y obras
      • (13) IMVDN: Impuesto municipal sobre las viviendas desocupadas en Navarra
      • (14) IMSN: Impuesto municipal sobre solares en Navarra
      • (15) IMGSN: Impuesto municipal sobre gastos suntuarios en Navarra
      • (16) IMPN: Impuesto municipal sobre publicidad en Navarra
      • (17) REIVA: Régimen especial de IVA para agencias de viajes
      • (18) REIGIC: Régimen especial de IGIC: para agencias de viajes
      • (19) REIPSI: Régimen especial de IPSI para agencias de viajes
      • In our case we will use either (01) IVA (in case of VAT and EC) and (04) IRPF (in case of Withholding)
    • “Impuesto repercutido - Porcentaje” => tax rate % (VAT-debit tax rate%)
    • “Impuesto repercutido - Base imponible” => Tax base amount (transaction currency)
    • “Impuesto repercutido - Cuota” => Tax amount (transaction currency)
    • “Impuesto repercutido – Totales Recargo de equivalencia” => Equivalence charge amount (not mandatory)
• INVOICE TOTALS section:
  • “Total importe bruto”=> total tax base amount (excluding tax)
  • “Total importe” => total tax base amount (excluding tax)
  • “Total impuestos repercutidos” => total tax amount (VAT-debit)
  • “Total impuestos retenidos (soportado)” => total tax amount (VAT-credit) = 0,00
  • “Total factura”=> total invoice amount
  • “Total a pagar” => total invoice amount
  • “Total a ejecturar” => total invoice amount
• INVOICE LINES section:
  • “Descripción del bien” => Good/ Services name/description
  • “Cantidad” => Goods/Services Quantity
  • “Unidad” = list of valid values => Unit of measure (not mandatory)
    • (01) Unidades
    • (02) Horas-HUR
    • (03) Kilogramos-KGM
    • (04) Litros-LTR
    • (05) Otros
    • (06) Cajas-BX
    • (07) Bandejas-DS
    • (08) Barriles-BA
    • (09) Bidones-JY
    • (10) Bolsas-BG
    • (11) Bombonas-CO
    • (12) Botellas-BO
    • (13) Botes-CI
    • (14) Tetra Briks
    • (15) Centilitros-CLT
    • (16) Centímetros-CMT
    • (17) Cubos-BI
    • (18) Docenas
    • (19) Estuches-CS
    • (20) Garrafas-DJ
    • (21) Gramos-GRM
    • (22) Kilómetros-KMT
    • (23) Latas-CA
    • (24) Manojos-BH
    • (25) Metros-MTR
    • (26) Milímetros-MMT
    • (27) 6-Packs
    • (28) Paquetes-PK
    • (29) Raciones
    • (30) Rollos-RO
    • (31) Sobres-EN
    • (32) Tarrinas-TB
    • (33) Metro cúbico-MTQ
    • (34) Segundo-SEC
    • (35) Vatio-WTT
  • “Precio unitario” => Unit price
  • “Coste”=> Invoice line amount
  • “Importe bruto” => Invoice line amount
  • “Impuesto repercutido – clase”= list of valid values => Tax type
    • (01) IVA: Impuesto sobre el valor añadido
    • (02) PSI: Impuesto sobre la producción, los servicios y la importación
    • (03) IGIC: Impuesto general indirecto de Canarias
    • (04) IRPF: Impuesto sobre la Renta de las personas físicas
    • (05) Otro
    • (06) ITPAJD: Impuesto sobre transmisiones patrimoniales y actos jurídicos documentados
    • (07) IE: Impuestos especiales
    • (08) Ra: Renta aduanas
    • (09) IGTECM: Impuesto general sobre el tráfico de empresas que se aplica en Ceuta y Melilla
    • (10) IECDPCAC: Impuesto especial sobre los combustibles derivados del petróleo en la Comunidad Autonoma Canaria
    • (11) IIIMAB: Impuesto sobre las instalaciones que inciden sobre el medio ambiente en la Baleares
    • (12) ICIO: Impuesto sobre las construcciones, instalaciones y obras
    • (13) IMVDN: Impuesto municipal sobre las viviendas desocupadas en Navarra
    • (14) IMSN: Impuesto municipal sobre solares en Navarra
    • (15) IMGSN: Impuesto municipal sobre gastos suntuarios en Navarra
    • (16) IMPN: Impuesto municipal sobre publicidad en Navarra
    • (17) REIVA: Régimen especial de IVA para agencias de viajes
    • (18) REIGIC: Régimen especial de IGIC: para agencias de viajes
    • (19) REIPSI: Régimen especial de IPSI para agencias de viajes
    • In our case we will use either (01) IVA (in case of VAT and EC) and (04) IRPF (in case of Withholding)
  • “Impuesto repercutido – porcentaje” => tax rate % (VAT
  • “Impuesto repercutido – base imponible”=> Tax base amount (transaction currency)
  • “Impuesto repercutido – cuota”=> Tax amount (transaction currency)
  • “Impuesto repercutido – Totales Recargo de equivalencia” => Equivalence charge amount (not mandatory)
• Payment data (not mandatory)
  • “Vencimiento” => Invoice due date
  • “Importe” => Invoice amount
  • “Medio de pago” = list of valid values => Payment Method
    • (01) Al Contado
    • (02) Recibo domicilido
    • (03) Recibo
    • (04) Transferencia
    • (05) Letra aceptada
    • (06) Crédito documentario
    • (07) Contrato Adjudicación
    • (08) Letra de cambio
    • (09) Pagaré a la orden
    • (10) Pagaré No a la Orden
    • (11) Cheque
    • (12) Reposición
    • (13) Especiales
    • (14) Compensación
    • (15) Giro Postal
    • (16) Cheque conformado
    • (17) Cheque bancario
    • (18) Pago contra reembolso
    • (19) Pago mediante tarjeta
  • “IBAN” => IBAN

OB ERP invoices contain all the information listed above as mandatory by default, therefore there is no need for any additional enhancement or change in OB ERP.
The XML file will not take into account not mandatory information such as "units of measure" or "Forms of payment"; rest will be taken into account while implementing facturae xml format as part of current development.

Functional Requirement nº 3 - Issuer company – Legal obligations regarding e-invoicing

Companies which issue sales invoices as electronic invoices have to comply with below listed law requirements:

• Invoices must have the content above required and must be created either by using an ERP or by using a software application.
• Invoices must be signed by valid Certificate (digital signature).
• Invoice must be sent from 1 computer to another computer via internet.
• A copy of the invoice sent must be archived
• Invoice must be post and noted in the correspondent VAT register book.
• It has to be possible to inquiry, search, copy, download or print an invoice whenever its needed.
• It is possible to get above invoice related features on behalf of a tax payer by using an intermediary platform/software, although the tax payer will keep on having the legal obligations not the intermediary.

Camerfactura web portal allows the user to comply with all the legal obligations listed above, therefore there is no need for any additional enhancement or change here.

Functional Requirement nº 4 - Recipient company - Legal obligations regarding e-invoicing

Companies which received invoices as electronic invoices have to comply with below listed law requirements:

• Invoice reception via internet which implies:
• Invoice content verification
• Digital signature verification
• Invoice posting and note in the correspondent VAT register book.
• Received invoice must be achieve as requested by law (originals signed).
• It has to be possible to inquiry, search, copy, download or print a received invoice whenever its needed.
• It is possible to get above invoice related features on behalf of a tax payer by using an intermediary platform/software, although the tax payer will keep on having the legal obligations not the intermediary.

Camerfactura web portal allows the user to comply with all the legal obligations listed above, therefore there is no need for any additional enhancement or change here.

It is important to note that received e-invoices is not in scope as described in section “Overview & Justification - Out of Scope”.

Functional Requirement nº 5 - Configuration

ID configuration

It is required that OB Organización is registered in Camerfactura web platform. For doing that Mike needs to go to Camerfactura platform and enter OB Organization data (generic data like organization name, tax id and location data) in order to get that OB organization is created in the platform together with a valid Camerfirma Certificate which will be used to sign the invoices.

Once OB Organization is registered there will be an ID number named “ID para ERP's” assign it to it. That ID can be found in the scree below:

That ID should be entered as an additional Client master data in a new field under application path General Setup / Organization / Organization / Information tab

That new field could be named “e-invoice platform id”.

Same goes with "Template ID" (which in this case is 55). That Invoice ID template number will allow to setup Entity invoice template as requested to Camerfactura web platform. Legally requested information such us different type of VAT's and EC view must be covered by default without any additional charge.

To get Template ID properly setup, XML file must have below structure:

<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" href=" http://desarrollo.camarafactura.es/public/xsl/XX_cci.xsl "?>

<namespace:Facturae xmlns:namespace="http://www.fact...

Where XX is = template ID

Electronic invoice configuration

In order to get that Mike can send “Issued Invoices” as “electronic invoices” below detailed UI (user interface) enhancements need to be implemented in OB ERP:

a) Business partner data. Below new fields needs to be added in the Application path: Master Data Management / Business Partner / Customer tab. Fields below must appear if “Customer” field is selected:

• e-invoice => as a check box (Yes/No)
• e-invoice file format => as a reference list with 2 possible values either None or Facturae 3.1 Facturae 3.1 whenever e-invoice module has been installed and applied to the corresponding Client/Organization as there could be other modules to be developed based on different format which will be added to the reference list
• e-invoice platform => as a reference list with 2 possible values either None or Camerfactura.
• e-mail => free text field to be filled-in by the user. It will be mandatory in case of e-invoice delivery “Adjunto e-mail”, “Usuario Portal” and “Descagar on-line”.
• Delivery mode => as a reference list based on Camerfactura web platform:
  • “Adjunto e-mail” => this option means that the invoice will be send as a signed xml file by email
  • “Correo ordinario”=> this option means that the invoice will be send by post as a signed pdf file containing pdf417 barcodes
  • “Usuario portal”=> this option means that the invoices will be send through Camerfactura portal in those cases when Mike company's customer are also Camerfactura users. Mike's company customers will received these invoices in the “Received invoices” folder of Camerfactura web platform. A notification e-mail is sent as well.
  • “Descarga on-line” => this option means that an email will be sent to the customer with an url where sales invoices can be found. In this case the way customer will access to that web link must be setup as either user id&password or via Digital Certificate; that info will be sent to the customer via e-mail after its configuration.

It is important to note that end-user will have to register manually the customers allowing e-invoicing in Camerfactura platform in “Clientes / Gestión de Clientes” platform path, as shown below:

b) Sales invoice. Below application objects needs to be added in the Application path: Sales Management / Transactions / Sales Invoice / Sales invoice Header.

• A new process button will be created named “Generate e-invoice”, which will be shown only for those customers allowing e-invoice via facturae format, and once an issued invoice is completed and posted. The user must press this button to generate the electronic invoice as xml file according to facturae formate. Once press its name will change to “e-invoice Generated”
• Another new process button will be created named “Generate and send e-invoice” which will create the xml file as well and send it to Camerfactura web platform. Once press its name will change to “e-invoice Created and Generated”

Persona based scenarios

As part of Small Bazaar company Mike should invoice Small Bazaar Pamp and Small Bazaar Barc Spanish customers for the goods delivered to them (or for the services provided to them) after monitoring that the corresponding good shipments have been entered and completed in the system once the goods have left the warehouse.

Besides Mike should be able to enter and post in the system the corresponding sales corrective invoices in case there are any error such as wrong prices, wrong quantities delivered affecting already post and sent sales invoices.

Sales invoices sent as a xml file

Mike needs to enter in OB ERP “electronic invoice” related information for the existing customers who allow Mike's company to send to them invoices electronically.

For doing that Mike should navigate to: Data Management / Business Partner - Customer tab create a new customer/s and fill-in below information for that customer/s:

• e-invoice => Mike should set to this parameter/check-box to “Yes”
• e-invoice file format => Mike should select here “Facturae 3.1”
• e-invoice platform => Mike should select here “Camerfactura”
• delivery mode => Mike must select only one from the list depending on how the corresponding customer can interact with Camerfactura platform. (For more information see scenarios below)
• e-mail => Mike should enter here the email account to which the xml file will be sent by Camerfactura platform. This field would be mandatory in case Mike selects either “Adjunto e-mail”, “Descarga on-line” or “Usuario portal” delivery options.

Besides Mike should create that customer/s in Camerfactura platform.

Sales Invoice generated for a National customer as a xml file

For this scenario Mike needs to create a customer “National Customer” which allows Mike's company to sent the invoice as xml files signed/certified by email by example; with at least below information:

• Customer Name => BP Name = “National Customer”
• Customer Tax Id => BP Tax Id = B12345678
• Customer location => BP Location/Address tab = Address, postcode, location, region and country (Spain)
• Contact person information => BP Contact tab = Contact person name, phone number, email, fax, tax id....
• e-invoice delivery => “Adjunto e-mail”
• e-invoice email => direccion@dominio.com
• e-invoice format => facturae 3.1
• Language => BP language = Spanish (Spain)
• Payment Method => BP Payment Method = Bank Transfer
• Payment terms => BP Payment terms = one month (30 days)
• Bank account (IBAN) => BP Transactional Bank Account = XXXX-XXXX-XX-XXXXXXXXXX
• Currency = EUR (depending on the Price List selected for the customer).

Mike should also create “National Customer” in Camerfactura (“Clientes / Gestión de Clientes” platform path) as a “Resident” Customer.

Next step for Mike to take is to enter in the system an “ordinary” sales invoice for the National Customer as an AR invoice document type by navigating to Sales Management / Sales invoice or as an AR invoice indirect document type by navigating to Sales Management / Generate Invoices.

Once the sales invoice header and lines are entered Mike should complete and post the sales invoice.

Once the above is done Mike needs at least to press the new button “Generate e-invoice”; that button will change to “e-invoice Generated” when the xml file according to facturae 3.1 format is created.

Facturae xml format will have to contain below information:

• Header section
  • “Version” = fixed value => 3.1
  • “Modalidad” = “I”
  • “Tipo Emisor” = “EM”
  • “Lote – Identificador de Lote” = “invoice id”
  • “Lote – Número total facturas” => “1”
  • “Lote – Importe total facturas” => “invoice amount”
  • “Lote – Total a pagar” => “invoice amount”
  • “Lote – Total a ejecturar” => “invoice amount”
  • “Lote – Código moneda factura” => “EUR”
• Issuer section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “OB ERP Client/Organization Tax ID”
  • “Datos personales – Razón Social => “OB Company/Organization name”
  • “Datos personales – Datos domicilio” => “Location data (address, postcode, Location, Region and Country)”
• Recipient section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “National Customer Tax ID”
  • “Datos personales – Razón Social => “National Customer name”
  • “Datos personales – Datos domicilio” => “National Customer location data (address, postcode, Location, Region and Country)”
• Invoice section
  • Invoice header
    • “Número de factura” => invoice number
    • “Tipo documento” => “FC”
    • “Clase factura” = “OO”
  • Invoice data
    • “Fecha expedición” => invoice date
    • “Moneda factura” => “EUR”
    • “Moneda impuesto” => “EUR”
    • “Lengua” => “ESP”
  • Tax data
    • “Clase impuesto” = to be grouped by Tax type (01) IVA or (04) IRPF
      • OB ERP tax rates applicable are:
      • Arrendamientos 16% (cobros)
      • Arrendamientos 16% - 18%R (cobros)
      • Entregas a Canarias, Ceuta y Melilla (16%=>0%)
      • Entregas a Canarias, Ceuta y Melilla (4%=>0%)
      • Entregas a Canarias, Ceuta y Melilla (7%=>0%)
      • Entregas IVA 16%
      • Entregas IVA 4%
      • Entregas IVA 7%
      • Entregas IVA + RE 16% + 4%
      • Entregas IVA + RE 4% + 0,5%
      • Entregas IVA + RE 7% + 1%
      • Transmissión B.Imuebles 16%
      • Transmissión B.Imuebles 7%
      • Ventas exentas 0%
      • Servicios prestados exentos 0%
      • Servicios prestados nacional 16%
      • Servicios prestados nacional 7%
      • Servicios prestados nacional 4%
      • Servicios prestados nacional 16% -15%R(IRPF)
      • Servicios prestados nacional 16% - 7%R(IRPF)
      • Servicios prestados a Canarias, Ceuta y Melilla (16%=>0%)
      • Servicios prestados a Canarias, Ceuta y Melilla (7%=>0%)
      • Servicios prestados a Canarias, Ceuta y Melilla (4%=>0%)
    • “Porcentaje” => tax rate %(either 0% - 16% - 7% - 4%- 1% - 0,5% - 15% - 7%)
    • “Base imponible” => Tax base amount (transaction currency)
    • “Cuota” => Tax amount (transaction currency)
    • “Recargo de equivalencia” => Equivalence charge amount
• Invoice totals section
  • “Total importe bruto”=> total tax base amount
  • “Total importe” => total tax base amount
  • “Total impuestos repercutidos” => total tax amount
  • “Total impuestos retenidos” => “0,00”
  • “Total factura”=> total invoice amount
  • “Total a pagar” => total invoice amount
  • “Total a ejecturar” => total invoice amount
• Invoice lines
  • “Descripción del bien” => Good/ Services name/description
  • "Cantidad” => Goods/Services Quantity
  • “Unidad” = list of valid values => (01) Unidades
  • “Precio unitario” => Unit price
  • “Coste”=> Invoice line amount
  • “Importe bruto” => Invoice line amount
  • “Impuesto repercutido – clase”= (01) IVA or (04) IRPF per line, regarding tax rate types see above
  • “Impuesto repercutido – porcentaje” => tax rate % (either 0% - 16% - 7% - 4% - 4% - 1% - 0,5%- 15% - 7%)
  • “Impuesto repercutido – base imponible”=> Tax base amount (transaction currency)
  • “Impuesto repercutido – cuota”=> Tax amount (transaction currency)
• Payment data (not mandatory)
  • “Vencimiento” => Invoice due date
  • “Importe” => Invoice amount
  • “Medio de pago” = (04) Transferencia
  • “IBAN” => IBAN or Bank account (IBAN preferably)

Negative/Credit sales invoice generated as xml file

Above scenarios apply here but in this case there are below listed specific things:

• 1. Mike needs to enter credit invoice as a negative AR invoice by navigating to Sales Management / Sales Invoice or negative AR invoice indirect by navigating to Sales Management / Generate Invoices or as a positive AR credit memo by navigating to Sales Management / Sales Invoice.
• 2. Facturae xml file would contain either negative amounts
• 3. Facturae xml file should contain in the Invoice header section below information:
  • “Número de factura” => invoice number
  • “Tipo documento” => “FC”
  • “Clase factura” = “OO”

Good Sales Invoices including several “National” VAT tax rates

In this case Mike needs to enter a goods sales invoice as an “AR invoice” in € for “National Customer” for several goods having different tax rates (Sales VAT 16% and Sales VAT 7%). For doing that he should navigate to Sales Management / Sales invoice and enter the corresponding AR invoice.

That AR invoice will have at least 2 sales lines for 2 different product having different sales VAT, 16% and 7%.

Mike can complete and post the invoice and after that is able to create facturae xml file by pressing the button “Generate e-invoice”; in this case facturae xml file should take into account below information:

• Header section
  • “Version” = fixed value => 3.1
  • “Modalidad” = “I”
  • “Tipo Emisor” = “EM”
  • “Lote – Identificador de Lote” = “invoice id =002A1005”
  • “Lote – Número total facturas” => “1”
  • “Lote – Importe total facturas” => “invoice amount = 7.557,48”
  • “Lote – Total a pagar” => “invoice amount = 7.557,48”
  • “Lote – Total a ejecturar” => “invoice amount = 7.557,48”
  • “Lote – Código moneda factura” => “EUR”
• Issuer section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “B31733934”
  • “Datos personales – Razón Social => “Openbravo”
  • “Datos personales – Datos domicilio” =>
    • Address = Landaben
    • Postcode = 31012
    • Location = Pamplona
    • Region = Navarra
    • Country= ESP
• Recipient section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “A41414141”
  • “Datos personales – Razón Social => “National Customer S.A”
  • “Datos personales – Datos domicilio” =>
    • Address = c/ San Vicente
    • Postcode = 31013
    • Location = Pamplona
    • Region = Navarra
    • Country= ESP
• Invoice section
  • Invoice header
    • “Número de factura” => invoice number = 002A1005
    • “Tipo documento” => FC
    • “Clase factura” = OO
  • Invoice data
    • “Fecha expedición” => invoice date = 2009-03-02
    • “Moneda factura” => EUR
    • “Moneda impuesto” => EUR
    • “Lengua” => “ESP”
  • Tax data

Clase impuesto	(01) IVA – Entregas IVA 16%	(01) IVA – Entregas IVA 7%
Clase impuesto	16,00%	7,00%
Base imponible	4578,00	2100,00
Cuota	732,00	147,00

• Invoice totals section
  • “Total importe bruto”=> total tax base amount = 6.678,00
  • “Total importe” => total tax base amount = 6.678,00
  • “Total impuestos repercutidos” => total tax amount (including EC) = 879,48
  • “Total impuestos retenidos” => 0,00
  • “Total factura”=> total invoice amount = 7.557,48
  • “Total a pagar” => total invoice amount = 7.557,48
  • “Total a ejecturar” => total invoice amount = 7.557,48
• Invoice lines

Descripción del bien	Cuadernos	Libros
Cantidad	500	60
Unidad	(01) Unidades	(01) Unidades
Precio unitario	9,16	35,00
Coste	4.578,00	2.100,00
Importe bruto	4.578,00	2.100,00
Impuesto repercutido – clase	(01) IVA Entregas IVA 16%	(01) IVA Entregas IVA 7%
Impuesto repercutido – Porcentaje	16	7
Impuesto repercutido - Base imponible	4.578,00	2.100,00
Impuesto repercutido - cuota	732,78	147,00

Good Sales Invoices including “National” VAT + Equivalence charge

In this case Mike needs to enter a goods sales invoice as an “AR invoice” in € for a “National Customer B” which allow e-invoice for several goods having different tax rates (Sales VAT 16% and Sales VAT 7%) and under Equivalence Charge.

He should make sure that the customer is created in both OB ERP (including e-invoicing information) and Camerfactura platform. Besides he needs to make sure National Customer B has properly setup “Equivalent Charge” Business partner tax category, therefore a equivalence charge tax rate will be prompt in Sales order lines, “Tax” field.

Mike must navigate to Sales Management / Sales invoice and enter the corresponding AR invoice.

That AR invoice will have at least 2 sales lines for 2 different product having different sales VAT, 16% and 7% and the corresponding Equivalence Charge.

Mike can complete and post the invoice and after that is able to create facturae xml file by pressing the button “Generate e-invoice”; in this case facturae xml file should take into account below information:

• Header section
  • “Version” = fixed value => 3.1
  • “Modalidad” = “I”
  • “Tipo Emisor” = “EM”
  • “Lote – Identificador de Lote” = “invoice id =002A1006”
  • “Lote – Número total facturas” => “1”
  • “Lote – Importe total facturas” => “invoice amount = 5.628,6
  • “Lote – Total a pagar” => “invoice amount = 5.628,6
  • “Lote – Total a ejecturar” => “invoice amount = 5.628,6
  • “Lote – Código moneda factura” => “EUR”
• Issuer section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “B31733934”
  • “Datos personales – Razón Social => “Openbravo”
  • “Datos personales – Datos domicilio” =>
    • Address = Landaben
    • Postcode = 31012
    • Location = Pamplona
    • Region = Navarra
    • Country= ESP
• Recipient section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “A42424242”
  • “Datos personales – Razón Social => “National Customer B S.A”
  • “Datos personales – Datos domicilio” =>
    • Address = c/ San Miguel
    • Postcode = 31014
    • Location = Pamplona
    • Region = Navarra
    • Country= ESP
• Invoice section
  • Invoice header
    • “Número de factura” => invoice number = 002A1006
    • “Tipo documento” => FC
    • “Clase factura” = OO
  • Invoice data
    • “Fecha expedición” => invoice date = 2009-10-20
    • “Moneda factura” => EUR
    • “Moneda impuesto” => EUR
    • “Lengua” => “ESP”
  • Tax data

Clase impuesto	(01) IVA Entregas IVA + RE 16+4	01) IVA Entregas IVA + RE 16 +4	01) IVA Entregas IVA + RE 7+1	01) IVA Entregas IVA + RE 7+1
Clase impuesto	16,00%	4,00%	7,00%	1,00%
Base imponible	1.500,00	1.500,00	3.545,00	3.545,00
Cuota	240,00	60,00	248,15	35,45

• Invoice totals section
  • “Total importe bruto”=> total tax base amount = 5.045,00
  • “Total importe” => total tax base amount = 5.045,00
  • “Total impuestos repercutidos” => total tax amount (including EC) = 583,6
  • “Total impuestos retenidos” => 0,00
  • “Total factura”=> total invoice amount = 5.628,6
  • “Total a pagar” => total invoice amount = 5.628,6
  • “Total a ejecturar” => total invoice amount = 5.628,6
• Invoice lines

Descripción del bien	Cuadernos	Libros
Cantidad	1	1
Unidad	(01) Unidades	(01) Unidades
Precio unitario	1.500,00	3.545,00
Coste	1.500,00	3.545,00
Importe bruto	1.500,00	3.545,00
Impuesto repercutido – clase	(01) IVA	(01) IVA
Impuesto repercutido – Porcentaje	16,00%	4,00%
Impuesto repercutido- Base imponible	1.500,00	1.500,00
Impuesto repercutido- cuota	240,00	60,00
Recargo Equivalencia	248,15	35,45

Services Sales Invoices including “National” VAT + Withholding

In this case Mike needs to enter a goods sales invoice as an “AR invoice” in € for a National Customer C which allows e-invoice for several services provided by Mike's company subject to withholding.

Mike needs to create National Customer C as appropriate both in OB ERP and Camerfactura platform.

Mike must navigate to Sales Management / Sales invoice and enter the corresponding AR invoice.

That AR invoice must have at least 2 sales lines for 2 different services (Services A and Services B) which have the same withholding rate depending on business partner specifics, but could be they have different VAT (16% & 7%), like the ones showed below:

• “Servicios prestados nacional 16% - 15%R” for Services A. Mikes needs to be sure this tax rate should have 2 child tax rates one of them set as withholding and with a rate of -15.
• “Servicios prestados nacional 7% - 15%R” for Services B. Mikes needs to be sure this tax rate should have 2 child tax rates one of them set as withholding and with a rate of -15.

Mike can complete and post the invoice and after that is able to create facturae xml file by pressing the button “Generate e-invoice”; in this case facturae xml file should take into account below information:

• Header section
  • “Version” = fixed value => 3.1
  • “Modalidad” = “I”
  • “Tipo Emisor” = “EM”
  • “Lote – Identificador de Lote” = “invoice id =002S102525”
  • “Lote – Número total facturas” => “1”
  • “Lote – Importe total facturas” => “invoice amount =6.109,31
  • “Lote – Total a pagar” => “invoice amount = 6.109,31
  • “Lote – Total a ejecturar” => “invoice amount = 6.109,31
  • “Lote – Código moneda factura” => “EUR”
• Issuer section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “B31733934”
  • “Datos personales – Razón Social => “Openbravo”
  • “Datos personales – Datos domicilio” =>
    • Address = Landaben
    • Postcode = 31012
    • Location = Pamplona
    • Region = Navarra
    • Country= ESP
• Recipient section
  • “Identificación fiscal – Tipo Persona”= “J”
  • “Identificación fiscal – Residencia” = ”R”
  • “Identificación fiscal – Código identificación => “A42424242”
  • “Datos personales – Razón Social => “National Customer B S.A”
  • “Datos personales – Datos domicilio” =>
    • Address = c/ San Miguel
    • Postcode = 31014
    • Location = Pamplona
    • Region = Navarra
    • Country= ESP
• Invoice section
  • Invoice header
    • “Número de factura” => invoice number = 002S102525
    • “Tipo documento” => FC
    • “Clase factura” = OO
  • Invoice data
    • “Fecha expedición” => invoice date = 2009-10-30
    • “Moneda factura” => EUR
    • “Moneda impuesto” => EUR
    • “Lengua” => “ESP”
  • Tax data

Clase impuesto	(01) IVA Servicios prestados nacional 16% - 15% R	04) IRPF Servicios prestados nacional 16% - 15%R	01) IVA Servicios prestados nacional 7% - 15%R	04) IRPF Servicios prestados nacional 7% - 15%R
Clase impuesto	16,00%	(-)15,00%	7,00%	(-)15,00%
Base imponible	2.500,75	2.500,75	3.895,17	3.895,17
Cuota	400,12	(-) 375,11	272,66	(-)584,28

• Invoice totals section
  • “Total importe bruto”=> total tax base amount = 6.395,92
  • “Total importe” => total tax base amount = 6.395,92
  • “Total impuestos repercutidos” => total tax amount (including EC) = 672,78
  • “Total impuestos retenidos” => 0,00
  • “Total factura”=> total invoice amount = 6.771,50
  • “Total a pagar” => total invoice amount = 6.771,50
  • “Retenciones” => total withholding amount = -959,39
  • “Total a ejecturar” => total invoice amount = 6.109,31
• Invoice lines

Descripción del bien	Cuadernos	Cuadernos	Libros	Libros
Cantidad	1	1	1	1
Unidad	(01) Unidades	(01) Unidades	(01) Unidades	(01) Unidades
Precio unitario	2.500,75	2.500,75	3.895,17	3.895,17
Coste	2.500,75	2.500,75	3.895,17	3.895,17
Importe bruto	2.500,75	2.500,75	3.895,17	3.895,17
Impuesto repercutido – clase	(01) IVA	(04) IRPF	(01) IVA	(04) IRPF
Impuesto repercutido – Porcentaje	16,00%	15,00%	7,00%	15,00%
Impuesto repercutido- Base imponible	2.500,75	2.500,75	3.895,17	3.895,17
Impuesto repercutido- cuota	400,12	(-) 375,11	272,66	(-)584,28

Shipment dates versus Invoice dates

Mike enters in the system a sales order for a customer dated on October 10^th, 2009. After that he completes.

Warehouse staff enters in the system and complete the corresponding Good Shipment for the goods dated on October 15^th, 2009

Some days later Mike manages to enter in the system and complete the corresponding sales invoice, therefore sales invoice date is October 20^th, 2009

There are 2 dates to take into account in facturae 3.1 format:

• Invoice date (fecha expedición) – which is OB ERP sales invoice date.
• Shipment / Operation date (fecha operación) – which is OB ERP good shipment date.

Only invoice date is mandatory, therefore only invoice date will be taken as part of xml file content.

Sales Invoice sent and signed as “Adjunto e-mail”

For this scenario Mike needs to create a customer “Customer A” which allows Mike's company to sent the invoice as xml files signed/ certified by email; with at least below information:

• Customer Name => BP Name = “Customer A”
• Customer Tax Id => BP Tax Id = B31313131
• Customer location => BP Location/Address tab = Address, postcode, location, region and country
• Contact person information => BP Contact tab = Contact person name, phone number, email, fax, tax id....
• e-invoice delivery => “Adjunto e-mail”
• e-invoice email => customerA@hotmail.com
• e-invoice format => facturae 3.1
• Language => BP language = Spanish (Spain)
• Payment Method => BP Payment Method = check
• Payment terms => BP Payment terms = one month (30 days)
• Bank account (IBAN) => BP Transactional Bank Account = XXXX-XXXX-XX-XXXXXXXXXX
• Currency = EUR (depending on the Price List selected for the customer).

Mike should create also "Customer D" in Camerfactura platform, in “Clientes / Gestión de Clientes” platform path and set as "Delivery form=Adjunto on-line"

Next step for Mike to take is to enter in the system an “ordinary” sales invoice for Customer A as an AR invoice document type by navigating to Sales Management / Sales invoice. Once the sales invoice header and lines are entered Mike should complete and post the sales invoice.

Once the above is done Mike needs to press the new button “Generate e-invoice”; that button will change to “e-invoice generated” when the xml file according to facturae 3.1 format is created, but in this case Mike would also like to send it to Camerfactura web platform, therefore he should press new process button “Generate and send e-invoice”; that button will change to “e-invoice generated and sent” when the xml file according to facturae 3.1 format is created and sent.

Next action is for Mike to go to Camerfactura platform, “Facturación / Pendientes de envío” platform path. Once there he could find the invoice he has just created and sent from OB ERP in order to get it signed and sent. For doing that Mike should select the invoice and press the menu button “Sign”, a new window will show the a valid “Certificate” Mike should select in other to sign the invoice; once the invoice is signed the system will inform Mike that the invoice has been successfully signed.

File:Adjuntoemail.png

Next action for Mike to take is to go back and send the invoice by pressing the menu button “Send”, a new window will show the default e-mail text in the corresponding language, to the corresponding e-mail account including the xml file as an attachment.

Once sent the invoice will be moved to “Facturación / Enviadas “ platform path.

Sales Invoice sent as “ Usuario portal”

This scenario is similar to previous one but e-invoice delivery which this time is “Usuario portal”, therefore Mike needs to create a new customer which is also a Camerfactura user; with below data at least:

• Customer Name => BP Name = “Customer B”
• Customer Tax Id => BP Tax Id = B32323232
• Customer location => BP Location/Address tab = Address, postcode, location, region and country
• Contact person information => BP Contact tab = Contact person name, phone number, email, fax, tax id....
• e-invoice delivery => “Usuario Portal”
• e-invoice email => customerB@hotmail.com
• e-invoice format => facturae 3.1
• Language => BP language = Spanish (Spain)
• Payment Method => BP Payment Method = Bank Transfer
• Payment terms => BP Payment terms = one month (30 days)
• Bank account (IBAN) => BP Transactional Bank Account = XXXX-XXXX-XX-XXXXXXXXXX
• Currency = EUR (depending on the Price List selected for the customer).

In this case there will not be any need for Mike to register “Customer B” in Camerfactura web platform as Customer B should be already registered.

Next step for Mike to take is to enter in the system an “ordinary” sales invoice for Customer B as an AR invoice document type by navigating to Sales Management / Sales invoice. Once the sales invoice header and lines are entered Mike should complete and post the sales invoice.

Once the above is done Mike needs to press the new button “Generate e-invoice”; that button will change to “e-invoice generated” when the xml file according to facturae 3.1 format is created, but in this case Mike would also like to send it to Camerfactura web platform, therefore he should press new process button “Generate and send e-invoice”; that button will change to “e-invoice generated and sent” when the xml file according to facturae 3.1 format is created and sent.

Next action is for Mike to go to Camerfactura platform, “Facturación / Pendientes de envío” platform path.

Once there he could find the invoice he has just created for Customer B and sent from OB ERP in order to get it signed and sent. For doing that Mike should select the invoice and press the menu button “Sign”, a new window will show the a valid “Certificate” Mike should select in other to sign the invoice; once the invoice is signed the system will inform Mike that the invoice has been successfully signed.

Next action for Mike to take is to go back and send the invoice by pressing the menu button “Send”, this time Camerfactura platform will generate an e-mail to let Customer B know that the invoice can be found in their Camerfactura platform environment under “Facturación / Recibidas” platform path; besides the invoice will be moved to “Facturación / Enviadas “ platform path.

Sales Invoice sent as “Descarga on-line”

This scenario is similar to previous one but e-invoice delivery which this time is “Descarga on-line”, therefore Mike needs to create a new customer which want to receive e-invoice through an url; with below data at least:

• Customer Name => BP Name = “Customer C”
• Customer Tax Id => BP Tax Id = B33333333
• Customer location => BP Location/Address tab = Address, postcode, location, region and country
• Contact person information => BP Contact tab = Contact person name, phone number, email, fax, tax id....
• e-invoice delivery => “Descarga on-line”
• e-invoice email =>customerC@hotmail.com
• e-invoice format => facturae 3.1
• Language => BP language = Spanish (Spain)
• Form of payment => BP Form of payment = Bank Transfer
• Payment terms => BP Payment terms = one month (30 days)
• Bank account (IBAN) => BP Transactional Bank Account = XXXX-XXXX-XX-XXXXXXXXXX
• Currency = EUR (depending on the Price List selected for the customer).
  

Mike should create also "Customer D" in Camerfactura platform, in “Clientes / Gestión de Clientes” platform path and set as "Delivery form=Descarga on-line"

For this scenario Mike needs to complete Customer C data in Camerfactura platform in order to allow Customer C to access to its sales invoices via a generated url. For doing that Mike needs to navigate to “Clientes / Gestión clientes” platform path and fill-in “Acceso on-line” tab as shown below:

Once he has entered the corresponding user & password information he should sent it to the customer by pressing the button “Envía cliente”. The platform will send and e-mail to the customer let it him know the user/password to use as described below:

An url will be generated for Customer C to have access to its e-invoice as shown below:

Sales Invoice sent as “Correo ordinario”

This scenario is similar to previous ones but e-invoice delivery which this time is set to “Correo Ordinario”.
Mike needs to create a new customer which would like to receive its invoices as a pdf file signed by entering in OB ERP below information at least:

• Customer Name => BP Name = “Customer D”
• Customer Tax Id => BP Tax Id = B55555555
• Customer location => BP Location/Address tab = Address, postcode, location, region and country
• Contact person information => BP Contact tab = Contact person name, phone number, email, fax, tax id....
• e-invoice delivery => “Correo ordinario” (informative field)
• Language => BP language = Spanish (Spain)
• Payment Method => BP Payment Method = Bill of Exchange
• Payment terms => BP Payment terms = one month (60 days)
• Bank account (IBAN) => BP Transactional Bank Account = XXXX-XXXX-XX-XXXXXXXXXX
• Currency = EUR (depending on the Price List selected for the customer).
  

Mike should create also "Customer D" in Camerfactura platform, in “Clientes / Gestión de Clientes” platform path and set as "Delivery form=Correo Ordinario"

Next step for Mike to take is to enter in the system an “ordinary” sales invoice for Customer D as an AR invoice document type by navigating to Sales Management / Sales invoice. Once the sales invoice header and lines are entered Mike should complete and post the sales invoice.

Once the above is done Mike needs to press the new button “Generate e-invoice”; that button will change to “e-invoice generated” when the xml file according to facturae 3.1 format is created, but in this case Mike would also like to send it to Camerfactura web platform, therefore he should press new process button “Generate and send e-invoice”; that button will change to “e-invoice generated and sent” when the xml file according to facturae 3.1 format is created and sent.

Next action is for Mike to go to Camerfactura platform, “Facturación / Pendientes de envío” platform path. Once there he could find the invoice he has just created for Customer D and sent from OB ERP in order to get it signed and sent by post "Correo Ordinario". For doing that Mike should select the invoice and press the button "Sign". Once signed he should double click on it or press the menu button “View invoice”, a new window will show the invoice. From there Mike should print it and pdf417 bar codes will be generated.

Assumptions & Dependencies

Assumptions

N/A

Dependencies

N/A

Design & Technical considerations

Design considerations

Electronic invoice feature should be implemented as an extended module part of the ES professional localization pack v2, moreover Electronic invoice extended module consist on 3 separated modules as described below:

• "Electronic Invoice" module (org.openbravo.module.einvoice-0.1.0.obx); which will allow the end-user to generate sales invoices as xml files
• "Facturae" module (org.openbravo.module.facturae31-0.1.0.obx); which will allow the end-user to generate sales invoices as xml file according to "Facturae v 3.1" format
• "Camerfactura web integration" (org.openbravo.module.wscamerfactura-0.1.0.obx); which will allow the end-user to send a facturae xml sales invoice to Camerfatura web platform via web services.

There is already a list of enhancement required for this feature:

1. Corrective invoice feature including corrective reason and corrective method (facturae invoice type OR)
2. xml file archive as an attachement
3. A Process to create several sales invoices as xml files at the same time (now it is just 1 by 1).
4. A Process to search which sales invoices are pending to be generated as xml files as well as to search the ones already sent as xml files
5. BP (customers) creation in Camerfactura platform by using the corresponding web services.
6. A sync process which allows the end user to know which is the Sales invoice status (signed, sent or delete) in Camerfactura in order to implement further actions related to un-post and reactivate process at OB ERP
7. Word plug-in
8. Heart beat enable to track e-invoice feature usability

Technical constraints

None

Technical Requirements

Object type	Data type	Value constraints	Default value	Editable	Label	Help text
New field path “General setup / Enterprise / Organization / Organization – Information tab name “Camerfactura ID”	Text file	n/a	n/a	Yes	“Camerfactura ID”	Enter here Camerfactura “ERP ID” value
New field path “Master Data management / Business Partner / Business Partner – customer tab name “e-invoice”	Check box	yes/no	No	Yes	“e-invoice”	Select in case current customer allows electronic invoice
New field path “Master Data management / Business Partner / Business Partner – customer tab name “e-invoice format”	Check box	None facturae v3.1	None	Yes	“e-invoice format”	Select electronic invoice format
New field path “Master Data management / Business Partner / Business Partner – customer tab name “e-invoice delivery mode”	Check box	None Adjunto e-mail Correo ordinario Descarga on-line Usuario portal	None	Yes	“e-invoice delivery mode”	Select electronic invoice delivery mode
New field path “Master Data management / Business Partner / Business Partner – customer tab name “e-invoice platform”	Check box	None Camerfactura	None	Yes	“e-invoice platform”	Select electronic invoice 3rd party platform
New field path “Master Data management / Business Partner / Business Partner – customer tab name “email”	Text file	n/a	n/a	Yes	“email”	Enter here Camerfactura email for electronic invoice
New process button path “Sales Management / Transactions / Sales Invoice / Header” name “Generate Electronic Invoice”	Button	“Generate Electronic Invoice”	n/a	n/a	“Generate Electronic Invoice”	Press in order to generate electronic invoice for the electronic invoice format setup for the customer
New process button path “Sales Management / Transactions / Sales Invoice / Header” name “Generate and Send Electronic Invoice”	Button	“Generate and Send Electronic Invoice”	n/a	n/a	“Generate and Send Electronic Invoice”	Press in order to generate an electronic invoice for the electronic invoice format setup for the customer; and send it to the electronic invoice platform setup for the customer.

User interface

New User Interface

N/A

User interface changes

1. Organization ERP ID

2. Business partner (Customer) configuration

3. Sales invoice

License

License code description

Spanish Professional Pack will be released under the Openbravo Commercial License (OBCL) as opposite as the Openbravo Public License (OPL) for open source modules

The OBCL needs to be accompanied by a "term sheet" that describes the specific licensing terms per module.

It is likely that a number of enhancements to modularity will be needed in order to store the term sheet as attributes of the module and to display them when the user acknowledges the license.

Product Strategy is responsible for publishing the license on the Openbravo web site. Developers are responsible for putting a reference to that license in the file header and to declare it in the module definition.

Functionality enabled by the license code

The functionality enabled by the license code will be:

1. Electronic Invoice generation as Facturae v 3.1 format ("facturae31" module)
2. Integration to Camerfactura web platform to which the Electronic Invoice as facturae v 3.1 format will be sent ("wscamerfactura" module)

The module which allows the end-user to generate sales invoice as an xml file format ("einvoice" module) will not be part of the license but a commercial module.

Discussion items

Open discussion items

Closed discussion items

Appendix

Facturae v 3.1 format & some examples can be found here:

link facturae_descargas