Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amounts: charges and discounts #1070

Open
yolile opened this issue Sep 15, 2020 · 6 comments
Open

Amounts: charges and discounts #1070

yolile opened this issue Sep 15, 2020 · 6 comments
Labels
Extensions - Drafted Relating to a drafted extension Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions

Comments

@yolile
Copy link
Member

yolile commented Sep 15, 2020

Problem

In Chile, (and Paraguay too) for the purchases made from a framework agreement, they have extra charges and discounts that apply to the items unit prices or the total amount of the purchase order.

In Chile, the charges are related to the shipping of the item and the discounts can be related to the volume of the item or agreements between the supplier and the buyer.

In OCDS there is only one field at item (unit/value/amount) and award level (value/amount) to indicate the total unit price or award amount, without breaking down it.

Example

https://www.mercadopublico.cl/PurchaseOrder/Modules/PO/DetailsPurchaseOrder.aspx?qs=mS1zfaUOjodqW7vgGO9H8A==
image

Proposal

A solution may be to add "charges" and "discounts" numeric fields to the "value" object to indicate the charges and discounts applied. Another option is to add an array of "amount breakdown", with the discounts as negative numbers, charges as positive, and a description of what the amount means.

@DCCP-Hugo @nenita05leyla

@jpmckinney jpmckinney added Extensions - Local Relating to a local extension Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions and removed Extensions - Local Relating to a local extension labels Sep 16, 2020
@jpmckinney
Copy link
Member

@yolile I prefer a breakdown; otherwise, users are very unlikely to correctly sum the numbers. We can consider a valueBreakdown that is parallel to the value object (not nested inside it).

@yolile
Copy link
Member Author

yolile commented Sep 17, 2020

so for this example, the proposal will look something like, if we use the same approach as the budget breakdown extension:

{
      "awards": [
        {
          "value": {
            "amount": 7526475.0,
            "amountGross": 8956505.0,
            "currency": "CLP"
          },
          "valueBreakdown": {
            "net": 7602500,
            "discounts": -76025,
            "taxes": 1430030
          },
          "items": [
            {
              "id": "111570611",
              "quantity": 500.0,
              "unit": {
                "value": {
                  "amount": 4313.0,
                  "currency": "CLP"
                },
                "valueBreakdown": {
                  "net": 4228,
                  "charges": 85
                }
              }
            },
            {
              "id": "111570613",
              "quantity": 2000.0,
              "unit": {
                "value": {
                  "amount": 2723.0,
                  "currency": "CLP"
                },
                "valueBreakdown": {
                  "net": 2670,
                  "charges": 53
                }
              }
            }
          ]
        }
      ]
}

or if we use the item's attributes extension approach (which is more verbose):

{
  "valueBreakdown": [
    {
      "id": "net",
      "description": "Precio unitario neto",
      "value": {
        "amount": 2670,
        "currency": "CLP"
      }
    },
    {
      "id": "charges",
      "description": "Monto por unidad a pagar por despacho",
      "value": {
        "amount": 53,
        "currency": "CLP"
      }
    }
  ]
}

@jpmckinney
Copy link
Member

I thought budget breakdown also didn’t have user assigned field names? I think I prefer the verbose, as it’s conceivable we want to attach more details about each value.

@yolile
Copy link
Member Author

yolile commented Sep 17, 2020

I thought budget breakdown also didn’t have user assigned field names?

Sorry I meant Budget and Spend classification extension, but ok I agree with you

@yolile
Copy link
Member Author

yolile commented Sep 30, 2020

FYI Peru also has information about the breakdown of the values so they will use this extension too, eg https://apps1.perucompras.gob.pe//OrdenCompra/obtenerPdfOrdenPublico?ID_OrdenCompra=1064277&ImprimirCompleto=1

@jpmckinney
Copy link
Member

Noting that the extension was drafted here https://github.com/open-contracting-extensions/ocds_valueBreakdown_extension

It is not in the registry.

@jpmckinney jpmckinney added the Extensions - Drafted Relating to a drafted extension label Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Extensions - Drafted Relating to a drafted extension Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions
Projects
None yet
Development

No branches or pull requests

2 participants