E-invoices from omnis

[Jordan, Christopher]

Check out  ISO 20022

-----Original Message-----
From: omnisdev-en-bounces at lists.omnis-dev.com [mailto:omnisdev-en-bounces at lists.omnis-dev.com] On Behalf Of Daniel Sananes
Sent: Wednesday, July 23, 2014 12:54 PM
To: 'OmnisDev List - English'
Subject: SV: E-invoices from omnis

Hi Andrew,

It is a large company, hundreds of invoices daily to and from.
Yes, some kind of mapping surely has to be done.
Seems the company want to buy the solution from Palette.
The work-flow is that suppliers send pdf-invoices which are translated online (don’t know where at the moment) and this information is sent to Palette which in return sends information back to our company in tabbed textfiles which the our omnis-program reads.
It is of course this translation that may be the difficult part.

Daniel

-----Ursprungligt meddelande-----
Från: omnisdev-en-bounces at lists.omnis-dev.com [mailto:omnisdev-en-bounces at lists.omnis-dev.com] För Andrew Stolarz
Skickat: den 23 juli 2014 17:26
Till: OmnisDev List - English
Ämne: Re: E-invoices from omnis

Daniel,

I don't think you can reliably receive PDF files from various suppliers and extract that data. If it was all standardized formats, perhaps.

As far as I understand, you will need to see if all your suppliers will send your "invoice" in XML or comma delimited format etc. With the raw XML file, you can essentially import the invoice transaction into your Omnis application. You would also have to create some sort of import map for all your suppliers, sounds like a nightmare unless your suppliers are sending in same format.

Unless you are a large company, I think you will have more challenges in getting your suppliers to send the XML data then it would be to built/import it into omnis.


Andrew








On Wed, Jul 23, 2014 at 11:13 AM, Daniel Sananes <danielsananes at hotmail.com>
wrote:

> Hi Doug,
>
> Yes, it may be worth while sending invoices like you say one can do.
> But as for now this company wants to receive invoices from suppliers 
> electronically and automatically transfer them into their economical 
> system built in Omnis.
> I don’t know how an electronic message, or invoice, is made of. What 
> is a pdf-file for instance? Can you extract the relevant data like 
> suppliers name and sums to be payed.
>
> Well, these are the questions I wonder about.
>
> Regards Daniel
>
> -----Ursprungligt meddelande-----
> Från: Doug Easterbrook
>
> hi Daniel:
>
> we do e-invoices from omnis all the time.  The basics are:
> print the invoice to screen (we use an omnis report) use PDFDevice 
> (From michael @ brainy data) and print to pdf add PDF as attachment to 
> email send (you can use SMTPsend if you want -- just make sure you've 
> got the mime types set up).
>
> Alternatively, you can:
> use oWrite to create your invoices
> merge the data into the invoice
> export the invoice from owrite as HTML send the html using SMTPsend.
>
>
> depends if you want to have the invoice as an attachment (via a PDF) 
> or as an HTML email (using owrite).
>
> either way works. ...   I don't recall, but michael may even have an
> invoice
> sample in his owrite documentation.
>
>
>
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug at artsman.com
> http://www.artsman.com
> Phone (403) 536-1205    Fax (403) 536-1210
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>
_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4716 / Virus Database: 3986/7904 - Release Date: 07/23/14

_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com



Please consider the environment before printing this email.


E-mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Henry Schein is not liable for any loss or damage arising from this message.

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.