How are debit and credit values signed?

LedgerConverzn treats a debit as an outflow and a credit as an inflow, then calculates a signed transaction value for the preview and basic IIF output.

What if both columns have values?

Review that row carefully. The converter calculates a net value from the two fields but does not infer whether a source export's simultaneous values represent a transfer, correction, or another special case.

Is debit and credit mapping available in the core workflow?

Separate debit and credit controls are provided by LedgerConverzn Plus. The standard workflow uses one signed amount column.

Debit and credit mapping

Convert debit and credit CSV columns to IIF

When a transaction export separates money out from money in, LedgerConverzn Plus gives you a direct way to map those two columns before creating a local IIF file.

Use one side per transaction where possible: an ordinary withdrawal should have a debit value and an ordinary deposit should have a credit value.

Why separate columns need careful mapping

A signed Amount column already carries direction: negative values represent outflows and positive values represent inflows. Debit/Credit exports store that direction in two different places, so the field mapping has to preserve the meaning rather than simply adding both columns together.

Expected columns

CSV field	Typical meaning	How to review it
Date	Transaction date	Confirm the month/day/year or ISO interpretation.
Description	Payee, memo, or transaction detail	Check that the useful text is in one column.
Debit	Money leaving the account	Usually positive in the source, then treated as a negative transaction value.
Credit	Money entering the account	Usually positive in the source, then treated as a positive transaction value.

How the workflow works

Load the CSV. Select the file locally after saving it as comma-separated data.
Choose debit/credit mode. Use the Plus controls added to the LedgerConverzn workspace.
Map each field. Select date, description, debit, and credit columns.
Analyze the net values. Inspect the normalized amount and row status.
Export after review. Download the IIF only after checking ambiguous rows and accounts.

Example

For Date,Description,Debit,Credit, a row such as 07/08/2026,Software renewal,18.00, becomes an outflow, while 07/09/2026,Refund,,18.00 becomes an inflow. Keep the original export so you can compare the result.

Ambiguous rows and limitations

If both debit and credit are populated, LedgerConverzn calculates a net value but does not know whether the row is a transfer, correction, or compound transaction. The current IIF generator focuses on basic deposits and checks; it does not build split entries or preserve every source-specific field. LedgerConverzn is independent and is not affiliated with, sponsored by, or endorsed by Intuit Inc.; Intuit and QuickBooks are registered trademarks of Intuit Inc.

Debit and credit CSV to IIF FAQ

Do I need Plus for a signed Amount column?

No. The standard workflow maps one signed amount column. Plus is useful when the export has separate debit and credit controls.

Should debit and credit values be negative?

The current mapping treats the debit and credit fields as magnitudes and applies direction itself. Review the preview if your source uses an unusual sign convention.

Can this preserve transfers?

Not reliably. Transfers and other specialized transaction types require additional modeling, so review or clean those rows separately before relying on the export.

Open LedgerConverzn Bank CSV workflow General CSV to IIF Spreadsheet workflow Account access Privacy Security Pricing