![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/64f6e029692fec672940ec6c/apero_odoo.jpeg\" "\\"apero_odoo.jpeg\\"")
Le jeudi 21 septembre 2023 (19h-21h30) aura lieu le premier des Apéros Odoo (OCA) de Lyon, organisés par Akretion.
Historiquement, Akretion a toujours été pionnier dans le domaine de la facturation électronique :
Akretion continue de maintenir activement les modules OCA de génération et d'import de factures Factur-X dans Odoo. Ces modules sont notamment utilisés par le connecteur Odoo-Chorus Pro de l'Odoo Community Association (OCA), dont la maintenance est assurée par Akretion et qui est largement déployé par les intégrateurs Odoo français.
Pour se conformer aux exigences de la réforme de la facturation électronique, Akretion développera en opensource une suite de modules pour implémenter les flux en émission et réception, à la fois pour les factures et aussi pour le e-reporting.
La stratégie d'implémentation sera la suivante :
Le choix du PDP qui sera fait par Akretion sera guidé par des critères d'excellence technique, de qualité du support technique et de prix. Étant donné que les 3 formats de la réforme (UBL, CII et Factur-X) sont supportés par les modules OCA, le PDP sera utilisé comme un simple canal de communication vers les clients/fournisseurs et la DGFIP et non comme un service à valeur ajoutée capable de convertir les factures générées par Odoo dans l'un des 3 formats de la réforme.
Ainsi, si les clients d'Akretion adoptent le PDP choisi par Akretion, ils bénéficieront d'un module prêt à l'emploi qui permettra, via l'API du PDP :
Si une entreprise fait le choix d'un autre PDP, elle devra en conséquence supporter les coûts de développement et de maintenance d'un module Odoo supplémentaire qui implémentera l'API spécifique de ce PDP. Dans tous les cas, les modules génériques assureront l'essentiel des fonctionnalités et seront conçus pour supporter de multiples modules PDP-spécifique.
De nombreux PDPs démarchent activement les entreprises et les incitent à souscrire à leurs offres sans attendre. Akretion conseille à ses clients de ne pas donner suite à ces sollicitations commerciales et d'attendre le choix d'un PDP qui sera fait par Akretion.
Lors de l'annonce de l'abandon du Portail Public de Facturation (PPF) en octobre 2024, la DGFiP a mis fin à la promesse d'APIs accessibles gratuitement pour les entreprises, mettant un coup d'arrêt au mouvement vers des APIs gratuites et ouvertes initié par Chorus Pro. Akretion avait critiqué cette décision, qui nous rappelait la situation sur la télétransmission de la TVA où les entreprises sont obligées de passer par des passerelles privées payantes pour remplir leurs obligations fiscales. Cette mauvaise nouvelle aura quand même permis de faire émerger une bonne décision : généraliser l'utilisation du réseau PEPPOL en France pour l'échange des factures entre clients et fournisseurs. PEPPOL est un réseau décentralisé d'échange de factures né en Europe, construit sur des standards ouverts et qui est déjà largement utilisée depuis de nombreuses années notamment en Europe du Nord (le PPF portait en lui le risque d'une plateforme trop centralisée qui aurait été un single point of failure). Avant l'annonce de l'abandon du PPF, Bercy avait toujours semblé très frileux sur l'adoption de PEPPOL ; l'échec du développement du PPF force Bercy à promouvoir les solutions existantes qui ont déjà fait leurs preuves ! Les PDPs pourraient maintenant être définis comme des points d'accès français au réseau PEPPOL avec une fonction \"mouchard\" qui envoie une copie de la facture à la DGFiP. Avec l'abandon du PPF, toutes les entreprises françaises devront choisir un PDP, et donc toutes les entreprises françaises seront raccordées au réseau PEPPOL. La réforme de la facturation électronique portait la promesse de généraliser le recours aux factures électroniques entre entreprises françaises ; elle porte maintenant la promesse additionnelle de pouvoir échanger des factures électroniques avec de nombreuses entreprises européennes.
Sur le choix du PDP, notre stratégie est de ne pas se précipiter. La raison de cette stratégie est la suivante : avant l'annonce de l'abandon du PPF en octobre 2024, le marché était scindé en deux :
A cette époque, les PDPs qui s'étaient lancés sur ce marché étaient des PDPs organisés avec des commerciaux B2B qui allaient démarcher des entreprises pour leur présenter leurs services à valeur ajoutée qui les différenciaient du PPF. Les tarifs étaient proposés dans le secret de négociations commerciales entre le PDP et son client ; aucun PDP n'affichait ses tarifs publiquement sur son site Internet.
Avec l'annonce surprise de l'abandon du PPF en octobre 2024, le marché est complètement chamboulé : 4,5 millions d'entreprises doivent choisir leur PDP avant le démarrage de la réforme ! Le marché des PDPs bascule d'un marché de niche à un marché de masse. Ce chamboulement du marché attire de nouveaux acteurs : il y a désormais des places à prendre pour de nouveau PDPs capables d'adresser un marché de masse avec des offres low cost dont les tarifs sont affichés en toute transparence sur Internet, sans frais de mise oeuvre et s'adressant à des PMEs capables de se raccorder de façon autonome en lisant la documentation de l'API. Chez ces nouveaux acteurs, les équipes de commerciaux B2B habitués à établir des devis sur mesure sont remplacées par un portail web qui présente les offres et les tarifs en toute transparence et où l'entreprise s'inscrit en ligne pour souscrire à l'offre qu'elle a choisie.
Cela explique notre stratégie de choisir un PDP sans se précipiter : il faut laisser le temps aux nouveaux acteurs qui vont adresser le marché comme un marché de masse de développer leur plateforme et lancer leurs offres low cost. On peut penser que ces nouveaux acteurs lanceront leurs offres d'ici fin 2025 et ou début 2026. S'engager avec un PDP dès maintenant nous priverait de l'accès à ces nouvelles offres.
Le 24 mars 2025, des députés réunis au sein de la commission chargée d'examiner le projet de loi de simplification de la vie économique ont adopté un amendement repoussant d'un an le démarrage de la réforme. Cet amendement était proposé par le député Christophe Naegelen du groupe LIOT. Un report d'un an de la réforme de facturation électronique signifie un report du démarrage de la réforme de septembre 2026 à septembre 2027, donc après l'élection présidentielle de mai 2027, ce qui revient à transférer la décision finale sur le sort de cette réforme au prochain président qui sortira des urnes en mai 2027. L'assemblée nationale a finalement voté le 11 avril 2025 contre cet amendement ; le calendrier actuel est donc maintenu avec un démarrage de la réforme en septembre 2026, sauf nouveau contre-ordre législatif.
Akretion continue sa veille active sur le projet de réforme la facturation électronique. Notre longue expérience de ce dossier nous incite à travailler sans précipitation. Tous ceux qui ont préparé un dossier de candidature à la phase pilote de la réforme en juin 2023 ont jeté leur travail à la poubelle (c'était le cas d'Akretion !). Tous ceux qui avaient commencé à implémenter les APIs du PPF ont jeté leur travail à la poubelle. Tous ceux qui ont commencé à implémenter les APIs d'un PDP vont devoir jeter leur travail à la poubelle si la commission AFNOR arrive à imposer une standardisation des APIs des PDPs. Qui a dit faire et défaire c'est toujours travailler ?
Akretion partage son analyse sur les annonces de ces derniers mois sur la réforme de la facturation électronique et annonce ses engagements envers ses clients et toute la communauté française d'Odoo d'implémenter cette réforme en opensource au sein de l'Odoo Community Association.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>["5a2fff0065a222020295cb9e", "5a26d2dc65a22202029545a4"], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"fr"}, {"_id"=>"664cc719e3952704e79f41f7", "_slug"=>"bicycode", "_visible"=>true, "_position"=>100.0, "content_type_slug"=>"posts", "created_at"=>"2024-05-21T16:08:57.673Z", "updated_at"=>"2024-07-02T15:35:28.464Z", "_label"=>"Bicycode", "title"=>"Bicycode", "posted_at"=>"2024-05-21T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Dans le monde du cycle, le [bicycode](https://fr.wikipedia.org/wiki/Bicycode) est un code d’identification unique apposé sur les cadres des vélos afin d’éviter le recel et donc le vol. C’est une preuve pour le propriétaire pour réclamer la restitution du cycle. C’est devenue une obligation pour les vendeurs d’inscrire chaque vélo vendu sur le fichier national unique des cycles identifiés ([FNUCI](https://www.ecologie.gouv.fr/identification-des-cycles)). Les fabricants peuvent également graver les vélos en usine.\r\n\r\nPour le compte d’un de nos clients, nous avons créé des modules pour gérer ces bicycodes dans odoo.\r\n\r\n\r\n### Obtention d’un code\r\n\r\nLe code à inscrire est généré par un tier, pour ce client il s’agit d’ocode. Pour le moment, les codes sont généré à l’avance et en masse puis importé en via un import de fichier csv.\r\n\r\n### Fabrication\r\n\r\nLors d’une des dernières étapes d’assemblage du vélo, le code est gravé sur le cadre puis enregistré au FNUCI à l’aide d’une application métier. Pour des raisons de praticité logistique, il est également collé sur le carton d’emballage du vélo.\r\n\r\n### A l’expédition\r\n\r\n\r\nAu moment de la préparation de commande, le bicycode est scanné sur le carton et ainsi associé à une commande.\r\n\r\nDes vérifications sont effectuées automatiquement afin de s’assurer que certains articles ne quittent pas l’entrepôt sans bicycode.\r\n\r\n### En boutique\r\n\r\nCharge ensuite au vélociste d’enregistrer les coordonnées de l’acheteur final au moment de la vente du vélo.\r\n\r\n### Service après-vente\r\n\r\nDans odoo, à partir d’un bicycode donné, il est possible de remonter à la facture et ainsi assurer une suivi de la garantie constructeur.\r\n\r\n\r\n\r\nDes modules additionnels permettent transmettre ce bicycode lors des appels API pour des services tels que l’échange de documents (EDI) et l’e-Commerce ainsi que le support technique.\r\n\r\n### Feuille de route\r\n\r\nPour le moment ces modules sont disponibles pour Odoo version 14, prochainement ils le seront également pour Odoo v16.\r\n\r\nDes fonctionnalités supplémentaires vont être ajoutées en fonction des besoins de nos clients.\r\n\r\nCes modules sont publiés sous licence libre sur un de nos dépôts : [github/akretion/vertical-bike](https://github.com/akretion/vertical-bike).\r\n\r\n", "thumbnail"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a22202029544c9/664cc719e3952704e79f41f7/files/etiquettev2-20deg.jpg", "filename"=>"etiquettev2-20deg.jpg", "size"=>128144.0, "updated_at"=>"2024-07-02T15:35:28.464Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-07-02T15:35:28.464Z"}, "summary"=>"Publication d'un module de marquage (bicycodes) pour la filière du véloAkretion est fière de présenter son nouveau module account_move_export qui, comme son nom l'indique, permet d'export des écritures comptables. Ce nouveau module s'adresse aux sociétés qui ont fait le choix de ne pas tenir leur comptabilité dans Odoo. Il s'agit souvent de petites entreprises qui confient la tenue de leur comptabilité à expert-comptable par manque de compétences en interne. Pour éviter au cabinet comptable de saisir la totalité des écritures comptables, la société exporte certains journaux (le journal de vente, souvent aussi le journal d'achat, etc.) générés par Odoo sous forme de fichier pour que le cabinet comptable puisse les importer dans son logiciel comptable et éviter une fastidieuse re-saisie.
Jusqu'à présent, quand une société avait besoin de mettre en place un export d'écritures comptables, nous avions 3 solutions possibles :
Avec l'arrivée du multi-axe analytique dans Odoo version 16, il est devenu encore plus complexe pour un utilisateur non expert d'exporter les écritures comptables avec l'analytique par la fonction native d'export d'Odoo. Par ailleurs, quand la solution 3 était retenue, nous étions amenés à développer du code très similaire d'un projet à l'autre : la seule différence résidait dans quelques mini-détails de format de fichier.
Nous avons donc décidé que cette fonctionnalité d'export d'écritures comptables, même si elle peut sembler simple et d'importance secondaire, méritait un vrai module communautaire bien conçu.
Etant donné que ce module s'adresse aux sociétés qui exportent leurs écritures vers un cabinet comptable, un des enjeux essentiel est d'exporter toutes les écritures depuis le dernier export, sans oublier aucune écriture et sans exporter une seconde fois une écriture qui aurait déjà été exportée. Comme cette fonctionnalité est essentielle pour les utilisateurs du module, nous avons décidé que l'export d'écriture comptable serait un objet stocké dans Odoo et que cet objet serait lié à toutes les écritures contenues dans cet export (pour les développeurs : champ many2one de account.move vers le nouvel objet account.move.export créé par le module). Ce modèle de donnée permet de garantir qu'une pièce comptable est exportée une seule fois. Et cela permet à Odoo de restreindre les nouveaux exports aux écritures non encore exportées.
Le module permet d'exporter les écritures comptables :
Par ailleurs, l'utilisateur pourra choisir d'exporter ou non l'analytique. En v16, il pourra choisir d'exporter tous les axes ou seulement certains axes.
Dans le module de base, deux formats génériques ont été implémentés :
Si vous souhaitez modifier les formats génériques, comme par exemple changer l'ordre des colonnes, vous pouvez le faire très facilement en héritant la méthode _prepare_columns() de l'objet account.move.export.
Ce module a été conçu pour permettre d'ajouter des formats supplémentaires très facilement. Akretion publiera prochainement un module communautaire, qui dépend du module account_move_export, ajoutant le support du format natif du logiciel Quadratus.
Cerise sur le gâteau : ce module est entièrement traduit en français. Il est disponible pour Odoo 14.0 et 16.0 sur https://github.com/akretion/account-move-export
Nous sommes à l'écoute de vos retours d'expériences et de vos suggestions pour améliorer ce module. Nous espérons de cette contribution vous sera utile !
Présentation et démonstration vidéo du nouveau module d'Akretion pour exporter les écritures comptables d'Odoo vers un autre logiciel. Ce module est conçu pour les entreprises qui ne tiennent pas leur comptabilité dans Odoo et qui doivent exporter règulièrement les écritures comptables d'Odoo vers un autre logiciel.
In an ever-evolving online commerce domain, companies are constantly seeking to enhance the customer experience on their online stores while offering increasingly more services. An innovative approach gaining popularity is headless e-commerce, combined with an ERP system, which allows greater flexibility in e-commerce developments.
Ne manquez pas la prochaine soirée Odoo à Lyon, le jeudi 21 mars 2024 à 19h !
Au programme de cette soirée conviviale :
Le point fort de la soirée : une présentation du point de vente d'Odoo par Alexis de Lattre !
Découvrez les secrets du point de vente dernière génération :
RDV le 21 mars à 19h au 27 rue Henri Rolland à Villeurbanne (à Charpennes) pour une soirée riche en découvertes et en échanges !
N'oubliez pas de vous inscrire : https://www.eventbrite.fr/e/billets-apero-meetup-odoo-a-lyon-opensource-849320449327?aff=oddtdtcreat...
#Odoo #OCA #Lyon #ERP #Community #Meetup
Informations pratiques :
Nous vous attendons nombreux !
Rejoignez-nous pour notre prochain Meetup Odoo à Lyon, jeudi 21 mars 2024 ! Au programme, présentation du POS (Point de vente) d'Odoo et du matériel de caisse, échanges et networking !
L'Agence pour l'Informatique Financière de l'Etat (AIFE), qui a notamment la charge de l'exploitation de la plateforme de facturation électronique de l'État dénommée Chorus Pro, a annoncé un changement dans les URLs utilisées pour l'API Chorus Pro. Les détails techniques de ce changement sont expliqués sur la page ci-dessous :
https://developer.aife.economie.gouv.fr/index.php?option=com_content&view=article&id=13
L'AIFE précise dans son annonce que les anciennes URLs ne seront plus joignables à partir du 30 septembre 2023.
Akretion a fait la mise à jour du module l10n_fr_chorus_account pour utiliser les nouvelles URLs pour l'API Chorus. Cette mise à jour a été fait sur toutes les versions d'Odoo de 10.0 à 16.0 :
Maintenant que la mise à jour a été publiée, il faut que toutes les entreprises qui utilisent le module OCA pour accéder à l'API de Chorus Pro déploient la mise à jour sur leur serveur Odoo d'ici au 30 septembre 2023.
L'AIFE a annoncé que les URL PISTE historiques en aife.economie.gouv.fr seront décommissionnées le 30 septembre 2023 et impose d'utiliser les URLs en piste.gouv.fr. Akretion France a publié la mise à jour du module OCA pour l'API Chorus Pro pour toutes les versions d'Odoo où cette fonctionnalité est disponible. Toutes les entreprises qui utilisent l'API Chorus Pro doivent déployer la mise à jour sur leur serveur Odoo.
Le jeudi 21 septembre 2023 (19h-21h30) aura lieu le premier des Apéros Odoo (OCA) de Lyon, organisés par Akretion.
Akretion,\r\n travaille depuis dix ans sur les modules communautaires d'Odoo et nous \r\nsouhaiterions faire vivre une communauté de passionnés d'Odoo qui \r\nhabitent et travaillent à Lyon et dans ses environs.
Notre entreprise souhaite donc organiser une rencontre trimestrielle,\r\n autour d'un verre, pour échanger sur les sujets fonctionnels et \r\ntechniques qui touchent au développement et à l'utilisation d'Odoo.
Pour quel public ?
Les\r\n rencontres sont à destination aussi bien d'intégrateurs qui font déjà \r\npartie de l'OCA (Odoo Community Association), mais également de ceux qui\r\n voudraient commencer à contribuer, des profils fonctionnels, des \r\nutilisateurs de l'ERP, des étudiants ou simplement des curieux qui \r\nvoudraient en savoir plus sur le logiciel et ces fonctionnalités.
Quand et où ?
RDV une fois par trimestre, dans les locaux d'Akretion à Charpennes , 27 rue Henri Rolland, Villeurbanne.
La première date étant prévue le jeudi 21 septembre 2023, de 19h-21h30.
Comment participer ?
Inscrivez-vous gratuitement sur le site d'Eventbrite :
https://www.eventbrite.com/e/billets-apero-odoo-lyon-opensource-668200615027
Le jeudi 21 septembre 2023 (19h-21h30) aura lieu le premier des Apéros Odoo (OCA) de Lyon, organisés par Akretion.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>["5a26d2dc65a22202029545ad", "5a26d2dc65a22202029545a4"], "author_id"=>"5ff83764f2a076389f9f18f3", "deprecated"=>false, "seo_title"=>"Akretion organise des Apéros Odoo à Lyon", "meta_description"=>"Le jeudi 21 septembre 2023 (19h-21h30) aura lieu le premier des Apéros Odoo (OCA) de Lyon, organisés par Akretion.", "meta_keywords"=>"apéro Odoo Lyon", "force_locale"=>"fr"}, {"_id"=>"64bc45cde39527290fd67b64", "_slug"=>"point-de-vente-odoo-liaison-caisse-lecteur-cb", "_visible"=>true, "_position"=>94.0, "content_type_slug"=>"posts", "created_at"=>"2023-07-22T21:10:37.966Z", "updated_at"=>"2024-07-11T17:28:31.472Z", "_label"=>"Point de vente Odoo : liaison caisse <-> lecteur CB", "title"=>"Point de vente Odoo : liaison caisse <-> lecteur CB", "posted_at"=>"2023-07-22T00:00:00.000Z", "published"=>true, "body"=>"Akretion annonce la disponibilité d'un nouveau module OCA qui implémente la liaison bi-directionnelle sur IP entre l'interface du point de vente d'Odoo et le lecteur CB. Le nom technique de ce nouveau module est l10n_fr_pos_caisse_ap_ip et il est disponible sur le projet Github l10n-france de l'OCA pour Odoo version 14 et version 16. Ce module implémente la version 3 du protocole caisse (anciennement appelé protocole Concert) de l'Association du paiement. En France, la liaison entre la caisse et le lecteur CB est standardisé par l'Association du paiement. Le protocole a d'abord été disponible sur port série et USB ; depuis la version 3 du protocole, il est également disponible sur IP. Il est implémenté par Ingenico, Verifone et d'autres constructeurs de terminaux de paiement pour les terminaux vendus en France.
Quand il est utilisé sur IP, le protocole fonctionne par un échange bi-directionnel de chaînes de caractères sur une liaison TCP directe entre la caisse et le lecteur CB. L'échange de caractères se fait directement sur TCP, sans aucun autre protocole au dessus de TCP.
Avantage : simplicité.
Inconvénient : le code Javascript d'un navigateur Web ne peut pas ouvrir une socket TCP \"brute\" (sauf à utiliser des APIs spécifique à un navigateur Web particulier). Il n'est donc pas possible d'implémenter ce protocole directement dans le code Javascript du point de vente d'Odoo. Dans l'implémentation actuelle, le code Javascript d'Odoo appelle une méthode du serveur Odoo et c'est le serveur Odoo qui ouvre la socket TCP vers le lecteur CB. Si le serveur Odoo est hébergé sur Internet, cela implique la mise en place d'une redirection de port TCP vers le lecteur CB. Il est conseillé de restreindre cette redirection de port par IP source, en la limitant à l'IP du serveur Odoo.
Avec l'implémentation qui a été réalisée, la liaison est bi-directionnelle :
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/64bc4509e39527290fd67b60/l10n_fr_pos_caisse_ap_ip-setup.png\" "\\"l10n_fr_pos_caisse_ap_ip-...\\"")
Une fois la configuration terminée, vous pouvez démarrer la session de caisse. La mini-vidéo ci-dessous montre l'utilisation de la liaison caisse <-> lecteur CB sur Odoo v14, sur un paiement réel que j'ai réalisé à l'abbaye de Randol le 15 juillet 2023.
\r\n\r\nPour pouvoir tester ce module Odoo ou développer sur ce module, il faut disposer d'un vrai lecteur CB et réaliser de vraies transactions... ce complique sérieusement les choses ! Pour que cela ne soit pas un obstacle, Rémi de Lattre a développé un simulateur de lecteur CB en python qui émule le protocole caisse AP sur IP. Il est disponible sous licence GPL sur le projet Github caisse-ap-ip. Le module Odoo l10n_fr_pos_caisse_ap_ip a été développé en utilisant ce simulateur, et il a marché du premier coup lors de sa mise en production avec un lecteur CB Ingenico... preuve que le simulateur est fidèle à la réalité !
Le développement de ce module Odoo a été co-financé par Akretion France et Camptocamp.
Akretion publie le module l10n_fr_pos_caisse_ap_ip qui implémente la liaison bi-directionnelle sur IP entre l'interface de point de vente d'Odoo et le lecteur CB. Avantage : le montant à payer est automatiquement transmis depuis Odoo vers le lecteur CB ; si le paiement passe sur le lecteur CB, la vente est automatiquement validée dans Odoo.
Suite à la mise à jour du serveur Odoo utilisé en interne à Akretion France de la version 12 à la version 14, nous étions impatients de pouvoir commencer à utiliser notre nouveau module de déclaration de TVA. Ce nouveau module l10n_fr_account_vat_return, annoncé le 2 décembre 2021 dans ce billet de blog, est maintenant disponible dans la branche principale du projet de localisation française de l'OCA pour Odoo version 14. Pour rappel, ce module permet :
Pour notre CA3 du mois de Septembre 2022, nous avons donc utilisé notre nouveau module de déclaration de TVA. La télétransmission de la CA3 depuis Odoo en 1 clic a parfaitement fonctionné :
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/6351b6acf2a07677e6e4fd49/tva_teletrans_akretion.png\" "\\"tva_teletrans_akretion.png\\"")
Et une demi-heure après avoir réalisé la télétransmission depuis Odoo, nous avons reçu de Teledec l'accusé de réception de la DGFIP :
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/6351bf29f2a07679606de913/tva_teletrans_akretion-AR.png\" "\\"tva_teletrans_akretion-AR...\\"")
En me connectant sur notre espace professionnel sur impots.gouv.fr, j'ai pu constater que notre CA3 de Septembre 2022 était bien déclarée et conforme aux données envoyées par Odoo.
Akretion est maintenant prête à généraliser le déploiement de ce module de déclaration de TVA française avec télétransmission à tous ses clients utilisant Odoo version 14 (ou supérieure) et ayant fait le choix de tenir leur comptabilité dans Odoo.
Akretion France a télé-transmis sa déclaration de TVA pour la première fois, en utilisant le nouveau module opensource de déclaration de TVA.
Suite à la publication du nouveau module de déclaration de TVA française avec télétransmission pour Odoo v14 en Décembre 2021, le module a été déployé chez plusieurs clients pilotes qui nous ont fait part de leurs remarques et souhaits d'amélioration. Pendant cette phase qui a duré plusieurs mois, le module de TVA a reçu plusieurs correctifs et améliorations importantes.
Les modifications les plus significatives sont les suivantes :\r\n
Après plusieurs mois d'utilisation en beta-test, le module de déclaration de TVA française avec télétransmission pour Odoo v14 est maintenant prêt pour une large diffusion. Il a bénéficié de plusieurs améliorations importantes et a été a été traduit en français.
Akretion est fier d'annoncer la publication d'un nouveau module Odoo dénommé account_cash_deposit permettant de gérer les remises d'espèces en banque, ainsi que les commandes d'espèces auprès de la banque. Ce nouveau module sera utile pour les sociétés qui disposent d'une caisse, en particulier les sociétés qui exploitent une boutique physique et qui doivent régulièrement déposer les espèces à la banque.
Ce module permet de formaliser le processus de remise d'espèces à la banque en déclarant les billets et les rouleaux de pièces qui composent la remise et le compte bancaire à créditer. Il permet ensuite d'imprimer un rapport de remise d'espèces et de générer une écriture comptable entre le compte de caisse (531) et le compte de virements internes (580).
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/62211571f2a076264fdfd568/cash_deposit1.gif\" "\\"cash_deposit1.gif\\"")
Il fonctionne de façon très similaire pour les commandes d'espèces à la banque : il permet de formaliser les quantités de billets et de rouleaux de pièces commandés et le compte sur lequel la banque doit prélever l'argent. L'utilisateur peut ensuite confirmer la commande et imprimer un rapport PDF de commande d'espèces prêt à être envoyé à la banque. Enfin, une fois les espèces reçues, Odoo va générer une écriture comptable entre le compte de virements internes (580) et le compte de caisse (531).
Ce nouveau module est disponible ici pour Odoo version 14.0. Il a été traduit en français. Si vous avez besoin de ce module sur une autre version d'Odoo, nous pouvons réaliser pour vous le portage du module sur la version d'Odoo que vous utilisez.
Akretion annonce la publication d'un nouveau module Odoo dénommé account_cash_deposit permettant de gérer les remises d'espèces en banque, ainsi que les commandes d'espèces auprès de la banque.
In an ERP project, we are regularly confronted to the problem of duplicate entries in the list of partners (customers and suppliers). Having duplicate entries in the list of customers or suppliers will always lead to problems. The first consequence is that users are confused when they need to select the partner, for a new quotation for example. But the most important consequence of this duplication is that overdue invoice reminders are not complete: the invoice reminders that you are sending by email to your customer don't have the full list of its overdue invoices!
Odoo v14 has great tools to detect those duplicate partners and merge them when a duplicate entry is found and confirmed.
How can you identify duplicate partners? For companies, the most reliable way is to use the VAT number or the national company identification number (SIREN in France). It's important to educate your users to always enter the VAT number or SIREN when they create a new company partner form.
In the base module from the official addons, a warning banner is displayed when another partner already exists with the same VAT number:
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/61ba71a2f2a0762069dca883/partner_vat_duplicate_warn.png\" "\\"partner_vat_duplicate_war...\\"")
By default, this yellow warning banner is only displayed when you are in Edit mode. If you use Akretion's base_usability module, the warning banner is also displayed when you are not in Edit mode.
In the OCA module l10n_fr_siret, I implemented the same warning banner when two partners have the same SIREN:
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/61ba72c9f2a07603c668d997/partner_siren_duplicate_warn.png\" "\\"partner_siren_duplicate_w...\\"")
In a B2C business, it's also important to fight against duplicate partners. For individual partners, the best way to identify duplicate partners is to use email addresses or mobile phone numbers.
So I developed a new module partner_email_duplicate_warn that shows a warning when two partners have the same email address (independently from the case, from starting spaces or ending spaces).
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/61ba75c9f2a0762069dca887/partner_email_duplicate_warn.png\" "\\"partner_email_duplicate_w...\\"")
And I also developed the module partner_mobile_duplicate_warn that shows the warning when two partners have the same mobile phone number. This module requires the module phone_validation from the official addons that handle the reformatting of phone numbers to the standard international format such as +33 6 98 76 54 32. When all the phone numbers are properly formatted, it becomes easy to identify duplicate phone numbers.
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/61ba7585f2a07603c668d99d/partner_mobile_duplicate_warn.png\" "\\"partner_mobile_duplicate_...\\"")
With all these modules, you should be able to identify duplicate partners in your Odoo v14 database.
Once you have identified duplicate partners, you will certainly decide to delete one of the 2 partners. But, if both partners have orders, invoices or any other objects attached to it, you will not be able to delete any of them. Odoo v14 has a well-designed merge wizard that will allow you to merge the 2 partners. For that, in the list view of partners, select the 2 partners and click on Action > Merge: Odoo will start the merge wizard on those 2 partners. In the merge wizard, select as Destination contact the partner that has the most complete and up-to-date information (address, phone numbers, emails, contacts, etc). The other partner will be deleted and all the orders, invoices and any other document attached to the other partner will be transferred to the destination partner.
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/61ba7b7bf2a0762069dca895/partner_merge_wizard.png\" "\\"partner_merge_wizard.png\\"")
Learn about the best techniques to identify duplicate partners in Odoo v14 and how to merge them.
Akretion contributed 2 new Odoo modules that show a warning banner on partners and sale orders form view in case of overdue invoices. The yellow banner warns the user about the number of overdue invoices and the total residual amount of these invoices.
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/612a7495f2a0766071497422/sale_order_overdue_invoice_warn.png\" "\\"sale_order_overdue_invoic...\\"")
This new feature is the result of a discussion this morning with a \r\ncustomer of Akretion who is deploying Odoo version 14. Our customer had a simple query: when encoding a new quote or order, he wanted to be alerted if the customer had overdue invoices. After \r\nevaluating different options, I proposed to implement this warning \r\nbanner. The work started immediately after this discussion and the initial idea was improved during the development to also add a banner on the customer form view. These 2 modules named account_invoice_overdue_warn and account_invoice_overdue_warn_sale have been contributed as opensource to the Odoo Community Association (OCA) : they are available for Odoo version 14 in this pull request on Github.
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/612a7502f2a07660a18787ce/partner_overdue_invoice_warn.png\" "\\"partner_overdue_invoice_w...\\"")
We hope that feature will benefit to many companies using Odoo! It is complementary to the overdue invoice reminder module that was published last year that sends emails and letters to customers that have overdue invoices: see our dedicated blog post about this module.
Don't hesistate to contact Akretion if you need a backport of this module to the version of Odoo your are using.
Akretion contributed 2 new Odoo modules that show a warning banner on partners and sale orders in case of overdue invoices. That way, you will never be in a situation where you confirmed an order ignoring that the customer had overdue invoices!
On December 25th 2015, I wrote a blog post to announce a new OCA module to automate the import of PDF invoices in Odoo. The title of this blog post was Akretion's Christmas present for the Odoo community. This module was named account_invoice_import_invoice2data because, to extract the relevant data from the PDF invoice (date, total with tax, total without tax, invoice number, etc.), it used a python library called invoice2data. This module later joined the OCA/edi project on Github. It was released for Odoo v8, and has been ported to higher versions including Odoo v14, the latest version of Odoo. This module is still the main opensource solution to import a simple PDF invoice as vendor bill in Odoo. If you have a structured invoice such as a Factur-X PDF invoice or an UBL invoice, there are specific modules to add support for these formats (account_invoice_import_facturx, account_invoice_import_ubl) that take advantage of the structured data.
At Akretion, we've been using this module for 6 years now and our customers use it too. It works well, but there is one major drawback: when you need to add support for a new vendor, you must write a new template, and this task involves writing regular expressions. In real life, it means that an accountant cannot add support for a new vendor by himself, he needs to ask a software developer to do it. The same thing happens when the layout of the invoices changes: the template often needs to be updated and this requires developer skills.
So far, I considered that investing time to improve this module was not a good investment because all invoices will eventually be available in Factur-X or UBL format in the future, so such a module that imported simple PDF invoices (without any XML file as attachment) would soon be deprecated. I was certainly too optimistic: I have to admit that 99% of the invoices I receive today are still simple PDF invoices.
On July 13th 2021, I made a presentation of my module account_invoice_import_invoice2data to the accountant of a company running on Odoo during an online meeting. The accountant was happy because the module was adressing his needs. Then he told me that he needed to support about 50 suppliers, so I would have to develop up to 50 invoice2data templates. When I hung up the call, I was quite unhappy because I thought: Damn-it, I'll have to develop 50 invoice2data templates: it not difficult... but it's not fun !
I started to wonder how I could avoid this mission to develop 50 invoice2data templates! I started thinking about a new module that would import simple PDF invoices as vendor bills in Odoo with one main requirement: the accountant should be able to add support for a new supplier by himself. No technical skills needed. Fast and easy.
By chance, the day after that online meeting was July 14th, which is the national day in France. My kids were at their scout camp, my wife was on holidays in Normandy and it was a rainy day. So I started developing a new module called account_invoice_import_simple_pdf. I took advantage of my 6 years of experience using the module account_invoice_import_invoice2data and developing invoice2data templates. And I came out with an easy-to-use solution where the accountant can add support for new vendors by himself. And, even for me with my strong experience writting invoice2data templates, it's faster to add support for a new vendor with that new module than writting an invoice2data template! I'm very happy to annonce the release of this new module today: it seems Christmas is in July this year! I hope you will have as much fun using this module than I had developing it... while watching the military parade on the Champs-Élysées! The module is available for Odoo v14 in this pull request.
How does it work? It's quite similar to the invoice2data module. When you import a new simple PDF invoice in Odoo:
\r\n\r\nI made a screencast that showcases the configuration and import of a real invoice of Mooncard, one of my vendors.
\r\n\r\n\r\n\r\nHere are some details about the setup on the partner form. In the Vendor Bill Import tab, you must configure:
\r\n\r\nNote that you should only configure 3 out of the 2 amount fields because Amount Total = Total Untaxed + Total Tax, so with 2 fields Odoo can compute the 3rd one. If the invoice is without VAT, you should only configure the Amount Total field. The Start Date and End Date fields are relevant if you use the OCA module account_invoice_start_end_dates available from the OCA/account-closing project and you want to have the start and end date on the invoice line.
\r\n\r\nFor each field, you must configure an extraction rule such as:
\r\nFor a particular field, you can restrict the scope of the extraction rule by giving a Start String and/or an End String. For example, if you set Total HT as Start String for the field Untaxed Amount and the extraction rule is Min, Odoo will search for the first occurence of Total HT in the raw text extraction and retrieve the minimum amount it finds after that string (in French, \"HT\" is the abbreviation of \"hors taxes\" i.e. \"without taxes\").
\r\n\r\nFor date fields, you can set a specific date format and separator. Let's consider an invoice where the Invoice Date and Due Date are written as 27/07/2021 but the Start Date and End Date are written as July 31, 2021. To support that, configure the date format of the partner with:
\r\nand, on the Start Date and End Date fields:
\r\nAt the bottom of the Vendor Bill Import tab, you have a test section where you can upload a PDF invoice of that partner and test the setup you made: you will get a clear analysis of the partner matching result and the extraction result for each field. It will help you finalize the configuration until you get a configuration which extracts the right values for each field.
\r\n\r\nOnce the configuration is finished, start the import wizard via to the menu Invoicing > Vendors > Import Vendor Bill, upload the PDF invoice and... enjoy the automatic creation of the vendor bill! Check that the vendor bill has been properly created and confirm it. Note that the PDF is automatically attached to the invoice.
\r\n\r\nDon't hesitate to contact Akretion is you need to backport this module to the version of Odoo you are using or if you need training or support on the module.
", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-07-11T17:22:46.454Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-07-11T17:22:46.454Z"}, "summary"=>"Discover our new opensouce PDF invoice import module for Odoo: account_invoice_import_simple_pdf. This module supports PDF invoices without XML attachment. With this new module, the accountant can add support for a new vendor by himself easily and rapidly.
Le développement de Pywebdriver continue et de nouvelles fonctionnalités sont ajoutées.
Pywebdriver est un logiciel permettant de remplacer l’IoT Box d’Odoo. En utilisant directement le poste client comme PosBox, cela évite d’ajouter du matériel. Cela permet aussi de limiter la complexité de l’installation car il n’y a pas besoin d’installer toutes les dépendances d’Odoo.
Pour en savoir plus, vous pouvez lire ce premier billet de blog: https://akretion.com/en/blog/pywebdriver
La nouveauté la plus notable est la compatibilité avec Windows. Il est maintenant possible d’utiliser simplement Pywebdriver sur Windows 10.En partant d'une machine Windows, vous pouvez maintenant vous passer de tout matériel superflu (PosBox, Raspberry Pi) et profiter pleinement de toutes les fonctionnalités de Pywebdriver.
Les fonctions suivantes ont été testées et sont fonctionnelles sur Windows 10:
La gestion des impressions a nécessité l’écriture d’un nouveau pilote spécifique car CUPS, utilisé pour les installations Mac et Linux, ne fonctionne pas sur Windows.
Les impressions ont été testées sur les appareils suivants:
En plus de la compatibilité Windows, de nombreuses petites améliorations de pywebdriver ont été réalisées :
Dans le futur, nous allons continuer d’améliorer Pywebdriver. Un travail pour le proposer à l’OCA a notamment été engagé ce qui permettra de le faire connaître plus largement. un travail est en cours pour permettre la communicaton bi-directionnelle avec le lecteur CB, ce qui permettra de tirer parti des améliorations d’Odoo v13+
Un grand merci à tous les contributeurs de Pywebdriver, notamment Acsone et GRAP.
Le développement de Pywebdriver se poursuit afin d'étendre les fonctionnalités et la compatibilité avec Windows 10
\"Brexit means Brexit !\" ; cette phase désormais célèbre de Theresa May s'est finalement traduite dans les faits le 1er Janvier 2021 avec le départ du Royaume Uni de l'Union Européenne. Cet article a pour objectif d'expliquer l'impact sur la DEB, la DES, la comptabilité, ainsi que l'impact dans Odoo.
A première vue, tout semble simple : avec le départ du Royaume Uni de l'Union Européenne le 1er Janvier 2021, les ventes B2B sans TVA pour des sociétés basés au Royaume Uni n'ont plus besoin d'être déclarées dans la DEB ni dans la DES à partir du mois de Janvier 2021 (dont la déclaration doit être déposée au plus tard le 11 Février 2021, cf le calendrier de la DEB/DES).
Mais, quand on creuse le sujet... tout se complique ! Vous avez certainement entendu parler de l'épineux problème de l'Irlande du Nord qui été un point délicat lors des négociations du Brexit, car les anglais ne voulaient pas le retour d'une frontière physique entre l'Irlande du Nord et l'Irlande du Sud. Pour éviter cela, l'accord de retrait a prévu un régime fiscal et douanier très spécial pour l'Irlande du Nord : les dispositions du droit de l'UE en matière de TVA concernant les marchandises continuent de s'appliquer à l'Irlande du Nord après le 1er Janvier 2021 (mais pas pour les prestations de service). Cela implique qu'il faut différencier les ventes à destination de la Grande Bretagne (i.e. le Royaume Uni sans l'Irlande du Nord) des ventes à destination de l'Irlande du Nord.
Concrètement, dans le cas d'une vente B2B sans TVA :
| Grande-Bretagne | Irlande du Nord | |
|---|---|---|
| DEB | non | oui |
| DES | non | non |
| Case CA3 | 04 | 06 |
| Vérifier le numéro de TVA du client | non | oui, et il doit commencer par XI |
| Formalités douanières | oui | non |
Les sociétés basées en Irlande du Nord se sont vues attribuer un nouveau numéro de TVA commençant par XI (en remplacement de leur ancien numéro de TVA qui commençait par GB). Le service VIES de vérification des numéros de TVA européens a été mis à jour et permet de vérifier ces nouveaux numéros de TVA commençant par XI.
Dans le cas d'un achat de marchandises sans TVA auprès d'une entreprise basée en Irlande du Nord, il faudra pratiquer l'auto-liquidation de la TVA, comme pour les autres pays européens.
Les impacts du Brexit sur la DEB, la DES et la comptabilité. Explications sur l'implémentation dans Odoo.
Akretion a publié ce jour un nouveau module Odoo pour les relances client. Ce module permet de générer des relances par e-mail, par lettre et de suivre les relances téléphoniques.
Ce nouveau module de relance est axé sur plusieurs idées fortes :
Vous pouvez consulter le cahier des charges pour le développement de ce module, ce qui vous permettra de comprendre certains choix de conception.
Ce module est publié sous licence libre AGPL. Son nom technique est account_invoice_overdue_reminder. Il est publié sur le projet Github OCA/credit-control (pull request 69 pour Odoo v12 et pull request 77 pour Odoo v10). Nous vous invitons à lire le README du module, qui explique un certain nombre de règles de fonctionnement du module. Si vous êtes intéressé par ce module de relance et qu'il n'est pas encore disponible pour la version d'Odoo que vous utilisez, Akretion peut vous proposer ses services pour porter ce module vers votre version d'Odoo.
Akretion a publié un nouveau module de relance client pour Odoo, qui permet de faire des relances par mail, lettre et téléphone, en gardant un contrôle très fin sur ce qui est envoyé au client. L'interface a été conçue pour être facile, pratique et rapide.
Yousign est une entreprise française qui propose un service en ligne de signature électronique conforme à la norme européenne eIDAS. Avec Yousign, il est possible de signer tout type de document (devis, contrat commercial, contrat de travail, etc.) sans papier ni stylo : tout se déroule en ligne, depuis la lecture du document à signer jusqu'à la signature avec l'envoi d'un code de confirmation par SMS ou e-mail.
Le connecteur Odoo-Yousign, initialement développé par Akretion en Février 2018 grâce au financement d'un de ses clients, permet d'initier une requête de signature depuis Odoo à partir d'un modèle, un peu à la manière d'un modèle de mail. Il permet ensuite de suivre l'avancement du process de signature et de déclencher des actions dans Odoo dès que le document est signé par l'ensemble des signataires. Enfin, il permet d'archiver dans Odoo le document signé.
Ce connecteur prend la forme d'un module Odoo opensource dénommé yousign_connector disponible sur le projet Github dédié. Ce module est accompagné du module yousign_sale qui fourni un modèle de signature basé sur les devis client ; ce module a aussi vocation à servir d'exemple pour ceux qui souhaiteraient définir un modèle de signature basé sur un autre objet Odoo.
Depuis quelques jours, le connecteur Odoo-Yousign supporte le nouvelle API de Yousign, ce qui permet d'accéder aux nouvelles fonctionnalités proposées par Yousign, tels que la définition d'un ordre des signataires, la possibilité de refuser la signature en indiquant une raison ou encore la définition d'une relance automatique des signataires.
Si vous êtes intéressé par ce connecteur Odoo-Yousign et que le module n'est pas encore disponible pour la version d'Odoo que vous utilisez, Akretion peut vous proposer ses services pour porter ce module vers votre version d'Odoo.
Le connecteur Odoo-Yousign supporte désormais le nouvelle API de Yousign, ce qui permet de bénéficier des nouvelles fonctionnalités proposées par Yousign.
Akretion est l'auteur d'une librairie Python pour Factur-X dont l'une des fonctionnalités est de générer une facture Factur-X à partir d'une facture PDF traditionnelle et d'un fichier XML au format CrossIndustryInvoice. Ainsi, les logiciels écrits en Python - Odoo par exemple - peuvent générer une facture Factur-X très facilement en une seule ligne de code. En suivant cet exemple, des librairies Factur-X sont apparues dans d'autres langages de programmation, notamment PHP, Java, etc...
Mais certains langages de programmation ne disposent pas encore d'une librairie native pour Factur-X. Devant ce constat et dans le but d'aider à l'adoption de la norme Factur-X par tous les éditeurs de logiciels, Akretion a développé un webservice permettant, en une seule requête HTTP, de générer une facture PDF Factur-X à partir d'une facture PDF traditionnelle et d'un fichier XML. Ainsi, les logiciels développés dans des langages de programmation pour lesquels il n'existe pas encore de librairie pour Factur-X disposent maintenant d'une solution simple et efficace pour générer des factures Factur-X. Mauvaise nouvelle : à partir de maintenant, il n'y a plus d'excuse pour ne pas générer des factures au format Factur-X !
Concrètement, il faut envoyer une requête HTTP POST de type multipart/form-data contenant la facture PDF, le fichier XML et les éventuelles pièces jointes additionnelles. La réponse contient la facture PDF au format Factur-X. Tous les profils de la norme Factur-X sont supportés. Ce webservice est fourni directement avec notre librairie Python factur-x (cf fichier bin/facturx-webservice) ; il utilise la librairie Flask.
Ce webservice a été déployé à des fins de test sur un serveur du FNFE-MPE. Pour l'essayer, vous pouvez utiliser l'outil curl qui est un client HTTP en ligne de commande. Voici un exemple d'utilisation du webservice :
\r\n\r\ncurl -X POST -F 'pdf=@facture_pdfa.pdf' -F 'xml=@factur-x.xml' -F 'attachment1=@pv_recette.pdf' -o facture_fx.pdf https://ws.fnfe-mpe.org/generate_facturxVous trouverez ci-dessous un schéma représentant le déploiement de ce webservice dans un environnement de production :
\r\n\r\n![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5e49c93c9730597d310177aa/archi_webservice.jpg\" "\\"archi_webservice.jpg\\"")
Akretion a développé un webservice pour générer des factures au format Factur-X. Ce webservice offre une solution pour générer des factures Factur-X à tous les logiciels qui n'ont pas encore de librairie pour Factur-X dans leur langage de programmation.
Akretion annonce aujourd'hui la publication d'un nouveau module Odoo opensource permettant de générer la DAS2, aussi appelée déclaration d'honoraires, à partir des informations comptables disponibles dans Odoo et du paramétrage des fournisseurs concernés. Ce module supporte la génération d'un fichier de déclaration au format TD/bilatéral que vous pourrez déposer sur le site https://teletd.impots.gouv.fr/teletd/connexionEFI.do, ce qui vous évitera une fastidieuse re-saisie d'informations.
La DAS2 est une déclaration fiscale annuelle obligatoire pour toutes les entreprises et associations françaises. Elle porte sur l'année civile précédente, même en cas d'exercice comptable décalé. Elle consiste à déclarer les honoraires, vacations, commissions, courtages, ristournes, jetons de présence, droits d'auteur, droits d'inventeur, avantages en nature et autres indemnités ou remboursements payés au cours de l'année civile précédente à des personnes physiques ou morales, françaises ou étrangères. Il n'est pas nécessaire de déclarer un bénéficiaire pour lequel le montant payé au cours de l'année civile précédente serait inférieur à 1 200 €.
La date limite pour déposer la DAS2 est le 30 Avril pour les sociétés qui clôturent au 31 Décembre, et 90 jours après la clôture de l'exercice pour les autres. Si votre exercice comptable est calé sur l'année civile, vous avez jusqu'au 30 Avril 2020 pour envoyer votre DAS2 2019.
Cette contribution s'inscrit dans la continuité des développements réalisés par Akretion ces dernières années sur la comptabilité d'Odoo pour faire gagner du temps aux comptables et leur éviter au maximum les tâches rébarbatives... et la DAS2 en fait clairement partie !
Akretion tient à remercier ses clients qui ont participé au financement de ce nouveau module.
Le module a été publié sur la localisation française de l'OCA sur Github pour Odoo version 10, cf cette pull request. Le nom technique du module est l10n_fr_das2. Si vous avez besoin de ce module pour une autre version d'Odoo, n'hésitez pas à nous contacter.
![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5e471537973059063c386a97/das2_teled.png\" "\\"das2_teled.png\\"")
Akretion a développé un nouveau module Odoo permettant de générer la DAS2, aussi appelé Déclaration d'honoraires, ainsi que le fichier de déclaration au format TD/bilatéral.
The revolution of electronic invoicing is moving forward, and a new milestone is just a few days away for French companies: starting January 1st 2020, French companies with less than 10 employees are now obliged to send electronic invoices for their public-entity customers via the Chorus Pro plateform.
Chorus Pro supports several electronic invoicing formats. At Akretion, we think that Factur-X is the most suitable format for SMBs. So we want to allow all companies to generate Factur-X invoices including companies that generate their invoices in a spreadsheet, and not only companies running Odoo or another modern ERP software. Thanks to our new LibreOffice extension, it is now possible to generate a Factur-X invoices with LibreOffice Calc.
This LibreOffice extension is:
You can download it from Github.
Akretion is proud to announce the release of its LibreOffice extension to generate Factur-X invoice with LibreOffice Calc. A useful feature for small companies that don't have an ERP and want to adopt Factur-X.
Akretion participe au Hackathon Factur-X organisé par le FNFE-MPE à Paris le 24-25 Janvier 2019. Pendant ces deux journées, les participants pourront travailler sur l'implémentation de la norme Factur-X dans leur logiciel, assisté par des experts de la norme, bénéficier du retour d'expérience de développeurs qui ont déjà implémenté Factur-X dans leur logiciel et échanger avec la communauté Factur-X.
Akretion participe au Hackathon Factur-X organisé par le FNFE-MPE à Paris le 24-25 Janvier 2019.
Sébastien Beau did a presentation of Shopinvader during a short meeting at OCA Days 2018 in Belgium.
\r\nThanks everyone for the great feedback you gave.
\r\n![\"undefined\"](\"https://cdn-fr.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5b02e5b3b89e760219aeab28/shopinvader.png\" "\\"shopinvader.png\\"")
Presentation slideshow
Direct link : docs.google.com/presentation
Akretion recently added one important feature to the Py3o reporting engine for Odoo. Py3o is a reporting engine for Odoo based on Libreoffice. It is part of the reporting-engine project of the Odoo Community Association (OCA). It is composed of 2 modules : report_py3o and report_py3o_fusion_server.
In Libreoffice Writer, when you export a document to PDF via the menu File > Export As > Export as PDF, you get a dialog box with a lot of options for the generation of the PDF:
![\"undefined\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5b76da15b89e7601d7611f6e/libreoffice_pdf_export_options.png\" "\\"libreoffice_pdf_export_op...\\"")
With our contribution on the module report_py3o_fusion_server for Odoo v10, all these options are now available in Odoo, with similar names and layout:
![\"undefined\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5b76dc00b89e7601d7611f70/py3o_pdf_export_options.png\" "\\"py3o_pdf_export_options.png\\"")
So, by adding one technical feature to the Py3o reporting engine, we added a lot of new features to Odoo:
If you already use Py3o on Odoo v10 and you want to benefit from this new feature, you need to update all the Py3o Python librairies that are installed on your system, update your code of OCA/reporting-engine and reload the module report_py3o_fusion_server. In Odoo, you will then see a new menu entry Settings > Technical > Reports > Py3o > Py3o PDF Export Options where you will be able to create several sets of PDF export options. One set of PDF export options can be associated with a report or with a Py3o server (in this case, it will apply on all the reports that are handled by this Py3o server).
At Akretion, we already deployed this new version of Py3o on several Odoo v10 servers in production. Our main use-case is to generate PDF/A documents for invoices, because, to have a fully compliant Factur-X invoice, the invoice must be in PDF/A format.
More technical information about this contribution:
Akretion contributed support for PDF export options on the Py3o reporting engine for Odoo. So Odoo can now generate PDF forms, watermarked PDF, password-protected PDF, PDF/A, etc.
Akretion made a presentation about our experience on the implementation of the Factur-X e-invoicing standard in Odoo at the FNFE meeting on September 15th 2017 in Paris.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"Akretion talks about Factur-X implementation experience at FNFE meeting", "meta_description"=>"Akretion talks about implementing the Factur-X standard in Odoo during the FNFE meeting in Paris", "meta_keywords"=>"FNFE, Facture-x standard, odoo, implementation, FNFE meeting, invoice", "force_locale"=>nil}, {"_id"=>"5a2ec52565a2220202959f18", "_slug"=>"akretion-publishes-an-opensource-factur-x-python-library", "_visible"=>true, "_position"=>36.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:25.669Z", "updated_at"=>"2018-08-17T14:38:11.406Z", "_label"=>"Akretion publishes an opensource Factur-X Python library", "title"=>"Akretion publishes an opensource Factur-X Python library", "posted_at"=>"2017-09-14T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"On July 28th 2017, Akretion [announced](http://www.akretion.com/fr/blog/odoo-first-erp-to-generate-factur-x-invoices) the support of the generation of Factur-X invoices in Odoo, only 3 weeks after the publication of the beta version of the Factur-X standard. This was the first implementation of the Factur-X standard in an ERP.\r\n\r\nFactur-X is the e-invoicing standard for France and Germany. It is published by the [FNFE-MPE](http://fnfe-mpe.org/factur-x/) (Forum National de la Facture Electronique et des Marchés Publics Electroniques) and its German counterpart [FeRD](http://www.ferd-net.de/) (Forum elektronische Rechnung Deutschland). A Factur-X invoice is a PDF invoice with an embedded XML file in *Cross Industry Invoice* format. The embedded XML file is the machine-readable equivalent of the printable invoice.\r\n\r\nAt Akretion, we are very enthousiastic about the new possibilities allowed by electronic invoices. We would love to see this standard implemented as widely as possible. In particular, we would love to receive Factur-X invoices from our suppliers, so that we will be able to import them in our ERP automatically, without any manual work ! In order to boost the adoption of this new standard by French and German companies, Akretion is proud to publish today an opensource Python library called **factur-x**. This library will make it very easy for other Python invoicing software to generate Factur-X invoices. In one single API call, this library is able to generate a Factur-X PDF invoice from a regular PDF invoice and a Factur-X XML file. It also has other interesting features such as validating a Factur-X XML file against the official Factur-X XML Schema Definition ([XSD](https://en.wikipedia.org/wiki/XML_schema)), extracting the XML file from a Factur-X PDF invoice, etc.\r\n\r\nIn order to have the widest possible adoption of this Factur-X library, we decided to publish it under the [BSD licence](https://en.wikipedia.org/wiki/BSD_licenses), which is one of the most permissive [OSI-approved](https://opensource.org/licenses) licence. This licence allows the use of the Factur-X library in opensource and proprietary software without restriction.\r\n\r\nThis library is available on [pypi](https://pypi.python.org/pypi/factur-x), the main repository for opensource Python libraries. The source code is hosted on Akretion's [Github repository](https://github.com/akretion/factur-x). The Odoo modules **account\\_invoice\\_factur-x** which generate Factur-X invoices and **account\\_invoice\\_import\\_factur-x** which imports Factur-X invoices are the first to use this library (they are available [here](https://github.com/OCA/edi/pull/22) for Odoo version 10). We hope that other ERP and invoicing software will adopt it very soon !", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-17T14:38:11.406Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-17T14:38:11.406Z"}, "summary"=>"Akretion publishes a Python library for Factur-X, the new e-invoicing standard for France and Germany. This library is available on Pypi under the BSD licence.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"Akretion publishes an opensource Factur-X Python library", "meta_description"=>"Akretion publishes an opensource Factur-X Python library, Factur-X is the e-invoicing standard for France and Germany", "meta_keywords"=>" Factur-X, e-invoicing", "force_locale"=>nil}, {"_id"=>"5a2ec52665a2220202959f1e", "_slug"=>"first-implementation-of-the-factur-x-standard", "_visible"=>true, "_position"=>38.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:26.160Z", "updated_at"=>"2018-08-09T18:31:14.638Z", "_label"=>"First implementation of the Factur-X standard", "title"=>"First implementation of the Factur-X standard", "posted_at"=>"2017-07-28T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"The benefits of electronic invoicing are now well-known: save time by avoiding the manual encoding of supplier invoices by the accounting department, reduce invoice processing delay and therefore payment delay, etc. In France, the administration launched the [Chorus](https://chorus-pro.gouv.fr/) platform on September 2016 and has decided an ambitious [calendar](https://www.economie.gouv.fr/entreprises/marches-publics-facture-electronique) that oblige its suppliers to send electronic invoices via Chorus: January 1st 2017 for large companies, January 1st 2018 for mid-size companies, January 1st 2019 for small companies and January 1st 2020 for micro-companies.\r\n\r\nBut several e-invoicing standards exist and France was missing an \"official\" standard for electronic invoicing. The Forum National de la Facturation Électronique ([FNFE-MPE](http://fnfe-mpe.org/)) and its German counterpart [FeRD](http://www.ferd-net.de/) (Forum elektronische Rechnung Deutschland) have worked together to develop a new standard named **Factur-X**. The [specifications](http://fnfe-mpe.org/factur-x/) of this new standard have been published on July 9th 2017 on the FNFE-MPE website. This standard is an evolution of the German standard named ZUGFeRD initially published on June 2014.\r\n\r\nThe Factur-X standard uses one of the 2 main XML standards to describe an invoice: the UNCEFACT XML standard also called Cross Industry Invoice. But the most important aspect of the Factur-X standard is that this XML file that describe the invoice is embedded inside the PDF file. The PDF/A-3 standard allows to insert a file inside a PDF file, just like you can insert an attachment in an e-mail. So a Factur-X invoice is a regular PDF invoice with an embedded XML file that describe the invoice following the UNCEFACT syntax and the european semantic data model EN 16931.\r\n\r\nWith a PDF invoice that follow the Factur-X standard:\r\n\r\n* the supplier sends the PDF file of the invoice to its customer as usual,\r\n* if the customer has a modern accounting software that supports the Factur-X standard, he will be able to import it in its accounting software and the invoice will be automatically read via the embedded XML file,\r\n* if the customer doesn't have an accounting software that supports the Factur-X standard yet, he will handle the invoice like any regular PDF invoice.\r\n\r\nAkretion announces today the world-wide availability of Odoo modules that enable the generation of Factur-X invoices as free software. Alexis de Lattre, co-founder of Akretion and developer of the Factur-X modules for Odoo declares:\r\n\"*Odoo is the first ERP to support the generation of Factur-X invoices, only 3 weeks after the publication of the specifications of this new standard! Akretion and the Odoo community are proud of this achievement. We know that this is an historic moment: the birth of the Factur-X standard and it's very first implementation to generate invoices from an ERP.*\"\r\n\r\nThis new module is already used in production by [Mooncard](https://www.mooncard.co/), one of the customers of Akretion. Mooncard is a Fintech that proposes an intelligent payment card for corporate expenses. The invoices of Mooncard of july 2017 are Factur-X invoices generated by Odoo. Tristan Leteurtre, co-founder of Mooncard declares: \"*We believe we are the very first French company that has sent Factur-X invoices on a large scale. Our corporate payment card is a great time-saver for our customers because it avoids the manual encoding of expense notes in the accounting software; the Factur-X standard also allows a big time-saving on supplier invoices, that's why we adopted it as soon as possible. We want to pave the way for the adoption of this new standard and boost its adoption.*\"\r\n\r\nFor French readers, here is our [press release](http://public.akretion.com/20170728-communique_presse-Akretion_Odoo_factur-X.pdf) in French.\r\n\r\n**Technical info**\r\n\r\nThe modules that allow the generation of Factur-X invoices are available for Odoo v10 on github under the AGPL licence:\r\n\r\n* module *account\\_invoice\\_factur-x*: [https://github.com/OCA/edi/pull/22/files](https://github.com/OCA/edi/pull/22/files)\r\n* module *l10n\\_fr\\_account\\_invoice\\_factur-x*: [https://github.com/OCA/l10n-france/pull/110/files](https://github.com/OCA/l10n-france/pull/110/files)\r\n\r\nThese modules add support for the generation of Factur-X invoices with the *Comfort* profile, also called the *EN 16931* profile.", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:31:14.638Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:31:14.638Z"}, "summary"=>"Akretion annouces the publication of Odoo modules to generate Factur-X invoices, the new franco-german standard for e-invoicing. Odoo becomes the very first ERP to support Factur-X!
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"First implementation of the Factur-X standard", "meta_description"=>"Akretion announces today the world-wide availability of Odoo modules that enable the generation of Factur-X invoices as free software", "meta_keywords"=>" Factur-X", "force_locale"=>nil}, {"_id"=>"5a2ec52665a2220202959f21", "_slug"=>"akretion-announces-the-odoo-mooncard-connector", "_visible"=>true, "_position"=>39.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:26.434Z", "updated_at"=>"2017-12-12T13:48:01.193Z", "_label"=>"Akretion announces the Odoo-Mooncard connector", "title"=>"Akretion announces the Odoo-Mooncard connector", "posted_at"=>"2016-11-28T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"![\"Odoo-Mooncard](\"http://public.akretion.com/banner_odoo_mooncard_small.jpg\")
Encoding expenses paid by card (restaurant invitations, parking, toll, taxi, ...) in the accounting software of the company has always been a long and painful process. Good news: with Mooncard, a new-generation corporate card solution, Odoo and a smartphone, it is now fast and easy!
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>nil, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a2ec52765a2220202959f2a", "_slug"=>"akretion-adds-support-for-the-import-of-e-fff-invoices-in-odoo", "_visible"=>true, "_position"=>42.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:27.291Z", "updated_at"=>"2018-02-09T15:55:46.958Z", "_label"=>"Akretion adds support for the import of e-fff invoices in Odoo", "title"=>"Akretion adds support for the import of e-fff invoices in Odoo", "posted_at"=>"2016-06-22T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Summary of the previous episode: on March 26th 2016, Akretion announced the support of the generation and import of ZUGFeRD electronic invoices, which is the German standard for electronic invoices. A ZUGFeRD invoice is a PDF invoice with an embedded XML file in Cross Industry Invoice (CII) format. Please read the [previous blog post](http://www.akretion.com/blog/akretion-publishes-zugferd-modules-to-create-and-import-electronic-invoices-with-odoo) for more details and watch the [screencast](http://public.akretion.com/odoo_electronic_invoicing_zugferd.ogv).\r\n\r\nToday, Akretion announces the support of the import of e-fff invoices, which is the Belgian standard for electronic invoices. The technical approach of the [e-fff standard](http://www.e-fff.be/FR/) is diametrically opposed to the technical approach of the ZUGFeRD standard: an e-fff invoice is an XML file (in UBL format) that embeds the PDF invoice, whereas the ZUGFeRD format is a PDF invoice that embeds an XML file (in CII format). So, if a company sends an e-fff invoice to a customer, as they cannot be sure that their customer has a modern accounting software such as [Odoo](https://www.odoo.com/) able to read and import e-fff invoices, they will probably send both the XML invoice in e-fff format and the regular PDF invoice (which means sending an e-mail with 2 attachments). But the benefit is the same: the customer will be able to reliably import this electronic invoice in his accounting software in a few clicks: no more manual encoding of the supplier invoice... accountants should save a lot of time !\r\n\r\nTo get this new feature on your Odoo version 8, you need to install the module **account\\_invoice\\_import\\_ubl**. This module is available on the github project of the [Odoo Community Association (OCA)](https://odoo-community.org/) in [this pull request](https://github.com/OCA/account-invoicing/pull/122). It requires some additional modules that are available in the main 8.0 branch of the [partner-contact](https://github.com/OCA/partner-contact/tree/8.0) OCA project (for the module *base\\_vat\\_sanitized*) and in the [community-data-files](https://github.com/OCA/community-data-files/tree/8.0) OCA project (for the modules that add the UNECE nomenclature on taxes, unit of measures and payment modes).\r\n\r\nOnce the module is installed, in order to be able to import an e-fff invoice of a supplier, you need to:\r\n\r\n* make sure that you have configured the VAT number of that supplier in Odoo,\r\n* on the supplier form, in the *Accounting* tab, create an Invoice Import Configuration (for the parameter *Method for Invoice Line*, select *Multi-line no product* to start)\r\n* in the menu *Accounting > Configuration > Taxes > Taxes*, you should at least configure the purchase VAT taxes that are used by your supplier ; you should set the *UNECE Tax Type* (select *[VAT] Value added tax*) and the UNECE Tax Category (select *[S] Standard rate* for a regular VAT tax).\r\n\r\nThen you can import the e-fff invoice via the menu *Accounting > Suppliers > Import Invoice*: select the XML file corresponding to the e-fff invoice and click on the *Import* button. Odoo will create the draft supplier invoice and will attach both the XML file and the embedded PDF file to this invoice.\r\n\r\nIf you want to test this module but you don't have an e-fff invoice, you can use the e-fff invoice of the automated test suite of the module (download it [here](https://raw.githubusercontent.com/akretion/account-invoicing/8.0-add-pdf-invoice-import/account_invoice_import_ubl/tests/invoices/efff_BE0505890632_160421_Inv_16117778.xml)). If you have a demo database, you can import it immediately because the corresponding supplier and the 21% purchase VAT tax are already created via the demo data of the module.\r\n\r\nWe hope that the Belgian members of the Odoo community will enjoy this contribution of Akretion ! I would like to thank the Belgian member of the Odoo community that sent us some real e-fff invoices to test this development. Don't hesitate to contact Akretion if you are interested by our work on electronic invoicing or if you require some additional development on e-fff invoices.\r\n", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T15:55:46.958Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T15:55:46.958Z"}, "summary"=>"After the support of the import and export of ZUGFeRD invoices, Akretion now adds the support for the import of e-fff invoices, the Belgian format for electronic invoices.
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"Akretion adds support for the import of e-fff invoices in Odoo", "meta_description"=>"After implementation of German standard for electronic invoices ZUGFeRD Akretion announced the support of the generation and import of e-fff invoices, which is the Belgian standard for electronic invoices", "meta_keywords"=>"ZUGFeRD, electronic invoices, Odoo, implementation, import, generation, e-fff invoices", "force_locale"=>"en"}, {"_id"=>"5a2ec52765a2220202959f2d", "_slug"=>"akretion-publishes-opensource-modules-to-create-and-import-electronic-zugferd-invoices-with-odoo", "_visible"=>true, "_position"=>43.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:27.622Z", "updated_at"=>"2018-02-09T15:55:59.256Z", "_label"=>"Akretion publishes opensource modules to create and import electronic ZUGFeRD invoices with Odoo", "title"=>"Akretion publishes opensource modules to create and import electronic ZUGFeRD invoices with Odoo", "posted_at"=>"2016-03-24T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Summary of the [previous episode](http://www.akretion.com/blog/akretions-christmas-present-for-the-odoo-community): on December 25th 2015, Akretion offered a Christmas present to the Odoo accounting community in the form of an opensource Odoo module named *account\\_invoice\\_import*. With this module, the accountant can upload a PDF invoice in Odoo and it will automatically create the supplier invoice with all the needed information : supplier, invoice date, invoice number, untaxed amount, VAT, amount with taxes, etc.\r\n\r\nThis import works with regular PDF invoices by using the [invoice2data](https://github.com/m3nu/invoice2data) Python library, which extracts text from the PDF, finds the appropriate template (the invoice2data library has templates for [many suppliers](https://github.com/m3nu/invoice2data/tree/master/invoice2data/templates) and you can add your own) and then uses regular expressions to grab the relevant information (invoice date, invoice number, amount without taxes, amount with taxes). The advantage of this solution is that it works with all PDF invoices. The drawback is that you have to develop a template in the invoice2data library for every supplier and, when the supplier changes the layout of its PDF invoice, you have to update the template.\r\n\r\nPDF format is great for viewing and printing, but it doesn't provide structured information about the invoice. XML is the most common format for structured information. There are 2 main international standards for XML invoices:\r\n\r\n* [Universal Business Language](http://ubl.xml.org/) (UBL) standardized by the [OASIS](https://www.oasis-open.org/),\r\n* [Cross Industry Invoice](http://tfig.unece.org/contents/cross-industry-invoice-cii.htm) (CII) published by an agency of the United Nations called [UN/CEFACT](http://www.unece.org/cefact).\r\n\r\nIf you receive an invoice in XML format and if your ERP supports the import of that format, you will have a reliable import solution thanks to the structured data provided by the XML format. But, if you send an invoice as an XML file to your customer, you may be afraid that he won't be able to read it... so you may never get paid ! The [ZUGFeRD](http://www.ferd-net.de/front_content.php?idcat=231&changelang=4) standard provides a pragmatic and clever solution to this problem: it defines a way to embed a standard XML file inside the PDF invoice. With the publication of the [PDF/A-3](https://en.wikipedia.org/wiki/PDF/A) standard in 2012 (the corresponding ISO standard is [19005-3:2012](http://www.iso.org/iso/catalogue_detail?csnumber=57229)), you can embed one or several files of any format inside a PDF document (if you use Acrobat Reader, you can view the files embedded in a PDF document by clicking on the paper-clip icon). So a ZUGFeRD invoice is a PDF invoice with an embedded XML file named *ZUGFeRD-invoice.xml* in [Cross Industry Invoice](http://tfig.unece.org/contents/cross-industry-invoice-cii.htm) (CII) format.\r\n\r\nThe ZUGFeRD specifications can be downloaded from the [FeRD](http://www.ferd-net.de/) (Forum elektronische Rechnung Deutschland) website. This standard is based on several international standards:\r\n\r\n* the [Cross Industry Invoice](http://tfig.unece.org/contents/cross-industry-invoice-cii.htm) (CII) format which uses the building blocks of the [Core Components Specification](http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=61433) (ISO 15000-5:2014),\r\n* the codification of units of measure, taxes and payment means defined by the [United Nations Economic Commission for Europe](http://www.unece.org), which has 56 members states in Europe, America and Central Asia according to [Wikipedia](https://en.wikipedia.org/wiki/United_Nations_Economic_Commission_for_Europe) (the other international XML invoice format, UBL, uses the same codification),\r\n* the recommendations of the [Message User Guide](https://www.cen.eu/work/areas/ICT/eBusiness/Pages/WS-eBES.aspx) (MUG) of the [CEN](https://www.cen.eu/), the European standardization organization.\r\n\r\nGermany, the author of the ZUGFeRD standard, encourages its companies to send their invoices in this format. Starting from January 1st 2017, the French administration will only accept electronic invoices from large companies, and this obligation will be extended progressively to all companies until January 1st 2020, following [this calendar](http://www.economie.gouv.fr/vous-orienter/numerique/secteur-public-facture-electronique-obligatoire-en-2017) (in French). In France, the FNFE-MPE (Forum National de la Facture Electronique et des Marchés Publics Electroniques) is coordinating the efforts on the standardization of electronic invoices. According to this [slide show](http://docplayer.fr/3120866-Facture-mixte-collaboration-franco-allemande-pourquoi-comment-cyrille-sautereau-admarel-conseil-fnfe-mpe.html) (in French), France is adopting the same technical approach as ZUGFeRD: standard XML file embedded inside the PDF invoice. This common [press release](http://www.institutionnel.gs1.fr/Communiques-de-presse/La-facturation-electronique-dans-l-agenda-numerique-commun-France-Allemagne) (in French) of FeRD and FNFE shows that France and Germany are working together to adopt a common standard for electronic invoices.\r\n\r\nAkretion has implemented the ZUGFeRD specifications both for the generation of customer invoices (Comfort level) and for the import of supplier invoices (all levels) in Odoo version 8. The generation of ZUGFeRD PDF customer invoices and refunds is provided by the module *account\\_invoice\\_zugferd* for the [Qweb](https://www.odoo.com/documentation/8.0/reference/qweb.html) reporting engine (which is the default reporting engine since Odoo v8). It also works with the [Aeroo](https://github.com/aeroo/aeroo_reports) reporting engine if you apply [this patch](https://people.via.ecp.fr/~alexis/report_aeroo-account_invoice_zugferd.diff). The resulting invoices have been checked by the [ZUGFeRD eInvoice validation portal](https://www.din-zugferd-validation.org) and the validation system confirms that the invoices are fully compliant. The import of ZUGFeRD PDF supplier invoices is provided by the module *account\\_invoice\\_import\\_zugferd*, which is an extension of the *account\\_invoice\\_import* module.\r\n\r\nAll these modules are published by Akretion under the [AGPL](http://www.gnu.org/licenses/agpl-3.0.en.html) licence on the [account-invoicing](https://github.com/OCA/account-invoicing/pull/122) project of the [Odoo Community Association](https://odoo-community.org/) (OCA). They require some data modules that provide the UNECE codification of units of measure, taxes and payment modes available in the [community-data-file](https://github.com/OCA/community-data-files/pull/14) project of the OCA. You can see a demo of these modules in this [screencast](http://public.akretion.com/odoo_electronic_invoicing_zugferd.ogv) (in English, high-resolution OGV file, 22 minutes, 200 MB, readable with [VLC](http://www.videolan.org/vlc/))\r\n\r\nSince February 23rd 2016, all the invoices sent by Akretion to its customers are ZUGFeRD PDF invoices. That way, our customers can reliably import our invoices in their Odoo ERP in just 4 clicks! Alexis de Lattre, who developed the ZUGFeRD modules for Odoo, declares : *\"I am very proud to publish the first opensource implementation for the generation and import of ZUGFeRD electronic invoices in an opensource ERP! It is also the first opensource implementation of ZUGFeRD in the [Python](https://www.python.org/) programming language. The fact that there is now an opensource implementation of ZUGFeRD for Odoo, the leading opensource ERP software, is important to boost the adoption of electronic invoicing. We are now ready for the take-off of electronic invoicing in Europe!\"*\r\n\r\n![Odoo ZUGFeRD invoice in Acrobat Reader](http://public.akretion.com/sshot-acroread-odoo-zugferd-invoice-resized.png \"Odoo ZUGFeRD invoice in Acrobat Reader\")\r\n\r\nDon't hesitate to contact Akretion if you are interested by our work on electronic invoicing or whether you want to generate or import invoices in ZUGFeRD or UBL format with Odoo in your company.", "thumbnail"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a22202029544c9/5a2ec52765a2220202959f2d/files/zugferd.jpg", "filename"=>"zugferd.jpg", "size"=>5077.0, "updated_at"=>"2018-02-09T15:55:59.256Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T15:55:59.256Z"}, "summary"=>"Akretion publishes opensource Odoo modules to create and import ZUGFeRD PDF invoices. Discover how electronic invoices can save time for you and your company.
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>"en"}, {"_id"=>"5a2ec52765a2220202959f30", "_slug"=>"akretions-christmas-present-for-the-odoo-community", "_visible"=>true, "_position"=>44.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:27.934Z", "updated_at"=>"2018-08-23T07:51:21.896Z", "_label"=>"Akretion's Christmas present for the Odoo community", "title"=>"Akretion's Christmas present for the Odoo community", "posted_at"=>"2015-12-25T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Akretion is happy to offer you a *Christmas present* ! This Christmas present is for all the users of the accounting module of Odoo version 8 (and hopefully for the users of Odoo version 9 soon). If you are one of them, we hope that you will use and appreciate our present !\r\n\r\nBut, before going more in details about our present, let me tell you its story. This story started during the last week-end of September 2015. Akretion France's fiscal year closes on June 30th and, in France, we have to send to the fiscal administration the financial statements and the corporate income tax declaration 3 months maximum after the end of the fiscal year. So the deadline for Akretion France was September 30th 2015. Of course, to generate the financial statements, we need to have all our supplier invoices in Odoo ! But, as we are very busy with the work for our customers and our contributions to the [Odoo Community Association](https://odoo-community.org/) (OCA), we are often very late on the encoding of the \"small\" invoices (phone bill, Internet bill, train ticket, ...) and the last fiscal year was no exception. So we had one week-end to encode the backlog of supplier invoices and finalize the financial statements...\r\n\r\nAs Sébastien Beau was looking at the many train tickets he had to encode as supplier invoices, he decided to try to develop a script to do it for him. As with most suppliers, we have access to the PDF of the invoice in the customer Web access, but there is no webservice nor API to retreive the invoices automatically. [OVH](https://www.ovh.com/), the leading hosting provider, provides a webservice to access the invoices with very detailed information and Akretion developped a module for Odoo 8 named [ovh\\_supplier\\_invoice](https://github.com/akretion/ovh-supplier-invoice) to automate the download of OVH invoices and their creation as supplier invoices in Odoo. But, for all the other suppliers of Akretion, no such thing exists. We only have the PDF file of the invoice in our mailbox or on the extranet of the supplier, and nothing else !\r\n\r\nSo Sébastien had all the PDF files of his train tickets in his mailbox and didn't want to spend one hour to encode them manually one by one in Odoo. So he started to explore the possibilities of extracting the text out of the PDF file with a Python library called [pdfminer](http://euske.github.io/pdfminer/index.html) and create the supplier invoice in Odoo. After several hours of work, he came out with a Python script that was able to extract all the data needed to encode the train ticket as invoice (date, amount, ticket number, description of the travel) for all the PDF files he had in his mailbox. Then we thought that, as it was working for the train tickets, it would be great to have it also for the phone bills, the Internet access bills, the hosting bills, the office rental bills and all those recurring invoices that we have receive without generating a PO from Odoo. That's how we got the idea of developping a module dedicated to PDF invoice import.\r\n\r\nThis reminds us about the introduction of [EDI](https://www.odoo.com/apps/6.1/edi/) in OpenERP 6.1. At that time, it was presented as a way to automate the transmission of invoices between a supplier and a customer. Have you ever used it ? Probably never. One of the reasons of the low adoption is that both the customer and the supplier would have to open-up Odoo on the Internet or setup a VPN link between them. Another reason is that the EDI format proposed by Odoo was yet another format (and there are already many in the EDI world).\r\n\r\nOur German friends are taking another approch for the transmission of invoices ; their approch is very simple and pragmatic. They published a standard called [ZUGFeRD](http://www.pdflib.com/knowledge-base/pdfa/zugferd-invoices/) that specifies that a PDF invoice should contain an embedded XML file that provides a structured representation of the invoice. For the XML file, they decided to use the [Cross Industry Invoice](http://tfig.unece.org/contents/cross-industry-invoice-cii.htm) (CII) format published by an agency of the United nations called [UN/CEFACT](http://www.unece.org/cefact). In this domain, there are 2 main standards for the description of invoices in XML : the CII format of UN/CEFACT and the [Universal Business Language](http://ubl.xml.org/) (UBL) standardized by the [OASIS](https://www.oasis-open.org/). This approch is very pragmatic because:\r\n\r\n* users don't have to change their habbits: they can continue to send the invoices to their customers via email with the PDF file attached,\r\n* the same PDF document contains both the computer-readable information in the embedded XML file and the human-readable information that is displayed by the usual PDF reader of the user,\r\n* the same PDF invoice can be used both by companies that have a modern ERP software such as Odoo that can take advantage of the embedded XML file and by the companies that have an old ERP software in which users will manually encode their supplier invoices by viewing the invoice in their prefered PDF reader.\r\n\r\nFor the good old PDF invoices that don't have any embedded XML file, we found an existing Python library called [invoice2data](https://github.com/manuelRiel/invoice2data) that was already doing what we needed: extract the text of a PDF file, try to match it to an existing template and parse the text via the regexp provided by the template to retreive the information needed to create a simple supplier invoice in an accounting software. If your suppliers are not yet supported by this library, you should take a few minutes to add a template for your supplier and submit of pull request on github. Akretion already contributed to this library the support of several French mobile phone operators (SFR, Bouygues Telecom, Free mobile, Sosh) and several French Internet operators (SFR, Free, Orange fiber) in this [pull request](https://github.com/manuelRiel/invoice2data/pull/3).\r\n\r\nWith all these discoveries, we started to develop an Odoo module that would be able to handle both the modern PDF invoices with an embedded XML file and the good old PDF invoices without embedded structured data. Our module, called *account\\_invoice\\_import*, works the following way:\r\n\r\n![Odoo PDF import wizard](http://public.akretion.com/account_invoice_pdf_import1.png \"Odoo PDF import wizard\")\r\n\r\n1. the user starts a wizard and uploads the PDF invoice, as shown in the above screenshot.\r\n2. if the PDF file has an embedded XML file in ZUGFeRD/CII format, Odoo will read the XML file.\r\n3. otherwise, Odoo will use the *invoice2data* Python library to try to interpret the text of the PDF.\r\n4. Odoo will create a new draft supplier invoice and attach the PDF to it.\r\n\r\nThis module is available in this [pull request](https://github.com/OCA/account-invoicing/pull/122) on the OCA project *account-invoicing* for Odoo version 8 under the [AGPL licence](http://www.gnu.org/licenses/agpl-3.0.en.html). Please take the time to read the [detailed instructions](https://github.com/akretion/account-invoicing/tree/8.0-add-pdf-invoice-import/account_invoice_import) to install, configure and use this module. French users may also need the module *l10n\\_fr\\_invoice\\_import* available in this [pull request](https://github.com/OCA/l10n-france/pull/55) on the French localization of the OCA ; this module allows to find the related supplier in Odoo by the SIREN number and not just by the TIN or VAT number.\r\n\r\nWhen you import a PDF invoice in Odoo and Odoo already has a draft invoice for the same supplier, it will ask you if you want to create a new invoice or update the existing draft invoice (that may have been generated from a PO or a reception), as you can see in the screenshot below:\r\n\r\n![Odoo invoice update](http://public.akretion.com/account_invoice_pdf_import2.png \"Odoo invoice update\")\r\n\r\nAkretion team wishes your a **merry Christmas** and hope that you will like our Christmas present ! Our dream is that this new Odoo module would transform your painful duty of manually encoding your recurring supplier invoices into a fast and enjoyable task ! If it is the case, please share your experience with us and with the Odoo community.\r\n\r\n\r\n\r\nUPDATE 2018: You will find the code and modules on OCA/EDI: https://github.com/OCA/edi/tree/10.0", "thumbnail"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a22202029544c9/5a2ec52765a2220202959f30/files/gift.jpg", "filename"=>"gift.jpg", "size"=>16470.0, "updated_at"=>"2018-08-23T07:51:21.896Z"}, "banner"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a22202029544c9/5a2ec52765a2220202959f30/files/gift-bg.jpg", "filename"=>"gift-bg.jpg", "size"=>30814.0, "updated_at"=>"2018-08-23T07:51:21.896Z"}, "summary"=>"Akretion is happy to offer you a Christmas present ! This christmas present is for all the users of the accounting module of Odoo. It is a module allowing to import pdf invoices directly into Odoo.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}, {"_id"=>"5a2ec52865a2220202959f33", "_slug"=>"odoo-module-connection-to-a-logistics-center", "_visible"=>true, "_position"=>45.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:28.204Z", "updated_at"=>"2018-08-09T18:10:43.206Z", "_label"=>"Odoo module - Connection to a Logistics Center", "title"=>"Odoo module - Connection to a Logistics Center", "posted_at"=>"2015-11-02T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"# Connect your Odoo to a logistics center\r\n\r\n\r\nExternal partners or sub contractors needs to share informations with you. \r\n\r\nIf you want your business fast grows up, it's impossible to use anymore fax or email copy/paste.\r\n\r\nYou should **connect in real time your information system to your partners**.\r\n\r\nHere is some modules to complete this use case: allow to exchange file datas between Odoo ERP and external warehouses\r\n\r\n\r\n![Logistics Connector](https://raw.githubusercontent.com/akretion/logistics-center/7.0/connector_logistics_center/doc/logistics_connector.png \"Logitics Center Connector\")\r\n\r\n\r\n## Quick Start\r\n\r\n\r\n* Install bleckmann\\_logistics\\_customize module\r\n\r\n* Got to Menu Connectors > Logistics > Backends\r\n\r\n* Click to create a new backend \r\n\r\n* Select 'Bleckmann' as Logistics Center field\r\n\r\n* Select 'Version' and 'Warehouse' under 'Logistics configuration' and save\r\n\r\n* Here is what you should see:\r\n\r\n\r\n![Logistics Backend and Tasks](https://raw.githubusercontent.com/akretion/logistics-center/7.0/connector_logistics_center/doc/logistics_task.png \"Logistics Backend and Tasks\")\r\n\r\n* Click on Bleckmann link to go to the repository to define ftp parameters\r\n\r\n* To attach your products to your Logistics Center, go to Product Connector tab and add it.\r\n\r\n* Optionnaly in this screen you may share products information with several partners: Sub contractors, external warehouses, etc.\r\n\r\n\r\n![Logistics product](https://raw.githubusercontent.com/akretion/logistics-center/7.0/connector_logistics_center/doc/product_log.png \"Logistics Product\")\r\n\r\n* To send your product catalog (only products attached to this backend) to your logistics center, just click on Green right arrow near 'Catalog' like here.\r\n\r\n* In the same way you can send files (triggered by a planified task) for other flows: incoming, delivery order.\r\n\r\n* Your partner can reply, and then you import data to confirm delivery or receptions\r\n\r\n* There is also a module to simulate the reply of the logistics center, very useful for developement and tests steps\r\n\r\n* It's required to care of send only the right informations to your partners. To ensure it, you need to manage checks and alerts on Sales. Just customize existing Exception Rules or create others like here.\r\n\r\n\r\n![Logistics Sale Rules](https://raw.githubusercontent.com/akretion/logistics-center/7.0/connector_logistics_center/doc/rules.png \"Logistics Sale Rules\")\r\n\r\n\r\nThese modules are only available on Odoo / OpenERP V7. It needs some work due the changes of the data model on stock between v7 and v8\r\n\r\n\r\nHere is the repository\r\n\r\nhttps://github.com/akretion/logistics-center\r\n\r\n\r\n## Required Code Dependencies\r\n\r\n\r\nhttps://github.com/akretion/file-exchange\r\n\r\nhttps://github.com/akretion/connector-import-data\r\n\r\nhttps://github.com/OCA/sale-workflow/tree/7.0\r\n", "thumbnail"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a22202029544c9/5a2ec52865a2220202959f33/files/logistics.jpg", "filename"=>"logistics.jpg", "size"=>27624.0, "updated_at"=>"2018-08-09T18:10:43.206Z"}, "banner"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a22202029544c9/5a2ec52865a2220202959f33/files/logistic-bg.jpg", "filename"=>"logistic-bg.jpg", "size"=>288107.0, "updated_at"=>"2018-08-09T18:10:43.206Z"}, "summary"=>"Here is a short presentation about a module to exchange data with a logistics center
\r\nExternal partners or sub contractors needs to share informations with you.
If you want your business fast grows up, it's impossible to use anymore fax or email copy/paste.
You should connect in real time your information system to your partners.
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a2ec52865a2220202959f35/barroux-abbaye-350-267.jpg\" "\\"Image:")
The Barroux Abbey, a Catholic Abbey, home of fifty Benedictine monks, located near the Mont Ventoux (France), has rolled out Odoo version 8 in production on January 1st 2015 with Akretion. This deployment aims at replacing several home-made applications and a proprietary accounting and retail software by a single unified ERP software with a large functional scope. Odoo version 8 is now used by the monks in many areas of their activity:
\r\nretail outlet: the monks run a retail shop - located next to the abbey - that sells their home-made products: olive oil (La Joïo, La Reïalo and La Siavo), wine (Ventoux Saint-Roman, Ventoux Saint-Alric, Ventoux Saint-Hilaire, Ventoux Saint-Louis), nougat, brioche, gingerbread, biscuits, bread, etc. This shop also sells products made by other abbeys, as well as religious articles, books and CDs. Odoo powers the two checkouts with bar code readers, receipt printers, credit card readers, checks printers and customer displays. It also handles the stock management with several warehouses and stock routes as well as the procurements.
\r\nmail orders: the Abbey also sells a large part of their products via mail orders and online. Odoo records the orders, generates the picking waves, delivery documents and legal documents for the customs. Odoo is connected to the webservices of La Poste to automatically generate the colissimo labels for France, the French over-sea territories and the foreign countries.
\r\nhospitality: the monks welcome male guests that wish to make a retreat. An Odoo module has been developed to record the stays of the guests, attribute their rooms and it also generates the list of the guests present for lunch and dinner.
\r\ndonations: generous donors support the Abbey and its missions by making donations. Several Odoo modules have been developed to manage simple and recurrent donations. These modules handle the record of simple donations via checks, credit card payment, online payment and wire transfers, but also the recurring donations via direct debit and credit transfers. Odoo also generates the tax receipts that are sent back to donors with the thank-you letter. The donations modules are fully integrated with the accounting and payment modules of Odoo.
\r\nmasses: anyone can offer a mass and ask for a special prayer intention. People can ask for a mass to be said on a special date (the anniversary of the death of a friend or relative, for instance); it can be a single mass or a novena or a gregorian mass. An Odoo module has been developed to record the mass requests and generate the daily planning of the various masses. This module is fully connected to the donation module so as to record the donation associated to each mass request.
\r\naccounting: the Abbey now manages its accounting with Odoo not only for the commercial company that runs the hand-crafted production, the shop and mail order service, but also for the non-profit organization that runs the Abbey as well as other non-profit organizations that support the religious missions of the Abbey. Odoo centralises all the accounting movements of all these legal entities thanks to its support for multi-company configurations. Odoo is used to generate SEPA credit transfers, SEPA direct debits, French letters of change (LCR) and manages the deposit of checks. Odoo is also used to generate the French legal custom declarations (DEB).
\r\n\r\n
The project will later be extended to connect Odoo to the new PrestaShop online shop that plans to be rolled out in the coming months.
\r\n\r\n
Sharing is an important value for the monks; it is also at the heart of the free software movement. The Odoo modules that have been developed to manage stays and masses have been published under the AGPL licence on the Github project vertical-abbey, also named Philemon project, of the Odoo Community Association (OCA). The Odoo modules that manage donations have been published under the same licence on the Github project donation of the OCA. All these modules use the new-API of Odoo version 8 and have automated tests. They have been developed by two monks of the Abbey and by Alexis de Lattre from Akretion. These modules could be useful for other abbeys that would like to deploy Odoo to manage stays, donations and masses. The donation modules could also be useful for non-profit organizations and non-governmental organizations that require an ERP system that manages donations.
\r\n\r\n
The OpenSource contributions made during this project at the Barroux Abbey also include several new modules that have been included in the OCA projects on Github (or are under review):
\r\nthe module account_banking_fr_lcr that adds support for French letters of change (LCR) now included in the French localization OCA project.
\r\nthe modules that add support for credit card readers, check printers and customer displays in the retail shop (hw_customer_display, hw_telium_payment_terminal, pos_customer_display and pos_payment_terminal) now included in the POS OCA project.
\r\nthe module base_location_geonames_import that automate the creation of the postal code database from the geonames.org database, now included in the partner-contact OCA project and its sister module l10n_fr_base_location_geonames_import that is now part of the French localization OCA project.
\r\nthe module base_phone which includes several interesting features to validate phone numbers; which is part of the connector-telephony OCA project.
\r\nthe module sale_tax_included_excluded which aims at being able to properly manage prices with tax included and tax excluded at the same time, which is under review in the sale-workflow OCA project.
\r\nseveral small modules to enhance the usability of the new stock management system of Odoo 8: stock_transfer_split_multi, which is now part of the stock-logistics-workflow OCA project, and the modules stock_packaging_usability and stock_packaging_usability_ul, which are under review in the stock-logistics-tracking OCA project.
\r\n\r\n
The contributions of the Barroux Abbey also implied porting many community modules to version 8, reporting and fixing 22 bugs in the official modules and 13 bugs in community modules (full list here) and enhancing several OCA modules, including the module that manages check deposits named account_check_deposit. Other community modules have been developed and published on the Github branches of Akretion: the module account_statement_completion_label_simple that automatically sets the partners from the labels of the bank statement lines, the module partner_relation that handle the relations between partners (X recommends Y, A is part of the familly of B, etc...), the module bank_statement_import_camt that handle the import of SEPA CAMT .052 and .053 bank statement files and many small usability modules published on the odoo-usability project of Akretion.
“Odoo version 8 was officially released on September 18th 2014, and it went live at the Barroux Abbey on January 1st 2015: it is one of the first large project to go live on version 8 with so many applications. I am very proud of this deployment and of all the free software contributions that we made during this project. We hope that the new Odoo modules that we released as free software and published on Github will benefit to other abbeys, other non-profit organizations and other corporate users of Odoo“, declares Alexis de Lattre, engineer at Akretion.
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a2ec52865a2220202959f36/barroux-ticket-pos-286-420.jpg\")
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a2ec52965a2220202959f37/philemon-logo-192.png\"){kind=logo}
The Barroux Abbey, a Catholic Abbey, home of fifty Benedictine monks and located in France, has rolled out Odoo version 8 in production on January 1st 2015 with Akretion.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"The Barroux Abbey deploys Odoo version 8 | Akretion", "meta_description"=>"The Barroux Abbey, a Catholic Abbey, home of fifty Benedictine monks, located near the Mont Ventoux (France), has rolled out Odoo version 8 in production on January 1st 2015 with Akretion.", "meta_keywords"=>"déploie Odoo, abbaye, Odoo version 8", "force_locale"=>nil}, {"_id"=>"5a26d2d065a2220202954531", "_slug"=>"openerp-pricelist-builder-module-presentation", "_visible"=>true, "_position"=>2.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:36.731Z", "updated_at"=>"2018-08-09T18:15:22.699Z", "_label"=>"Pricelist Builder module", "title"=>"Pricelist Builder module", "posted_at"=>"2014-05-13T00:00:00.000Z", "published"=>true, "body"=>"
This module is an addition to the standard 'Product & pricelist' OpenERP module.
It simplifies the pricelist management.
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cf65a2220202954529/0-pricelist_std.png\")
Indeed, the standard module of OpenERP allows you to create pricing rules that are applied to a product and / or a category as shown in this picture.
But what happens when I have to apply this rule (eg deduction of 10 € + 10% discount rounded to € integer) of 5 products that are potentially in different categories ?
I have to create my rule 5 times (not to mention that the duplication of the rule is not possible from the interface).
Duplication => Public enemy of the data control
The typical case of this scenario is a special offer targeting some products that changes regularly throughout the year.
Changing the products category each time is not an option.
Our module presented here addresses this issue:
- Create the rule once
- Apply to X and / or Y categories and / or products that have the Z option
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cf65a222020295452a/1-install.png\")
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cf65a222020295452b/2-installed.png\")
Note: This module was originally created to facilitate the synchronization of price lists with prestashop.
So far it also syncs 'Special price' Magento.
But it can operate autonomously in OpenERP.
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cf65a222020295452c/3-builder.png\")
The main page of the module is as follows:
- On the top, the pricing rule and the concerned 'pricelist version'.
- In 'price elements' the price rule themselves with identical lists of standard prices settings.
- In 'Involved product' products / categories / options that the price rule applies: here the price rule applies to all products in category Y, but also those of the categories that have the Z option 'blue color' but also the product 'product in other categ'
The button 'update pricelist' ensures the consistency with the standard pricelist.
However, it is an optional use since scheduled task provides the same function.
The field 'last update' indicates the number of products affected by the update of the rules (deleted, created, udpated) or not (untouched)
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2d065a222020295452d/4-categ.png\")
In addition, the module ‘pricelist_from_product_or_category' allows, as its name suggests, to apply a rule set to a category / product directly from their interfaces (above the field 'pricelist builder')
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2d065a222020295452e/5-involved.png\")
Subsequent to the selection of this rule in categories, the 'Involved product' of our pricelist builder are modified accordingly (the 'Red' color was added in the meantime by another action)
![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2d065a222020295452f/6-version.png\")
We are back on the pricelist versions page of OpenERP.
This page is slightly different because there are 2 lists instead of a single one (all datas are nevertheless stored in the same table).
The one that we originally had now answers to the name 'Manual rules. Its behaviour remains unchanged.
The other list is called 'Automatically created rules' and data found in previous screens.
Even if OpenERP is more modular as an Open Source project (very modular compared to proprietaries ERP) on the side of pricelists it is a good old (and successful) sql query that takes care of everything.
Difficult in this case to 'overload' existing methods to alter their behavior without breaking compatibility with the native operation.
The easiest solution is to bring these rules at the product level as shown above.
Side performance if you have a very large amount of products with many different price lists, some points should be considered:
- Whether the rule applies only to a single category, the easiest way is to use the standard method of pricing rule.
- In case of performance problems, joint use of this module and openerp-connector could be considered this would smooth the update load.
The module is now translated from English to French only.
This module is limited to the management of public price (not ‘cost price' or ‘supplier price')
Akretion is at your disposal to develop additional modules, do not hesitate to contact us.
Modules:
- https://code.launchpad.net/~akretion-team/+junk/pricelist_advanced
", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:15:22.699Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:15:22.699Z"}, "summary"=>"
Ce module est un complément au module standard 'Product & pricelist' d'OpenERP.
Il étend les fonctionnalités du système de tarification des produits, appelé sur OpenERP 'liste de prix'.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544ec", "deprecated"=>false, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}, {"_id"=>"5a26d2d165a222020295453b", "_slug"=>"training-synchronisation-openerp-magento-15-16-17-april-2014-lyon", "_visible"=>true, "_position"=>4.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:38.024Z", "updated_at"=>"2018-02-09T16:00:16.084Z", "_label"=>"Formation OpenERP / Magento : 15, 16, 17 Avril 2014 à Lyon", "title"=>"Formation OpenERP / Magento : 15, 16, 17 Avril 2014 à Lyon", "posted_at"=>"2014-03-07T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"**Akretion** organise une nouvelle formation sur le connecteur **OpenERP-Magento**.\r\nConsécutivement à la formation de Redwood city en Californie en partenariat avec OpenERP, nous organisons cette fois la formation MagentoERPconnect en France à Lyon.\r\nCe connecteur repose sur Connector, le framework de synchronisation de la communauté d'OpenERP.\r\nCet outil est devenu un standard de fait pour toute synchronisation avec notre outil favori.\r\nPlusieurs nouveautés au menu de cette formation notamment la gestion du catalogue possible dans l'ERP et export dans Magento\r\n\r\n## Pourquoi un ERP pour l'ecommerce ?\r\n\r\nOn le sait tous, les comparateurs rendent la concurrence rude dans l'ecommerce, les marges sont faibles.\r\nUn impératif, se démarquer par la nature de son catalogue mais aussi par le volume de ses ventes.\r\nUn nombre de commandes élevé impose un traitement administratif colossal dans de nombreux domaines : gestion de stock, logistique, transport, achats, comptabilité.\r\nIls devient rapidement impossible de réaliser cette gestion sans outil approprié. Un ERP devient un allié incontournable. Mais encore faut-il avoir un outil souple pour s'adpater aux pratiques qui évoluent beaucoup dans le cadre de l'ecommerce ? Pour beaucoup OpenERP est le meilleur choix dans ce domaine.\r\n\r\n## A qui est destinée cette formation ?\r\n\r\nCette formation s'adresse aux e-commerçants actuels ou futurs qui veulent gérer l’ensemble de leurs processus avec deux des meilleurs outils du moment : OpenERP et Magento. C'est également la formation idéale pour les intégrateurs OpenERP qui veulent mener à bien leur projet e-commerce.\r\n\r\nElle vous permettra de prendre en main OpenERP dans le cadre d’un projet e-commerce. Cette formation est indispensable pour quiconque souhaiterais se lancer dans la mise en place d’OpenERP avec Magento.\r\n\r\n## Pourquoi le framework Connector ?\r\n\r\nConnector est utilisé par plusieurs intégrateurs important pour synchroniser OpenERP avec d'autres applications, notamment PrestaShop, Solr et OpenERP avec lui-même dans le cadre d'une utilisation en multi-companies.\r\nette utilisation dans plusieurs domaines est un gage de fiabilité puisqu'on mutualise la maintenance, sujet très important lors des changements de versions de l'ERP.\r\n\r\nIl est basé sur des tâches individuelles d'import et d'export, ce qui amène un maximum de visibilité sur les données en cours de synchronisation mais surtout de la fiabilité en ne bloquant pas tous les imports lorsqu'une seule commande pose problème.\r\n\r\nConsultez le sommaire détaillé de cette formation\r\n\r\nPour toute information complémentaire, merci de nous contacter à formation@akretion.com", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:00:16.084Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:00:16.084Z"}, "summary"=>"Akretion organise une nouvelle formation sur le connecteur OpenERP-Magento.
De nombreuses nouveautés attendent les stagiaires.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544ec", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"fr"}, {"_id"=>"5a2ec52a65a2220202959f48", "_slug"=>"formation-openerp-prestashop-1-2-3-avril-2014-a-lyon", "_visible"=>true, "_position"=>51.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:31.040Z", "updated_at"=>"2018-01-05T16:19:25.660Z", "_label"=>"Formation OpenERP / Prestashop : 1, 2, 3 Avril 2014 à Lyon", "title"=>"Formation OpenERP / Prestashop : 1, 2, 3 Avril 2014 à Lyon", "posted_at"=>"2014-02-17T00:00:00.000Z", "published"=>true, "body"=>"\r\n
Grâce au sharefunding de MagentoERPconnect, Camptocamp a pu revoir la conception du framework de synchronisation e-commerce. En mars 2013,les équipes de Camptocamp et Akretion se sont réunis pour lancer le portage du connecteur MagentoERPconnect sur ce nouveau framework.
\r\n\r\n
Au vu de l’efficacité de ce nouveau framework, Akretion a décidé de porter d’ores et déjà PrestaShopERPconnect sur celui-ci.
\r\nC’est donc sur cette nouvelle version optimisée pour OpenERP V7 que la formation aura lieu.
\r\n\r\n
On le sait tous, les comparateurs rendent la concurrence rude dans l'ecommerce, les marges sont faibles. Un impératif, se démarquer par la nature de son catalogue mais aussi par le volume de ses ventes. Un nombre de commandes élevé impose un traitement administratif colossal dans de nombreux domaines : gestion de stock, logistique, achats, comptabilité.
\r\n\r\n
Ils devient rapidement impossible de réaliser cette gestion sans outil approprié. Un ERP devient un allié incontournable. Mais encore faut-il avoir un outil souple pour s'adpater aux pratiques qui évoluent beaucoup dans le cadre de l'ecommerce ? Pour beaucoup OpenERP est le meilleur choix dans ce domaine.
\r\n\r\n
Cette formation s'adresse aux e-commerçants actuels ou futurs qui veulent gérer l’ensemble de leurs processus avec deux des meilleurs outils du moment : OpenERP et PrestaShop.C'est également la formation idéale pour les intégrateurs OpenERP qui veulent mener à bien leur projet e-commerce.
\r\nElle vous permettra de prendre en main OpenERP dans le cadre d’un projet e-commerce. Cette formation est indispensable pour quiconque souhaiterais se lancer dans la mise en place d’OpenERP avec PrestaShop.
\r\n\r\n
Consultez lesommaire détaillé de cette formation
\r\n\r\n
\r\n
Pour toute information complémentaire, merci de nous contacter à formation@akretion.com
\r\n", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-01-05T16:19:25.660Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-01-05T16:19:25.660Z"}, "summary"=>"
Akretion organise une nouvelle formation e-commerce basée sur OpenERP version 7 et PrestaShop 1.5 du 1 au 3 Avril 2014. Cette formation est basé sur le nouveau framework e-commerce.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>[], "author_id"=>"5a26d2c665a22202029544f8", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"fr"}, {"_id"=>"5a26d2cc65a222020295451e", "_slug"=>"run-a-locomotivecms-engine-in-minutes-and-upload-sites-to-it-with-devstep-docker", "_visible"=>true, "_position"=>0.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:32.505Z", "updated_at"=>"2018-02-09T16:01:00.566Z", "_label"=>"run a LocomotiveCMS engine in minutes and upload sites to it with Devstep (Docker)", "title"=>"run a LocomotiveCMS engine in minutes and upload sites to it with Devstep (Docker)", "posted_at"=>"2014-02-11T00:00:00.000Z", "published"=>true, "body"=>"![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cb65a2220202954518/loco-after-push.png\")
![\"\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cb65a2220202954519/create-account.png\")
![\"\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cb65a222020295451a/set-site.png\")
![\"\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cb65a222020295451b/credentials.png\")
![\"\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2cc65a222020295451c/pushing.png\")
LocomotiveCMS is a brilliant CMS. I personnaly consider it's way ahead all of the open source competition. It has a client server structure where designers can edit website locally and then upload them to a multi-tenant engine. But installing that Engine can be a bit daunting, especially as it is still running Rails 3.2 that may conclict with newer Rails 4 or because you need to install MongoDB. In this tutorial however we wlll use Devstep and Docker tools to do it easily without cluterring your computer so you can start hacking every aspect of LocomotiveCMS and use all its power.
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e0", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a26d2d365a2220202954543", "_slug"=>"openerp-magento-connector-v7-training-by-akretion", "_visible"=>true, "_position"=>6.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:39.182Z", "updated_at"=>"2018-02-09T16:01:49.528Z", "_label"=>"OpenERP-Magento connector v7 training by Akretion!", "title"=>"OpenERP-Magento connector v7 training by Akretion!", "posted_at"=>"2014-01-15T00:00:00.000Z", "published"=>true, "body"=>"\r\n
Akretion gave the first training on the new OpenERP-Magento connector in Redwood city, CA USA, from the 16th to the 18th of september 2013,
\r\nThe training session was organized by OpenERP SA themselves in their California headquarters:
\r\n\r\nMeanwhile, connector specialized engineers from Akretion Sebastien Beau and Benoît Guillot traveled from France to deliver the training session!
\r\n![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2d265a2220202954540/training_oe_mag_redwood_benoit.JPG\")
Akretion is indeed a strategic gold partner of OpenERP since 2012, official partner since 2009 and has built a very unique expertise with Magento OpenERP connector since 2008 with probably the largest number of Magento OpenERP SMB customers around! It’s also worth mentioning that Akretion is the official Certified Training center of OpenERP in Brazil since 2011 after we succesfully introduced OpenERP to that market so this kind of training partnership with OpenERP SA was natural for us.
\r\nSeven students from all over the world (Wisconsins, Florida, Dominican Republic, Philipins) came to learn a lot about the connector!
\r\n![](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2d265a2220202954541/training_oe_mag_redwood_seb.JPG\")
The training gave the students all the practical details to implement the brand new OpenERP v7 / Magento v1.7 connector released in november 2013 and featuring the new job queue framework for OpenERP designed by Camptocamp.
\r\nIn addition to the specific content of the connection between OpenERP and Magento, the students learned a lots of e-commerce features. Indeed, the training covers also the e-banking, bank statement reconciliation, management of delivery time and carriers, the logistic center integration and the shipping label printing.
\r\nOther OpenERP-Magento training sessions will soon be scheduled in France so don’t hesitate to contact us for further information.
\r\nAlso don’t forget that Akretion released OpenERP-Prestahop connector for Openerp v7
\r\nAn OpenERP-Prestashop training session will also be scheduled in France soon, so don’t hesitate to contact us for further information.
\r\nAkretion gave the first training on the new OpenERP-Magento connector in Redwood city, CA USA, from the 16th to the 18th of september 2013.
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e9", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a26d2d365a2220202954547", "_slug"=>"run-locomotivecms-websites-locally-in-minutes-using-wagon-and-devstep-docker", "_visible"=>true, "_position"=>7.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:39.635Z", "updated_at"=>"2018-08-09T18:17:03.403Z", "_label"=>"run LocomotiveCMS websites locally in minutes using Wagon and Devstep (Docker)", "title"=>"run LocomotiveCMS websites locally in minutes using Wagon and Devstep (Docker)", "posted_at"=>"2014-01-11T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"At Akretion we really love the [Locomotive CMS](http://locomotivecms.com/) which powers this corporate website and some other of our websites. LocomotiveCMS is all the more exciting as it shares a lot of its technological stack with Shopify, like [the Liquid templating language](https://github.com/Shopify/liquid/wiki/Liquid-for-Designers) for instance. And Akretion made it possible to integrate LocomotiveCME with Odoo business logic layer seamlessly using the [erpify gem](https://github.com/akretion/erpify). Something exciting we will talk about in an other post...\r\n\r\nBut in a company where we already ask our collaborators to master Python, not everybody has the proper Ruby runtime locally nor is willing to clutter his computer with all the dependencies. This is where Docker and Devstep really shine. Here is how to hack a LocomotiveCMS in minutes using Wagon in Devstep;\r\n\r\nYou may first need to install Docker on your computer in case you have been living on another planet over the last months:\r\n[https://docs.docker.com/installation/](https://docs.docker.com/installation/)\r\nDon't forget to give your user the privilege to run Docker as it saves you from doing sudo everytime when using docker.\r\n\r\nHere is how this tutorial looks like (recorded after steps 1 and 2 have been done):\r\n\r\n\r\n\r\n## 1) Install Devstep\r\n\r\ninstall Desvtep (voodoo includes the Devstep image because it's derived from it. But you should still install the client launcher). [http://fgrehm.viewdocs.io/devstep/getting-started](http://fgrehm.viewdocs.io/devstep/getting-started)\r\n\r\n\r\n## 2) Install Java in the Devstep image (LocomotiveCMS requires Java in yui-compressor)\r\n\r\n docker run -ti fgrehm/devstep:v0.2.0 bin/bash\r\n developer@aa5578cfaeff:/$ sudo apt-get update\r\n developer@aa5578cfaeff:/$ sudo apt-get install openjdk-7-jre\r\n\r\nin an other terminal/tab; note the container id (here aa5578cfaeff from the container shell prompter) and commit the changed image:\r\n\r\n docker commit aa5578cfaeff fgrehm/devstep:v0.2.0\r\n\r\nThat commit will allow us to have Java in all our future containers based on Devstep.\r\n\r\n\r\n## 3) Clone an existing Wagon website (unless you want to create a new one and follow the doc).\r\nFor instance we will start a blog example from [the official LocomotiveCMS tutorial](http://doc.locomotivecms.com/making-blog)\r\n\r\n git clone git@github.com:locomotivecms/wisdom-for-wanderers.git\r\n cd wisdom-for-wanderers\r\n\r\nbut because we are lazy we will go straight to the branch containing the final result:\r\n\r\n git fetch origin chapter-4.2:chapter-4.2\r\n git checkout chapter-4.2\r\n\r\nand because this is no mission critical ERP, we even suggest living on the edge and changing the Gemfile to grab the latest Wagon from git. So you can make this change in the Gemfile:\r\n\r\n -gem 'locomotivecms_wagon', '~> 1.4.0'\r\n +gem 'locomotivecms_wagon', git: 'https://github.com/locomotivecms/wagon.git'\r\n\r\n## 4) Start a Devstep container to run our website locally using Wagon:\r\nmake sure you are inside the wisdom-for-wanderers folder and do:\r\n\r\n devstep hack -p 3333:3333\r\n\r\n(you may double check where you downloaded/installed the devstep client command)\r\n\r\nBy doing that, you will enter a new Devstep container where the Ruby Buildpack will fire and converge the dependencies specified in the Gemfile, including the Wagon too to run LocomotiveCMS locally.\r\n\r\n## 5) Start wagon and you are done!\r\n\r\n bundle exec wagon serve\r\n\r\nNow browse http://localhost:3333 and you should be able to see the LocomotiveCMS blog!\r\n\r\n![\"\"](\"https://cdn.shopinvader.com/sites/5a26d1f365a2220202954490/assets/5a26d2d365a2220202954545/loco.png\")
Docker is all the rage these days and Akretion has been using it for a while now, including for Odoo. In this post however we will see how we can use the Desvetp tool combined with Wagon to edit locally a LocomotiveCMS website.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e0", "deprecated"=>false, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>nil}, {"_id"=>"5a26d2d365a222020295454a", "_slug"=>"sepa-support-in-openerp-by-akretion", "_visible"=>true, "_position"=>8.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:39.882Z", "updated_at"=>"2018-08-09T19:27:13.467Z", "_label"=>"SEPA support in OpenERP by Akretion", "title"=>"SEPA support in OpenERP by Akretion", "posted_at"=>"2014-01-01T00:00:00.000Z", "published"=>true, "body"=>"\r\n
The Single Euro Payments Area (SEPA) is an initiative of the European Union to simplify bank transfers in Euro currency and reduce delays. The 28 countries of the European Union (plus 5 others) are part of SEPA. So far, the main changes introduced by SEPA impacted the technical mechanisms of money transfers between banks. But the next milestone in the SEPA calendar impacts the data exchange between companies and their banks : starting from February 1st 2014, companies will not be allowed to use the old national file format any more, only the new SEPA file format will be accepted by banks.
\r\nThis new SEPA file format is based on the ISO 20022 standard and is XML-based. As a consequence, the companies that use files to send credit transfer orders or direct debit orders to their banks must make sure that their accounting software is able to generate SEPA XML files.
\r\nThanks for the work of Akretion in coordination with the OpenERP community, OpenERP is able to generate SEPA XML files for credit transfers and direct debits. The implementation of SEPA made by Akretion follows the guidelines of the European Payment Council, which federate the european banking industry and publish guidelines and rulebooks to use the ISO 20022 standard for SEPA. The OpenERP modules developed by Akretion are part of the banking addons, which is project managed by the OpenERP Community Association :
\r\nthe module account_banking_sepa_credit_transfer adds support for SEPA Credit Transfers (SCT),
\r\nthe module account_banking_sepa_direct_debit adds support for SEPA Direct Debits (SDD) including the management of direct debit mandates.
\r\nThe latest version of these modules for OpenERP 7.0 are available in the following branch : lp:~akretion-team/banking-addons/70-sepa-trf-dd-updates
\r\nBackports for some older versions of OpenERP are already available.
\r\nOnce theses modules are installed, OpenERP will be able to generate a SEPA XML file from a payment order and from a direct debit order. The SEPA files generated by OpenERP have already been used by several EU companies with many different banks for real-life credit transfers and direct debit transactions.
\r\nAkretion France is available to help you add SEPA support to your OpenERP system and carry out the required tests with your banks. Akretion would like to thank all the OpenERP integrators who subcontracted SEPA development and testing to Akretion ; this has been a great help in the implementation of SEPA for OpenERP.
\r\nAbout Akretion
\r\nAkretion is an OpenERP-expert company based in Brazil (Rio de Janeiro and São Paulo) and France (Lyon) with a strong experience in e-commerce projects. Akretion key contributions to Open Source software include the Magento-OpenERP connector, the PrestaShop-OpenERP connector, the Amazon-OpenERP connector, the eBay-OpenERP connector, the Asterisk-OpenERP connector, the Brazilian localization for OpenERP, support for French customs formalities (DEB and DES) in OpenERP and support for SEPA Credit Transfer and SEPA Direct Debit in OpenERP. Akretion sells training, consulting, software development and SaaS (Software as a Service) on OpenERP.
\r\n\r\n
Press contacts
\r\n\r\n
Akretion add the SEPA support for OpenERP
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>true, "seo_title"=>"SEPA support in OpenERP by Akretion | Akretion", "meta_description"=>"Module for SEPA support in OpenERP by Akretion", "meta_keywords"=>"SEPA, OpenERP, Odoo", "force_locale"=>"en"}, {"_id"=>"5a2ec52c65a2220202959f55", "_slug"=>"formation-openerp-prestashop-21-22-23-mai-2013-lyon", "_visible"=>true, "_position"=>52.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:32.477Z", "updated_at"=>"2018-02-09T17:09:27.759Z", "_label"=>"Formation OpenERP / Prestashop : 21, 22, 23 mai 2013 à Lyon", "title"=>"Formation OpenERP / Prestashop : 21, 22, 23 mai 2013 à Lyon", "posted_at"=>"2013-08-04T00:00:00.000Z", "published"=>true, "body"=>"
Grâce au sharefunding de MagentoERPconnect, Camptocamp a pu revoir la conception du framework de synchronisation e-commerce. En mars les équipes de Camptocamp et Akretion se sont réunis pour lancer le portage du connecteur MagentoERPconnect sur ce nouveau framework.
Au vu de l’efficacité de ce nouveau framework, Akretion a décidé de porter d’ores et déjà PrestaShopERPconnect sur celui-ci.
C’est donc sur cette nouvelle version optimisée pour OpenERP V7 que la formation aura lieu.
\r\n
On le sait tous, les comparateurs rendent la concurrence rude dans l'ecommerce, les marges sont faibles. Un impératif, se démarquer par la nature de son catalogue mais aussi par le volume de ses ventes. Un nombre de commandes élevé impose un traitement administratif colossal dans de nombreux domaines : gestion de stock, logistique, achats, comptabilité.
Ils devient rapidement impossible de réaliser cette gestion sans outil approprié. Un ERP devient un allié incontournable. Mais encore faut-il avoir un outil souple pour s'adpater aux pratiques qui évoluent beaucoup dans le cadre de l'ecommerce ? Pour beaucoup OpenERP est le meilleur choix dans ce domaine.
\r\n
Cette formation s'adresse aux e-commerçants actuels ou futurs qui veulent gérer l’ensemble de leurs processus avec deux des meilleurs outils du moment : OpenERP et PrestaShop. C'est également la formation idéale pour les intégrateurs OpenERP qui veulent mener à bien leur projet e-commerce.
Elle vous permettra de prendre en main OpenERP dans le cadre d’un projet e-commerce. Cette formation est indispensable pour quiconque souhaiterais se lancer dans la mise en place d’OpenERP avec PrestaShop.
Consultez le sommaire détaillé de cette formation
Lieu : 35 rue Montgolfier - 69100 Villeurbanne
Accès par le métro depuis la gare de la Part-Dieu
Date de la session : 21 au 23 Mai 2013 - 3 jours
\r\nHébergements à proximité :
\r\n\r\n
Pour toute information complémentaire et/ou pré inscription, merci de nous contacter à formation@akretion.com
", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T17:09:27.759Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T17:09:27.759Z"}, "summary"=>"Akretion organise sa première formation e-commerce basée sur OpenERP version 7 et PrestaShop 1.5 du 21 au 23 mai.
\r\nCette formation est basé sur le nouveau framework e-commerce.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544ec", "deprecated"=>true, "seo_title"=>"Formation OpenERP / Prestashop : 21, 22, 23 mai 2013 à Lyon | Akretion", "meta_description"=>"Formation OpenERP / Prestashop : 21, 22, 23 mai 2013 à Lyon", "meta_keywords"=>"Formation, OpenERP / Prestashop, Odoo", "force_locale"=>"fr"}, {"_id"=>"5a26d2d565a2220202954559", "_slug"=>"training-openerp-magento-connector-june-19-20-21-2013-in-redwood-city-ca-usa", "_visible"=>true, "_position"=>13.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:41.430Z", "updated_at"=>"2018-02-09T16:04:31.070Z", "_label"=>"Training OpenERP - Magento connector : June 19, 20, 21 2013 in Redwood City, CA (USA)", "title"=>"Training OpenERP - Magento connector : June 19, 20, 21 2013 in Redwood City, CA (USA)", "posted_at"=>"2013-07-05T00:00:00.000Z", "published"=>true, "body"=>"This training will extensively cover the latest version of the OpenERP-Magento Connector: MagentoERPConnect. This connector runs with OpenERP 7 and Magento 1.5 and up. MagentoERPConnect is an open source project developed for the most part by a group of companies specialized in open source business applications and acting as core editors (Akretion, Camptocamp,...). More information is available on the project's home page at https://launchpad.net/magentoerpconnect
\r\nConsult the course summary of the training
\r\nFirst Akretion training in USA on the OpenERP-Magento connector organized with OpenERP SA in Redwood City, CA from June 19 to June 21 2013.
\r\nTraining based on the new e-commerce framework.
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e9", "deprecated"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>"en"}, {"_id"=>"5a26d2d465a2220202954550", "_slug"=>"training-openerp-prestashop-15-16-17-october-2013-lyon", "_visible"=>true, "_position"=>10.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:40.504Z", "updated_at"=>"2018-02-09T16:05:17.959Z", "_label"=>"Formation OpenERP / Prestashop : 15, 16, 17 octobre 2013 à Lyon", "title"=>"Formation OpenERP / Prestashop : 15, 16, 17 octobre 2013 à Lyon", "posted_at"=>"2013-06-26T00:00:00.000Z", "published"=>true, "body"=>"
Akretion poursuit ses formations sur la connexion de PrestaShop avec OpenERP. Des nouveautés attendent les stagiaires
On le sait tous, les comparateurs rendent la concurrence rude dans l'ecommerce, les marges sont faibles. Un impératif, se démarquer par la nature de son catalogue mais aussi par le volume de ses ventes. Un nombre de commandes élevé impose un traitement administratif colossal dans de nombreux domaines : gestion de stock, logistique, achats, comptabilité.
Ils devient rapidement impossible de réaliser cette gestion sans outil approprié. Un ERP devient un allié incontournable. Mais encore faut-il avoir un outil souple pour s'adpater aux pratiques qui évoluent beaucoup dans le cadre de l'ecommerce ? Pour beaucoup OpenERP est le meilleur choix dans ce domaine.
Cette formation s'adresse aux e-commerçants actuels ou futurs qui veulent gérer l’ensemble de leurs processus avec deux des meilleurs outils du moment : OpenERP et PrestaShop. C'est également la formation idéale pour les intégrateurs OpenERP qui veulent mener à bien leur projet e-commerce.
Elle vous permettra de prendre en main OpenERP dans le cadre d’un projet e-commerce. Cette formation est indispensable pour quiconque souhaiterais se lancer dans la mise en place d’OpenERP avec PrestaShop.
Consultez le sommaire détaillé de cette formation
Lieu : 35 rue Montgolfier - 69100 Villeurbanne
Accès par le métro depuis la gare de la Part-Dieu
Date de la session : 21 au 23 Mai 2013 - 3 jours
Hébergements à proximité :
Pour toute information complémentaire et/ou pré inscription, merci de nous contacter à formation@akretion.com
", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:05:17.959Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:05:17.959Z"}, "summary"=>"Akretion poursuit ses formations sur la connexion de PrestaShop avec OpenERP du 15 au 17 octobre. Des nouveautés attendent les stagiaires
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544ec", "deprecated"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>"fr"}, {"_id"=>"5a26d2d465a2220202954553", "_slug"=>"webinar-br-brazilian-location-openerp-v7", "_visible"=>true, "_position"=>11.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:40.818Z", "updated_at"=>"2018-08-09T18:23:03.840Z", "_label"=>"Webinar BR - Localização Brasileira no OpenERP V7", "title"=>"Webinar BR - Localização Brasileira no OpenERP V7", "posted_at"=>"2013-05-14T00:00:00.000Z", "published"=>true, "body"=>"No dia 9 de maio de 2013 realizamos um webinar juntamente com a OpenERP S.A. apresentando a comunidade e parceiros as principais mudanças da localização brasileira em relação a versão 6.1, e os novos recursos implementado na versão 7.0.
<iframe width='560' height='315' src='http://www.youtube.com/embed/zktCtust2r0?list=UU2oHy0qFpbrNR4sbl5NK9eA' frameborder='0' allowfullscreen></iframe>
", "body_markdown"=>nil, "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:23:03.840Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:23:03.840Z"}, "summary"=>"No dia 9 de maio de 2013 realizamos um webinar juntamente com a OpenERP S.A. apresentando a comunidade e parceiros as principais mudanças e os novos recursos da localização brasileira para o OpenERP versão 7.0.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544dd", "deprecated"=>false, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>nil}, {"_id"=>"5a26d2d565a2220202954556", "_slug"=>"synchronisation-prestashop-and-openerp-v7-prestashoperpconnect", "_visible"=>true, "_position"=>12.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:41.167Z", "updated_at"=>"2018-01-05T16:25:12.748Z", "_label"=>"Synchronisation Prestashop et OpenERP v7 - PrestaShopERPconnect", "title"=>"Synchronisation Prestashop et OpenERP v7 - PrestaShopERPconnect", "posted_at"=>"2013-05-14T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Akretion a débuté l'implémentation de PrestaShopERPconnect pour la version 7 d'OpenERP.Akretion a débuté l'implémentation de PrestaShopERPconnect pour la version 7 d'OpenERP.
Voici quelques captures d'écran qui illustrent le niveau de fonctionnalité atteint à ce jour.
No dia 9 de maio de 2013 realizamos um webinar juntamente com a OpenERP S.A. apresentando a comunidade e parceiros as principais mudanças da localização brasileira em relação a versão 6.1, e os novos recursos implementado na versão 7.0.
\r\n<iframe width=\"560\" height=\"315\" src=\"http://www.youtube.com/embed/zktCtust2r0?list=UU2oHy0qFpbrNR4sbl5NK9eA\" frameborder=\"0\" allowfullscreen></iframe>
", "body_markdown"=>" ", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:06:11.735Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:06:11.735Z"}, "summary"=>"No dia 9 de maio de 2013 realizamos um webinar juntamente com a OpenERP S.A. apresentando a comunidade e parceiros as principais mudanças e os novos recursos da localização brasileira.
", "force_locale_id"=>"5a26d2c265a22202029544d5", "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544dd", "deprecated"=>false, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>"pt-BR"}, {"_id"=>"5a2ec52d65a2220202959f60", "_slug"=>"synchronisation-prestashop-et-openerp-v7-prestashoperpconnect", "_visible"=>true, "_position"=>55.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:33.465Z", "updated_at"=>"2018-02-09T16:06:52.868Z", "_label"=>"Synchronisation Prestashop et OpenERP v7 - PrestaShopERPconnect", "title"=>"Synchronisation Prestashop et OpenERP v7 - PrestaShopERPconnect", "posted_at"=>"2013-05-14T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Akretion a débuté l'implémentation de PrestaShopERPconnect pour la version 7 d'OpenERP.\r\nVoici quelques captures d'écran qui illustrent le niveau de fonctionnalité atteint à ce jour.\r\n\r\nA noter que le connecteur utilisé pour PrestaShop repose sur les mêmes briques de bases (modules génériques aux fonctionnalités communes) que celles utilisées pour MagentoERPconnect.\r\n\r\nHistoriquement Akretion avait développé une grosse partie des connecteurs e-commerce pour la version 5 et 6 d'OpenERP. Pour le cas de la version 7, nous tenons à remercier Camptocamp pour avoir investi de nombreux jours sur le nouveau framework de synchronisation sur lequel le nouveau connecteur Prestashop se base.\r\n\r\n===\r\n\r\n## Connexion\r\n\r\nLe module 'Connector' amène à OpenERP la notion de 'backend'. C'est ici que l'on définit le paramétrage permettant d'établir la connexion avec l'application à synchroniser : ici PrestaShop.\r\n \r\n \r\n \r\n\r\n\r\n\r\n\r\nPrestaShop donne accès à ses webservices par l'intermédiaire d'une clé qui est connu d'OpenERP.\r\n\r\n\r\n\r\n\r\nLe backend permet de synchroniser au préalable les objets de bases (stores, languages, etc...) de PrestaShop.\r\n\r\n\r\n===\r\n\r\n## Premiers imports\r\nLes clients, les adresses et groupes de clients de PrestaShop sont importées\r\n\r\n\r\n\r\n\r\nLe nouveau système de synchronisation des données repose sur des bases très différentes de l'ancien connecteur. Chaque synchronisation se découpe en 3 phases :\r\n\r\n * création d'un job de recherche des identifiants PrestaShop de l'objet à synchroniser\r\n * création de jobs individuels d'import dans une file d'attente : un job pour chaque enregistrement/objet correspondant aux identifiants PrestaShop\r\n * exécution des jobs issus de la file d'attente.\r\n\r\n\r\nPar exemple dans cet écran on trouve le job de recherche des clients nouveaux ou modifiés depuis une date donnée\r\n\r\n\r\n\r\n\r\nLe job ci-dessous défini l'import d'une adresse client (consécutivement à l'import du client)\r\n\r\n\r\n\r\n\r\nOn constate que les clients présents dans PrestaShop sont bien importés dans OpenERP.\r\n\r\n\r\nLes produits de PrestaShop sont également importés ...\r\n\r\n\r\n\r\n\r\n... comme on le voit ici\r\n\r\n\r\n\r\n\r\nDe même les commandes existantes dans PrestaShop peuvent être importées\r\n\r\n\r\n\r\n\r\n... via un découpage en tâches (jobs) individuels.\r\n\r\n\r\n\r\n\r\nLa commande est bien importé dans OpenERP. \r\n\r\nOn retrouve notre commande rattaché au shop 'Ma boutiq de rêve'.\r\n\r\n\r\n\r\n\r\n## Export des données\r\nConcernant l'export des données, le statut des commandes confirmées (quotation -> sale order) dans OpenERP est remonté dans PrestaShop\r\n\r\nL'export de l'inventaire des produits est en cours de finalisation.\r\n\r\nCette notion est très importante car il faut que le stock de PrestaShop tienne compte :\r\n\r\n * des achats fait sur OpenERP\r\n * des ventes faites sur d'autres canaux : Ebay, Amazon, autres boutiques (Magento ou un autre PrestaShop)\r\n\r\n\r\n\r\n\r\n\r\nLe développement est en cours, le périmètre 1 étant le portage du module PrestaShopERPconnect a été atteint et est période de test et de stabilisation. \r\n\r\nLe périmètre 2 étant la gestion du catalogue dans OpenERP est en cours de réalisation et sera fini au cours des projets clients.\r\n", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:06:52.868Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:06:52.868Z"}, "summary"=>"Akretion a débuté l'implémentation de PrestaShopERPconnect pour la version 7 d'OpenERP.
Voici quelques captures d'écran qui illustrent le niveau de fonctionnalité atteint à ce jour.
Grâce au sharefunding de MagentoERPconnect, Camptocamp a pu revoir la conception du framework de synchronisation e-commerce. En mars les équipes de Camptocamp et Akretion se sont réunis pour lancer le portage du connecteur MagentoERPconnect sur ce nouveau framework.
Au vu de l’efficacité de ce nouveau framework, Akretion a décidé de porter d’ores et déjà PrestaShopERPconnect sur celui-ci.
C’est donc sur cette nouvelle version optimisée pour OpenERP V7 que la formation aura lieu.
On le sait tous, les comparateurs rendent la concurrence rude dans l'ecommerce, les marges sont faibles. Un impératif, se démarquer par la nature de son catalogue mais aussi par le volume de ses ventes. Un nombre de commandes élevé impose un traitement administratif colossal dans de nombreux domaines : gestion de stock, logistique, achats, comptabilité.
Ils devient rapidement impossible de réaliser cette gestion sans outil approprié. Un ERP devient un allié incontournable. Mais encore faut-il avoir un outil souple pour s'adpater aux pratiques qui évoluent beaucoup dans le cadre de l'ecommerce ? Pour beaucoup OpenERP est le meilleur choix dans ce domaine.
Cette formation s'adresse aux e-commerçants actuels ou futurs qui veulent gérer l’ensemble de leurs processus avec deux des meilleurs outils du moment : OpenERP et PrestaShop. C'est également la formation idéale pour les intégrateurs OpenERP qui veulent mener à bien leur projet e-commerce.
Elle vous permettra de prendre en main OpenERP dans le cadre d’un projet e-commerce. Cette formation est indispensable pour quiconque souhaiterais se lancer dans la mise en place d’OpenERP avec PrestaShop.
Consultez le sommaire détaillé de cette formation
Lieu : 35 rue Montgolfier - 69100 Villeurbanne
Accès par le métro :
ligne A - station flachet (remonter la rue Flachet à pied à la sortie du métro)
depuis la gare de la Part-Dieu prendre la ligne B vers Charpennes puis la ligne A direction Vaulx en Velin la soie (station Flachet)
Date de la session : 21 au 23 Mai 2013 - 3 jours
Hébergements à proximité :
Pour toute information complémentaire et/ou pré inscription, merci de nous contacter à formation@akretion.com
", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:07:14.833Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:07:14.833Z"}, "summary"=>"Akretion organise sa première formation e-commerce basée sur OpenERP version 7 et PrestaShop 1.5 du 21 au 23 mai.
Cette formation est basée sur le nouveau framework e-commerce.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544ec", "deprecated"=>false, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>"fr"}, {"_id"=>"5a26d2d865a2220202954580", "_slug"=>"new-openerp-product-supplier-warranty-module-by-akretion", "_visible"=>true, "_position"=>26.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:44.926Z", "updated_at"=>"2018-02-09T16:09:00.130Z", "_label"=>"New OpenERP - product (supplier) warranty module by Akretion ", "title"=>"New OpenERP - product (supplier) warranty module by Akretion ", "posted_at"=>"2012-11-19T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"## OpenERP - RMA\r\nAkretion implemented supplier warranty management in OpenERP :\r\n\r\n### product_warranty : \r\nExtend the warranty details to a specific product/supplier relation\r\n\r\n* supplier warranty\r\n* return product to company, supplier, brand\r\n\r\nAll the modules related to RMA have been gathered in a dedicated launchpad project lp:openerp-rma", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:09:00.130Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:09:00.130Z"}, "summary"=>"OpenERP - RMA
Akretion implemented supplier warranty management in OpenERP
Grâce au sharefunding de MagentoERPconnect, Camptocamp a pu revoir la conception du framework de synchronisation e-commerce. En mars 2013,les équipes de Camptocamp et Akretion se sont réunis pour lancer le portage du connecteur MagentoERPconnect sur ce nouveau framework.
Au vu de l’efficacité de ce nouveau framework, Akretion a décidé de porter d’ores et déjà PrestaShopERPconnect sur celui-ci.
C’est donc sur cette nouvelle version optimisée pour OpenERP V7 que la formation aura lieu.
On le sait tous, les comparateurs rendent la concurrence rude dans l'ecommerce, les marges sont faibles. Un impératif, se démarquer par la nature de son catalogue mais aussi par le volume de ses ventes. Un nombre de commandes élevé impose un traitement administratif colossal dans de nombreux domaines : gestion de stock, logistique, achats, comptabilité.
Ils devient rapidement impossible de réaliser cette gestion sans outil approprié. Un ERP devient un allié incontournable. Mais encore faut-il avoir un outil souple pour s'adpater aux pratiques qui évoluent beaucoup dans le cadre de l'ecommerce ? Pour beaucoup OpenERP est le meilleur choix dans ce domaine.
Cette formation s'adresse aux e-commerçants actuels ou futurs qui veulent gérer l’ensemble de leurs processus avec deux des meilleurs outils du moment : OpenERP et PrestaShop.C'est également la formation idéale pour les intégrateurs OpenERP qui veulent mener à bien leur projet e-commerce.
Elle vous permettra de prendre en main OpenERP dans le cadre d’un projet e-commerce. Cette formation est indispensable pour quiconque souhaiterais se lancer dans la mise en place d’OpenERP avec PrestaShop.
Pour toute information complémentaire, merci de nous contacter à formation@akretion.com
", "body_markdown"=>"", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:14:46.866Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:14:46.866Z"}, "summary"=>"
Akretion organise une nouvelle formation e-commerce basée sur OpenERP version 7 et PrestaShop 1.5 du 1 au 3 Avril 2014.
Cette formation est basé sur le nouveau framework e-commerce.
Dear OpenERP community,
\r\nThings have been moving really fast for OpenERP and Tiny during those last 2 years. A lot of indicators (Google Insight, Launchpad inscription rates, partner list...) show OpenERP matured from a confidential francophone ERP to the global leader of open source ERP's. As you may have noticed this hasn't been without a clash. Especially, the main editor Tiny has been recently totally overwhelmed by the huge demand and community activity, unable to interact with the community anymore. This bottleneck around Tiny leaded to frustrations in the forums. Hard for Tiny however to react as their best elements where more and more busy with their own customers and growing company. This is time for action, and I believe this is finally happening.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e0", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}, {"_id"=>"5a2ec52d65a2220202959f66", "_slug"=>"formation-openerp-magento-3-4-5-avril-2012-lyon", "_visible"=>true, "_position"=>57.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:34.013Z", "updated_at"=>"2018-02-09T17:11:26.582Z", "_label"=>"Formation OpenERP - Magento : 3-4-5 avril 2012 - Lyon ", "title"=>"Formation OpenERP - Magento : 3-4-5 avril 2012 - Lyon ", "posted_at"=>"2012-06-19T00:00:00.000Z", "published"=>true, "body"=>"##Formation OpenERP - Magento : solution complète pour le e-commerce
**Informations générales :**
* **Dates** : 24 au 26 janvier (à confirmer) : 3 jours de formation
* **Lieu** : Région parisienne
* **Type** : Formation fonctionnelle découverte
* **Objectif** : Découverte des principales fonctionnalités OpenERP appliquées aux besoins métiers du e-commerce. Présentations des modules, paramétrages, processus et fonctionnalités de base.
* **Public** : E-commerçants & intégrateur e-commerce (OpenERP / Magento)
* **Places disponibles** : 10
* **Coût total de la formation** : 1 500€
**Contenu prévisionnel :**
Installation et utilisation du connecteur MagentoErpConnect (1j)
* Installation & paramétrage
* Intégration depuis un Magento existant
* Création d’un nouveau Magento
* Gestion quotidienne : synchronisations catalogues, prix, stock, clients, commandes, etc...
Processus de vente e-commerce (0,5j)
* Processus de vente
* Dropshipment (livraison directe du fournisseur au client)
* Alertes anti fraudes
Logistique (0,5j)
* Gestion des stocks & inventaires
* Achat & approvisionnement
* Réceptions & expéditions
* Transporteurs & livraisons
Marketing & CRM (0,5j)
* Prospection, campagnes & qualifications
* Profilage & segmentation
* Support & réclamation
* Gestion des retours de marchandise
Comptabilité (0,5j)
* Configuration du plan comptable & des taxes
* Gestion des factures / paiements / avoirs
* Relevés bancaires & lettrage
* Exemple d’interfaçage (Paypal, Ogone, Amazon)
Pour toute information complémentaire et/ou pré inscription, merci de nous contacter à <formation@akretion.com>
Formation OpenERP - Magento : solution complète pour le e-commerce
\r\nFormation OpenERP - Magento/PrestaShop : solution complète pour le e-commerce
Akretion is proud to announce a new feature on the [OpenERP-Asterisk connector](https://launchpad.net/openerp-asterisk-connector) : the ability to open the calling partner in one click !
===
## Open calling partner in 1 click with the OpenERP-Asterisk connector
Akretion, the author of the [OpenERP-Asterisk connector](https://launchpad.net/openerp-asterisk-connector), is proud to announce the immediate availability of a new feature on the connector: the ability to open the calling partner in one click in OpenERP.
Here is a typical usage scenario of this new feature:
1. Someone calls you and you pickup the phone. You click on the button *Open calling partner* in OpenERP : OpenERP sends a query to Asterisk to get a list of the current phone calls.
2. If OpenERP finds a phone call involving the user's phone, it gets the phone number of the calling party.
3. OpenERP searches the phone number of the calling party in its database and, if a record matches, it shows the name of the related Partner and proposes to open it, or open its related sale orders or invoices:
Another incredible thing about this new feature is that it's already fully documented on the [dedicated web page](/en/products-and-services/openerp-asterisk-voip-connector) on Akretion's Web site.
This page also presents Akretion's service offering to help you deploy the OpenERP-Asterisk connector. Who can better help you deploy this solution than the author of the module himself ?
Please note that this new feature is only available for OpenERP **version 6.1** for the moment. But Akretion can backport it to your version of OpenERP on request.
Akretion is proud to announce a new feature on the [OpenERP-Asterisk connector](https://launchpad.net/openerp-asterisk-connector) : the ability to open the calling partner in one click !
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a26d2d665a2220202954568", "_slug"=>"release-of-the-prestashop-openerp-connector", "_visible"=>true, "_position"=>18.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:42.729Z", "updated_at"=>"2023-04-17T20:03:56.567Z", "_label"=>"Akretion and Camptocamp announce the release of the PrestaShop-OpenERP connector", "title"=>"Akretion and Camptocamp announce the release of the PrestaShop-OpenERP connector", "posted_at"=>"2012-02-23T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"## Akretion and Camptocamp announce the release of the PrestaShop-OpenERP connector\r\n\r\n*February 23rd 2012*\r\n\r\n[Akretion](http://www.akretion.com/) and [Camptocamp](http://www.camptocamp.com/) announce the immediate and worldwide availability of the PrestaShop-OpenERP connector version 0.1.\r\n\r\n[PrestaShop](http://www.prestashop.com/) is an Open Source e-commerce software written in PHP that provides an easy-to-use and high-performance solution to set up an online shop. [OpenERP](http://www.openerp.com/) is an Open Source ERP software written in Python that provides an extended functional coverage: Customer Relationship Management (CRM), sales and purchase administration, stock management, Material Requirement Planning (MRP), accounting, etc.\r\n\r\nMany e-commerce companies running PrestaShop are looking for a global solution that includes stock management and accounting. For a successful e-commerce company, automating stock management, supplier orders and accounting are critical in order to have a profitable business. OpenERP and PrestaShop complement each other perfectly:\r\n\r\n* PrestaShop manages the *front office*: product catalog, customer accounts, carts, order validation and payment by credit card;\r\n* OpenERP handles the *back office*: stock management, supplier orders, customer claims, accounting, etc.\r\n\r\nThe only thing that was missing was a connector between these two software!\r\n\r\nThis first version of the PrestaShop-OpenERP connector has been developed during a one-week *code sprint* that took place on February 6th - 10th 2012 in Seythenex (Haute-Savoie, France). This large R&D effort of Akretion and Camptocamp (with the participation of one developer from Julius Network Solutions) is the kick-start of a new Open Source software project called **PrestashopERPconnect**. Akretion and Camptocamp form the *PrestashopERPconnect core editors* and are the official maintainers of the project.\r\n\r\nSebastien Beau, e-commerce project manager at Akretion, declares: \"*Our target was to be capable of importing orders from PrestaShop to OpenERP at the end of our one-week code sprint. But before importing the first order, we needed to develop the synchronization of shops, currencies, languages, countries, carriers and products. We reached our target on Thursday evening, so we deserved to go skiing on Friday afternoon at the [La Sambuy](http://www.lasambuy.com/) ski resort!*\"\r\n\r\nJoël Grand-Guillaume, Business Solution Division Manager at Camptocamp in Lausanne adds: \"*We did not only bring the finest swiss chocolates to this code sprint; we also brought our long experience of software development on the OpenERP framework and our knowledge of software architecture.*\"\r\n\r\nThe PrestaShop company contributed to the development of the connector by providing technical support on the PrestaShop webservices that are used by the connector. Nebojsa Stojanovic, Chief Technical Officer of PrestaShop, declares: \"*The development of the PrestaShop-OpenERP connector is the proof that our large developers community is a key differentiator compared with proprietary e-commerce solutions. We are very happy to see our award-winning Open Source e-commerce platform connected to one of the leading Open Source ERP solutions.*\"\r\n\r\n### FAQ about the PrestaShop-OpenERP connector\r\n\r\n1. **What is the license of the connector? Where can I get the source code?**\r\nThis connector is published under the GNU Affero General Public License version 3 (the same license as OpenERP). The source code is available on Launchpad: [https://launchpad.net/prestashoperpconnect](https://launchpad.net/prestashoperpconnect/) (Launchpad is a development platform that hosts many Open Source software projects, including OpenERP and Ubuntu).\r\n\r\n2. **Which versions of OpenERP and PrestaShop are supported?**\r\nRegarding OpenERP, the connector has been developed on OpenERP 6.1, which was released yesterday. And concerning PrestaShop, it supports all versions of PrestaShop starting from version 1.4, which is the first version of PrestaShop to propose a webservice interface. It doesn't require any module in PrestaShop. The current version of the connector comes with the mapping of objects between OpenERP 6.1 and PrestaShop 1.5 only. PrestaShop 1.5 is currently under development and will introduce multi-shop support and many other features. Adding support for PrestaShop 1.4 should be easy.\r\n\r\n3. **You publish this connector for free on the Internet... how do you earn a living?**\r\nAkretion and Camptocamp - the *PrestashopERPconnect core editors* - have developed this connector as part of their R&D effort. Both companies are strong supporters of Open Source software and have a long history of code contributions to OpenERP and other Open Source projects. Instead of spending millions in Sales and Marketing, they estimate that this code contribution is a better means to generate customer demand for software development on the connector and/or OpenERP and also for their trainings, professional services and SaaS (Software as a Service) offers.\r\n\r\n4. **Is the connector ready for production use?**\r\nThis version 0.1 has all the essential building blocks to connect OpenERP and PrestaShop and already supports the import of orders from PrestaShop to OpenERP in simple scenarios. Depending on how PrestaShop is used, generic or specific developments on the connector may be required.\r\n\r\n5. **What should I be aware of before deploying the connector?**\r\nThis connector can be downloaded by anyone on the Internet but it requires deep knowledge of OpenERP, PrestaShop and the connector's internals to be deployed successfully in production. The *PrestashopERPconnect core editors* are available to help you deploy this solution for your PrestaShop-based e-commerce business.\r\n\r\n### About Akretion\r\n\r\nAkretion is an OpenERP-expert company based in Brazil (Rio de Janeiro) and France (Lyons) with a strong experience in e-commerce projects. Akretion key contributions to Open Source software include the Magento-OpenERP connector, the Asterisk-OpenERP connector, the Brazilian localization for OpenERP, support for French customs formalities (DEB and DES) in OpenERP and the OOOR connector to use OpenERP from the Ruby programming language. Akretion sells training, consulting, software development and SaaS (Software as a Service) on OpenERP.\r\n\r\n### About Camptocamp\r\n\r\nIncorporated in 2001, Camptocamp is an Open Source software editor and integrator in three complimentary areas: Business Solutions (OpenERP, Business Intelligence, e-commerce), Geospatial Solutions and Infrastructure Solutions. Camptocamp strives to deliver high value-added services (consulting, R&D, training, support) to its customers in order to assist them in deploying efficient and sustainable Open Source applications. Based in Lausanne (Switzerland), Chambéry (France) and Vienna (Austria), Camptocamp counts 43 employees with functional as well as technical skills.\r\n\r\n\r\n### Press contacts\r\n\r\n* Akretion: Alexis de Lattre - Mail: alexis.delattre (at) akretion.com\r\n\r\n* Camptocamp: Maxime Wiot – Mail: maxime.wiot (at) camptocamp.com – Phone: +33 4 79 44 44 94 or +41 21 619 10 10", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2023-04-17T20:03:56.567Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2023-04-17T20:03:56.567Z"}, "summary"=>"Akretion and Camptocamp announce the release of the PrestaShop-OpenERP connector
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a26d2d665a222020295456b", "_slug"=>"formation-openerp-magento-3-4-5-april-2012-lyon", "_visible"=>true, "_position"=>19.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:42.959Z", "updated_at"=>"2018-01-05T16:32:21.585Z", "_label"=>"Formation OpenERP - Magento : 3-4-5 avril 2012 - Lyon ", "title"=>"Formation OpenERP - Magento : 3-4-5 avril 2012 - Lyon ", "posted_at"=>"2012-02-19T00:00:00.000Z", "published"=>true, "body"=>"##Formation OpenERP - Magento : solution complète pour le e-commerce
**Informations générales :**
* **Dates** : 24 au 26 janvier (à confirmer) : 3 jours de formation
* **Lieu** : Région parisienne
* **Type** : Formation fonctionnelle découverte
* **Objectif** : Découverte des principales fonctionnalités OpenERP appliquées aux besoins métiers du e-commerce. Présentations des modules, paramétrages, processus et fonctionnalités de base.
* **Public** : E-commerçants & intégrateur e-commerce (OpenERP / Magento)
* **Places disponibles** : 10
* **Coût total de la formation** : 1 500€
**Contenu prévisionnel :**
Installation et utilisation du connecteur MagentoErpConnect (1j)
* Installation & paramétrage
* Intégration depuis un Magento existant
* Création d’un nouveau Magento
* Gestion quotidienne : synchronisations catalogues, prix, stock, clients, commandes, etc...
Processus de vente e-commerce (0,5j)
* Processus de vente
* Dropshipment (livraison directe du fournisseur au client)
* Alertes anti fraudes
Logistique (0,5j)
* Gestion des stocks & inventaires
* Achat & approvisionnement
* Réceptions & expéditions
* Transporteurs & livraisons
Marketing & CRM (0,5j)
* Prospection, campagnes & qualifications
* Profilage & segmentation
* Support & réclamation
* Gestion des retours de marchandise
Comptabilité (0,5j)
* Configuration du plan comptable & des taxes
* Gestion des factures / paiements / avoirs
* Relevés bancaires & lettrage
* Exemple d’interfaçage (Paypal, Ogone, Amazon)
Pour toute information complémentaire et/ou pré inscription, merci de nous contacter à <formation@akretion.com>
Treinamento OpenERP - Magento : solução completa para e-commerce.
", "force_locale_id"=>"5a26d2c265a22202029544d4", "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e3", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"fr"}, {"_id"=>"5a26d2d765a222020295456e", "_slug"=>"training-openerp-magento-24-25-26-janvier-2012-paris", "_visible"=>true, "_position"=>20.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:43.231Z", "updated_at"=>"2018-02-09T16:16:07.012Z", "_label"=>"Formation OpenERP - Magento : 24-25-26 janvier 2012 - Paris", "title"=>"Formation OpenERP - Magento : 24-25-26 janvier 2012 - Paris", "posted_at"=>"2012-01-19T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"##Formation OpenERP - Magento : solution complète pour le e-commerceFormation OpenERP - Magento : solution complète pour le e-commerce
**We recently updated the mrp_prodlot_autosplit module by :**
\r\nAkretion announces the availability of the module coface_credit_insurance in the extra-addons section under the AGPL licence...
\r\nAkretion's Christmas present to the OpenERP community : new feature on the Asterisk connector...
\r\nFormation OpenERP - Magento : solution complète pour le e-commerce
\r\nThe module Product_variant_multi now use a generic and powerfull syntax for the automatic generation of the variant name.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e0", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}, {"_id"=>"5a26d2d865a222020295457a", "_slug"=>"benchmarks-with-openerp-server-hosted-on-the-internet", "_visible"=>true, "_position"=>24.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:44.342Z", "updated_at"=>"2018-02-09T16:11:42.559Z", "_label"=>"Benchmarks with OpenERP server hosted on the Internet", "title"=>"Benchmarks with OpenERP server hosted on the Internet", "posted_at"=>"2010-11-19T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"As Akretion starts to host some OpenERP servers for its SMB customers, we wanted to know which protocol is best for accessing an OpenERP server hosted on the Internet. So we made a comparision of the performances of Net-RPC, XML-RPC, XML-RPC SSL, HTTP, HTTPS, etc... Of course, only secure protocols should be selected when using an OpenERP server hosted on the Internet.\r\n\r\n=========\r\n\r\n\r\n## Benchmarks with OpenERP server hosted on the Internet\r\n\r\n_October 27th, 2011_\r\n\r\nAs Akretion starts to host some OpenERP servers for its SMB customers, we want to propose them a solution that is both fast and secure. So far, the majority of our customers host the OpenERP server on their LAN and access it via the Gtk Client through the Net-RPC protocol. The Net-RPC protocol is fast but not secure : the passwords and all the data are sent in clear, but our customers consider that, as the connection is made over their LAN, it's not a problem. By the way, it is probably a bad assumption, because a lot of IT attacks against companies come from the inside ! And when our customers need to access OpenERP from outside the office, they connect by VPN to their LAN and then they use OpenERP as usual with Gtk Client and Net-RPC protocol.\r\n\r\nIn order to select the best option for our customers that access an OpenERP server over the Internet, we made a real-life benchmark with an OpenERP server running on a machine in a datacenter, and elaborated a precise usage scenario. Basically, the scenario consist in a full purchase workflow (PO, reception of goods, supplier invoice) and a full sale workflow (SO, delivery order, customer invoice). For each protocol, we executed this scenario manually multiple times. We kept the fastest timing that was measured. As we ran the scenario manually, we estimate that the results are valid with a 10 seconds accuracy.\r\n\r\n#### Bench with OpenERP server hosted on the Internet\r\n\r\n| \r\n | Net-RPC | \r\nNet-RPC inside SSH tunnel | \r\nXML-RPC | \r\nXML-RPC SSL | \r\nHTTP access with Firefox 7 | \r\nHTTP access with Chrome 14 | \r\nHTTPS access through an Nginx proxy with Chrome 14 | \r\n
|---|---|---|---|---|---|---|---|
| Secure ? | \r\nno | \r\nyes | \r\nno | \r\nyes | \r\nno | \r\nno | \r\nyes | \r\n
| OpenERP 6.0.3 | \r\n1 min 49 | \r\n1 min 47 | \r\n2 min 11 | \r\n3 min 08 | \r\n2 min 04 | \r\n2 min 11 | \r\n2 min 05 | \r\n
| OpenERP 6.1 (trunk) | \r\n1 min 42 | \r\n1 min 40 | \r\n1 min 52 | \r\nnot available ? | \r\nbuggy | \r\n1 min 43 | \r\n1 min 40 | \r\n
| \r\n | Net-RPC | \r\n
|---|---|
| OpenERP 6.0.3 | \r\n1 min 15 | \r\n
| OpenERP 6.1 (trunk) | \r\n1 min 08 | \r\n
Benchmarks with OpenERP server hosted on the Internet
\r\nOpenERP - RMA
\r\nAkretion implemented Management of Return Merchandise Authorization (RMA) in OpenERP through two modules
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e3", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}, {"_id"=>"5a26d2d965a2220202954586", "_slug"=>"accounting-contribs-of-the-akretion-camptocamp-code-sprint", "_visible"=>true, "_position"=>28.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:45.462Z", "updated_at"=>"2018-08-09T19:17:48.976Z", "_label"=>"Accounting contribs of the Akretion-Camptocamp code sprint ", "title"=>"Accounting contribs of the Akretion-Camptocamp code sprint ", "posted_at"=>"2010-11-19T00:00:00.000Z", "published"=>true, "body"=>"", "body_markdown"=>"Two new modules to enhance your experience of accounting with OpenERP.\r\n========\r\n\r\nDuring the [Akretion](http://www.akretion.com) - [Camptocamp](http://www.camptocamp.com) code sprint that took place last week in the Camptocamp Lausanne office, two new modules were developped that are very usefull when using OpenERP's accounting in real life :\r\n\r\n* **account_reversal** : with this module, you can create *reversal* account moves in 2 clicks. Imagine the amount of time you will save when doing your cut-off accounting work!\r\n\r\n![\"Screenshot](\"http://akretion.s3.amazonaws.com/assets/c2c_sprint/account_reversal.jpg\")
![\"Screenshot](\"http://akretion.s3.amazonaws.com/assets/c2c_sprint/account_analytic_required.jpg\")
Two new modules to enhance your experience of accounting with OpenERP.
\r\n![](\"http://akretion.s3.amazonaws.com/assets/ooor_m.jpg\")
\r\n\r\nHello folks, after several months of hard work and aggregating feedback of the community, the OpenERP - (J)Ruby connector OOOR 1.5.0 is finally out!\r\nIf you don't know what is OOOR, you can read [that introduction](/en/blog/2010/01/18/introducing-ooor---openobject-on-rails-drivingrequesting-your-openerp-became-a-child-play/)\r\nand the [project's homepage](https://github.com/rvalyi/ooor).\r\n\r\nWe remind you that OOOR has been a hard work from Akretion since early 2009 and is licensed under the [AGPL v3](http://www.gnu.org/licenses/agpl.html) open source license, just like OpenERP itself. It has been installed - not just downloaded, but really installed via Rubygems.org [more than 8000 times!](http://rubygems.org/gems/ooor) Despite its name, OOOR doesn't hold a dependency on Rails and is used in many applications, including on the Java platform via JRuby. If you don't want to disclose your strategical client-side code under the viral AGPL v3 license, Akretion is open to sell commercial licences of OOOR, as well as support if you need. Contact us for details.\r\n\r\nTo install or update, install Ruby and Rubygems and then just do **gem install ooor** in terminal as explained on [Rubygems](http://rubygems.org/gems/ooor)\r\n\r\nHere is what's new in OOOR 1.5.0:\r\n\r\n**code clean up & bugfix:**\r\n\r\n* Rails 3 compatility (still compatible with Rails 2.x too)\r\n* Ruby 1.9.2 compatibility (+JRuby and Ruby 1.8.7 of course)\r\n* scoped classes under the Ooor module namespace without API break (except for UML)\r\n* refactored and debugged associations method_missing dispatch\r\n* renamed relations into associations to match Rails terminology\r\n* refactored RSpec test suite and show 0 error with OpenERP v6 and Ruby 1.9.2\r\n* much better exception handling, showing better error messages\r\n* unlike OpenERP, o2m and m2m relations should return empty arrays rather than false/nil for iteration consistency\r\n* unlike OpenERP read, Object.find(ids) respect initial ids order as you would expect\r\n* externalized type casting methods into a specific module\r\n\r\n**new features:**\r\n\r\n* more powerful domain mapping: Ruby hash such as {:origin = \"OUT04\"} automagically mapped to OpenERP domain, automagical array nesting Object.search ['name', 'ilike', 'foo'] just works\r\n* instance method always properly dispatch with foo.method_name passing [foo.id] as the first argument under the hood\r\n* OpenERP v6 client side log method\r\n* experimental subset of ActiveRecord Arel implemented via OpenObjectResource.where\r\n* much smarter ActionWindow proxy, successfully tested with Netzke\r\n* revamped UML with HTML nodes + [Sinatra](http://www.sinatrarb.com) dynamic UML explorator (yes that's awesome!)\r\n* faster startup because reading less model meta-info\r\n* field lazy loading works\r\n* loading specific fields can be achieved using the :only keyword to match Rails semantic (as well as :fields)\r\n* password not in the debug logs anymore\r\n\r\nWe also announce you that we have fantastic OOOR applications coming soon too, such as:\r\n\r\n* new more powerful Kettle ETL [TerminatOOOR](https://github.com/rvalyi/terminatooor) extension for OpenERP\r\n* a new set of unparalleled ecommerce connectors based on TerminatOOOR and the OpenERP base_sale_multichannels common platform \r\n* [Sencha Touch](http://www.sencha.com/) HTML5 mobile clients and framework\r\n* [Netzke](http://netzke.org/) and other HTML5 applications\r\n* Google Apps deep integration\r\n* OOORBIT, a secret Akretion project that really puts your OpenERP in orbit. But hey! we will give you the details when it's out (soon).\r\n\r\nEnjoy and stay tuned for more innovation with Akretion!", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:43:40.353Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-08-09T18:43:40.353Z"}, "summary"=>"OOOR 1.5.0 released!
\r\nAkretion enhances the French localization of OpenERP by adding full support for DEB and DES, which are two intrastat reports that French companies must send out to France's customs administration every month.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}, {"_id"=>"5a26d2da65a2220202954592", "_slug"=>"akretion-and-anevia-present-the-asterisk_click2dial-module-unleash-your-asterisk-phones-in-openerp", "_visible"=>true, "_position"=>32.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:46.590Z", "updated_at"=>"2018-02-09T16:13:37.328Z", "_label"=>"Akretion and Anevia present the \"asterisk_click2dial\" module: unleash your Asterisk phones in OpenERP! ", "title"=>"Akretion and Anevia present the \"asterisk_click2dial\" module: unleash your Asterisk phones in OpenERP! ", "posted_at"=>"2009-10-19T00:00:00.000Z", "published"=>true, "body"=>"Module Asterisk_click2dial for OpenERP
\r\n
\r\n
Author : Alexis de Lattre <alexis _at_ via.ecp.fr>
\r\n\r\n\r\n
This module adds a dial button in the partner address view so that users can directly dial a phone number through Asterisk. This feature is usually known as click2dial.
\r\n\r\n
Here is how it works :
\r\n\r\n\r\n
You should install the asterisk_click2dial modules on OpenERP just like any regular OpenERP module. What you need to know :
\r\n\r\n
Note : the module named asterisk in the extra-addons repository is useless and doesn't have any working functionality. The asterisk_click2dial module doesn't depend on it.
\r\n\r\n\r\n
OpenERP will communicate with Asterisk through the Asterisk Manager Interface (AMI).
\r\nSo the first step is to configure AMI :
\r\nThe configuration file of AMI is /etc/asterisk/manager.conf (depending on your Linux distribution, the directory may be different). Here is an example of the configuration with my comments inline :
\r\n\r\n
; It starts with the \"general\" section first
\r\n[general]
\r\n; You must enable the AMI feature
\r\nenabled=yes
\r\n; TCP Port on which AMI will listen
\r\nport = 5038
\r\n; I suppose Asterisk and OpenERP are on two different machines,
\r\n; so you must bind AMI on 0.0.0.0
\r\nbindaddr = 0.0.0.0
\r\n; We don't need to activate the HTTP AMI interface (the module uses the native
\r\n; interface)
\r\nwebenabled = no
\r\n\r\n
; Then, we create an AMI account for OpenERP
\r\n[click2dial] ; This is the AMI login
\r\nsecret = mypassword ; This is the AMI password
\r\n; We deny AMI access for everybody
\r\ndeny = 0.0.0.0/0.0.0.0
\r\n; We accept AMI access for OpenERP server (192.168.0.42)
\r\npermit = 192.168.0.42/255.255.255.255
\r\n; We give the minimum access rights required for the click2dial feature
\r\n; For Asterisk 1.4.x, you need the \"call\" rights
\r\nread = call
\r\nwrite = call
\r\n; For Asterisk 1.6.x, you need the \"originate\" rights :
\r\n;read = originate
\r\n;write = originate
\r\n\r\n
Warning : simply reloading Asterisk is not enough to activate the AMI ; you need to restart Asterisk (check that nobody is on the phone, because a restart of Asterisk will cut the communications).
\r\n\r\n
You can check that you can access the AMI from the OpenERP server :
\r\n% telnet <asterisk_server> 5038
\r\nIt should display :
\r\nConnected to <asterisk_server>.
\r\nEscape character is '^]'.
\r\nAsterisk Call Manager/1.0
\r\n\r\n\r\n
Log on as administrator on OpenERP.
\r\n\r\nFirst, you must create one or several Asterisk servers. The click2dial module supports several Asterisk servers. Then, for each OpenERP user, you must configure on which Asterisk server he is connected.
\r\nGo to Administration > Users > Company's structure > Companies. Select the company in the list. Then, go to the IPBX tab. Create one or several Asterisk servers. All the fields have a detailed contextual help, so you should be able to understand how to set each parameter by reading the help.
\r\nTwo parameters require additional explanations :
\r\n\r\n\r\n
Go to Administration > Users > Users. For each user that require the click2dial feature, you need to set 4 parameters that the asterisk_click2dial module has added in the User tab :
\r\nAlexis de Lattre <0141981242>
\r\n\r\n
That's it, the configuration is finished, you can start playing... or debug !
\r\n\r\n\r\n
How phone numbers are reformated
\r\nThis diagram explains it all.
\r\nIn the diagram, the two examples (ex1 and ex2) are based on the following configuration :
\r\nGo to the menu Partners > Partners and open a partner that you want to call. In the General tab, select the Partner contact that you want to call. Next to the Phone and Mobile fields, you should see a Dial button.
\r\n\r\n
\r\n
Important : the phone number in OpenERP should be in international format, for example :
\r\n+33 1 41 98 12 42
\r\nThis is the same format that you must use in your mobile phone's directory when you want to be able to call a number saved in your phone's directory when you are in a foreign country. For example, check this Nokia user manual page 19, section Make calls, look at the tip.
\r\nIf the phone number is not in the international format, you will get an error message when you click on the Dial button, unless you activated the option \"Allow national formats ?\" for this the Asterisk server.
\r\n\r\n
Here is the complete usage scenario :
\r\n\r\n\r\n\r\n
Imagine you share the same workroom with other colleagues. When one of your colleagues makes a phone call, the workroom stays quiet until the conversation starts. Now, if the colleague uses the click2dial feature of OpenERP, his phone will ring and bother everyone before the conversation even starts ! I think it's an important drawback...
\r\n\r\n
Hopefully, there is a solution to his : when Asterisk \"calls\" the user (before calling the remote party), he should tell the phone not to ring. In fact, when I say \"tell the phone not to ring\", I mean \"tell the phone to use a silent ring tone\". This is usually possible with SIP phones. In the SIP protocol, you can use the Alert-Info header to tell the phone to choose a particular ring tone. This feature is often called \"distinctive ringing\" or \"priority alerting\". Most SIP phones support the Alert-Info header, but :
\r\n\r\n
I have tested this feature with 2 different phone manufacturers : Thomson (ST2030 model, it probably works the same way with other models) and Aastra (6731i model, I am sure the other models work the same way). I give the details below ; if you have some experience with other phones, don't hesitate to edit this document and share your knowledge.
\r\n\r\nI suppose you use TFTP to configure the phone. If you edit the default configuration file for system melodies which is called Tone-RG.txt, you will see a ring tone Silent defined like this :
\r\nSilent:d=32,o=5,b=160:8P,2D
\r\nWith this configuration, it is a \"quiet\" ring tone, but not a fully silent one. To make it a fully silent, change the definition of this ring tone to :
\r\nSilent:d=32,o=5,b=160:P
\r\nNote : for the changes to take effect, don't forget to change the name of the ring tone file and update the filename in the parameter system_melodies of the <MAC_address>.inf file.
\r\nThen, in OpenERP, in the configuration of the Asterisk server, you should give the following value to the the Alert-info SIP header
\r\ninfo=<Silent>
\r\n\r\nAccording to the Aastra documentation, a Silent ring tone exists, but it can't be used for distinctive ringing. I found a workaround for this : choose a ring tone that is not used but default, for example Bellcore-dr5 (which is a \"quiet\" ring tone, but not a fully silent one), and redefine it in the configuration file (aastra.cfg to change it for all Aastra phones or <MAC_address>.cfg to change it only for one phone) :
\r\nbellcore cadence dr5: 0,-1
\r\nThis will transform the ring tone Bellcore-dr5 into a fully silent ring tone.
\r\nThen, in OpenERP, in the configuration of the Asterisk server, you should give the following value to the the Alert-info SIP header :
\r\ninfo=<Bellcore-dr5>
\r\n\r\n
Note : if you have a mix of Aastra and Thomson phones and you don't want to configure 2 Asterisk servers in OpenERP that point to the same server with just a different Alert-info SIP header parameter, here is a trick : rename the Silent ring tone of the Thomson IP phone to Bellcore-dr5 !
\r\n\r\n\r\n
If you have some issues with the module :
\r\n% asterisk -rvvvvvvvvvvvv
\r\nThis module adds a dial button in the partner address view so that users can directly dial a phone number through Asterisk. This feature is usually known as click2dial.
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a26d2d565a222020295455f", "_slug"=>"update-of-the-crm-specific-module-of-the-openerp-asterisk-connector", "_visible"=>true, "_position"=>15.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:41.970Z", "updated_at"=>"2023-04-17T20:05:07.502Z", "_label"=>"Update of the CRM-specific module of the OpenERP-Asterisk connector", "title"=>"Update of the CRM-specific module of the OpenERP-Asterisk connector", "posted_at"=>nil, "published"=>true, "body"=>"", "body_markdown"=>"The *asterisk_click2dial_crm* module of [Zikzakmedia](http://www.zikzakmedia.com) has been moved to the [OpenERP-Asterisk connector project](https://launchpad.net/openerp-asterisk-connector) on Launchpad. Akretion ported the module to OpenERP 6.1 and added some great enhancements.\r\n\r\n============\r\n\r\n\r\n## Update of the CRM-specific module of the OpenERP-Asterisk connector\r\n\r\nThe OpenERP-Asterisk connector was initially made of a single module : *asterisk_click2dial*, which only depends on the *base* module.\r\n\r\nThe Spanish company [Zikzakmedia](http://www.zikzakmedia.com) developped a CRM-specific module called *asterisk_click2dial_crm* for OpenERP 6.0 and [published](http://bazaar.launchpad.net/~openerp-commiter/openobject-addons/extra-6.0/revision/5585) it on Launchpad in the *extra-6.0* repository on November 2011. With this CRM-specific module, when the user made a click2dial, OpenERP would automatically create an outbound phone call in the CRM and open it in a new tab.\r\n\r\nWith the approval of [Zikzakmedia](http://www.zikzakmedia.com), the *asterisk_click2dial_crm* module has been moved to the [OpenERP-Asterisk connector project](https://launchpad.net/openerp-asterisk-connector) on Launchpad. Akretion ported the module to OpenERP 6.1 and enhanced it :\r\n\r\n* When you do a click2dial, instead of automatically creating an outbound phone call in the CRM, OpenERP will *propose* you to create one :\r\n\r\n\r\n\r\nIf you answer *Yes*, OpenERP will create the outbound phone call in the CRM. If some users don't want to be asked\r\nto create a phone call in the CRM each time they do a click2dial, they should disable the corresponding option in the *Telephony* tab of the *User*\r\nform.\r\n\r\n* When you receive a phone call and run the wizard *Open calling partner*, if the partner is found in OpenERP, you will see a button that proposes to create an inbound phone call in the CRM :\r\n\r\n\r\n\r\nPlease note that these enhancements are only available in the [6.1 branch](https://code.launchpad.net/~openerp-asterisk-team/openerp-asterisk-connector/6.1) of the OpenERP-Asterisk connector. The [documentation of the connector](/en/products-and-services/openerp-asterisk-voip-connector) has already been updated to reflect these changes.\r\n\r\nSo, if you are using OpenERP 6.1 in your company, you should throw away your old PBX and get an Asterisk PBX in order to benefit from the great features of the OpenERP-Asterisk connector ! If you don't know anything about how to deploy an Asterisk PBX in your company, you can read my page about [lessons learnt from an Asterisk deployment (French only)](http://people.via.ecp.fr/~alexis/asterisk/).", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2023-04-17T20:05:07.502Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2023-04-17T20:05:07.502Z"}, "summary"=>"Update of the CRM-specific module of the OpenERP-Asterisk connector
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "force_locale"=>"en"}, {"_id"=>"5a26d2d765a2220202954571", "_slug"=>"master-your-openerp-data-integration-with-akretion-terminatooor", "_visible"=>true, "_position"=>21.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:43.517Z", "updated_at"=>"2018-02-09T16:16:33.186Z", "_label"=>"Master your OpenERP data integration with Akretion TerminatOOOR! ", "title"=>"Master your OpenERP data integration with Akretion TerminatOOOR! ", "posted_at"=>nil, "published"=>true, "body"=>"", "body_markdown"=>"OpenERP is all the rage among open source ERP's but its native import/export has limitations when it comes to data integration. Server side OpenERP import/export is powerful but not so easy to get started and get interfaced. On the contrary, the famous Kettle open source ETL from Pentaho connects to almost anything (just last week it got a brand new EDI plugin for instance), any SGBD thanks to the JDBC connectors, any CSV, Excell files...\r\n\r\n![](\"http://akretion.s3.amazonaws.com/assets/terminatooor/image08.png\")
\r\n\r\nAkretion is here unveiling a technology we used for nearly 2 years now. Prepare you to step into the future...\r\n\r\n\r\nOpenERP is all the rage among open source ERP's but its native import/export have limitations when it comes to data integration. Server side OpenERP import/export is powerful but not so easy to get started and get interfaced. On the contrary, the famous Kettle open source ETL from Pentaho connects to almost anything, any SGBD thanks to the JDBC connectors, any CSV, Excell files...\r\n\r\nWith TerminatOOOR you have all the power of the full OpenERP API right inside your ETL data in/out flow. You can do any Create Read Update Delete operation enforcing the access rights of OpenERP. But you are absolutely not imited to that, in fact you can just do anything you would do with your OpenERP client: click buttons, perform workflow actions, trigger on_change events... This is because [OOOR](https://github.com/rvalyi/ooor) gives you the full access to OpenERP API.\r\n\r\n\r\n\r\nWe created TerminatOOOR back in late 2009 for a customer doing ecommerce sales on several different channels: Magento, OSCommerce, Amazon, Ebay, using several payments gateways and bank interfaces. Later we continued to use it in similar projects where integration with other systems would make the difference. It's also used a lot for loading your data into OpenERP when you migrate to it. But those are just a few possibilities... We finally got the time to package TerminatOOOR for an easier installation and we also documented it extensively.\r\n\r\nAll right, so don't wait any longer and read the [detailed documentation](http://www.akretion.com/en/products-and-services/openerp-kettle-bi-connector-terminatooor)\r\nYou might also be interested in [downloading it](https://github.com/rvalyi/terminatooor) or looking at its [source code](https://github.com/rvalyi/terminatooor)\r\n\r\nWe would also here thank all the great people who made this possible: the Kettle guys, Slawomir Chodnicki who revolutionized the Ruby Kettle plugin, all the JRuby team and specially people like Charles Headius Nutter, Yannick Buron for helping in the first doc version a year ago, CampToCamp and Ting.es for their testing and patches on OOOR and all the people who tested and helped in a way or another.\r\n\r\nEnjoy!", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:16:33.186Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T16:16:33.186Z"}, "summary"=>"OpenERP is all the rage among open source ERP's but its native import/export has limitations when it comes to data integration. Server side OpenERP import/export is powerful but not so easy to get started and get interfaced. On the contrary, the famous Kettle open source ETL from Pentaho connects to almost anything (just last week it got a brand new EDI plugin for instance), any SGBD thanks to the JDBC connectors, any CSV, Excell files...
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e0", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a26d2da65a2220202954595", "_slug"=>"introducing-ooor-openobject-on-rails-drivingrequesting-your-openerp-became-a-child-play", "_visible"=>true, "_position"=>33.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-05T17:09:46.903Z", "updated_at"=>"2023-04-17T17:22:35.076Z", "_label"=>"introducing OOOR - OpenObject On Rails: driving/requesting your OpenERP became a child play ", "title"=>"introducing OOOR - OpenObject On Rails: driving/requesting your OpenERP became a child play ", "posted_at"=>nil, "published"=>true, "body"=>"", "body_markdown"=>"One year ago, much for the fun, I started a small open source project [OOOR - OpenObject on Rails](http://github.com/rvalyi/ooor): the idea was to explore Ruby metaprogramming techniques to remotely access the whole API of OpenERP using the standard OpenERP webservices just like the genuine Rails ActiveResource API.\r\nThe thing is that OOOR is more and more being used for awesome stuff today, so I think it was the right time to finally present it to the general public...\r\n\r\n\r\n\r\n\r\n##introducing OOOR - OpenObject On Rails\r\n\r\n![](\"http://sites.google.com/site/assetserversite/_/rsrc/1257126460164/home/ooor_s.jpg\") | \r\n BY | \r\n![](\"http://akretion.s3.amazonaws.com/assets/logo.png\"){kind=logo} | \r\n
\r\n>sudo apt-get install ruby irb rubygems\r\n\r\n\r\nnow make sure your rubygems package is aware of the 'gemcutter' gem repository with:\r\n\r\n>sudo gem tumble\r\n\r\n\r\nNow install OOOR automagically:\r\n\r\n>sudo gem install ooor #last version so far is 1.2.3\r\n\r\n\r\n###Playing with OOOR:\r\nstart an OpenERP server with a demo data database with XML/RPC on port 8069 (default settings), then open an irb session\r\n\r\n\r\n\r\n###A few characteristics:\r\n* OOOR tries to 'fix' the OpenERP ORM awkward API:\r\n * So instead of accessing the persistence with Class Methods only like in OpenERP (you know the self.pool.get('my.resource').write(cr, uid, [id\\_of\\_my\\_current_object], my\\_value\\_hash), well you just do in OOOR: my\\_entity.update after you changed some values eventually. This is much easier to learn for the occasional coder/functional consultant needing to get his hands dirty.\r\n * you would also just to p.taxes\\_id = [1,2]; p.save rather than self.pool.get('product.product').write(cr, uid, [my_id], {taxes\\_id : [6, 0, [1,2]]}) in OpenERP and the same goes for one2many relations\r\n* OOOR supports Create, Read, Update, Delete (CRUD) operations but also any OpenERP expose business object methods, including:\r\n * button clicks\r\n * on_change events\r\n * workflows\r\n * wizards you get the full detail on [the project page here](http://github.com/rvalyi/ooor)\r\n* In any case, the API of OOOR is not an accident. It's actually a careful respect of the the standard exemplar Rails ActiveResource API, extended with relations supports and domain + context support to exactly match the OpenERP API itself.\r\n* OOOR doesn't connect to the database directly, it enforces the OpenERP layer encapsulation, object models and custom access rights.\r\n* OOOR supports connecting to several OpenERP instances at the same time, using a scoping prefix in the front of its class names, very handy to migrate data from one instance to an other, see: http://wiki.github.com/rvalyi/ooor/howto-connect-ooor-to-multiple-openerp-instance-easy-data-migration\r\n* OOOR is 100% compatible with JRuby, meaning you can use it from Java and you'll see how in my next post about its usage in the famous Kettle ETL (Pentaho Data Integration).\r\n* OOOR can also expose your OpenERP entities Restfully to other consumers using standard Rails support for REST, for that you should install the ['OooREST' extra gem\r\n* ever wonder how OpenERP could have such a bug and always thought that its current unit test framework has its limits when it comes to testing full real life functional/cross modules scenarios? Well in that case you should give a look to the \"Cucumber\" testing framework. Now, the dream comes true, CampToCamp just rolled a version of it for OpenERP, using OOOR to drive/query OpenERP. If you are willing to help making OpenERP a more robust system or if you want to package some tests with your OpenERP custom module to always be able to tell exactly and deterministically what works and what is broken, I totally encourage to you to jump in OERPScenario led by CampToCamp. By the way, OERPScenario is also able to play the OpenERP built'in unit test suite now, so it does just more and not less. Seriously, did you see something better than Cucumber/RSpec for testing? Me never, and I can tell you than when I worked 6 months on airline GDS testing at Amadeus before, I would have loved have something approaching Cucumber/RSpec, so having it for your ERP is totally awesome.\r\n\r\n\r\nAll right, I hope it provided you an insight of the OOOR unleashed power. If you need more, Akretion is willing to provide professional support to OOOR, but in any case we are committed to OOOR as a community open source (MIT liberal license) project. In a next post, I'll show you how you a noob programmer can easily pull/push any complex data form/to OpenERP using the Kettle ETL + OOOR embedded as a step plugin. We are already using it for customer projects at Akretion and it's a life saver.\r\n", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2023-04-17T17:22:35.076Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2023-04-17T17:22:35.076Z"}, "summary"=>"One year ago, much for the fun, I started a small open source project [OOOR - OpenObject on Rails](http://github.com/rvalyi/ooor): the idea was to explore Ruby metaprogramming techniques to remotely access the whole API of OpenERP using the standard OpenERP webservices just like the genuine [Rails ActiveResource API](http://api.rubyonrails.org/classes/ActiveResource/Base.html).
\r\nThe thing is that OOOR is more and more being used for awesome stuff today, so I think it was the right time to finally present it to the general public...
", "force_locale_id"=>"5a26d2c265a22202029544d3", "tag_ids"=>[], "author_id"=>"5a26d2c465a22202029544e0", "deprecated"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>"en"}, {"_id"=>"5a2ec52665a2220202959f27", "_slug"=>"akretion-adds-support-for-ubl-based-electronic-orders-in-odoo", "_visible"=>true, "_position"=>41.0, "content_type_slug"=>"posts", "created_at"=>"2017-12-11T17:49:26.990Z", "updated_at"=>"2018-02-09T17:12:20.883Z", "_label"=>"Akretion adds support for UBL-based electronic orders in Odoo", "title"=>"Akretion adds support for UBL-based electronic orders in Odoo", "posted_at"=>nil, "published"=>true, "body"=>"", "body_markdown"=>"Summary of the previous episodes: On December 25th 2015, Akretion developed the [import of regular PDF invoices](http://www.akretion.com/blog/akretions-christmas-present-for-the-odoo-community) via the use of the [invoice2data](https://github.com/m3nu/invoice2data) library. This solution requires the development of an [invoice import template](https://github.com/m3nu/invoice2data/tree/master/invoice2data/templates) for each supplier. This invoice template must be updated when the layout of the invoice is changed by the supplier, which is a major drawback. Akretion's customers discovered this drawback a few weeks after the deployment of the solution in production: as Akretion upgraded its Odoo server from v7 with the *Webkit* reporting engine to Odoo v8 with the *Qweb* reporting engine, the layout of Akretion's invoices changed and the import of Akretion's invoices was broken because Akretion's invoice template required an update.\r\n\r\nThe solution to overcome this drawback was to switch to electronic invoicing. A few months later, in March 2016, Akretion [announced](http://www.akretion.com/blog/akretion-publishes-zugferd-modules-to-create-and-import-electronic-invoices-with-odoo) the support of the generation of [ZUGFeRD](http://www.ferd-net.de/) invoices. A ZUGFeRD invoice is a PDF invoice with an embedded XML file in Cross Industry Invoice (CII) format. ZUGFeRD is the official electronic invoice format for Germany. Akretion's contribution also featured the support of the import of UBL (Universal Business Language) invoices, which is used by several countries in Northern Europe and is also the basis of the [e-fff format](http://www.e-fff.be) used in Belgium. Since April 2016, Akretion France's invoices are ZUGFeRD compliant and Akretion's customers can import them into Odoo thanks to the *account\\_invoice\\_import\\_zugferd* module. Using the ZUGFeRD format for Akretion's invoices was a nice move... but the benefit for Akretion's customers was still limited.\r\n\r\nOn January 1st 2015, Akretion [rolled out in production Odoo v8](http://www.akretion.com/blog/barroux-abbey-deploys-odoo-version-8-with-akretion) at the [Barroux Abbey](http://www.barroux.org/). On May 1st 2015, the [Randol abbey](http://www.randol.org/) deployed Odoo v8 in production and on January 1st 2016 the [La Garde monastery](http://www.la-garde.org/) also adopted Odoo v8. Each abbey has a retail shop that sells the production of the monks and also the home-made products of other abbeys (along with books, CDs, religious items, etc.). The honey and sandals produced by the La Garde monastery are sold at the Barroux abbey for instance; the nougat and the biscuits produced by the Barroux abbey are sold both at the Randol abbey and at the La Garde monastery, etc. When the development on ZUGFeRD invoices was completed, I suggested the monk in charge of the finances at the Barroux abbey that he deploy the module to generate ZUGFeRD invoices on the Odoo server of the abbey. That way, the Randol abbey and the La Garde monastery would be able to import the invoices of the Barroux abbey into their Odoo ERP without manual encoding, saving time for more important things. But the answer of the monk wasn't the one I expected: he told me that, as a draft supplier invoice is automatically generated from the purchase order, there was no real benefit in using electronic invoices! The real benefit would be to use electronic orders instead...\r\n\r\nSo I decided to continue the development to support electronic orders! I started to look for the best solution for electronic orders. I wanted to keep the great idea of the ZUGFeRD standard to have PDF documents with an embedded XML file. But which format was best suited to describe an order in XML? I found out that [UBL](http://ubl.xml.org/) (Universal Business Language) was the best format for the job. The UBL standard is both simple and accurate. It became the [ISO/IEC 19845](http://www.iso.org/iso/catalogue_detail.htm?csnumber=66370) standard in December 2015 (cf. the [official announcement](http://www.prweb.com/releases/2016/01/prweb13186919.htm)). UBL is already widely adopted for electronic invoices throughout Northern Europe, in Belgium (the [e-fff standard](http://www.e-fff.be)), in Turkey ([UBL-TR format](http://www.efatura.gov.tr)) and in [Australia](http://ubl.xml.org/news/australia-choses-ubl-for-whole-of-economy-einvoicing). In France, [EDF](https://www.edf.fr/), the national electricity company, already offers to send its invoices in UBL format (cf. [their specifications](https://entreprises.edf.com/fichiers/fckeditor/Commun/Entreprises/pdf/Guide%20technique%20facture%20EDF%20en%20XML%20V1.2.pdf)). The UBL standard supports the XML encoding of many different business documents: not only orders and invoices but also product catalogues, requests for quotations, quotations, packing lists, waybills, certificates of origin, etc.\r\n\r\nToday, Akretion announces the availability of an UBL stack for Odoo to manage purchase and sale orders in Odoo:\r\n\r\n* the module *purchase\\_order\\_ubl* embeds a request for quotation (RFQ) UBL XML file inside each RFQ PDF file generated by Odoo.\r\n* the module *sale\\_order\\_import\\_ubl* imports UBL RFQ XML files (or the PDF file with an embedded XML file) to generate new quotations.\r\n* the module *sale\\_order\\_ubl* embeds a quotation UBL XML file inside each PDF quotation file.\r\n* the module *purchase\\_order\\_import\\_ubl* imports quotations to update prices and/or quantities on RFQs.\r\n* when the purchase order is approved in Odoo, the module *purchase\\_order\\_ubl* embeds an order UBL XML file inside the PDF file of the purchase order.\r\n* the module *sale\\_order\\_import\\_ubl* imports UBL order XML files to update the quotations (or create new quotations).\r\n* when the order is accepted and the sale order is confirmed in Odoo, the module *sale\\_order\\_ubl* will embed an *order simple response* UBL XML file in the order acknowledgment PDF file of Odoo.\r\n\r\nAt the end of the sale workflow, when the goods have been successfully shipped, the supplier can generate a ZUGFeRD invoice with the *account\\_invoice\\_zugferd* module; this e-invoice will be used by the customer to update the draft supplier invoice generated by Odoo. For the payment, the [SEPA modules of the Odoo Community Association](https://github.com/OCA/bank-payment) can be used by the customer to generate a SEPA credit transfer XML file (with the module *account\\_banking\\_sepa\\_credit\\_transfer*) or by the supplier to generate a SEPA direct debit file (with the module *account\\_banking\\_sepa\\_direct\\_debit*).\r\n\r\nThis process is illustrated in the diagram below:\r\n\r\n![Odoo electronic ordering, invoicing and payment](http://public.akretion.com/ubl_customer_supplier.jpg \"Odoo electronic ordering, invoicing and payment\")\r\n\r\nPlease watch [this screencast](http://public.akretion.com/odoo_electronic_orders_ubl.ogv) (19 minutes long, 141 MB; or watch in lower-quality on [Youtube](https://youtu.be/bs8GPYlHa9Y)) that shows a demo of a procurement workflow between a supplier and a customer from RFQ to invoice. With this screencast, you will understand all the benefits of Odoo's UBL and ZUGFeRD stacks developed by Akretion.\r\n\r\nThe support of electronic orders and electronic invoices with the ZUGFeRD and UBL standards in Odoo uses 23 OCA ([Odoo Community Association](https://odoo-community.org/)) modules located in 5 different OCA projects:\r\n\r\n* the [edi](https://github.com/OCA/edi/tree/8.0) project,\r\n* the [partner contact](https://github.com/OCA/partner-contact/tree/8.0) project.\r\n \r\nThese modules use the new API of Odoo and most of them have an automated test suite. These modules are for Odoo v8 but most of them are migrated to Odoo v9 or v10.\r\n\r\n![OCA modules for e-orders and e-invoices](http://public.akretion.com/ubl_oca_modules.jpg \"OCA modules for e-orders and e-invoices\")\r\n\r\nThe Barroux abbey, the Randol abbey and the La Garde monastery will be the first users of these modules to exchange orders and invoices. Their feedback will be essential to fine-tune the UBL stack of Odoo.\r\n\r\nAfter this first deployment, the next step will be to test the interoperability of Odoo's UBL stack with other ERPs. According to [this blog post](https://blog.tradeshift.com/ubl-is-an-iso-international-standard-so-now-what/), Oracle, SAP and Microsoft ERP solutions now support UBL natively or via third-party add-ons.\r\n\r\nAlexis de Lattre, who developed the UBL stack of Odoo, says: '*The development of the UBL stack of Odoo is probably my biggest opensource contribution ever! I am very enthusiastic about the potential of UBL-based electronic orders and electronic invoices for B2B transactions. I hope that we won't have to wait for too long before having embedded UBL XML files in most PDF orders and PDF invoices!*'\r\n\r\nThis opensource contribution is brought to you by Akretion for free under the [AGPL licence](https://www.gnu.org/licenses/agpl.html). Don't hesitate to give your feedback on the pull requests under review on Github. If you have some real-life UBL orders or invoices, we would be grateful if you could share a copy with us so that we can enhance our knowledge of the UBL standard and fine-tune Odoo's UBL stack (we will keep these files confidential unless you give us an explicit authorization to publish them).", "thumbnail"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T17:12:20.883Z"}, "banner"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2018-02-09T17:12:20.883Z"}, "summary"=>"After the support of electronic invoives with the ZUGFeRD standard, Akretion now adds the support of electronic orders with the Universal Business Language (UBL) XML standard.
", "force_locale_id"=>nil, "tag_ids"=>[], "author_id"=>"5a26d2c565a22202029544e6", "deprecated"=>false, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "force_locale"=>nil}], "collaborators"=>[{"_id"=>"5a26d2c465a22202029544dd", "_slug"=>"renato-lima", "_visible"=>true, "_position"=>0.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:24.463Z", "updated_at"=>"2018-08-23T17:02:08.177Z", "_label"=>"Renato Lima", "name"=>"Renato Lima", "title"=>"Founder", "description_short"=>nil, "description_long"=>"Renato has over 11 years experience with Brazilian ERP's (Microsiga, Datasul...) and 3 years experience with OpenERP bothas a consultantand as aend user.Heisthe project leaderof theBrazilian LocalizationofOpenERP.
", "organisation_id"=>"5a26d2c265a22202029544a6", "twitter_url"=>"http://twitter.com/renatonlima", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"http://www.linkedin.com/in/renatonlima", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/renatonlima", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5a26d2c465a22202029544dd/files/29595382_2009959662366573_5745156141560596942-2_n.jpg", "filename"=>"29595382_2009959662366573_5745156141560596942-2_n.jpg", "size"=>45073.0, "updated_at"=>"2018-08-23T17:02:08.177Z"}, "published"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "organisation"=>"Brazil"}, {"_id"=>"5a26d2c465a22202029544e0", "_slug"=>"raphael-valyi", "_visible"=>true, "_position"=>1.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:24.762Z", "updated_at"=>"2018-01-02T11:18:02.336Z", "_label"=>"Raphaël Valyi", "name"=>"Raphaël Valyi", "title"=>"Founder", "description_short"=>"", "description_long"=>"Raphael, when he worked in Smile the French IT company, led the most thorough comparative study on ERP OpenSource (OpenERP, Openbravo, Compiere, Adempiere, ERP5 Ofbiz, etc ...) that led to writing a white paper of 120 pages. It has over 5 years experience in OpenERP and achieved more than 10 OpenERP deployments in companies.
\r\n", "organisation_id"=>"5a26d2c265a22202029544a6", "twitter_url"=>"http://twitter.com/rvalyi", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"http://www.linkedin.com/in/raphaelvalyi", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/rvalyi", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5a26d2c465a22202029544e0/files/collaborator-raphael-valyi.jpg", "filename"=>"collaborator-raphael-valyi.jpg", "size"=>13317.0, "updated_at"=>"2018-01-02T11:18:02.336Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"Brazil"}, {"_id"=>"5a26d2c465a22202029544e3", "_slug"=>"sebastien-beau", "_visible"=>true, "_position"=>2.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:25.030Z", "updated_at"=>"2018-08-23T17:52:58.730Z", "_label"=>"Sebastien Beau", "name"=>"Sebastien Beau", "title"=>"Founder", "description_short"=>"", "description_long"=>"
\r\n
Sebastien has over 3 years experience in OpenERP/Odoo, especially in integrating OpenERP/Odoo / Magento. After 6 months of internship in Akretion Brazil, he returned to France to work with the European customers compagnies. He works as a temporary self-employed in partnership with Brazil Akretion while preparing the pole Akretion France.
\r\n", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"https://twitter.com/Seb_Beau", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"http://www.linkedin.com/in/sebastienbeau", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/sebastienbeau", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5a26d2c465a22202029544e3/files/seb2.jpg", "filename"=>"seb2.jpg", "size"=>55714.0, "updated_at"=>"2018-08-23T17:52:58.730Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"5a26d2c565a22202029544e6", "_slug"=>"alexis-de-lattre", "_visible"=>true, "_position"=>3.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:25.337Z", "updated_at"=>"2018-08-23T17:08:37.472Z", "_label"=>"Alexis de Lattre", "name"=>"Alexis de Lattre", "title"=>"Founder", "description_short"=>"Specialist in Odoo and free software", "description_long"=>"
Com formação na área de engenharia participou do time da Akretion em 2011
", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/florian-dacosta", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5a26d2c665a22202029544ef/files/collaborator-florian-da-costa.jpg", "filename"=>"collaborator-florian-da-costa.jpg", "size"=>24672.0, "updated_at"=>"2018-04-23T11:20:26.139Z"}, "published"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "organisation"=>"France"}, {"_id"=>"5a26d2c665a22202029544f2", "_slug"=>"magno-costa", "_visible"=>true, "_position"=>7.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:26.562Z", "updated_at"=>"2018-08-23T16:59:25.096Z", "_label"=>"Magno Costa", "name"=>"Magno Costa", "title"=>"Odoo developer", "description_short"=>nil, "description_long"=>nil, "organisation_id"=>"5a26d2c265a22202029544a6", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/mbcosta", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5a26d2c665a22202029544f2/files/IMG_1724-2.JPG", "filename"=>"IMG_1724-2.JPG", "size"=>146655.0, "updated_at"=>"2018-08-23T16:59:25.096Z"}, "published"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "organisation"=>"Brazil"}, {"_id"=>"5a26d2c665a22202029544f8", "_slug"=>"chafique-delli", "_visible"=>true, "_position"=>9.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:27.106Z", "updated_at"=>"2017-12-12T10:20:31.934Z", "_label"=>"Chafique Delli", "name"=>"Chafique Delli", "title"=>"Associate", "description_short"=>nil, "description_long"=>nil, "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/chafique-delli", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2017-12-12T10:20:31.934Z"}, "published"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "organisation"=>"France"}, {"_id"=>"5a26d2c765a22202029544fb", "_slug"=>"raphael-reverdy", "_visible"=>true, "_position"=>10.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:27.375Z", "updated_at"=>"2021-01-08T11:18:36.962Z", "_label"=>"Raphaël Reverdy", "name"=>"Raphaël Reverdy", "title"=>"Odoo consultant", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/hparfr", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2021-01-08T11:18:36.962Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"5a26d2c765a22202029544fe", "_slug"=>"mourad-elhadj-mimoune", "_visible"=>true, "_position"=>11.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:27.646Z", "updated_at"=>"2017-12-12T10:20:50.425Z", "_label"=>"Mourad Elhadj Mimoune", "name"=>"Mourad Elhadj Mimoune", "title"=>"Odoo consultant", "description_short"=>nil, "description_long"=>nil, "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/mourad-ehm", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2017-12-12T10:20:50.425Z"}, "published"=>true, "seo_title"=>nil, "meta_description"=>nil, "meta_keywords"=>nil, "organisation"=>"France"}, {"_id"=>"5a26d2c865a2220202954504", "_slug"=>"thibault-rey", "_visible"=>true, "_position"=>13.0, "content_type_slug"=>"collaborators", "created_at"=>"2017-12-05T17:09:28.198Z", "updated_at"=>"2021-01-08T11:19:03.883Z", "_label"=>"Thibault Rey", "name"=>"Thibault Rey", "title"=>"Web consultant", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"https://fr.linkedin.com/in/thibault-rey-138710a6", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/thibaultrey", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5a26d2c865a2220202954504/files/collaborator-thibault-rey.jpg", "filename"=>"collaborator-thibault-rey.jpg", "size"=>9594.0, "updated_at"=>"2021-01-08T11:19:03.883Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"5ad4afdccc893d01d44b7d7b", "_slug"=>"alexandre-pollet", "_visible"=>true, "_position"=>15.0, "content_type_slug"=>"collaborators", "created_at"=>"2018-04-16T14:14:52.680Z", "updated_at"=>"2018-04-16T14:38:53.502Z", "_label"=>"Alexandre Pollet", "name"=>"Alexandre Pollet", "title"=>"Odoo consultant ", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"https://twitter.com/Dolmayan62", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"https://www.linkedin.com/in/alexandre-pollet-809a2a66/", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5ad4afdccc893d01d44b7d7b/files/alexandre-pollet.jpg", "filename"=>"alexandre-pollet.jpg", "size"=>10828.0, "updated_at"=>"2018-04-16T14:38:53.502Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"5e94c13af2a0762f94c0bffe", "_slug"=>"clement-mombereau", "_visible"=>true, "_position"=>16.0, "content_type_slug"=>"collaborators", "created_at"=>"2020-04-13T19:44:58.477Z", "updated_at"=>"2024-03-12T22:04:58.012Z", "_label"=>"Clément Mombereau", "name"=>"Clément Mombereau", "title"=>"Associate", "description_short"=>"Odoo developer", "description_long"=>"Clément is French engineer living in Brazil since 2012. He joined the Akretion team from Rio de Janeiro in 2018.
", "organisation_id"=>"5a26d2c265a22202029544a6", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/clementmbr", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-03-12T22:04:58.012Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"Brazil"}, {"_id"=>"5ff83764f2a076389f9f18f3", "_slug"=>"dora-jurcevic", "_visible"=>true, "_position"=>17.0, "content_type_slug"=>"collaborators", "created_at"=>"2021-01-08T10:43:48.592Z", "updated_at"=>"2021-01-08T10:47:14.973Z", "_label"=>"Dora Jurcevic", "name"=>"Dora Jurcevic", "title"=>"Web consultant", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/dora-jurcevic", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/5ff83764f2a076389f9f18f3/files/Dora_Jurcevic.jpg", "filename"=>"Dora_Jurcevic.jpg", "size"=>50747.0, "updated_at"=>"2021-01-08T10:47:14.973Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"5ff8389bf2a0762c16937329", "_slug"=>"kevin-roche", "_visible"=>true, "_position"=>18.0, "content_type_slug"=>"collaborators", "created_at"=>"2021-01-08T10:48:59.849Z", "updated_at"=>"2021-01-08T10:49:29.032Z", "_label"=>"Kévin Roche", "name"=>"Kévin Roche", "title"=>"Odoo consultant", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"https://github.com/Kev-Roche", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2021-01-08T10:49:29.032Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"65f0d276e395271b83f773db", "_slug"=>"paul-goubert", "_visible"=>true, "_position"=>20.0, "content_type_slug"=>"collaborators", "created_at"=>"2024-03-12T22:08:54.293Z", "updated_at"=>"2024-06-09T09:21:06.988Z", "_label"=>"Paul Goubert", "name"=>"Paul Goubert", "title"=>"Consultant Odoo", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"https://fr.linkedin.com/in/paul-goubert-b7b50943", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/65f0d276e395271b83f773db/files/paul_goubert.png", "filename"=>"paul_goubert.png", "size"=>35208.0, "updated_at"=>"2024-06-09T09:21:06.988Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"666575c5e395275a1a8ca3b8", "_slug"=>"matthieu-saison", "_visible"=>true, "_position"=>21.0, "content_type_slug"=>"collaborators", "created_at"=>"2024-06-09T09:28:37.134Z", "updated_at"=>"2024-06-09T09:28:37.134Z", "_label"=>"Matthieu Saison", "name"=>"Matthieu Saison", "title"=>"Consultant Odoo - France ", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-06-09T09:28:37.134Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"6665776de395275d64a0007c", "_slug"=>"olivier-nibart", "_visible"=>true, "_position"=>22.0, "content_type_slug"=>"collaborators", "created_at"=>"2024-06-09T09:35:41.997Z", "updated_at"=>"2024-06-09T09:37:23.527Z", "_label"=>"Olivier Nibart", "name"=>"Olivier Nibart", "title"=>"Consultant Odoo - France", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"https://www.linkedin.com/in/olivier-nibart-2041b6312/", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-06-09T09:37:23.527Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"66657811e395275d64a00086", "_slug"=>"thomas-bonnerue", "_visible"=>true, "_position"=>23.0, "content_type_slug"=>"collaborators", "created_at"=>"2024-06-09T09:38:25.103Z", "updated_at"=>"2024-06-09T09:38:25.103Z", "_label"=>" Thomas Bonnerue", "name"=>" Thomas Bonnerue", "title"=>"Consultant Odoo - France", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-06-09T09:38:25.103Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"6665787ee395275916060e80", "_slug"=>"mathieu-delva", "_visible"=>true, "_position"=>24.0, "content_type_slug"=>"collaborators", "created_at"=>"2024-06-09T09:40:14.664Z", "updated_at"=>"2024-06-09T09:44:07.248Z", "_label"=>"Mathieu Delva", "name"=>"Mathieu Delva", "title"=>"Consultant Odoo - France", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>nil, "filename"=>nil, "size"=>nil, "updated_at"=>"2024-06-09T09:44:07.248Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}, {"_id"=>"66657ca7e395275916060e87", "_slug"=>"elodie-lestrat", "_visible"=>true, "_position"=>25.0, "content_type_slug"=>"collaborators", "created_at"=>"2024-06-09T09:57:59.274Z", "updated_at"=>"2024-06-09T09:58:08.904Z", "_label"=>"Elodie Lestrat", "name"=>"Elodie Lestrat", "title"=>"Consultant Odoo - France", "description_short"=>"", "description_long"=>"", "organisation_id"=>"5a26d2c265a22202029544a5", "twitter_url"=>"", "facebook_url"=>"", "skype_url"=>"", "linkedin_url"=>"https://www.linkedin.com/in/elodie-lestrat/", "viadeo_url"=>"", "vimeo_url"=>"", "youtube_url"=>"", "github_url"=>"", "photo"=>{"url"=>"/sites/5a26d1f365a2220202954490/content_entry5a26d2c265a2220202954495/66657ca7e395275916060e87/files/elodie-jpeg-1663164551584.webp", "filename"=>"elodie-jpeg-1663164551584.webp", "size"=>3046.0, "updated_at"=>"2024-06-09T09:58:08.904Z"}, "published"=>true, "seo_title"=>"", "meta_description"=>"", "meta_keywords"=>"", "organisation"=>"France"}], "posts_tags"=>[]}