Enter a Set of Payment Terms for a Set of Contract Terms

You can enter payment terms for each invoice iteration type, or specific to credit notes, debit notes or demurrage/despatch invoices.

Because payment terms are specific to invoice types, Specify Invoice Iteration Types for a Set of Contract Terms before specifying payment terms.

Security Note: You need the Allow contract maintenance security right in the Contracts domain security rights group for this activity.

Activity Steps

  1. Open the Sales Contract or Purchase Contract.
  2. Expand the required set of contract terms.
  3. Select the Payment Terms node.
  4. Right-click in the Issue Date Terms table and select New » [Invoice Type] / [Document Type] from the menu.

    If only an invoice type is selected, Reference Document is Standard Document.

    Otherwise, Reference Document can be Credit Note, Debit Note or Despatch/Demurrage.

    Note: If a set of payment terms already exists for the selected invoice type, the new payment terms are set on the next invoice iteration. Only one final invoice for despatch/demurrage can be created.

  5. Complete the following fields.
    • Start Invoice—Invoice iteration from which the payment term is applied. If not specified, this is open-ended. If specified, the iterations cannot be more than the maximum iterations specified for the contractual invoice type.
    • End Invoice—Invoice iteration up to which the payment term is applied. If not specified, this is open-ended. If specified, the iterations cannot be more than the maximum iterations specified for the contractual invoice type.
    • Payable Percentage—Percentage of the invoice total that must be paid. May be greater than 100% for non-final invoices. May be less than 100% for all invoice types. Default: 100%. Examples:
      • Greater than 100%—A business protects itself against commodity price moves by requiring overpayment of provisional invoices.
      • Less than 100%—A business avoids issuing credit notes by requiring only partial payment of provisional invoices.
    • Payment Term Concept—Calculation method for the payable amount. Select from:
      • Total Value (default)—The payable amount is calculated on the total value.
      • Net Amount—The payable amount is calculated on the net amount and no tax component is added.
      • Net Amount before adding Tax—The payable amount is calculated on the net amount. Any tax component is calculated based on the net amount and then added to the instalment.
    • Installment Basis—Calculation method for the payable amount. Select from:
      • Percentage (default)—Instalments for each concept must add up to 100%.
      • Value—Instalments are based on a currency value, with the last instalment for each concept having a blank value for any balance.

      Example: Instalments are defined based on value:

      • 100,000 USD due 60 days after the bill of lading
      • 200,000 USD due 90 days after the bill of lading
      • Balance due 100 days after the bill of lading

      An invoice for 80,000 USD would have a single instalment due 60 days after the bill of lading.

      An invoice for 350,000 USD would have three instalments:

      • 100,000 USD due 60 days after the bill of lading
      • 200,000 USD due 90 days after the bill of lading
      • 50,000 USD due 100 days after the bill of lading
  6. If the snapshot settings (see Specify Snapshot Settings) include the estimation of invoice dates using issue date terms:
    1. Select a predefined Reference Date or check IsCalculated.

      The estimated invoice date displays in the despatch order snapshot.

      Select from:

      • Bill of Lading Date—The bill of lading date, or else the first available date out of ATD at origin, ETD at origin or planned despatch date. (Snapshots, revaluations and non-final invoices use the bill of lading date, or else the first available date out of: ATD at origin, ETD at origin, ATA at origin, ETA at origin, the quota end date, or planned despatch date.)
      • Arrival at Destination—The ATA at destination or for non-final invoices can use the ETA at destination. (Snapshots, revaluations and non-final invoices use the first available date out of: ATA at destination, ETA at destination, estimated arrival based on the travel and duration time of a route that matches the planned loading and unloading locations or quota contractual source and destination, bill of lading date of the despatch order, or planned despatch date of the despatch order.)
      • ETA at Origin—ATA at origin or ETA at origin, or bill of lading date if no origin can be determined. (Snapshots, revaluations and non-final invoices use the ATA at origin, or else the first available date out of: ETA at origin, bill of lading date, or planned despatch date of the despatch order.)
      • Invoice Date (default)—The invoice date, or else the first available date out of: estimated invoice date, or current date.
      • Credit Note
      • Debit Note
      • Demurrage Invoice
      • Despatch Invoice
      • Unload Completion—Actual end unloading, actual start unloading, planned end unloading, ATA at destination or for non-final invoices can use the ETA at destination. (Snapshots, revaluations and non-final invoices can use the first available date out of: actual end unloading, actual start unloading, planned end unloading, ATA at destination, ETA at destination, estimated arrival based on the travel and duration time of a route that matches the planned loading and unloading locations or quota contractual source and destination, bill of lading date, or planned despatch date.)
      • Sample Date—The final sample date. (Snapshots, revaluations and non-final invoices use the sample date, or else the first available date out of: bill of lading date, ATD at origin, ETD at origin, ATA at origin, ETA at origin, the quota end date, or planned despatch date.)
      • Departure from Origin—ATD at origin or ETD at origin, or bill of lading date if no origin can be determined. (Snapshots, revaluations and non-final invoices use the first available date out of: ATD at origin, bill of lading date, ETD at origin, ATA at origin, ETA at origin, quota end date, or planned despatch date.)
      • Receipt Of Documents—If an actual invoice does not exist with a recorded Receipt Of Documents/Date of Agreement, MineMarket uses the estimated invoice date to determine the instalment due date that displays in the despatch order snapshot.
      • Date of Agreement
      • Assay Exchange Completion—The Final Assay Agreement date in the despatch order's additional contract fulfilment dates (see Enter Additional Dates for Contract Fulfilment), or else the first available date out of: Estimated Assay Exchange Completion date; BL date; ATD at origin; ETD at origin; ATA at origin (except for final invoices); ETA at origin (except for final invoices); quota end date; or planned despatch date of the despatch order.
    2. If the reference date is to be calculated, select a tested expression or create an expression for the Calc. Expression. See Expression Editor.
    3. Enter the Number Of Days. The estimated invoice date is this number of days after the reference date.
    4. Select the Type Of Days to include in counting forward the Number of Days from the reference date. Select from Calendar and Business.
    5. Select the Calendars to use when determining the days to add to the reference date. Select from the calendars defined in the Calendar Editor.
  7. Complete the remaining fields as required.
    • Copy Previous Payment Condition Line Items—Whether to copy the payment condition line items from the previous invoice iteration. If checked, the line items are copied from the previous invoice iteration. If unchecked, the line items are recalculated for this invoice iteration.
    • Comments
  8. Click Save.