Transmissions and Receipts
An AS2 partnership has separate incoming and outgoing transmissions. The folders show the files available to your workflow; message logs and Message Disposition Notifications (MDNs) establish what happened during the exchange. A successful AS2 delivery does not establish that the receiving business application imported the file.
AS2 Folders
Once you have configured AS2, a new top-level folder named as2_home appears in your Files.com site.
The as2_home folder contains a folder for each of your AS2 Identities, and each AS2 Identity folder contains a folder for each of your AS2 trading partners. For example, if your AS2 Identity is ME and your trading partner's AS2 Identity is THEM, the folder structure is:
/as2_home/ME/THEM/inbox
/as2_home/ME/THEM/outbox
/as2_home/ME/THEM/sent
Files sent to you via AS2 by your trading partner appear in the inbox folder.
Files placed into the outbox folder are sent via AS2 to your trading partner. After a file is successfully sent, Files.com automatically moves it from the outbox folder to the sent folder.
Incoming File Names
When a trading partner sends a file whose name already exists in its inbox, your site's Overwrite Behavior setting determines whether the existing file is replaced or the new file is renamed. Choose the behavior before accepting deliveries that reuse filenames, so a later delivery is handled as your workflow expects.
To preserve separate deliveries under names that identify when they arrived, configure the inbox folder's Rename Uploaded Files setting to include a timestamp. This gives downstream processing a way to distinguish files that the partner sends with the same name.
Transmission Information
The AS2 Logs show details of incoming and outgoing AS2 transmissions. Incoming and outgoing messages are listed separately. Use each table's Columns menu to choose which transmission details to display.
| Column Name | Description |
|---|---|
| Date/Time | Shows the date and time of the transmission. |
| Status | Shows the outcome of the transmission. |
| File Size | Shows the size of the transmitted file. |
| File Name | Shows the name of the transmitted file, if available. |
| Sender ID | Shows the AS2 Identifier of the sender. |
| Receiver ID | Shows the AS2 Identifier of the receiver. |
| HTTP Response Code | Shows the HTTP Response Code of the AS2 transmission, which can be useful in troubleshooting AS2 setup and configuration issues. An HTTP success response alone does not establish AS2 success; also review the MDN and AS2 processing results. Other HTTP codes can help identify transport or endpoint errors. |
| HTTP Response Headers | Shows the HTTP Response Headers of the AS2 transmission, which can be useful in troubleshooting AS2 setup and configuration issues. The important headers used by AS2 are Content-Type, MIME-Version, Message-ID, AS2-From, AS2-To, and AS2-Version. |
| File Contents | Provides a link to open and view the file contents, if available. |
| MDN Exists | Specifies if a Message Disposition Notification is available for this transmission. |
| AS2 Processing | Provides information about the outcomes of the various AS2 processing steps that were performed. |
| MDN Contents | Provides a link to open and view the Message Disposition Notification, if available. |
| Transmission Duration | Shows the estimated duration of the transmission, if available. |
| ID | The Files.com record ID identifying an individual incoming-message attempt. Available as an optional column in the incoming table. |
| Replayed From Message | The record ID of the incoming message used to create a replay, with a link to that message's details. Available as an optional column in the incoming table. |
Incoming Message Details
To investigate an incoming transmission, select its File Name in the incoming AS2 log. If the message has no recorded filename, the link uses a label such as Message 12. The incoming-message tables on the AS2 Identity and AS2 Trading Partner pages provide the same links. Workspace Administrators can use those pages to open messages in their Workspace.
The details header shows the attempt's status, received time, sender and receiver, file size, and AS2 Message-ID, with links to File Contents and MDN Contents when available. AS2 Processing shows the result of each processing step, helping you identify where delivery failed. The HTTP Response Headers tab provides the response headers when available.
Message Disposition Notifications (MDNs)
A Message Disposition Notification (MDN) is a digital receipt, returned by the receiver of the AS2 payload (message), to provide confirmation of delivery to the sender.
The MDN can indicate successful delivery or a failure outcome. A failed MDN typically contains details about why the delivery failed.
When an incoming transmission identifies one of your configured AS2 Identities, Files.com signs the MDN with that identity's private key. This includes failure receipts, so the sender can verify the source of the result even when Files.com could not accept the file into the inbox. A receipt's signature alone does not establish successful delivery.
For successfully processed incoming messages, Files.com returns a signed MDN containing a Message Integrity Check (MIC) in the Received-Content-MIC field. The MIC lets the sending partner compare the received content with what they sent. Files.com includes it for signed and unsigned messages, with or without S/MIME message encryption.
A valid MDN signature lets the sender verify that the receipt came from the receiving AS2 identity. Together with the MIC, it provides evidence of the content received, which helps trading partners reconcile delivery records. It does not authenticate the original sender or mean that the original message was signed or that its signature was validated. The partner's incoming signature validation level controls that separate check.
MDNs are optional in the AS2 protocol, but they are widely adopted and often required by trading partners. You can view incoming and outgoing MDNs in the AS2 Logs.
Viewing Receipts
You can view Message Disposition Notifications in the MDN Contents column of the incoming messages and outgoing messages sections of the AS2 Logs.
The AS2 incoming messages table shows MDNs that Files.com generated in response to inbound AS2 transmissions from your trading partners.
The AS2 outgoing messages table shows MDNs that your trading partners generated in response to outbound AS2 transmissions from Files.com.
The MDN Exists column indicates whether a Message Disposition Notification is available for that transmission.
Replaying Incoming Messages
Replaying a retained incoming AS2 message processes its original content again without asking the trading partner to resend it. This can recover a file after a delivery failure or deliver it again when a downstream workflow lost or mishandled the file.
A Site Administrator or an administrator of the message's Workspace can replay it for as long as the message is retained, regardless of its age or previous success or failure. Each request creates a new incoming-message record and preserves the original record and its result.
Files.com processes the original message content and headers using the current AS2 configuration. The current certificates, private key, and incoming signature validation requirements apply. Correct the cause of a failed delivery before replaying it. A previously successful message can fail if the current configuration cannot decrypt it or validate its signature.
Messages that matched an AS2 Identity stay in their Workspace when replayed. Failed attempts already in a named Workspace also stay there. For a Default Workspace message that never matched an AS2 Identity, a Site Administrator can configure the Identity in any Workspace and replay the message. Files.com opens the new attempt in the Workspace whose Identity routes it.
Another delivery follows the existing incoming filename rules, including overwrite and renaming settings. The receiving folder's processing can run again, and a downstream system may import the file again. Before replaying, confirm that the workflow is ready for another delivery, especially when the original attempt succeeded.
To replay a message, open its details, select Replay Message in the header, and confirm. Files.com reports the processing result and opens the new attempt. Creating its record does not establish successful file delivery: check its status and AS2 Processing results. Confirm any subsequent import in the receiving application's own records.
Each attempt has its own record ID, while the AS2 Message-ID remains the same. Replayed From Message on the details page identifies and links to the attempt's immediate source. The source record ID remains visible when that source has expired or is unavailable in the selected Workspace.
The Replays tab lists the retained replays made directly from the message in the selected Workspace. Open a replay to inspect its result. A replay of a replay appears on its immediate source's Replays tab, rather than on the first message's tab.
Message Retention
The system retains all AS2 messages, including their full payloads and debugging details, for 90 days by default. You can adjust this duration in the Message Retention Timeframe setting.
This retention setting applies globally to your entire site and includes both inbound and outbound AS2 messages. It controls how long message logs and message content remain available before they are automatically removed.
AS2 Data Residency
Retained AS2 message data is stored in the United States, regardless of the storage region configured for the rest of your site. This covers the AS2 message logs, the message payloads, and the transmitted file contents, and it applies even when the transmitted file is not otherwise stored in Files.com. Files.com's AS2 logging infrastructure runs in the United States, and there is no setting to change where AS2 data is stored.