Non-PO Invoice Processing in Infor SyteLine AP Automation
Processing Non-PO invoices in Infor SyteLine? Nimbello makes it easy with automated approval groups and GL coding. In this video, you’ll learn how to:
🔹 Assign invoices to approval groups (by person, dollar amount, or sequential order)
🔹 Auto-route invoices based on vendor, OCR data, or historical approvals
🔹 Apply hierarchical GL coding while ensuring totals match
🔹 Handle approval authority limits so invoices move smoothly through the queue Save time and reduce errors with automated Non-PO invoice approvals in SyteLine!
Transcript
The way the non-PO process works is through approval groups.
-
The groups can be a single person or multiple people.
-
The groups can be assigned by dollar amount—each person has a limit.
-
The groups can also be ordered, meaning everyone in the group (whether it's one person or 100) must approve the invoice.
When the invoice comes in, it does not have a purchase order number.
-
We are OCR-ing the header and total amount.
-
When this data enters the workflow, the invoice can be auto-assigned to an approval structure.
-
Auto-assignment can be based on:
-
Information from the OCR.
-
The group assigned to the vendor.
-
Historical invoices—if the last four invoices went to the same group, the next one will follow.
-
Or, it can stop with AP, and AP can assign it manually.
-
When you go into Details, your Header Section will look the same.
-
You have your invoice with all backup details.
-
You have your header and address.
-
You now have approval groups that can be assigned.
-
These approval groups can be configured however you choose.
You also have GO Coding:
-
GO Coding can be set up with six hierarchical segments.
-
Example:
-
You can’t choose a department or cost center without first selecting an account.
-
If I only have one option, I am limited to that choice.
-
If I choose Account One, I now have multiple options.
-
-
I can assign the wrong GL code, but I can’t create a GO Code that does not exist in Plex.
You can also have three non-hierarchical segments for things like:
-
Projects
-
Tax accounting
-
Other additional segments
These extra segments can be entered with GL data, but they are not required.
When you GL code, the total of the GO Coding must match the total invoice amount.
-
If the totals don’t match, the invoice must return to AP.
-
The user cannot change the invoice total.
-
The user cannot give final approval without the totals matching.
-
AP must adjust the total, and then the user can finalize coding and approval.
If the invoice is within the user's approval authority, they will see a Final Approval button.
If it is not within their approval authority:
-
They will see an Approve button.
-
The invoice will automatically move to the next person in the approval queue.
AP does not have to manage this manually—there’s no need to check whether it went to the CEO, for example. The workflow handles that automatically.
Related articles: How to approve a NonPO Invoice