The source contains one signed amount field. In this example, incoming transactions are positive and outgoing transactions are negative. The result needs separate Credit and Debit values.
Create Credit and Debit from the same source field. Clear zero and negative amounts from Credit, clear zero and positive amounts from Debit, then remove the minus sign from Debit. Only the selected value is cleared; the transaction remains.
amount, Credit, and Debit are example names. Your source field may have any other name: select the field that actually contains the amount. Use Credit and Debit as output names only when the target file requires them.
How to do it in Eofferix
- Create two output values from the same source amount. For a table result, use two columns; for JSON, two keys; for XML, two leaf nodes. In XML, set the output node name separately and apply the rules to its value.
- Open Transformations for
Creditand add: sourceamount→ Less than or equal →0→ Do not export field. With-100and0, onlyCreditis cleared.

Credit for negative and zero amounts.- Open Transformations for
Debitand add: sourceamount→ Greater than or equal →0→ Do not export field. With+100and0, onlyDebitis cleared. - Add the next rule: Current value → Contains substring →
-→ Remove substring →-. An input of-100becomes100inDebit.

- Click Save and run a small test export with
+100,-100, and0.
Result
| Transaction | Source amount | Credit | Debit | Record |
|---|---|---|---|---|
| Incoming payment | +100 | +100 | empty | remains |
| Expense | -100 | empty | 100 | remains |
| Zero amount | 0 | empty | empty | remains |
The recipe does not add a plus sign: an input of 100 remains 100, while +100 remains +100.

Credit and Debit values are cleared.Why the transaction remains
In this recipe, Do not export field is an action in Transformations. It clears only Credit or Debit and ends the chain for that value. It does not remove the table row, JSON object, or XML record.
In a table, the cleared value is an empty cell. In JSON, the cleared key may be omitted. In XML, the parent record remains and the leaf value is empty. To remove a complete transaction, use Export conditions.
Before using the file in QuickBooks
This recipe assumes a convention of positive incoming amounts and negative outgoing amounts. That convention is not universal across bank files or QuickBooks import workflows.
This recipe does not guarantee that a particular QuickBooks product will accept the file. Check the required column names, date format, column delimiter, and decimal separator before importing.
See also Value transformations and Transformation rule conditions.