The instructions below allow to use the Transactions app in the commandline mode. Use it to automate conversions.
The command line mode is activated when you pass parameters to the Transactions app.
On windows, it would look like the following:
"path to transactions.exe" "path to input file 1" "path to input file 2" /OPTIONS /OUTPUT="path to output file"
On mac OS, it would look like the following:
/Applications/Transactions.app/Contents/MacOS/transactions "path to input file 1" "path to input file 2" /OPTIONS /OUTPUT="path to output file"
Options are added with slash (/) character in front and optional value after the equals character (=):
This option set the output file name. The value is required to activate this option. When this option is activated, the app does the conversion and closes without showing the user interface. The output file extension defines the file format (for .QBO, .IIF, .QIF, and so on). The output filename may include the full path to the file. All directories included in the path must be already created and accessible. When the path or filename includes a space, include the whole path in double quotes. For example, /OUTPUT="path to output file.QBO".
This option turn on OCR (optical character recognition) when processing PDF files. No value is required.
This option allows to set the CSV target for command line processing
For example, /CSVTarget="Quickbooks Online"
This option sets the custom mapping for CSV input files. For example, /Mapping="Mapping1"
This options sets the ending balance for formats supporting it (QBO, QFX, OFX). For Example, /EndBalance=1000.23