Understanding C H Accounting Credit Adjustment Fdes
If you are working with C H Accounting Credit Adjustment Fdes, you already know this isn't one of those tools that makes everything click into place automatically. It does what it says on the tin, which is adjust credit entries across accounts when transactions don't reconcile properly. The system itself is functional but the documentation is scattered, and the edge cases will bite you if you haven't dealt with them before. I ran into a situation last year where a client had a partial credit memo applied to an invoice that was already marked as paid through a batch payment process. The adjustment function wouldn't let me reverse the credit because the original transaction was tied to a closed fiscal period. What actually worked was manually unhooking the payment from the invoice first, then running the credit adjustment, then reapplying the payment. Took about 20 minutes instead of the three hours I'd expected while I was poking around trying to find a button that didn't exist.
How C H Accounting Credit Adjustment Fdes Actually Works
The core mechanism is straightforward. You enter the original transaction reference, specify the credit amount, and the system creates a reversing entry that flows through the appropriate general ledger accounts. The key detail most people miss is that the adjustment doesn't modify the original invoice or receipt. It creates a separate offsetting record that appears on reconciliation reports as a paired entry. This matters because auditors will look at both records independently, and if your descriptions don't match up properly, you end up spending time explaining discrepancies that technically aren't there. When setting up your adjustment, make sure you are using the correct GL account mapping. The system has default mappings for common scenarios like customer returns, vendor credits, and write-offs, but these defaults assume a standard chart of accounts. If your organization uses cost centers, departments, or projects as secondary dimensions, you need to populate those before submitting. I've seen adjustments rejected at the validation stage because someone forgot to fill in the department field, and the system treated it as an incomplete record rather than flagging it as a simple data entry error. There is also a timing issue worth noting. Credit adjustments made in one period can affect the closing status of that period depending on your configuration. Some setups allow adjustments to open periods that are marked as closed for posting, while others lock everything down once the period close runs. Check your period status carefully before processing. Running an adjustment against a locked period will either fail silently or throw an error that points you in the wrong direction depending on your version.
Common Pitfalls and What to Watch For
The biggest issue I see people hit with C H Accounting Credit Adjustment Fdes is duplicate adjustments. The system doesn't have a built-in duplicate check based on transaction reference, so if you run the adjustment twice by accident, you now have two offsetting entries and your books are out of balance again. The workaround is to create your own tracking log before you start. I keep a simple spreadsheet with the transaction ID, original amount, adjustment amount, date processed, and the person who approved it. It sounds tedious, but it saves you from explaining to your controller why there is a mismatch during month-end close. Another thing that catches people off guard is the handling of tax on credit adjustments. If the original transaction included sales tax or VAT, the adjustment should ideally reverse that tax component proportionally. The system will do this automatically in most cases, but only if the tax codes are configured correctly on the original entry. I worked with a client whose adjustment kept pulling the wrong tax rate because the original invoice had been entered with a manual tax override, and the system didn't inherit that override into the adjustment logic. We ended up calculating the correct tax reversal manually and entering it as a separate line item to fix the discrepancy. Troubleshooting tip: if your adjustment appears to go through but the accounts still don't reconcile, check the posting status in the transaction detail screen. Sometimes the system shows a success message but the actual GL posting fails due to a budget check or account combination validation error. The failure message can be buried several clicks deep, and if you only look at the summary screen, you might assume the adjustment posted when it actually sits in a pending or error state.
Get the Full Details

Where to Get the Software
C H Accounting Credit Adjustment Fdes is distributed through the official C H software portal at ch-accounting.com/downloads/adjustment. You will need an active support contract to access the download page, and the installer requires administrative privileges on the machine where you are installing it. The current version is 4.2.1, and it supports the latest ERP integrations but not the legacy versions from before 2019. If you are running an older system, you will need to check compatibility before purchasing the license. There is no free trial available, but the vendor does offer a sandbox environment for testing. If you are serious about implementing this, set up a test environment first and run through your actual transaction types before rolling it out to production. I always recommend testing with a small set of real transactions from the current period rather than sample data, because sample data never quite replicates the edge cases you deal with in normal operations. The license model is per-seat with an annual maintenance fee that covers updates and support. Pricing starts around $299 per seat per year, though volume discounts are available if you are deploying across a larger team. The maintenance contract is where most people cut corners, but skipping it means you miss patch releases that fix known bugs, and those bugs tend to show up right before month-end close.
Final Thoughts on Practical Use
C H Accounting Credit Adjustment Fdes is competent software that does its job if you understand the quirks. It is not the kind of tool where you can wing it and expect clean results. The setup phase matters, the period timing matters, and the documentation you keep around each adjustment matters. Treat it like any other process in your accounting workflow, document your steps, and verify the output rather than assuming the system handled everything correctly. If you are dealing with high volumes of credit adjustments, the manual tracking I mentioned above becomes even more important. I have teams that process over fifty adjustments per month, and without a systematic approach, errors accumulate quickly. A simple naming convention for adjustment records, consistent GL account usage, and regular reconciliation checks will catch most issues before they become real problems.