Sage 100: Fix for "Transaction not found REFID" error when capturing payments
Posted: October 10, 2024
Affects Sage 100 implementations with SQL databases. Flat file storage isn't affected.
Recently, transaction IDs from the payment gateway increased to 11 digits. By default, Sage 100 supports 10-digit transaction IDs. Pre-authorizations were still successful, but only the first 10 digits of the transaction ID were stored in Sage 100. Running the Daily Sales Reports/Update process to capture pre-authorizations resulted in Transaction not found REFID
errors like the following example.
Version 7.09 of the REPAY addition increases the field length to 15 digits and ensures that all future transactions will be supported.
Resolving Payment Captures That Failed
- Update to the REPAY addition version 7.09. REPAY installers are available from the Sage 100 7.09 Release Notes.
- Sign in to the payment gateway and run a report to retrieve the transactions with the error. Download the report. The first column of the report contains the transaction ID.
- In Sage 100, fix incomplete transaction IDs:
- Go to Library Master > Utilities > Data File and Display Maintenance and open the Sales Order (
so_salesorderpayment
) or Sales Invoice (so_salesinvoicepayment
) payment table (as applicable). - Browse or search the records and locate the sales invoice or sales order to update. Click Edit.
- Copy the transaction ID you downloaded from the payment gateway and paste it in the
CreditCardTransactionID$
field. Click Update to save changes. - Repeat this step to fix other payments.
- Go to Library Master > Utilities > Data File and Display Maintenance and open the Sales Order (
- Re-run the Daily Sales Reports/Update to resolve payment captures that previously failed due to the error.
- Go to Sales Order > Daily Sales Reports/Updates and select Perform Payment Processing.
- Click Print to process payments.
For detailed instructions with screenshots, see Sage100 7.09: How to fix "Transaction Not Found REFID" error.