Click on the question choices below to find solutions to your questions.
The NSF charge occurred because there weren’t enough funds in the customer’s account
to cover the payment. We recommend clearing any NSF charges before processing further
ACH payments to avoid additional issues.
To correct an ACH batch error where the wrong account type was selected, you can
manually edit the transaction code in the ACH export file (EDIFILE.txt). After making the
correction, re-import the updated file into your ACH processing software to send the
corrected batch to your bank. If the payment batch has not been finalized, you can also
make corrections directly in your financial software before generating a new ACH file.
Ensure to export ACH credits using the EDIFILE before running any additional batches, as
running the RCR will refresh the EDIFILE each time. This step prevents any loss of data and
maintains the integrity of your disbursements and payments in separate files.
If an ACH disbursement is denied due to an incorrect account number, correct the
account number in your ACH setup. Then, create a temporary transaction in your payment
system for the same amount and date to generate a new EDIFILE. After the new EDIFILE is
created, delete the temporary transaction and send the updated EDIFILE to your bank to
complete the process.
If the totals do not match, rerun the RCR for the credit batch to ensure all transactions are
accurately captured and the totals align.
If a voided check was accidentally cleared, causing a discrepancy in the balance, you
should perform a Manual Transaction Entry (MTE) to correctly adjust the funds in the trust.
Then, disburse a replacement check from the trust account to correct the error.
Additionally, ensure to align and verify all transaction dates and details to prevent future
discrepancies.
If a check does not have the correct void date when voiding it, and the check was purged
during the last purge while the void was not, you need to delete the void line in the register.
Rerun your RCR to recreate batch and reprint checks. Only the correct ones will update to
Bank Rec.
The check numbers were incorrect because a check was reissued using Write Check,
which caused the daily processing check numbers to be off by one. To fix this, you can edit the
check numbers for all the regular processing transactions. However, for the Write Check, you
will need to delete and re-enter it because it has already been printed and attempting to edit it in
Write Check results in an error message.
Go into your check register, delete it, and then re-write the check.
Since these void entries are different from the usual two-line void process, you should
delete the incorrect void entries and re-enter them with the correct void amount, which should be
zero. This ensures that the checks are properly updated and reconciled in the system, then they
can be updated in BAR.
Re-run RCR, run all your reports again, and compare these results with the first run.
Line up the check numbers from each batch and print to a blank piece of paper.
In the past, we have seen where an extra S may have been added to the file name (ex.
WCCSS.mdb) or someone changed the name in another way. Find the database with the
incorrect name and change it back to WCCS2023, WCCS2024, etc. The current year database
should always be named WCCS.mdb.
Another workstation may have the app open, minimized, or someone may have an
executable running in the background. Make sure everyone on your team is logged out first (you
can check this by going to Utilities > Active Users), then run Utilities > Compact & Repair.
This almost always indicates that an incorrect interest start date is in one of the accounts
(ex. Either a
year that has already happened or a year way in the future). Check that the dates entered in your
accounts are accurate.
Reboot your workstation and try again. If the same error occurs, ODP suggests you
upgrade the Netmover, as you are likely on an older version.
Had what looks like a partial delete that left the cust, disb and tax records but no
account # in the Master. I will have her send the db and I will remove the leftover from the
deletion.
This is not a Lincoln Data error, but we can help you solve the problem.
How to register msstdfmt.dll for Windows 7, 10, or 11:
1. Login as user.
2. Run “cmd” as the Administrator.
3. Change directory to cd\Windows\SysWOW64
4. In the “cmd” window from the directory, type: C:\Windows\SysWOW64 then ENTER
5. Now type regsvr32 /u msstdfmt.dll and hit RUN/ENTER. **If you do not run this first it will
not work.
6. Now type regsvr32 msstdfmt.dll and hit RUN/ENTER
Reversing the payment will primarily affect the principal and interest parts of the payment, as
well as
reverse any assessed late charges. This reversal will adjust the balances, including the number of
loan
payments and dates, the late charge balance, principal balance, and Year-to-Date (YTD) and
Life-to-Date
(LTD) Principal & Interest. However, the buyer fees and late charge payments are not part of the
payment
reversal and will need to be handled separately as a bookkeeping task to return the amounts to the
buyer.
When your Lincoln Data account is set up, the payment frequency is set, so you can customize
this to
a bi-monthly payment structure. However, you cannot create bi-weekly payments.
If you encounter an error message about your calculations when posting payments, try the
following
steps to resolve the issue:
1. Rerun RCR to create fresh temporary files.
2. Run the registers and assign the same check numbers as you previously used.
3. Run UPF to update your day’s work.
These steps usually fix the problem and ensure your calculations are correct.
The best way to back out payments due to an NSF check is to perform an MTE adjustment for both
payments. This method will ensure that the adjustments are clear and easy for the customer to review
on their
account history. Additionally, check the last good payment to see if any accrued or prepaid interest
needs to be
adjusted accordingly.
To fix a payment posted to the wrong account due to an incorrect account number, follow these
steps:
1. Use MTE to adjust the Principal Balance (PBAL), Year-to-Date Principal (YTDP), Year-to-Date
Interest
(YTDI), interest paid-to-date, and payment due date to the correct values.
2. Print the Account History Log (AHL) and highlight the last correct payment to establish a
baseline for the
adjustments.
If a negative balance is showing on the Batch Calculation Summary after running RCR, it is
likely
because a debit payment was updated in the ACH Debit payment amount but not in the reserve field. To
resolve this, ensure that the debit payment is also correctly updated in the reserve field. This
should correct the
negative balance in the summary.