TWODSignature Filter

The TWODSignature Filter is used for calling the TrustWeaver On Demand service that signs the e-invoices digitally.

Note:

If the countries of the Seller and the Buyer have different levels of legal requirements for digital signatures, double signatures are applied. If the format of the invoice to be signed is XML (other than cXML), you must use the signature format XMLCON. If the format is cXML, you must use the signature format XMLSIG.

Figure 6

The TWODSignature Filter

The settings are described in the table below.

Setting	Description
Service type	The type of web service that produces and validates the digital signature. TrustWeaver E-invoice test environment – Used during the development and testing phases. Does not produce legally binding digital signatures. TrustWeaver E-invoice production environment – Used during the production phase. Produces legally binding digital signatures.
Proxy host	The name of the proxy server (if StreamServer connects through a proxy server when calling the TrustWeaver service).
Proxy port	The port used by the proxy server.
Logon credentials	The security configuration resource containing the logon credentials and password.
Signature format	The signature format specified in the trading partner agreement between the Seller and the Buyer. You can use the Default option, select a specific signature format, or specify the signature format using a variable. Default – The signature format is mapped against the content type of the invoice to be signed (“content type – Signature format” in the list below): • application/pdf– PDF • text/xml – XMLSIG • application/xml – XMLSIG • For any other data – PKCS7 PDF – Used when the format of the invoice is PDF. The signature is placed inside the PDF document and can be viewed using Adobe® Reader®. PKCS7 – Used when the invoice is treated as binary data and has any format. The invoice is contained within the PKCS7 (Cryptographic Message Syntax Standard) signature. XMLSIG – Used when the format of the invoice is cXML (commerce XML). The signature is placed inside the cXML document. The cXML format can handle double signatures. XMLCON – TrustWeaver specific format. Used when the format of the invoice is an XML format other than cXML. The XML data and signature are placed inside an XML container. The XML container can handle double signatures. SMIME – Used when the format of the invoice is to be presented as S/MIME (Secure/MIME). The invoice is contained within the S/MIME standard.
Seller’s tax country code	The name of the variable that contains the country code of the country where the Seller is registered for VAT. For example: $sellerscode The country code must be two characters long and comply with the ISO 3166 standard. The country must be TrustWeaver compliant.
Buyer’s tax country code	The name of the variable that contains the country code of the country where the Buyer is registered for VAT. For example: $buyerscode The country code must be two characters long and comply with the ISO 3166 standard. The country must be TrustWeaver compliant.
Signature type	The type of signature. Normal – Creates legal, country compliant e-invoices with a protection level based on the CAdES-A or XAdES-A profile, intended for B2B (business-to-business) scenarios. This option should normally be used. Simple – Creates legal e-invoices with a protection level based on the CAdES-T or XAdES-T profile. This option can be used in certain B2C (business-to-consumer) scenarios for signing invoices to be sent to the Buyer. A faster signature is used, but there is no evidence that the e-invoice was validated upon reception and there is no long term validation information stored with the signature. To ensure a correct validation over time, the Seller must still archive a copy signed with the Normal option.
	Using Signature type > Simple affects the signature applied. If you are uncertain of the protection level requirements, always use Signature type > Normal.
Number of items	Use if the signing requests include several invoices. The number of invoices sent to the TrustWeaver On Demand service in each signing request. You can use variables. Note: Leave this option blank if every signing request includes one single invoice.
Agreement identifier	Use if different agreements are used for different signing requests. A text string that associates each signing request with an agreement. You can use variables. For example, if different pricing models are used for different types of signing requests, this setting can be used to identify the requests. The agreement identifier can: • Contain a maximum of 256 characters. • Only contain the letters A to Z (uppercase or lowercase), digits, hyphen, @, dot and underscore.
Content type	Use if a driver is not selected for the output connector. For example, when using RedirectOUT. The content type to be used for the final delivery. For example, application/pdf. You can configure a specific content type, or you can configure the content type using a variable. Note: This content type overrides any content type derived from a driver.