> that's not really a best practice.
>
> why would the vendor pay to implement the customer? that seems to be the
> customer responsibility.
Well, depends.
A couple of years ago two major healthcare plans teamed up and engaged me to
create a piece of desktop software to create a remittance report from the
X12N X091A1 835 Healthcare remittance advice document.. software normally
the responsibility of the recipient.
They then GAVE copies of the software to their providers.... and
simultaneously gave all providers a url, a user ID and a password to pick up
'835' documents ....AND stopped producing and mailing printed remittance
reports.
They paid me less (a lot less!) than the $500,000 per year they now save on
paper and postage.
So, I guess it depends what's in it for the 'vendor,' huh?
Michael C. Mattias
Tal Systems Inc.
Racine WI
[EMAIL PROTECTED]
------------------------------------
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
