28 apr

tolerance days


E-invoicing in Germany: How to implement the obligation with SAP Business One

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.


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 ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: AI hype or what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Wird geladen …