Being a Dealer Owned Co-Op, we require the ITD segment on all inbound invoices 
from all suppliers.

There are two sides to our business, product being purchased by corporate for 
distribution to our dealer network
from our distribution centres. Most of these invoices will have terms as per 
our vendor agreement, but not always.
There are always promotional orders or special deals being requested or offered 
with different terms than what is
on file with our supplier agreement. These aren't too bad as our PO will have 
the terms that were offered, but many times
we see vendors sending in their standard terms on the invoices instead of the 
special terms, even though the PO we sent
them has these special terms.

On the other side, mostly lumber products, are being ordered by our dealers and 
shipped directly to the store from our suppliers.
We see terms that are all over the place for the same supplier, sometimes a 
specific dealer, usually based on volume, will get
different terms than others, sometimes it can be regional within the same 
supplier, the west offers 2% 15 days, central offers 2%
15th month following, etc..., but we treat them as a single supplier for 
payment. Certain products, concrete comes to mind, suppliers
will  offer a fall booking for product delivered in the slow months (Jan-Mar), 
but payment isn't required until May. These are outside of
their normal invoice terms from March-October.

Do we always get the correct terms on invoices, not a chance.

I think someone asked about the equal payment terms invoices on this thread 
before, where the invoice could be payable in three
installments.

Our Oracle system can handle this and the 810 can handle it, but for the number 
of times it happens, we chose not to create the integration
logic to handle this. For a vendor sending us 810 invoices, we put the 
requirement back on them to send us three invoices with different due
dates, most of the time a supplier will do this, but not always. We handle 
these manually on our AP side if required. We also communicate
this to our Product Managers to try and avoid making the agreement for this 
type of payment in the first place.

For Invoice Terms, this can be quite unique to each retailer as can the payment 
schedule.

The 810 invoices we receive, I would say 90% of the invoices getting held for 
some problem is due to Store # issues or Invoice Terms.

Just for information sake, even though the dollar value of invoices is about 
equal on the above two scenario's, the transaction volume for
direct to store shipments is 80%.





Bruce Shannon
Vendor E-Commerce Coordinator
Home Hardware Stores Limited
519-664-4997



________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Michael 
Mattias/LS
Sent: Wednesday, August 18, 2010 9:27 AM
To: [email protected]
Subject: Re: [EDI-L] Re: ITD mapping question for the group



>>I wonder if there are more companies using this kind of philosophy out
>>there
>> - taking the best due date and terms that they can get, holding on to
>> their
>> money for as long as they can..

> Every single one of them, I'd imagine....

Maybe in some of the larger, more sophisticated firms.. those who actually
*request* electronic invoices in ANSI EDI format.

I still think these purchasers primarily record the vendor's invoice number,
invoice date, amount subject to terms, total amount and their PO number and
then just pay "as we customarily pay this particular vendor."

Anyone big enough to actually use inbound EDI invoices is probably paying
on some kind of 'cycle' anyway, maybe weekly, maybe bi-monthly, maybe
monthly.. at which time they select for payment "all approved invoices with
an invoice, due or discount date less than 'some arbitrary cutoff date.'

Michael C. Mattias
Tal Systems Inc.
Racine WI
[email protected]<mailto:mmattias%40talsystems.com>





This e-mail may contain privileged, private, proprietary or confidential 
information which is intended only for the intended recipient.  If you are not 
the intended recipient, or the person responsible for delivering this message 
to the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.  If you 
have received this communication in error, please reply with the notation 
"Received in Error" in the subject line and delete the e-mail from your 
computer.

Ce courriel renferme des renseignements privilégiés, privés, exclusifs ou 
confidentiels et est destiné uniquement à l’usage de la personne à laquelle il 
est adressé. S’il ne vous est pas destiné ou si vous n’avez pas la 
responsabilité de le remettre à son destinataire, sachez que toute diffusion, 
distribution ou reproduction en est strictement interdite. Si vous avez reçu ce 
courriel par erreur, veuillez en informer l’auteur, en indiquant dans le champ 
«Objet :» la mention «Courriel reçu par erreur», et le supprimer immédiatement.


[Non-text portions of this message have been removed]



------------------------------------

...
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:
    [email protected] 
    [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/

Reply via email to