Daily Archives: August 2, 2010

You Say You Know How To Do A Make-vs-Buy Analysis. Are You Sure?

Should you make or should you buy? It’s a difficult question that requires a detailed analysis. Consider the example of a car engine. Do you source each major assembly — the engine, the frame, etc.; or do you source sub-assemblies — the carburetor, the fuel injector, etc; or do you source component parts — the throttle body, the choke pull-off, etc.; and so on. Do you build the final product in house from the major assemblies, or do you have a first tier supplier do it, or do you have one first tier supplier assemble the major assemblies from the sub-assemblies and send those assemblies to another first tier supplier who will assemble the car, or do you chose one of a thousand other supply chain models that can also get the job done?

The figures below hint at the complexity that needs to be considered to truly arrive at a best solution. The best, and most cost-effective, scenario will depend on the particular strengths and cost efficiencies of each supplier in the supply chain.

Engine Complexity

The only true way to find the best, and most cost-effective, scenario is by way of decision optimization with integrated make-vs-buy analysis capability that can span a multi-level Bill of Materials (BOM). While most SSDO (strategic sourcing decision optimization) platforms do not yet support this capability, it is a good bet that most of tomorrow’s will. To find out what other capabilities are forthcoming in the world of decision optimization, visit BravoSolution‘s website, fill out a short 8-field registration form, and receive your free, exclusive, copy of The Future of Optimization, a new Sourcing Innovation white-paper with groundbreaking insight on eight directions that strategic sourcing decision optimization is likely to take in the decade ahead.

Or, fill out the quick-request form below:

Request The Future of Optimization










Share This on Linked In

A Hitchhiker’s Guide to e-Procurement: Invoices, Part II

Mostly Harmless, Part XI

Previous Post

In the last post, the invoice was defined as well as some of the associated data requirements. This post will address the associated challenges with invoice processing, some associated best practices, and the benefits that could be expected from an appropriate e-Procurement solution that was flexible and efficient in its processing of invoices.

Common Challenges

  • Purchase Order Partitioning

    The line items on the invoice can relate to one or more purchase orders … but which items go with which purchase orders? If an invoice is for a large shipment of hundreds of line items, this can be a challenge.

  • Billing Validation

    Were all of the items ordered? Were they received in acceptable condition? Are they at contracted or otherwise agreed to rates? Do any discounts apply? Are there early payment discounts to be taken advantage of?

  • Duplicate Detection

    Is this invoice unique? Is each line item a unique billing against received goods?

Best Practices

  • Automatic Acceptance / Import

    The system should be capable of automatically receiving invoices from suppliers and automatically accepting them (conditionally) if no reason for automatic rejection is found.

  • Automatic Uniqueness Validation

    The system should automatically match each line item of the invoice against the indicated and/or outstanding purchase orders and automatically reject the invoice if it, or any part of it, is determined to be a duplicate of an already submitted, and (conditionally) accepted, invoice. This notice should automatically be sent to the supplier, along with the reason for rejection.

  • Automatic m-Way Matching

    As soon as an invoice is received, it should be matched against any and all relevant goods receipts, purchase orders, and contracts to make sure that all goods were ordered, received, and billed at contracted rates. If unacceptable errors are found, the invoice should be automatically rejected. If only minor (billing) errors are found, the invoice should be accepted with modifications. If one or more items are under dispute, the invoice should be conditionally accepted and a note made that it can not be paid automatically until the dispute is resolved and that manual intervention will be required if this resolution does not occur before the due date. If one or more line items can’t be matched, the invoice needs to be flagged for manual review.

Potential Benefits

  • Reduced Overspending

    Automatic uniqueness validation insures that duplicate payments are not made, automatic m-way matching prevents overpayments, and automatic flagging of invoices under disputes prevents payments for unacceptable merchandise.

  • Faster Payments

    Invoices that are determined to be problem free can be queued for payments according to the payment terms. Automatic payments can prevent interest charges or reduced goodwill on the part of the supplier.

  • Greater Savings

    The prevention of duplicate payments, overpayments, and payments for goods not yet accepted, the ability to take advantage of early payment discounts, and increased supplier goodwill all contribute to greater savings.

Once the invoices are accepted, it is time for final reconciliation of (conditionally) accepted invoices and invoices that are marked for manual reconciliation (due to one or more problems that are not cause for automatic rejection), which is the subject of the next post.

Next Post: Reconciliation, Part I

Share This on Linked In