Clever Credit can be driven through Origo Cloud Events, letting you ask about and act on your credit control data in natural language rather than navigating the pages yourself. You simply ask a question or request an action, and the matching Clever Credit operation runs in Business Central and returns the result.
The actions fall into two groups: Ask actions that read information, and Do actions that make a change. All amounts are in LCY unless stated otherwise, and each action respects the user's existing Clever Credit permissions and setup.
Before you start
The actions use your existing Clever Credit configuration, so make sure the following are in place.
| Credit Management Setup | The "Credit Control Setup" must be complete (Credit Mgt. Setup Complete enabled) so that credit checking and hold logic are active. Enable Calc. Credit Statistic if you want payment statistics and trends to be available. |
| Credit Controllers | Each user who releases documents needs a Credit Controller record linked to their User ID. The Credit Held Rel. Limit (LCY) sets the maximum document value that user may credit release; tick Credit Held Rel. Unlimited for no ceiling. |
| Customers | Customers should have a Credit Limit (LCY) and, where used, a Credit Controller Code assigned. See Customer Credit Status. |
Ask actions
Use these to get an up-to-date picture of your credit position. They only read data and make no changes.
| Customers over their credit limit | Lists customers whose current balance is above their credit limit, with the balance and the amount over the limit. You can narrow it with a minimum over-limit value or a credit controller. Example: "Which of my customers are over their credit limit right now?" |
| Customer payment statistics | Returns a credit snapshot for a customer: average days-to-pay, average overdue days, overdue balance, open and overdue to-dos, credit-held documents, and a recent-90-days vs previous-90-days trend that indicates whether payment behaviour is getting worse. Example: "What's the average days-to-pay for Adatum, and is it getting worse?" |
| Credit-held documents | Lists the sales documents currently on credit hold, including value, held reason, credit controller and over-limit/overdue values. You can set a minimum value to focus on larger documents. Example: "Show me everything on credit hold worth more than £10k." |
| Chase list | Returns your open Clever Credit to-dos prioritised for the day, including promised-payment due dates and held-entry indicators. By default it shows items due up to the work date; you can include future-dated items or filter by credit controller. Example: "What should I chase today?" |
Do actions
These make a change in Business Central. Each one records the result against the relevant customer or document so there is a clear audit trail.
| Release a sales document | Credit releases a sales document using your credit-controller authorisation ceiling. If the document value is above your Credit Held Rel. Limit (LCY), the release is refused and you are told you do not have permission, so you can escalate it. A document may be re-held automatically if the customer remains over their credit limit. Example: "Release sales order SO-1043 - I'm authorising it against my credit limit." |
| Log a promised payment | Records a promised payment against a customer and creates the follow-up to-do and interaction. If you name a document the promise is logged against that entry; otherwise it is logged against the first of the customer's open entries. If you don't give an amount, the outstanding balance of that entry is used. Example: "Log that Adatum promised to pay invoice 10245 by Friday and set me a follow-up." |
| Hold a customer's sales documents | Sets Credit Hold All Documents on the customer and puts their open positive sales documents (Quotes, Orders, Invoices and Blanket Orders) onto credit hold. You can supply a reason, which is recorded as a credit control interaction against the customer. Example: "Put all of the Sales Documents for Adatum onto credit hold as they've not made their promised payment." |
Note: the Do actions apply the same credit checks and authorisation limits as the equivalent actions in Business Central. For example, releasing a document still respects your authorisation ceiling, and a promised payment still creates the follow-up to-do that appears on your chase list. See Automating Interactions & To-Do's.