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.
Why companies are hesitant about AI in ERP
Predictive maintenance: how to turn SMEs into smart factories
RPA in the ERP environment: increasing efficiency through digital process assistants
Generative AI in ERP: How LLMs are changing the role of ERP systems
Preparing the ERP future with APIs and microservices
