> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upflow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding Fix Transactions

> Learn what fix transactions are in Upflow, why they appear, and how they keep your balances aligned with NetSuite, QuickBooks, Chargebee, or other accounting systems.

Fix transactions are synthetic transactions that Upflow creates to ensure your account balances match your accounting system (source of truth - i.e., NetSuite, QuickBooks, Chargebee, etc.).

While they may look unusual at first, they serve an important purpose in keeping your data accurate.

## What are fix transactions?

There are two types:

#### Fix transactions

Example: the reference starts with "fix:".

* Created at the invoice level
* Adjust or compensate a specific invoice balance
* Used when Upflow cannot import or fetch the exact original payment application from your accounting system

#### Customerfix transactions

Example: the reference starts with "customerfix:".

* Created at the customer level as an unapplied adjustment
* Correct the overall customer balance without being tied to a single invoice
* Ensure the total balance matches your source system even when individual transaction details are unavailable

## Fix transactions dates

You may notice fix transactions show dates that are 1-2 years in the past. This is intentional:

* **Customerfix transaction** s: Usually created 1-2 years in the past to avoid affecting your analytics and payment list views
* **Invoice fix transactions** : Created on the invoice date to compensate for payments we couldn't import

The day and month are usually accurate or close to the actual date, but the year is adjusted to minimize visibility in current reporting.

## Common reasons fix transactions are created

* Upflow cannot import the complete payment application details from your accounting system
* There are balance discrepancies between your source system and Upflow
* Currency conversion rate differences exist between systems
* Integration limitations prevent full data import
* Payment records exist in your source system but cannot be matched to invoices in Upflow

## Troubleshooting: How to identify fix transactions

### In the Payments list view:

1. Go to your Payments list or the Payments tab at the customer level
2. Type "fix:" in the search bar
3. This will show all fix transactions (both fix: and customerfix:)
4. You can export this list if needed
5. Sort by columns like "Received date", “Imported date”, or use filters to refine results (e.g., filter by Type to see payments vs. refunds)

### What to do if you see fix transactions?

Most fix transactions are “expected”, and indicate that Upflow is working to keep your balances as accurate as possible. However, if you notice:

* A high volume of fix transactions
* Recurring fix transactions for the same customers
* Balance discrepancies that concern you

Contact Upflow support with examples from Upflow, and related customers from your Source of truth:

* Screenshots from the customer balance and recent invoices + payments/refunds/credit notes.
* References of the related data (invoice/payment/refund/credit note **number** + **external ID**).
* Any history/audit trails on the missing reference (usually payment) would be very useful to our team as well.

Our team can investigate whether there's an underlying sync issue with your integration or if adjustments can be made to reduce fix transaction creation.