rtc: Add data models and parser for AECs

[jtrh]

• Add data model for the SII's "Archivo Electrónico de Cesión" (AEC) in XML format.
• Add data model for the "cesiones" contained in an AEC.
• Add parser for AECs in XML format.
• Add tests.

[codecov-io]

Codecov Report

Merging #180 (3713486) into develop (73df96e) will increase coverage by 2.18%.
The diff coverage is 90.02%.

@@             Coverage Diff             @@
##           develop     #180      +/-   ##
===========================================
+ Coverage    78.65%   80.83%   +2.18%     
===========================================
  Files           28       30       +2     
  Lines         2024     2505     +481     
  Branches       331      377      +46     
===========================================
+ Hits          1592     2025     +433     
- Misses         286      306      +20     
- Partials       146      174      +28     

Impacted Files	Coverage Δ
cl_sii/rtc/parse_aec.py	89.74% <89.74%> (ø)
cl_sii/rtc/data_models_aec.py	90.38% <90.38%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73df96e...3713486. Read the comment docs.

[yaselc]

Wow... 🤯
Just add that you should include the "Identificador de Envio" field, from the RPETC email:
RPETC email: attachment / 'Identificador de Envio'
This is a key piece of information to check the status of an AEC submission and can only be obtained from the RPETC email or submitting the AEC.

[jtrh]

Just add that you should include the "Identificador de Envio" field, from the RPETC email:
RPETC email: attachment / 'Identificador de Envio'
This is a key piece of information to check the status of an AEC submission and can only be obtained from the RPETC email or submitting the AEC.

@yaselc Can I extract the "identificador de envío" from the contents of an AEC XML file?

The scope of this pull request is modelling and parsing an AEC in XML format, not other related entities such as the RPETC email, unless those entities are embedded in the AEC XML file.

[jtrh]

The scope of this pull request is modelling and parsing an AEC in XML format, not other related entities such as the RPETC email, unless those entities are embedded in the AEC XML file.

Of course, that does not exclude the possibility of creating a separate data model for the RPETC Email Message in a future pull request.

[yaselc]

@yaselc Can I extract the "identificador de envío" from the contents of an AEC XML file?

The scope of this pull request is modelling and parsing an AEC in XML format, not other related entities such as the RPETC email, unless those entities are embedded in the AEC XML file.

Makes sense, but I'm thinking here of the use case that FP generates the AEC and submits it to the SII, the response is the "Identificador de Envio" and FP will want to store this AEC together with the "Identificador de Envio" to later check its status.
Even if the responsibility for generating and submitting the AEC were assigned to FD, it would still need to store it.

[glarrain]

Of course, that does not exclude the possibility of creating a separate data model for the RPETC Email Message in a future pull request.

I agree

[jtrh]

@yaselc Can I extract the "identificador de envío" from the contents of an AEC XML file?
The scope of this pull request is modelling and parsing an AEC in XML format, not other related entities such as the RPETC email, unless those entities are embedded in the AEC XML file.

Makes sense, but I'm thinking here of the use case that FP generates the AEC and submits it to the SII, the response is the "Identificador de Envio" and FP will want to store this AEC together with the "Identificador de Envio" to later check its status.
Even if the responsibility for generating and submitting the AEC were assigned to FD, it would still need to store it.

@yaselc: We can store the submission identifier in an optional field of the AEC Django model of FD CL Data.