Skip to content
Penahak now runs hotels, restaurants and retail on one ledger.
Penahak

What CRM does not do

What CRM does not do in this release, and the behaviour worth knowing before you rely on it, with what to do instead.

  • CRM Troubleshooting
  • 4 min read
  • Updated October 20, 2026
On this page

This page says plainly what CRM does not do today, so you can plan around it.

Not in this release

Not availableWhat to do instead
Leads and campaignsThere are no leads or campaigns screens. Opportunities holds deals for customers already in Accounting
CRM quotationsCRM has no quotations of its own: Create quotation on an opportunity opens Accounting's sales quotation
Changing a customer's tier, account owner, relationship status, do-not-contact mark or CRM noteNo screen changes them; Customer 360 shows them as they are (Standard, Unassigned, Active unless set). The collector of an account is set on Collections. To mark a customer do not contact, or remove the mark, ask your Penahak contact
Changing the dunning ladderThe five stages are fixed (The dunning ladder and collection cases)
CRM workflows and CRM notification managementTheir permissions exist, but there are no screens for them
Changing credit limits or credit days in CRMThey are changed on the customer in Accounting (Customer details in Accounting that CRM uses)
Posting anything to the booksCRM posts no voucher. Receipts, credit notes and write-offs are made in Accounting; Written off on Collections closes the CRM work only

Credit control

  • The POS cannot ask for a credit release. A blocked POS credit sale must be paid now, or the customer's limit reviewed (Which sales are checked).
  • A recurring invoice held back by the credit check does not notify the approvers. Its pending release request waits in the Credit Desk's Release queue: look there regularly.
  • Sales orders have no credit-days rule. Only the credit limit and credit hold apply to orders, and they block an order only when your order settings block over-limit orders; otherwise they warn.
  • A release covers one sale of one person. A colleague cannot use it, and a second sale needs a second release (Credit releases: ask, decide, use).
  • Check a sale on the Credit Desk uses the balance of all branches and 0 days to pay, while the save uses the sale's branch and the invoice's due days (The Credit Desk).
  • Stop credit-blocked sales on save is one switch for the whole company: switched off, every block, on every sales screen, the POS and recurring invoices, becomes a warning (CRM settings and what each one does).
  • CRM is switched on for the whole company by your Penahak contact; a licence does not switch it on by itself (Get CRM ready for your company).

Collections and service

  • The nightly run does collections only: it judges promises, moves collection cases and expires releases. The dispute, renewal and recovery timers and the ticket scan run only when someone presses a button (The nightly run and the run-now buttons).
  • Promises are judged only by the nightly run. Between runs, a promise can still show Open although the money has arrived (Promises to pay).
  • A promise can be at most 180 days away. For a longer payment plan, record the next promise only after the previous one has been judged.
  • "At risk" on Service tickets means due within one hour. The At-risk window setting is used only by the ticket scan (Service tickets and document threads).

Screens and figures

Common questions

Can the POS ask for a credit release?

No. A blocked POS credit sale must be paid now, or the customer's limit reviewed.

How do I mark a customer do not contact, or take the mark off?

No screen does this in this release. Ask your Penahak contact.

Can I change the five dunning stages?

No. They are fixed, and there is no screen to change them.

Related guides

More in Troubleshooting