EDocument is created with “to include in a batch” state and in manual way you can:
- Create a batch: it will create a new batch for eDocument
- Mark as corrected: The eDocument changes to a corrected state and is sent as a modification.
- Hold: eDocument remains retained without including in a batch.
- Release: Release of a "Retained" eDocument.
- Add a batch: an eDocument is included inside the existing batch.
- Extract from batch: Extract an edocument from a Batch
- Exceptional processing: Change of record status.
- Undo Exceptional processing : Return of status in the registry (maximum up to the previous two).
| Note: The button "exceptional processing" and "undo exceptional processing" will only be available for the Administrator Role. |
Create a batch:
Once an eDocument is being created with an “include in a batch” state, press “create a batch” to create a new batch where we include an eDocument (a type of the batch that is being created depends on the terms of the conditions that have been configurated):
A state now is changing into: “included in a batch”:
Mark as corrected
Selecting the eDocument and pressing "Mark as corrected" automatically changes the status. Once the eDocument has been in the "Rejected" state directly it changes to "To include batch" to be sent again in a new batch.
Hold/Release:
Once you mark an eDocument by pressing “ hold up” button , it stays with the “ retain” status.
From the “retained” state you can:
- Add a batch
- Release: a released state is similar to an initial state, the way that it allows to make the same actions.
From the retained state, you cannot create a new batch, for this you should release an eDocument and once is released, create a new batch.
Include/Extract a batch:
We press “include in a batch” when we want to include an eDocument in an existing batch:
The system shows the batches that exists and continuing open to accept new eDocument. (Possible change to validate and only show batches that by definition can include).
A status change now into “included in a batch”
Once eDocument was being included in a batch, it is possible to take it away by pressing “Extract from a batch”. In this case the statement changes from “included in a batch” into “ to include in a batch again”.
Excepcional Processing/Undo (ROL-ADMIN)
The eDocument to be treated is selected and clicked on "Exceptional processing".
Next, a pop-up appears where you choose the state to change the eDocument.
In the same way when pressing "undo exceptional processing", the status of the record is changed to the immediately previous one (only goes back two exceptional states).
EDOCUMENT STATUS
-Accepted: eDocument accepted by the AEAT.
-Accepted with errors: it is necessary to correct errors that have the eDocument and to send it back to the AEAT.
-Corrected: Modified eDocument. B+ warns with a pop-up if you want to mark the document as "Corrected" (except if you click "Mark as corrected directly", it does not warn with pop-up).
-To be included in batch : eDocument ready to include in a batch already created or in a new one.
-Hold: in this status the eDocument can not be included in any batch.
-Included in batch file: registration already included in a batch that has not yet been sent.
-Obsolete: state to which the eDocument automatically changes when a new record with the same ID is created (that state is also generated when a record occurs). Even if the registration has been sent to the tax office and has been accepted, if you subsequently unsubscribe in the B + solution Cockpit appears obsolete.
-Rejected: eDocument with complete rejection. Fix errors and send in a new batch.
Obsolescencce:
In the following graph you can see the operation diagram of the obsolete within B+ SII:
F1 = Original Invoice.
BF1 = Original invoice low.
F2 (=IDInvoice) = New invoice with same Original Invoice ID..
When an electronic document is generated from an invoice, it can be registered in the AEAT (accepted status) or not registered (either because the shipment has not yet been made, because it is not accepted for a specific reason).
Therefore, our original F1 invoice will be under two situations with the AEAT (Accepted or not registered).
- F1 has been accepted in the AEAT
In this case, if a low invoice (BF1) about the F1 invoice, F1 would go to the accepted-obsolete state while the BF1 would be in the to be included in the batch state. This is because, as the original invoice has been accepted, it is necessary to send the unsubscribe to the AEAT so that it is registered as low.
On the other hand, an F2 invoice with the same IDInvoice was generated as F1, what would happen is that F1 would pass to the accepted-obsolete state, and the F2 new invoice would be in the corrected state
- F1 has not been accepted in the AEAT.
In this case, it may be that it was sent and rejected or that it has not been sent directly. In any case, it is not registered in the AEAT.
If a low invoice BF1 is generated; both the F1 invoice and the low BF1 invoice will be automatically placed in an obsolete state. This is because, as the original invoice has never been accepted by the AEAT (afterwards there is no record of this invoice in the AEAT), it is not necessary to send the unsubscribe to the AEAT.
If what happens is that a F2 new invoice is generated with the same Invoice ID, the state to which the original invoice would pass, would be obsolete, while the new invoice F2 would change to the to be included in the batch state.