Accounts Payable for Epicor Eagle
Every vendor document in the AP mailbox is read overnight and matched to Eagle’s AP subledger and the PO receipt. Your team imports what’s right with the AP Assist file and chases only what isn’t.
Accounts payableUpdated Oct 202620 ERPs
See it work on Eagle.
Click through the steps. Fictional data, in Eagle’s terms; the real thing runs on Eagle.
Read overnight: vendor, invoice number, PO, lines, total.
The problem, as it happens in Eagle.
On Eagle, AP is a stack: the PDF from the vendor, the PO in Eagle, the receipt in MRV, the delivery ticket scanned into WebDocs, and the voucher keyed in by hand. The iNet match screen tells you Pass or Variance only after somebody has typed the invoice in.
The expense invoices have no PO at all, so they get coded from memory. The marketplace vendors send EDI invoices to the buying group’s portal, never to accounting, and those get downloaded one at a time.
It all works. It just takes the whole AP desk, every day, and the one percent by the tenth goes unclaimed while the pile is sorted.
How it works.
- 1
Documents come in overnight
One pass a night reads what landed in the AP mailbox: invoices, statements and credit memos, as PDFs, photos or spreadsheets. EDI invoices from your buying group’s marketplace come in the same way.
- 2
Each one is matched to Eagle
Vendor, PO, receipt and amounts, line by line against what Eagle has. Any figure Eagle can’t confirm is read twice, by two different models, and only agreement counts. A disagreement waits for a person.
- 3
The board sorts the work
Perfect matches sit in Ready to pay. Discrepancies land in Issue identified with the difference spelled out. Vendor questions are drafted; a person sends them, and the reply lands on the card.
- 4
Your team enters what’s right
Matched invoices go into Eagle the way they always have, as an AP Assist import file. The signed delivery ticket is appended behind the invoice as one PDF, and a person imports or keys the voucher.
How it connects to Eagle.
Lunica reads Eagle’s AP subledger, open purchase orders and receipts through the Eagle data warehouse, read-only. Each document from the AP mailbox is matched to its PO and MRV receipt line by line. Figures Eagle can confirm are trusted; figures it can’t are read by two models and accepted only when they agree. Marketplace EDI invoices are fetched as data and matched the same way.
Lunica never posts a voucher. A matched invoice becomes an AP Assist import file. Your team imports it in Eagle, under APA, Misc, Import AP Assist File, and Eagle matches it to the receipt in MRV as it always has. The scanned delivery ticket is appended behind the invoice as one PDF, the file the AP team used to assemble by hand.
What a week looks like.
- Clean invoices wait in Ready to pay with their import file.
- Issues say what’s off: a quantity short on the receipt, a price off the PO, a statement line Eagle can’t place.
- Vendor questions are drafted on the card; a person sends them, and the reply lands back on it.
- Expense vendors skip the PO match and go to coding review.
Questions
Does Lunica write to Eagle?
No. It prepares the AP Assist import file. A person imports it, exactly as they did with the files from the WebDocs scanner.
What about the iNet match screen?
Still yours. Lunica does the matching before the invoice is keyed, so most invoices arrive at iNet already right.
How do marketplace EDI invoices come in?
Fetched from the marketplace as structured invoices, never read by a model, and matched to Eagle by invoice number and PO.
What happens to the scanned delivery tickets?
They keep flowing into WebDocs as before. Lunica reads the scan share, pairs each ticket with its invoice, and never writes to the share.
What about expense invoices with no PO?
Vendors tagged as expense skip the PO match and go straight to coding review.
Does it read photos and spreadsheet statements?
Yes. PDFs, photos, and Excel or CSV statements rendered to text, reconciled line by line against the subledger.
The same workflow, on another ERP.
Accounts Payable is written for every system on the list. You’re reading the Eagle version.
See it on your Eagle data.
Thirty minutes. We walk the workflow on Eagle data, then map it to yours.