Transaction Management API fields

This table lists the fields included in the request body for O Series Transaction Management API requests.

Field	Details	Description
`data`	object (`ReversalRequestResponseType`)	Object: - `transactionId` - `postingDate` - `documentNumber`
`documentNumber`	string `[ 0 .. 50 ] characters`	The document number in the host application that references the event.
`id`	required string `[ 1 .. 40 ] characters`	An identifier that further defines the document and corresponds to the transaction stored in the host system. The Transaction ID is used for synchronization services, but is not used for reporting purposes.
`transactionid`	string `[ 1 .. 40 ] character`	An identifier that further defines the document and corresponds to the transaction stored in the host system. The Transaction ID is used for synchronization services, but is not used for reporting purposes. Stored in the Tax Journal as `transSyncIdCode`.
`transactionId` (`ReversalRequestResponseType`)	string `[ 0 .. 40 ] characters`	An optional unique user-defined value to identify the new reversal document created by this operation. This will allow transaction operations (such as delete) on this new reversal document.
`postingDate`	string `<date>`	Defines when the transaction is reported for use with reporting and returns filing. If you do not define the Posting Date, the Calculation Engine sets it for the date when the transaction is processed.