Agreement Card
What Is an Agreement?
An agreement is a commercial or incentive contract based on actual sold or purchased quantities. You can create agreements with your customers, vendors, or employees.
An agreement is made of 4 parts.
1 — General
This is the header section of the Agreement Card. It defines the scope and validity of the agreement.
| Field | Description | Mandatory |
|---|---|---|
| Agreement No. | Agreement number, defined by the number series set up in Commissions & Rebates Setup. | Yes |
| Type | Sales or Purchase. Defines whether the agreement is calculated on sales or purchase entries. | Yes |
| Starting Date | Starting date of the agreement. Only entries on or after this date are included in the agreement. | Yes |
| Ending Date | Ending date of the agreement. Only entries on or before this date are included in the agreement. | Yes |
| Entry Period | Date formula defining how entries are grouped within the agreement. | Yes |
| Description | General description for the agreement. | No |
| Salesperson / Purchaser Code | Informational. Identifies the salesperson or purchaser who negotiated this agreement. | No |
| Your Reference | Informational. Agreement reference for your trading partner. | No |
| External Reference | Informational. External reference for the agreement. | No |
| Companies Included | Displays the number of companies included in the agreement. In a multi-company environment, this allows an incentive contract to span sales across different companies. If no company is specified, this defaults to 1 (current company) when the agreement is released. | Yes |
| Status | Defines the current state of the agreement. See the Status Values table below. | Yes |
| Sending Date | Informational. Date the agreement was sent to the partner. | No |
| Signing Date | Informational. Date the agreement was signed with the partner. | No |
| Agreement Category | Agreement attribute category. Populated by default from the Commissions & Rebates Setup. | No |
Status Values
| Status | Description |
|---|---|
| Open | Agreement is being set up and is not yet operational. Evaluation cannot be performed. |
| Released | Agreement is active and can be evaluated. |
| Cancelled | Agreement has been cancelled. Evaluation cannot be performed. Cannot be reopened. |
| Closed | Agreement is closed. Evaluation cannot be performed. Cannot be reopened. |
ℹ️ Note: Only Released agreements can be reopened. Cancelled and Closed agreements cannot be reopened.
2 — Agreement Lines
This section defines the calculation targets and methods for the agreement. You can define as many lines as needed. Within each line, you can also define multiple target levels.
| Field | Description | Mandatory |
|---|---|---|
| Description | General description for the agreement line. | No |
| Distribution Base | Defines the base on which the target or incentive is calculated. Options are: Amount, Quantity, Quantity (Base) (in base unit of measure), or Net Weight (requires net weight to be set on the item card). | Yes |
| Distribution Base Period | Defines whether the target is measured per period (as defined by the Entry Period) or cumulatively over the entire contract period. | Yes |
| Computation Mode | Defines how the calculation is performed. Options are: Amount (fixed amount when the target is reached), Unit Amount (amount multiplied by the number of units), or Percentage (percentage of the base amount). | Yes |
| First Target Level | Displays the first target level, expressed in the Distribution Base unit. Multiple target levels can be defined by clicking this column. | Yes |
| First Value | Displays the value applied (using the Computation Mode) when the target level is reached. | Yes |
| Detailed Values Amount | Displays the current evaluation of the agreement in local currency (LCY). This is a calculated field. | — |
| Document Entry Amount | Displays the total amount already posted in the General Ledger (in LCY). This is a calculated field. | — |
| Balance Amount | Calculated as Detailed Values Amount minus Document Entry Amount. Represents the remaining amount to be paid. | — |
| Base Value | Displays the total base amount consolidated from all detailed value entries associated with this agreement line. Hidden by default. Can be added to the view using the Personalize feature. | — |
💡 Tip — Displaying the Base Value column: The Base Value field is not visible by default on the Agreement Lines subform. To display it, use the Personalize option on the Agreement Card page and add Base Value to the Agreement Lines subform. This is useful when you need to verify the aggregated base amount used as the foundation for rebate or commission calculations.
3 — Included / Excluded
This section defines which sales or purchase entries are within the scope of the agreement. At least one Included/Excluded line is required for the agreement evaluation to work correctly.
| Field | Description | Mandatory |
|---|---|---|
| Type | Included: defines references that should be included in the agreement scope. Excluded: defines references that should be excluded. | No |
| Reference | The agreement can filter on Customer, Vendor, Item, Value Entry, or Salesperson/Purchaser. All fields of the selected reference entity are available for filtering. | Yes |
| Table Filter | Click the lookup to open the table filter window. This displays all fields of the reference entity, enabling you to build complex filter conditions. If no filtering is required, enter * in the first displayed field to include all entries. |
Optional (mandatory if Treeview Level is empty) |
| Treeview Level | Allows filtering based on the Treeview structure (see the Entity Treeviews app for more details). Not available when using Value Entry as the reference. | Optional (mandatory if Table Filter is empty) |
ℹ️ Note: When using Treeview-based filtering, ensure that the user has the appropriate Entity Treeview permissions set up. See the Commissions & Rebates Setup page for details.
4 — Payment
This section defines how the agreement payment is created and posted.
| Field | Description | Mandatory |
|---|---|---|
| Blocked for Payments | When checked, no payment can be created for this agreement. Default is unchecked. | — |
| Payment Type | Can be None, Customer, Vendor, or Employee. Default is None, meaning no payment can be created. | Yes |
| Payment To No. | Only visible when Payment Type is Customer, Vendor, or Employee. Identifies the recipient of the payment. | No |
| Payment Period Details | When checked, one payment line is created per agreement period, per agreement line. Default is unchecked. See note below. | — |
| Payment Periodicity | Date formula used when triggering payment creation. Determines how frequently payments are expected. | Yes |
| Last Period Paid | Automatically updated when a payment is created. Used together with Payment Periodicity to evaluate the next payment period. | Yes |
| General Product Posting Group | Used when creating payments for Customer or Vendor to organise General Ledger posting. | Yes (when Payment Type is Customer or Vendor) |
| VAT Product Posting Group | Used when creating payments for Customer or Vendor to organise VAT or Sales Tax posting. | Yes (when Payment Type is Customer or Vendor) |
💡 Tip — Payment Period Details: Enabling Payment Period Details causes the payment document to include one line per calculation period, making it easier to trace which period each amount relates to. When this option is active, the period range is shown directly on each individual rebate line in the generated document, rather than in a global comment at the header level. See the Creating Payments page for full details on document structure depending on this setting.
Agreement Attributes
On the Agreement Card, you can manage attribute values for the agreement in the Agreement Attributes section of the page.
You can:
- Add new attribute values.
- Update existing attribute values.
The Agreement Attributes Factbox on the right-hand side of the Agreement Card displays a summary of the current attribute values assigned to the agreement.