the Contract type In SAP Business One, defines how a framework agreement between companies and business partners is structured and processed in the system. It determines which document types are permissible as a reference, what quantity or value limits apply, and how subsequent documents can be automatically offset against the agreement.
Context
SAP Business One distinguishes between two principles: In the Article method The contract serves as an agreement to sell or procure a predefined planned quantity of certain items within a date range, with a fixed per-item price. When it comes to Monetary method instead, an overall budget is agreed; the specific items are not fixed but are priced via a price list with a discount. Furthermore, there is a Document typeLevel: article for stock items and service for services not managed in inventory (e.g. one-off consultancy). The contract type is specified in the framework agreementOOAT / Once and for all) is set and controls the behaviour upon copying to customer order, delivery and invoice. Via statuses such as Approved, Exposed, Finished Is the lifecycle controlled; evaluations show residual quantities or amounts and thus support call-off orders and forecasting.
Demarcation
The contract type is not identical to the Document type a single sales or purchase receipt and also not with the Type of business partner (Customer/Supplier/Lead). It differs from customer order, which documents a single transaction, and by the Service contract, which governs the processing of services (maintenance, support, warranty) based on the service module — there, the service contract type (Standard, Warranty, Custom) determines response times, covered items, and billing logic.
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
