> ## Documentation Index
> Fetch the complete documentation index at: https://docs.transitive.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Versions and attempts

> How one document can have more than one CFDI over time.

A document can have more than one CFDI over time. Versions and attempts tell you which CFDI is current and how Transitive got it.

## Versions

A version is one CFDI that you intend for the document. Transitive starts a new version in three conditions:

| Version | When it starts |
| - | - |
| Version 1 | The first stamp of the document. |
| A replacement | You cancel a CFDI with motive 01 and stamp a new replacement. The replacement is the next version. |
| A new stamp | You stamp the document again after the SAT cancelled its CFDI. |

Motive 01 can also refer to a newer version that is valid. Then no new version starts.

The status always shows one version. Usually, that version is the newest one.

## Attempts

An attempt is one try to stamp a version. Each attempt has a method:

* **Auto**: Transitive uses the data from CargoWise.
* **By hand**: You edit the data in a form before the stamp.
* **Outside Transitive**: A different system stamped the CFDI. Transitive only records it.

If an attempt fails, the next try is a new attempt on the same version. The version does not change.

## Two valid CFDIs

Usually, a version has one CFDI. In some conditions, a document has two valid CFDIs, for example when a different system also stamped it. Then the status is **Two valid CFDIs**. Find the CFDI that must not exist. If Transitive stamped it, cancel it in Transitive and select it by its UUID. If a different system stamped it, cancel it in that system.

## On the timeline

The [timeline](/concepts/timeline) shows each version as a group. The newest version is at the top. Each entry of an attempt shows the attempt number.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.