View document details in Control: metadata, audit trail, XML view and available actions.
When you open a document in Control, you see the full story of that document: who sent it, through which channel, what the current status is and which processing steps it has been through. This detail screen is the heart of Control and gives you the insight you need to quickly identify issues and track document progress.
From the document list, click on a document to open the detail screen. You can also navigate directly to a document if you know the document number, using the search function.
At the top of the detail screen, you'll find the key information about the document:
This information gives you immediate context about the document before you dive into the details.
Control gives you direct access to the source file of the document. You can view the original XML or UBL file in the interface and download it for further analysis or archiving. This is especially useful if you have technical questions about the content of a document, or if you want to compare the file with what arrived in your financial system.
Tip: the XML file contains all structured data of the document. If you notice a discrepancy between what you expected and what was delivered, the XML file is the best place to check.
The audit trail is one of Control's most powerful features. Each document has a chronological overview of all processing steps it has been through, from the moment of receipt to the final delivery (or failure).
For each step in the audit trail, you can see:
The audit trail gives you full transparency into the processing workflow. If a document hasn't reached the recipient, you can see in the audit trail exactly where it got stuck.
The detail screen shows the current delivery status of the document. For a failed delivery, you can see the error message and the number of retry attempts the PSB has made. For server errors (5xx), the PSB retries up to 8 times, spread over a period of approximately 35 hours.
If all attempts have failed, the error message often reveals the root cause. Common causes include technical issues at the receiving party or an invalid endpoint.
Note: if you see a document with "Failed" status and multiple retry attempts, it is advisable to contact the receiving party or reach out to [email protected] if the issue persists.
From the detail screen, you can perform actions on a document. The available actions depend on the status and type of document:
Not all actions are available in every situation. Control only shows the actions that are relevant at that moment for the selected document.
Log in to Control