0:07 — Where AP costs actually sit — The presenter frames data extraction and validation as the largest cost in accounts payable and the place where customers see the biggest return. Nimbello is introduced as a suite that collects, digitizes, processes, and routes invoices, then integrates with the ERP, with strong adoption in the Plex and Infor SyteLine communities and integrations with about 30 ERPs overall. 0:54 — Questions that reveal AP gaps — Instead of reading the slide, the presenter poses diagnostic questions: whether AP can scale without added headcount, how many invoices sit unapproved in inboxes, whether late or duplicate payments have happened, confidence in coding accuracy, and visibility into invoices nearing their due dates. 1:48 — Customer spotlight and product scope — Lakewood is described as a customer of about three years that processes over 100,000 invoices per year and has grown to 14 sites, with work focused on both PO and non-PO invoices. The capability list is then laid out: AP inbox collection, digitization, PO item pairing and matching, routing and approvals, and two-way ERP integration. 3:16 — Demo begins: the My Tasks page — The demo starts on a demo site with sample data. After login every user lands on the My Tasks page, which tracks invoices so they reach the right person; Nimbello regularly receives vendor, PO, and warehouse receipt data from the ERP and aims to stay touchless, stopping invoices only when they fall outside client-specific tolerances. 5:10 — Task queues and security — The tiles on My Tasks are security-based, so a non-PO approver sees fewer than an AP specialist. Queues covered include my directed-to tasks for invoices with an identified issue, priority vendor queues, a multi-PO queue for invoices covering more than one purchase order, non-PO invoices, invoice verification, and ready-to-export for completed invoices heading to the ERP to create a voucher. 7:32 — Non-PO approval groups: limited — In setup, non-PO approval groups are shown. A limited group routes by invoice dollar amount across configurable thresholds, with defaults of 100, 500, and 1,000, and can assign one person or group to review and general-ledger-code the invoice regardless of amount before it escalates until someone has enough authority to give final approval. 9:25 — Ordered groups and group automation — An ordered group sends the invoice through a fixed sequence of approvers every time rather than by dollar amount. Default approval groups can be set on a vendor record for recurring bills such as freight or utilities, and Nimbello can learn a vendor's group from the last three invoices and apply it automatically until someone changes it. 11:08 — Searching for invoices — The search invoice page addresses the difficulty of tracking down invoices in paper files or email threads. Searches can filter by vendor number and date range and return vendor details, invoice and PO numbers, PO totals, import date, export status, current directed-to person, status, time since last action, and payment information from the payments module. 13:37 — Divisions and invoice source — Division functionality changes how the site looks and how security works for companies with multiple locations, letting plant users see only their own division while AP specialists get a broader view. The record also shows the invoice source, which may be OCR, EDI, or cXML, plus a view invoice image option. 14:45 — Attendee question on hold reasons — An attendee asks whether hold reasons can be seen from the search invoice function. The answer is that hold reasons and notes appear on the separate easy page search — examples shown include a purchase order not found in the data, a price variance, and multiple quantity matches on receiving — and that a hold reason column can likely be added to search invoice but appeared disabled on the demo site. 15:52 — Invoice details, headers, and images — Clicking view on a queue opens the PO invoices that stopped in workflow with their hold reasons listed. The invoice details page shows header and vendor or pay site data with field-level security, save header changes, a switch between non-PO and PO type, an open-edit mode for administrators, and both a pop-out and inline image viewer that help when working long invoices across monitors. 18:38 — Comment log and directing invoices — Totals, subtotal, self-assessed tax, and the comment log appear below the header. The log date-stamps every system and user action, comments can be emailed to a named user or left in the log alone, and the directed-to control reassigns the invoice into another person's queue while also recording a comment. 20:30 — Audit trail, navigation, and attachments — The comment history shows each workflow action, who took it, who the invoice was directed to next, any emails sent, and the resulting status, including examples of a price variance and a hold for an additional tax charge. Previous and next buttons cycle through the queue or search results the invoice was opened from, and an additional documents section holds the original invoice image plus uploaded supporting documentation.

Home / Resources / Webinars

Demo: Nimbello AP Automation for PLEX and Infor SyteLine

Key takeaways

Nimbello is an AP automation suite that collects, digitizes, processes, and routes invoices, then integrates two-way with the ERP; it is used heavily with Plex and Infor SyteLine but has been integrated with roughly 30 different ERPs.
The presenters said the largest cost in AP is extracting and validating invoice data, which is where they expect customers to see the biggest return.
A customer example, Lakewood, has been on Nimbello about three years, processes over 100,000 invoices per year, and has grown from a smaller number of sites to 14 sites across both PO and non-PO invoices.
The 'My Tasks' landing page splits work into security-controlled queues — directed-to tasks, priority vendors, multi-PO invoices, non-PO invoices, and ready-to-export — so users only see what they are responsible for.
Non-PO approvals use configurable approval groups, either 'limited' (routing escalates by invoice dollar amount) or 'ordered' (a fixed sequence of approvers regardless of amount), with default groups assignable per vendor.
Invoices are found through a robust search invoice page and a separate 'easy page' search; the easy page shows hold reasons such as PO not found, multiple quantity match, or an unreviewed freight charge.
The invoice details page holds header edits, inline and pop-out image viewers, a full date-stamped comment log, and a directed-to control that reassigns an invoice and emails the new owner.

Overview

This session is a product demonstration of Nimbello, an accounts payable automation suite, presented with emphasis on Plex and Infor SyteLine environments. The opening framing is that the larger cost in AP is not the payment itself but extracting and validating invoice data, and that this is where customers see the biggest return. The suite is described as covering invoice collection through an AP inbox, digitization, PO line item pairing and matching, routing and approvals, and a two-way integration with the ERP. While Plex and SyteLine are the communities where the presenters report the most traction, they noted that Nimbello has been integrated with about 30 different ERP systems over the years.

The business case was posed as a set of diagnostic questions rather than a feature list: whether the current AP process can scale without adding headcount, how many invoices are sitting in someone's inbox awaiting approval, whether late payments to strategic suppliers or duplicate payments have occurred, how confident the organization is that every invoice is coded correctly, and how much visibility exists into invoices approaching their due dates. A customer spotlight covered Lakewood, which has used Nimbello for around three years, processes over 100,000 invoices annually, and has expanded to 14 sites, with the project focused on both PO and non-PO invoice handling.

The demo, run on a populated demo site, starts at the 'My Tasks' page that every user lands on after login. Its tiles are security-driven, so a non-PO approver sees fewer queues than an AP specialist or admin. The queues shown include 'my directed to tasks' (invoices flagged with an issue the logged-in user is responsible for, such as coding, approval, or a price variance), priority vendor queues for a short list of vendors a company wants seen first, a multi-PO queue for invoices spanning more than one purchase order, non-PO invoices, invoice verification, and 'ready to export', which holds completed invoices due to go to the ERP and create a voucher. The presenters stressed a touchless goal: Nimbello receives vendor, PO, and warehouse receipt data from the ERP on a regular basis, and invoices only stop when they fall outside the tolerances configured for that client, such as a freight tolerance.

Setup was demonstrated through non-PO approval groups. In a 'limited' group, routing is driven by invoice dollar amount across configurable thresholds — the defaults shown were 100, 500, and 1,000 — and the invoice escalates down the list until it reaches someone with sufficient approval authority; the first person can be assigned to review and general-ledger-code the invoice regardless of amount, which is often given to an AP person because approvers may not know the codes. An 'ordered' group instead sends the invoice through a fixed sequence of people every time, independent of amount. Approval groups can be set as a default on a vendor record, which suits recurring bills like freight or utilities, and there is automation that remembers when the same approval group has been applied to a vendor's last three invoices and starts applying it automatically until someone changes it.

The rest of the demo covered finding and working invoices. The search invoice page supports queries such as all invoices for a vendor number over a date range and returns vendor number and name, invoice number, PO number and totals, import date, export status, current directed-to person, status, time since last action, division, source (OCR, EDI, cXML), and payment information from the payments module. An attendee asked whether hold reasons are visible in search invoice; the answer was that they appear in the separate 'easy page' search and that a hold reason column can likely be added to search invoice but appeared disabled on the demo site. The invoice details page shows header data and vendor or pay site information with field-level security controls, view and inline image viewers useful on multiple monitors, a button to switch an invoice between non-PO and PO type, and an open-edit mode for administrators. Below that sit invoice totals, self-assessed tax, and a comment log that date-stamps every system and user action; comments can be posted to the log alone or emailed to a specific user, and the directed-to control both leaves a comment and reassigns the invoice into another person's queue. Previous and next buttons cycle through whatever queue or search result set the invoice was opened from, and an additional documents section holds the original invoice image plus any supporting documentation a user uploads.

Chapters

0:07 — Where AP costs actually sit — The presenter frames data extraction and validation as the largest cost in accounts payable and the place where customers see the biggest return. Nimbello is introduced as a suite that collects, digitizes, processes, and routes invoices, then integrates with the ERP, with strong adoption in the Plex and Infor SyteLine communities and integrations with about 30 ERPs overall.
0:54 — Questions that reveal AP gaps — Instead of reading the slide, the presenter poses diagnostic questions: whether AP can scale without added headcount, how many invoices sit unapproved in inboxes, whether late or duplicate payments have happened, confidence in coding accuracy, and visibility into invoices nearing their due dates.
1:48 — Customer spotlight and product scope — Lakewood is described as a customer of about three years that processes over 100,000 invoices per year and has grown to 14 sites, with work focused on both PO and non-PO invoices. The capability list is then laid out: AP inbox collection, digitization, PO item pairing and matching, routing and approvals, and two-way ERP integration.
3:16 — Demo begins: the My Tasks page — The demo starts on a demo site with sample data. After login every user lands on the My Tasks page, which tracks invoices so they reach the right person; Nimbello regularly receives vendor, PO, and warehouse receipt data from the ERP and aims to stay touchless, stopping invoices only when they fall outside client-specific tolerances.
5:10 — Task queues and security — The tiles on My Tasks are security-based, so a non-PO approver sees fewer than an AP specialist. Queues covered include my directed-to tasks for invoices with an identified issue, priority vendor queues, a multi-PO queue for invoices covering more than one purchase order, non-PO invoices, invoice verification, and ready-to-export for completed invoices heading to the ERP to create a voucher.
7:32 — Non-PO approval groups: limited — In setup, non-PO approval groups are shown. A limited group routes by invoice dollar amount across configurable thresholds, with defaults of 100, 500, and 1,000, and can assign one person or group to review and general-ledger-code the invoice regardless of amount before it escalates until someone has enough authority to give final approval.
9:25 — Ordered groups and group automation — An ordered group sends the invoice through a fixed sequence of approvers every time rather than by dollar amount. Default approval groups can be set on a vendor record for recurring bills such as freight or utilities, and Nimbello can learn a vendor's group from the last three invoices and apply it automatically until someone changes it.
11:08 — Searching for invoices — The search invoice page addresses the difficulty of tracking down invoices in paper files or email threads. Searches can filter by vendor number and date range and return vendor details, invoice and PO numbers, PO totals, import date, export status, current directed-to person, status, time since last action, and payment information from the payments module.
13:37 — Divisions and invoice source — Division functionality changes how the site looks and how security works for companies with multiple locations, letting plant users see only their own division while AP specialists get a broader view. The record also shows the invoice source, which may be OCR, EDI, or cXML, plus a view invoice image option.
14:45 — Attendee question on hold reasons — An attendee asks whether hold reasons can be seen from the search invoice function. The answer is that hold reasons and notes appear on the separate easy page search — examples shown include a purchase order not found in the data, a price variance, and multiple quantity matches on receiving — and that a hold reason column can likely be added to search invoice but appeared disabled on the demo site.
15:52 — Invoice details, headers, and images — Clicking view on a queue opens the PO invoices that stopped in workflow with their hold reasons listed. The invoice details page shows header and vendor or pay site data with field-level security, save header changes, a switch between non-PO and PO type, an open-edit mode for administrators, and both a pop-out and inline image viewer that help when working long invoices across monitors.
18:38 — Comment log and directing invoices — Totals, subtotal, self-assessed tax, and the comment log appear below the header. The log date-stamps every system and user action, comments can be emailed to a named user or left in the log alone, and the directed-to control reassigns the invoice into another person's queue while also recording a comment.
20:30 — Audit trail, navigation, and attachments — The comment history shows each workflow action, who took it, who the invoice was directed to next, any emails sent, and the resulting status, including examples of a price variance and a hold for an additional tax charge. Previous and next buttons cycle through the queue or search results the invoice was opened from, and an additional documents section holds the original invoice image plus uploaded supporting documentation.

Questions this webinar answers

Which ERP systems does Nimbello work with?

Nimbello has seen the most adoption in the Plex and Infor SyteLine communities, but it is not limited to those two systems. The presenters said Nimbello has been integrated with about 30 different ERPs over the years.

What happens to an invoice that arrives without any problems?

If everything lines up, the invoice comes into the system, gets tracked, has receipts attached to it automatically, and is sent to the ERP, which creates the voucher for payment. Invoices only stop for human attention when something falls outside the tolerances configured for that client, such as a freight tolerance or a price variance.

How do users know which invoices they personally need to work on?

After logging in, each user lands on a My Tasks page made up of queues. The most important is 'my directed to tasks', which holds invoices where an issue was identified and the logged-in user is the responsible party — for example an invoice needing general ledger coding, an invoice awaiting that person's approval, or a price variance. The visible queues are security-based, so a non-PO approver sees fewer than an AP specialist or administrator.

How are non-PO invoice approvals routed?

Non-PO invoices route through configurable approval groups. A 'limited' group escalates by invoice dollar amount across thresholds you define — the demo defaults were 100, 500, and 1,000 — passing down the list until it reaches someone with enough approval authority for the final sign-off. An 'ordered' group instead sends every invoice through the same fixed sequence of people regardless of amount. A first reviewer can be assigned to general-ledger-code the invoice no matter the amount, which is often given to an AP person because approvers may not know all the codes.

Can approval routing be automated for recurring vendors?

Yes. A default approval group can be set directly on a vendor record inside Nimbello, which suits recurring bills such as freight or utilities so no one has to choose a group each time. There is also automation that watches invoice history: if the same approval group has been applied to a vendor's last three invoices, Nimbello remembers it and starts applying it going forward until someone changes it.

How do you find a specific invoice or see where it is stuck?

There is a search invoice page that supports queries such as all invoices for a given vendor number over a date range. Results include vendor number and name, invoice number, PO number and totals, import date, whether the invoice has exported to the ERP, who it is currently directed to, its status, how long since the last action, division, the source it arrived through, and payment information. A separate 'easy page' search shows notes and hold reasons — examples given were a purchase order not found in the data, a price variance, and multiple quantity matches on receiving. A hold reason column can likely be added to the search invoice page as well, though it appeared disabled on the demo site.

How can two people collaborate on a problem invoice?

Each invoice has a comment log that date-stamps every action taken by the system or by a user. A comment can be left in the log for anyone who later opens the invoice, or addressed to a specific user, in which case Nimbello also emails the address assigned to that person in the site. Separately, a 'direct to' control reassigns the invoice to another person so it appears in their directed-to queue, and it records a comment at the same time.

How is access to editing invoice fields controlled?

Field-level editing is security controlled and configured per client. Super users and AP administrators can be given the ability to edit fields such as the invoice number and PO number, while a buyer might be limited to changing only the PO number or the division. The presenters described the environment as being as controlled as the customer wants it to be, provided they specify the rules.

Table of Contents

Get A Demo:

Simple solutions. Powerful results. Seamlessly integrated.

Get a PairSoft Demo