28 apr

tolerance days

Versino Financial Suite

tolerance days In SAP Business One, you specify how many days a due date or delivery date can be exceeded without triggering a follow-up process (dunning run, MRP re-scheduling). You thereby define a pre-determined grace period between the target date and the point at which the system or user should intervene.

Context

In the receivables and payments area, tolerance days are part of the payment terms.Administration → Definition → Business partners → Terms of payment. Example: Payment term 30 days, tolerance days 5 → a payment on the 35th day is not yet considered overdue, even if the actual due date has already passed. The dunning system takes this buffer into account and only sends reminders when the due date + tolerance has been exceeded. In the planning area, article master data has the field tolerance days (OITM.ToleranDayThis is where you set how many days an open order or goods receipt can deviate from the planned date before MRP reports the demand as late and generates a replenishment proposal. In both cases, tolerance days reduce unnecessary activity: fewer reminders for minor payment overruns, fewer MRP alarms for documents that deviate only slightly from the target date.

Demarcation

tolerance days are not identical to Bank statement, which define the period during which a cash discount is permissible, and they are also not Waiting days or Replenishment days, which represent the normal lead and delivery times. In accounting, tolerance days have no effect on the actual due date of a receivable: they only shift the reminder date, not the start of default according to the German Civil Code (BGB) – this is independent of tolerance days and can vary in case of dispute.


AI in everyday work: Person starts with their own task instead of the learning pile

AI in everyday work: Here's how to find the right start

Anyone who wants to use AI in their daily work is familiar with this: You read an article about prompts. A new model appears in it ...
AI-SHOP

AI assistant meets SAP Business One: Two paths out of the Versino AI shop

AI assistants like Claude or Copilot write emails, compile documents, and explain technical terms. But when you ask them about the open-source code...
SPRINT & SWIRL

Sprint and Swirl: How an AI agent divides work and learns from trials

This series deals with artificial intelligence in conjunction with SAP Business One. It takes a close look at fundamental AI principles...
LATS

LATS: Considering several paths simultaneously with AI — and the availability check in SAP B1

This series focuses on artificial intelligence in conjunction with SAP Business One. Not as a collection of product announcements, but as...
ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Wird geladen …