Credit card CSV signs: why payments can be negative

A minus sign can mean less debt or more debt

This guide covers transaction CSVs, not journal entries. We checked QuickBooks Online US help, YNAB web file-based import, Xero Central (United States) and Sage 50 Canada 2023 Bank Services help on October 17, 2026. The Sage steps are version-specific, so they aren't confirmed for every current edition. These are documented workflows, not live import tests.

If you have a usable bank export, you don't need PDF conversion to fix its signs. Keep the bank's original CSV and statement for comparison as you work out which convention the export uses:

• In the card-liability view, positive means more owed. Purchases and interest add to debt, while refunds and payments subtract from it. This matches the arithmetic of a statement that shows debt as a positive balance.
• In the bank-account cash view, positive means money in, so spending is negative and receipts are positive. Purchases push an indebted card's balance farther below zero. Payments move it toward zero and can take it above zero. Debt is negative here.

Those conventions explain direction, not the format your app needs. Intuit's CSV guide, updated August 24, 2026, explains why a card payment may be negative and says to select a credit card account. Xero's CSV guide, checked October 17, 2026, asks for card payments positive and purchases negative. You can't carry one vendor's rule over to another app.

A credit balance isn't automatically a sign error. In a separate fictional example, owing 50.00 and receiving a 100.00 refund gives 50.00 - 100.00 = -50.00 in the liability view, or +50.00 in the bank-style view. Both mean a 50.00 credit, not 50.00 of debt. The statement's balance label tells you which it is, so don't take the absolute value or force it below zero. See YNAB's positive-balance guide, updated July 28, 2026.

A Credit or Debit header alone won't settle the sign question either. Start with a transaction you can identify, and use the debit/credit column guide to check what separate columns mean.

Four transactions, opposite signs, same debt

Suppose your September 2026 card statement is in USD and you start owing 1,000.00. This fictional example shows the same four transactions under both conventions:

In the liability view, the movement is 240.00 - 35.00 - 300.00 + 12.50 = -82.50. Your debt falls by 82.50: 1,000.00 + (-82.50) = 917.50 owed at closing.

In the bank-style view, the opening balance is -1,000.00, movement is +82.50, and closing is -917.50. You owe the same amount. The balance convention has to change with the transaction convention, because positive debt balances combined with bank-style transaction signs give a false mismatch.

The positive 300.00 is the payment arriving in the card account, while it leaves checking as negative 300.00. Purchases, refunds and interest still belong to the card, so don't copy all four rows into checking just because they use bank-style signs.

A 300.00 payment in both downloads represents two sides of one transfer, not a reason to delete a valid statement row or book the supplies twice. Match an existing payment rather than creating another. For QuickBooks, follow Intuit's credit-card payment and pairing instructions, updated August 5, 2026.

Reversing signs won't fix the wrong account

In the same fictional example, checking opens at 5,000.00 with only the 300.00 card payment. If you import all four liability-signed card rows into checking as ordinary cash movements, the arithmetic looks like this. It's not an observed app result:

Checking is 217.50 too high, and reversing all four rows wouldn't make them belong there. The account selection and amount mapping need correcting instead. Intuit's instruction to choose a card account isn't just about its name.

Even in the right card account, reversing all four movements while keeping a positive amount-owed opening balance gives 1,000.00 + 82.50 = 1,082.50 owed instead of 917.50. The difference is 165.00, twice the original net movement's magnitude. A fully reversed file can look plausible if you only check its closing total.

If you reverse just the payment from -300.00 to +300.00 in the liability view, debt closes at 1,517.50, a 600.00 error. A sign flip changes the total by twice the transaction's amount. That's why a global reversal won't fix a mixed file: it breaks the other rows.

The statement is your reference, not today's balance

1. Your reference is one complete statement period's opening and closing balances, not today's online balance, available credit or minimum payment due. Record whether positive means cash available or debt owed, keeping cards and currencies separate. Check the full statement before removing already-imported rows, because a partial upload needn't reproduce the full closing balance.
2. A known purchase and payment let you check direction against the statement and CSV by description and amount. Here, the 240.00 purchase increases debt and the 300.00 payment reduces it, whatever their printed signs.
3. Refunds and interest need checking too, even outside the purchase section: the 35.00 refund reduces debt, while 12.50 interest increases it. Include every posted row, including fees, cash advances, statement credits and reversals, but don't count summary totals or payment-due figures as extra transactions. A reversal has the opposite effect of the original entry, so check the source rather than deciding the sign from the word "payment" alone.
4. Adding every transaction in one convention should give 917.50 owed in the liability view, or -917.50 in the bank-style view. Keep this calculation separate from your upload copy.

Running balances, if available, give you another comparison. Calculated debt after each fictional row is 1,240.00, 1,205.00, 905.00 and 917.50; these aren't balances from a real statement. Without running balances on yours, you can't independently check these checkpoints against its rows.

The statement balance checker compares opening plus rows with closing, all in one convention. A zero difference checks arithmetic, not categories, agreement with your books or statement authenticity. Offsetting errors can still leave a statement balanced, so you still need to compare the rows with the source.

If the importer is unfamiliar, use synthetic transactions in a separate test company or account to learn it without touching a client's live books. A preview showing unexpected directions is a reason to stop, not confirm.

QuickBooks Online: choose the card account first

Intuit's US CSV formatting page, updated August 24, 2026, allows three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit). Its ordinary three-column example shows a negative payment. A separate card note says payments may be negative because they reduce the card balance. It tells you to choose a credit card account, not a bank account.

That doesn't promise automatic recognition of any card CSV. Once you've selected the actual card account and mapped the file, check the preview to see whether the purchase and payment increase or reduce what you owe.

The video transcript on Intuit's manual-upload page, also updated August 24, 2026, shows reverse all values on the amount-check screen. It's for a consistently reversed file, so don't also reverse the spreadsheet: two reversals restore the problem. For column or date errors, see fix a QuickBooks CSV import.

YNAB: the preview should show a payment inflow

YNAB's File-Based Import guide, updated September 22, 2026, recommends CSV and maps your columns to its fields. The web import window lets you check the account and adjust field dropdowns if needed, while Swap Inflow and Outflow corrects reversed directions.

If your file has one signed Amount column, you can select it for both Inflow and Outflow without splitting it first. Before confirming, look for a purchase outflow and a payment inflow, as in YNAB's card-activity guide, updated October 11, 2026. If the preview is already correct, leave the swap option alone.

Because Remember setting for this account is selected by default, it needs another look when your source file changes. A reversal that fixed one export may be wrong for another.

Deleting a bad import doesn't necessarily let you start again. The File-Based Import guide says imported-then-deleted transactions can't ordinarily be re-imported into that account. Checking the preview first avoids this problem. Before deleting rows, read the guide's recovery options or contact support.

Xero: card payments positive, purchases negative

Xero Central's US CSV import guide, checked October 17, 2026, says to use one Amount column with card payments positive and purchases negative, as in our bank-style example. For negatives, a leading minus or brackets are accepted, but commas aren't allowed as decimal separators.

If your source uses liability signs throughout, reverse all four signs in a separate upload copy once you've confirmed that convention. Keep the original and statement check. Xero says to remove opening/closing balance columns from the upload, but they still belong in your review workpaper.

Before you reach Complete import, the guide takes you through selecting the account, assigning columns and reviewing transactions. That review should include the purchase, payment and any remembered mapping. For file preparation, see prepare a bank CSV for Xero.

Sage 50 Canada: check money in and money out

Sage 50 Canada 2023's Bank Services upload help, published July 17, 2023, covers CSV and OFX uploads with a service plan that includes Bank Services. The flow asks you to confirm each transaction as money in or money out, then review. If you find discrepancies, return to Verify before choosing Import transactions. That imports into the cloud bank account; Get Transactions in Match Transactions then brings the rows into Sage 50.

The known purchase and payment matter here because the page gives no universal credit-card CSV sign rule. We aren't deriving one or claiming these steps apply to Sage 50 UK, US or other releases, so check the help for your installed product and account setup.

Recreating an account isn't a way to test a sign change. The page says this flow prefixes an existing imported account with ARCHIVE when creating its cloud-based account, and you must finish matching and reconciling remaining transactions in that archive account.

Stop if the preview is wrong

Before confirming, have the untouched statement, original CSV and separately named upload copy ready for comparison. Check the product, region and actual card account together with any remembered swap or reversal setting, then check whether the dates and transactions are already imported.

When every row is backwards, look at the account type and global mapping. If only one transaction type is backwards, those rows need correcting from the source instead. If the amounts and directions are right but the total isn't, check the opening balance, missing rows and overlapping imports. Changing a balance or adding an adjustment just to make it pass won't fix those problems.

If you've already imported the bad file, another upload can add duplicates. Before uploading a corrected copy, find which rows were accepted, matched or reconciled and follow the app's recovery instructions. The historical-import guide covers where to start and stop. After import, match the transactions and reconcile to the statement.

If you only have a PDF

A PDF doesn't have to mean conversion: ask the bank for a native export first, or enter the rows manually for a short statement period. QuickBooks Online also documents PDF and image statement upload with side-by-side review, though you'll need to check whether that route is available in your account.

If you need reviewable data from the PDF instead, you can convert it with AnyStatement. Transactions link to source PDF lines, and available statement balances are checked against the rows, so you can investigate whether a sign came from a printed amount, column or extraction mistake. You still need the right destination account and must check the import preview.

What we checked, and what we didn't test

On October 17, 2026, we opened the linked Intuit CSV-formatting, manual-upload and card-payment pages; YNAB file-import, card-activity and positive-balance guides; and Sage 50 Canada 2023 Bank Services upload help. In Xero Central, we selected United States and expanded CSV preparation and import, including the card sign rule. Xero showed no article update date.

We independently recomputed every fictional figure with Python Decimal, including both conventions' totals, opening and closing balances, checkpoints, the credit balance, wrong checking account, and full-file and payment-only reversals. We also checked the product description against the repository README, source-line review interface and reconciliation implementation. No customer data was used. We didn't test live QuickBooks, Xero, YNAB or Sage imports, account migration, deletion/re-import recovery or PDF conversion, so these are documented behaviors, not tested compatibility or a professional review of your books.