Table 04 - Payment Conditions
- This article presents the fields of the Payment Terms integration layout. To better understand the concept behind payment terms, see our article on Payment Terms Concept.
| Order | Field Description | Format and Size | Required | Version | Remarks |
| 1 | Table identifier (IDENTIFICADOR) | FIXO=04 (2) | Yes | 1.0 | |
| 2 | Code (code) | Text (20) | Yes | 1.0 | |
| 3 | Description (description) | Text (255) | Yes | 1.0 | |
| 4 | No Used | - | Not | 1.0 | Send empty |
| 5 | Not Used | - | No | 1.0 | Send empty |
| 6 | Active (active) | Integer (1) | Yes | 1.0 | (1=Active / 0=Inactive) Inactive records do not appear to the seller |
| 7 | Minimum Order Value (valorMinimoPedido) | Decimal (15.2) | No | 2.7 | When issuing the order, when using a certain payment condition, the system considers this field to validate the minimum value of the order. Ex: To use the 30/60/90 condition, the order value must be greater than R$ 2,000.00 |
| 8 | Interest or Discount Percentage (percJurosDesconto) | Decimal (15.2) | No | 2.23 | O The system takes this field into account to automatically add interest or discount to the total order value, according to the payment condition. EX: If in the “CASH” condition, you send “-2.5” and in the “30/60” condition, you send “5.5”. Assuming that the seller places an order totaling R$ 1,000.00 (including shipping and taxes), when selecting the “CASH” condition, the system will calculate a discount of R$ 25.00, leaving the total order value as “R$ 975.00”, whereas for the same order, if the payment condition “30/60” had been chosen, the total order value would be “R$ 1,055.00”. NOTE: Currently this difference is not prorated in the value of the products, it appears as a separate field in the order (Amount Interest/Discount by Payment Method) |
| 9 | Blocks the use of Demander (bloqueiaUsoDemander) | Integer (1) | No | 3.10 | (1 = Active / 0 = Inactive) When active, it blocks the use of Demander |
| 10 | Blocks the use of Pedidos.La (bloqueiaUsoPedidoLa) | Integer (1) | No | 3.10 | (1 = Active / 0 = Inactive) When active, it blocks the use of Request.La |
| 11 | Blocks the use of Web Request (bloqueiaUsoPedidoWeb) | Integer (1) | No | 3.10 | (1 = Active / 0 = Inactive) When active, it blocks the use of Demander Web |
| 12 | Average payment period (prazoMedioPagamento) | Decimal (15.2) | No | 3.37 | |
| 13 | Considers credit limit (consideraLimiteCredito) | Integer (1) | No | 3.37 | (1 = Active / 0 = Inactive) When active, when issuing an order, it takes into account the validation of the customer’s credit limit |
| 14 | Deadlines (deadlines) | Text(255) | No | 4.30 | Payment interval. EX: “30,60,90”. Currently this field is used when returning orders for some ERP’s. |
Registration Example:
04|1|6/30/90 DAYS|0|0|1|2000|0|0|0|