Sage 100

 View Only
  • 1.  AP Automation with PO 3 way Match - need solutioning help!

    Posted 12-03-2021 20:04
    So..my client is going to use Medius Go for AP Automation including PO's.  Integration is via VI jobs.  The plan is PO's will be created in Sage, sent to Medius Go.  Then ROG will be done in Sage, then sent to Medius Go.  MG will do the Invoice Match and send back to Sage.
    1. Originally client was thinking to only send PO information to Medius Go as the product was received rather than sending up full PO at time of creation.  IE: PO is created with 10 lines, 1 gets received, the export would be only for the 1 line and quantity received.  That's how I built my 1st report.
    2. After a meeting with Medius Go the other day, the question came up about handling an Invoice received before product received and therefore Medius Go has no record of the PO/Line.  
    3. The way I understood it was if there is no PO Line to apply invoice to at time it's processed (because it hasn't been received, therefore PO/ROG hasn't been exported yet, it goes into a Hold and client would have to then match the Invoices Lines to the PO lines manually once the PO/ROG was sent to Medius Go.  Not a good solution considering it's supposed to be Automated!
    4. If I send the full PO upon creation, how do I handle changes to the PO?  If I use the Modified/Updated date, all the lines are going to re-export (vs just the fields that changed).  MG didn't like that idea either.

    Has anyone dealt with an AP Automation using VI Jobs and how are PO's, ROG's & ROI handled?
    Thanks in Advance
    #JustdotheworkinSage!




    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------


  • 2.  RE: AP Automation with PO 3 way Match - need solutioning help!

    Posted 12-03-2021 21:34
    I am not sure if PM is in play here and if during the use of VI jobs you will need to use VI exports.

    I have a customer on v2020 who just implemented PM and we think it breaks VI export functionality. They use Acupos which makes heavy use of VI Export jobs for the integration. As of now they are down with no easy workaround due to the reliance on VI export jobs ( which Acupos uses on some type of integration dashboard ).

    Just an FYI in case any of this is similar to your situation

    ---------------------------------
    Wayne Schulz
    Schulz Consulting
    860-516-8990
    ---------------------------------





  • 3.  RE: AP Automation with PO 3 way Match - need solutioning help!

    Posted 12-03-2021 21:50
    Thankfully no PM and I've been creating Crystal reports for the exports to accommodate the layout MG needs.

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------



  • 4.  RE: AP Automation with PO 3 way Match - need solutioning help!

    Posted 12-04-2021 14:53
    Isn't this a problem with MG's workflow? These are NOT issues unique to Sage 100, are they?

    MG apparently has no automated mechanism to handle invoices that don't precisely match the PO? Partial shipments, invoices arriving via email before UPS can deliver on 3-day shipment, multiple invoices per PO, and mismatching item quantity and cost are all common occurrences within Pareto's Real World. And yet MG simply kicks out those variances for manual processing? Maybe, but each of those cases is also a decision node, where the workflow should offer choices to the customer during setup about how they want to handle it. This is not a mature app.

    You should point these out to your customer and make sure they understand that Sage 100 can't magically cure weaknesses in the input source. You could also offer a small project to research and vet other AP Automation solutions to see if maybe their IT department bought the wrong tool.

    ------------------------------
    Jerry Norman
    At-Large BOD Member, 90 Minds
    Smartbridge Partners
    512.419.1444 x112
    ------------------------------