Skip to content

Credit Limit Reviews for Dynamics 365 Business Central

Every limit in Business Central checked nightly against the account’s exposure, pay history and growth, with a recommendation under your written policy. Your credit manager approves or holds, and the new limit is keyed into Business Central by a person.

CreditUpdated 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.

Limits · checked overnight
Illustrative
CustomerLimitExposureAvg days to pay12-mo volumeFlag
Harbor Point Builders$25,000$31,840.5028$412,300Over limit
Pine Hollow Contractors$15,000$13,210.0061$96,400Slowing
Cedar & Stone Framing$50,000$22,106.0024$538,900Within
Westfield Masonry$10,000$9,980.0044$71,200Due review

Exposure against limit, pay history and growth, for every account.

1 / 4

The problem, as it happens in Business Central.

A limit is set the day the account opens, from the application and a gut feel, and then it sits. Three years on, a framer is running twice the volume, pays on 30 EOM without fail, and bumps the limit every month, so the counter calls the credit desk and the limit goes up on the phone. The customer card in Business Central says whatever was last typed into it.

The other direction nobody tracks. The account whose balance has crept to three times what it was, paying slower every quarter, still has the limit it got when it was small. The Aged Accounts Receivable report shows the balance. It doesn’t show that the exposure has quietly outgrown the policy, and nobody reviews limits until something is already past due.

How it works.

  1. 1

    Exposure against limit, nightly

    Every account’s open balance, orders released but not yet invoiced where Business Central has them, and the limit on the customer card, read each night. Pay history and twelve months of volume sit beside it.

  2. 2

    A recommendation under your policy

    Raise, hold or lower, with the reason in your policy’s words: months on terms, days to pay, utilisation, growth. The numbers decide who gets reviewed; a model only writes the explanation.

  3. 3

    Your credit manager approves or holds

    The desk opens on accounts due a review, largest exposure first. Approve the new limit, change the figure, or hold and set a date to look again. Every decision is recorded with who and why.

  4. 4

    The new limit is keyed into Business Central

    An approved limit goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared. Until a person keys it, Business Central keeps the old one, and the review stays open on the desk.

How it connects to Business Central.

Lunica reads the customer card, open items and sales history through Business Central’s API, under a user that can only read, nightly: the limit as Business Central has it, the open balance, orders released but not yet invoiced where Business Central carries them, and twelve months of invoices and payments. Terms are read per account, so an account on 2% 10 Net 30 is judged on 2% 10 Net 30, not on a flat thirty.

Nothing is written to Business Central by Lunica and nothing is sent on its own. An approved limit goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared, and the review shows who keyed it and when. Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server; the recommendation and the decision live there, not in Business Central.

What a week looks like.

  • Every account with exposure past its limit is on the desk by morning.
  • Accounts that have earned a higher limit come up before the counter calls.
  • Each recommendation says why, in your policy’s words.
  • Every limit change has a name, a date and a reason behind it.

Questions

Does Lunica change limits in Business Central?

No. It recommends. Your credit manager approves, and the new limit goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared. Until then Business Central keeps the old one.

Where does the policy come from?

From you. Your credit policy is written down in plain English as a spec your admins edit, with history and revert. Each recommendation cites the lines it used.

What counts as exposure?

Open balance plus orders released and not yet invoiced where Business Central has them. The figures are read from Business Central each night and never stored.

Does it lower limits too?

It can recommend one. Lowering is a decision for a person, and nothing changes on the customer card until someone keys it.

Can we exclude house accounts?

Yes, by rule. House accounts, cash accounts and anything you name are left alone.

How often is an account reviewed?

Exposure is checked nightly. A full review comes up on the schedule your policy sets, when exposure crosses the limit, or when a person asks for one.

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.

Credit Limit Reviews is written for every system on the list. You’re reading the Business Central version.

See it on your Business Central data.

Thirty minutes. We walk the workflow on Business Central data, then map it to yours.