| Info |
|---|
This service will be available for the province of Gipuzkoa province from version 1.4 . |
Servicio habilitado por la Foral de Guipúzcoa para el envío de la información correspondiente al bloque de datos adicionales de Ticketbai de las facturas emitidas que no figuran en el fichero de alta de Ticketbai.
El servicio de Osatu permitirá registrar la información correspondiente a los siguientes campos:
Referencia externa
Importe transmisión sujeto a IVA
NIF Representante legal
NIF Representante contraparte
Número registro acuerdo facturación
Entidad sucedida
Cupón
Inmuebles
...
and from version 1.5 for the province of Araba. |
Service enabled by the province of Gipuzkoa and Araba for the submission of additional data not included in the TicketBAI registration file.
...
External reference
VAT transmission amount
NIF (Tax identification number) of legal representative
NIF (Tax identification number) of counterpart representative
Registration number of billing agreement
Succeeded entity
Coupon
Properties.
Osatu file reception service
Once the TicketBAI invoice registration reaches status 6240, "TBAI invoice accepted," the Osatu file is automatically sent to the Osatu service for structure and data verification and validation. Upon completion of these checks, a response is received from the Osatu service indicating the status of the previously submitted Osatu file.
...
| Advertencia |
|---|
Currently, the Osatu service of Gipuzkoa province and Araba is defaulting to rejecting all Osatu files. This is because when the invoice registration file is received, it is not immediately recorded by the Osatu service, so when an Osatu file is sent, it cannot be linked to its corresponding invoice registration file as it has not yet been recorded. This results in the error message: "TicketBAI invoice registration to be complemented does not exist in the system." The solution is to reprocess the registration file after a reasonable period of time and resubmit the Osatu file until it is accepted by the Osatu service. |
Osatu file correction service
When If the Osatu file is rejected due to errors related to its structure or minimum content, an icon of ‘Error’ or ‘Warning’ will be shown in the Message colum of the ALV Screen. In this case, the error must be corrected and the file must be resubmitted to the Foral through the "Reprocess invoice" button (General TBAI monitor functionality).
The required action for error correction will depend on the type of error as indicated in the following table:
...
ERROR TYPE
...
CODE
...
CORRECCIÓN DEL ERROR
...
Related to the issueing certificate or the identity linked to the issueing certificate.
...
001
007
...
Resend the Osatu file once the error has been corrected.
...
Reception service not available
...
006
...
Resend the Osatu file once the error has been corrected.
...
Related to the structure or minimum content of the TBAI registration file.
...
002
017
...
Resend the Osatu file once the error has been corrected.
...
Errors resulting from the rest of the data that must be reported in the Osatu file.
...
...
Resend the Osatu file once the error has been corrected.
...
The main file to be complemented must have been previously received in the system.
...
021
...
No action needed.
Osatu file deletion service
El servicio Osatu no contempla un servicio de anulación de ficheros Osatu como tal, en su defecto, proporciona la opción del borrar directamente el fichero de datos adicionales enviados al servicio, esta acción podremos llevarla a cabo a a través del botón Borrar Osatu. (Funcionalidad general del monitor TBAI)
Se generará un fichero Osatu vacío con los datos del ID Factura borrado y se enviará a la Foral, la cual responderá con un fichero de confirmación del borrado.
Se permite volver a enviar al servicio Osatu un fichero adicional borrado anteriormente a través del botón Reprocesar factura. (Funcionalidad general del monitor TBAI). Al enviarlo, se sobre escribirá la información borrada anteriormente y se reactivará el bloque de datos adicionales.
The Osatu service does not have a service for canceling Osatu files per se, instead it provides the option to directly delete the additional data file sent to the service, this action can be performed through the "Delete Osatu" button (general functionality of the TBAI monitor).
An The deletion of a previously received Osatu file is possible by generating and sending an empty Osatu file will be generated and sent to the Osatu service, which will respond with a confirmation of the deletion.
The "Reprocess invoice" button (general functionality of the TBAI monitor) can generate and send a new Osatu file after having sent an empty Osatu file (Delete Osatu), as sending a new Osatu file overwrites the previously deleted information and reactivate the additional data block.
Every Osatu file that is received by the Osatu service, overwrites the previously received Osatu file.
Osatu reception service flowchart
...
Links for the configuration of the Osatu service
It is crucial to have the paremeterization configured correctly for the functioning of the OSatu service
Check the configuration of the following tables:
Provincial treasury agency by company
Settings for creating annotations
In case the ‘Successor entity’ or the ‘Real estate location’ and ‘Cadastral reference’ data block is required to be informed, the following tables will also need to be configured acordingly.