Non PO workflow

Hello,

We are trying to come up with a workflow for non-PO invoice approval process within Lawson using Inbasket. Curious what others are doing? Do you have an electronic approval process in place or are invoices being scanned and emailed to end users for approvals? Do all invoices require a PO? Any feedback is appreciated.

Thank you,

Andrea Silva

Find more posts tagged with

Infor Lawson Financials Group - Discussion

Comments

unknown

Our invoice approval process occurs in our document imaging system - OnBase.

tina-cosgrove

MaryBeth, how does that work? Is the invoice entered into AP20 or just scanned using OnBase? I believe they came in a few years ago, but I was not involved in the process at the time.

jreese

We also use a document imaging system to handle our invoice approval but we are using Ascend. The invoices are scanned or electronically copied into Ascend and all routing and approvals are done before they are entered into Lawson. EDI invoices are handled through MA540, but if they do not match then the invoices are moved into Ascend where to be worked.

plancor

We use integrations between Lawson and Laserfiche. The user enters the invoice on AP20. AP20 has a design studio added button that when clicked, pulls values off of the AP20 screen as indexes and brings up the Laserfiche import window pre-populated with the index values. The user then imports the invoice document and a workflow starts in Laserfiche. The Laserfiche workflow uses AGS calls to AP40 to put the invoice on hold. When routing is complete in Laserfiche, the Laserfiche workflow again does an AGS call to AP40 to release the invoice from hold.

For POs, we also have a Lawson workflow that runs nightly to create PDFs of all POs created that day and move them to the Laserfiche server. There is another Laserfiche workflow that picks up the PO PDFs and files them.

unknown

I don't know all the details. Invoices are scanned into OnBase and entered into Lawson. Much of the indexing in OnBase is done via an AP20 "screen scrape" so that AP staff do not need to duplicate entry between systems. A hold code is entered in Lawson to not allow payment until all approvals are received. Approvals are routed through OnBase and a detailed audit of activity (view, approve, add note, etc.) is easily available in OnBase. If you are considering this option and want to schedule a call with our users and other staff that support the OnBase product, we would welcome a call.

johannes-bade

We also use OnBase - but do the coding the other direction. The end users code in OnBase using a Unity Form, then route for approval and export the file to Lawson. The OnBase keywords are imported using the AP520 and the MA540.

Copyright © 2025 Infor. All rights reserved.