Accounts Payable for Dynamics 365 Business Central
Every vendor document in the AP mailbox is read overnight and matched to Business Central’s open purchase orders and receipts. Your team imports what’s right as a purchase invoice and chases only what isn’t.
Accounts payableUpdated Oct 202620 ERPs
See it work on Business Central.
Click through the steps. Fictional data, in Business Central’s terms; the real thing runs on Business Central.
Read overnight: vendor, invoice number, PO, lines, total.
The problem, as it happens in Business Central.
Vendor invoices arrive as PDFs, photos and the odd spreadsheet statement, and the AP desk retypes them, finds the PO in Business Central, finds the receipt, and pulls the signed delivery ticket from the attachments on the record to staple behind. Most of them match. All of them take the same time.
The ones that don’t match are the ones that matter, and they’re buried in the pile: a quantity short on the receipt, a price off the PO, a statement line nobody can place. By the time someone emails the vendor, the discount date has passed.
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 Business Central
Vendor, PO, receipt and amounts, line by line against what Business Central has. Any figure Business Central 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 Business Central the way they always have, as a purchase invoice. The signed delivery ticket is appended behind the invoice as one PDF, and a person imports or keys the voucher.
How it connects to Business Central.
Lunica reads Business Central’s open purchase orders, receipts, vendor file and AP subledger through Business Central’s API, under a user that can only read, and the AP mailbox and scan share for the documents themselves. Each document is matched to its PO and receipt line by line. Figures Business Central 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.
Nothing is posted to Business Central on its own. A matched invoice goes back as a purchase invoice, imported or keyed by your team, and Business Central matches it to the receipt as it always has. Vendor questions are drafts until a person sends them. The signed delivery ticket from the attachments on the record is appended behind the invoice as one PDF, the file the AP desk used to assemble by hand.
What a week looks like.
- Clean invoices stop costing time.
- Every exception says what’s wrong and by how much.
- Delivery tickets attach themselves.
- Statements reconcile line by line against Business Central’s subledger.
Questions
Does Lunica post vouchers to Business Central?
No. The board tells you what’s right. A matched invoice becomes a purchase invoice; your team imports or keys it, and nothing lands in Business Central without a person.
What about EDI invoices?
Marketplace EDI invoices are fetched as structured data, never read by a model, and matched to Business Central by invoice number and PO.
Do vendor emails go out automatically?
Never. Vendor questions are drafts until a person sends them.
How accurate is the reading?
Figures Business Central can confirm are trusted. Figures it can’t are read by two independent models and only agreement is accepted; anything else waits in Issue identified for a one-click pick.
What about expense invoices with no PO?
Vendors you tag as expense skip the PO match and go straight to coding review.
What happens to the scanned delivery tickets?
They keep flowing into the attachments on the record as before. Lunica reads them and pairs each ticket with its invoice; the archive keeps working exactly as it did.
Does it need a server?
Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server, set up and maintained by Lunica. It reads Dynamics 365 Business Central through Business Central’s API, under a user that can only read. There is no inbound connection from outside your network.
What does Lunica read in Business Central?
The customer card, open items and terms, purchase orders and receipts, the item card, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Business Central?
Nothing lands in Business Central without a person. What belongs in Business Central goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the attachments on the record. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Accounts Payable is written for every system on the list. You’re reading the Business Central version.
Lumber and building materials
Wholesale distribution
General business
- Dynamics 365 Business Central
- NetSuite
- Sage 100
- QuickBooks Enterprise
- Acumatica
- SAP Business One
- Epicor Kinetic
Another system? Tell us which →
See it on your Business Central data.
Thirty minutes. We walk the workflow on Business Central data, then map it to yours.