Skip to content

Payables Outlook for Dynamics 365 Business Central

Every open voucher in Business Central, by week and by vendor, with the discount date beside it and thirteen weeks of cash out against expected collections. Read from Business Central; the paying still happens in Business Central.

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.

Payables outlook · read from Business Central at 6:10 am
Illustrative
Open AP$412,380118 vouchers · 41 vendors
Due this week$86,12023 vouchers
Discount still capturable$2,940on $147,000 if paid by date
Discounts lost last month$1,8607 vouchers · 3 vendors

Open AP, what’s due, what’s still worth paying early, what was lost. Each figure opens its vouchers.

1 / 4
Request a demoSee it for NetSuite →See it for Sage 100 →

The problem, as it happens in Business Central.

The AP board answers one question at a time: is this invoice right? Business Central’s open AP report answers another: what’s due. Nobody answers the ones the controller carries around all week. What is owed and when. Which discount dates are still worth money. What was lost last month and why. Whether what’s coming in covers what’s going out.

Those answers exist in Business Central. Getting them means exporting the open AP, pivoting by due date, remembering which vendors give one percent by the tenth, and doing it again next week.

How it works.

  1. 1

    Open AP, by week

    Every open voucher from Business Central, laid out by when it’s due, by vendor, with the discount date beside it.

  2. 2

    Discounts still worth taking

    Which invoices still carry an early-pay discount, what it’s worth, and the day it expires.

  3. 3

    What was lost, and why

    Discounts missed last month, by vendor, with the reason: paid late, paid on time to the wrong date, never on the terms you thought Business Central had.

  4. 4

    Thirteen weeks of cash

    Payables due against expected collections, week by week, with the controller’s own liquidity figure as the one thing the page lets you type. Paying is still done in Business Central.

How it connects to Business Central.

Lunica reads Business Central’s AP detail, vendor terms and payment history through Business Central’s API, under a user that can only read, and the same open-item read the collections workflow uses for expected collections. Vendor terms are read as Business Central has them, so a vendor on one percent by the twentieth of the following month is tracked to that date, not to a generic net.

Nothing is written to Business Central, and nothing is paid, approved or sent from the page on its own. It reads and organises; the one thing it stores is the controller’s own liquidity figure, on the Lunica server. Which vendors get paid this week is decided and keyed by your team in Business Central, as it always was.

What a week looks like.

  • Every figure opens the rows behind it.
  • Refresh reads Business Central now, not last night.
  • Any table exports to CSV for the people who still want the spreadsheet.
  • Benchmarks are labelled as benchmarks.

Questions

Does it write anything to Business Central?

No. It reads and organises. The one thing it stores is the controller’s liquidity figure, on the Lunica server.

Can it pay vendors or approve payments?

No. The team decides what to pay in Business Central. This page tells you what that decision costs.

Where do the collections numbers come from?

From the same read of Business Central as the collections workflow: open items aged on each invoice’s own terms.

Does it see vendors paid by check?

Yes. Payment history is read from Business Central, so paid late and paid to the wrong date both show up with the discount they cost.

How current is it?

As of the last read, shown on the page. Refresh reads Business Central again.

Can the owner see it without an Business Central login?

Yes. The page is Lunica’s, so anyone you enrol can open it. Each person sees the same figures from the same read.

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.

Payables Outlook is written for every system on the list. You’re reading the Business Central version.

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.

Request a demoBrowse workflows