Registration event

This event allows documenting that the Issuer/Legitimate Holder has the will to register the sales electronic invoice in order to negotiate a given Sales Electronic Invoice that meets the tax and commercial requirements as a negotiable instrument in RADIAN.

Event 036 depends on the following events:

• Acknowledgement of Receipt (30-RF)
• Receipt of the Good/Service (32-RM)
• Express and/or tacit Acceptance. (33-A and/or 34-AT)
• This means that these events must already exist for the current event to be generated.
• It must not exceed the due date of the sales electronic invoice. (*)
• /Invoice/cac:PaymentMeans/cbc:PaymentDueDate
• It must correspond to a credit sale. (**) /Invoice/cac:PaymentMeans/cbc:ID=2

This event can only be issued by the issuer or legitimate holder.

The following events prevent this event:

• Claim (31-R)
• Circulation limitation (41-LCFEVT)

For this request, the parameters we will use are the following:

Parameter	Required	Description	Value
globalDocumentId	✓	Gosocket id associated with the electronic invoice treated as a negotiable instrument
status	✓	Event code	036
description	✓	Text describing the Registration
operationType	✓	Registration code 361 = First registration of the sales electronic invoice as a negotiable instrument for General Negotiation 362 = First registration of the sales electronic invoice as a negotiable instrument for Prior Direct Negotiation 363 = Subsequent registration of the sales electronic invoice as a negotiable instrument for General Negotiation 364 = Subsequent registration of the sales electronic invoice as a negotiable instrument for Prior Direct Negotiation
valuePaid	✓	Value paid by the Registration receiver. It can be 0.
holderID	C	Holder Tax ID when operationType is = 362 or 364.
holderTypeID	C	Holder type when operationType is = 362 or 364
holderName	C	Holder name when operationType is = 362 or 364
endorseeID	C	Endorsee Tax ID when operationType is = 362 or 364.
endorseeName	C	Endorsee name when operationType is = 362 or 364

✓ = required data

C = conditional data

Request example

As a first example, we see a JSON request for event 036 (registration) type 361 (First registration of the sales electronic invoice as a negotiable instrument for General Negotiation).

{
"globalDocumentId": "00000000-0000-0000-0000-000000000000",
"status": "036",
"description": "Inscripcion",
"operationType": "361",
"valuePaid": "0"
}

In the following example we show how to make a JSON request sending event 036 (Registration) type 362 (First registration of the sales electronic invoice as a negotiable instrument for Prior Direct Negotiation).

{
"globalDocumentId": "00000000-0000-0000-0000-000000000000",
"status": "036",
"description": "Inscripcion",
"operationType": "362",
"valuePaid": "1000",
"endorseeName": "Nombre endosatario",
"endorseeID": "NIT endosatario"
}

Now let's see how to make a JSON request sending event 036 (Registration) type 363 (Subsequent registration of the sales electronic invoice as a negotiable instrument for General Negotiation).

{
"globalDocumentId": "00000000-0000-0000-0000-000000000000",
"status": "036",
"description": "Test",
"operationType": "363",
"holderID": "NIT tenedor",
"holderTypeID": "Tipo tenedor",
"holderName": "Nombre tenedor",
"valuePaid": 0.00
}

Let's make a JSON request sending event 036 (Registration) type 364 (Subsequent registration of the sales electronic invoice as a negotiable instrument for Prior Direct Negotiation).

{
"globalDocumentId": "00000000-0000-0000-0000-000000000000",
"status": "036",
"description": "Test",
"operationType": "364",
"holderID": "NIT tenedor",
"holderTypeID": "Tipo tenedor",
"holderName": "Nombre tenedor",
"endorseeID": "NIT Endosatario",
"endorseeName": "Nombre endosatario",
"valuePaid": 0.00
}

Fictitious data

The identifiers in the examples on this page are fictitious.