| Notes on Transferring A/R and Transactions |
Keep in mind the following when transferring information.
Transferring A/R Balances
|
|
When transferring A/R, Ledger, and Client Funds, all ledger amounts and billing history for the client will be transferred. For example, let's say you have a client you've billed every month for over 5 years. This client has a $65.00 accounts receivable balance and you want to transfer this balance to another client. If you use this utility to transfer the A/R, Ledger, and Client Funds information, all client ledger amounts and payments for the past 5 years for this client will be transferred to the new client number. If you want to transfer the current accounts receivable balance only, you can use the following method as an alternative. Enter credit transactions to the client with the balance. Then enter transaction(s) for the client you want the balance transferred to, run a final statement and update it. This method has the advantage of retaining the original client's billing history with the original client. |
|
|
When transferring A/R, Ledger, and Client Funds, the client funds balance, archived client funds transactions, and work-in-process client funds transactions are transferred to the new client. Other Client Funds information such as Fund Application, Minimum Balance, Target Balance, Statement Format, One Time Retainer, Retainer Amount, and Amount to Bill is not transferred. |
|
|
You will not be able to transfer A/R, Ledger, and Client Funds information if the Receipt Allocation by Invoice option is set differently for the two clients. |
|
|
If the original client's accounts receivable and receipt allocation amounts are out of balance, then the new client's accounts receivable and receipt allocation amounts will also be out of balance after the transfer. |
|
|
If you transferred A/R in prior versions and are numbering at the client level, then it is possible that you will have duplicate statement numbers. |
|
|
If you transfer A/R and are numbering at the client level, the default statement number for future statements will be based on the highest statement number used by the client before A/R was transferred (plus 1). This can present a situation where newly run statements can have duplicate statement numbers. For example, let's say client A has 5 statements and client B has no statements and the A/R for client A is transferred to client B. If a statement is run for client B, the default statement number will be "1" because the highest statement number used for client B was "0" (i.e., no statement had been run). The new statement number 1 will be a duplicate statement number. However, this is not a problem because each statement has a unique internal statement ID field. |
|
|
If you transfer A/R and a write off is included in the A/R, the associated description only fee is also transferred, even if it is currently work-in-process. |
Transferring Transactions
|
|
If the category on a fee transaction is the client's default category from the Client Information window, then the category will be changed to the new client's category when the transaction is transferred. Otherwise, the category on the fee transaction is not changed. |
|
|
If the rate on a fee transaction is the client's default rate, then the rate will be changed to the new client's default rate when the transaction is transferred. Additionally, the amount will be recalculated and changed to reflect the new rate. Otherwise, if the rate specified on a fee transaction is not the client's default rate, then neither the rate nor amount is changed when the fee transaction is transferred. |
|
|
If the sales tax rate on a fee or cost transaction is the client's default sales tax rate from the Client Information window, then the sales tax rate will be changed to the new client's sales tax rate when the transaction is transferred. Otherwise, the sales tax rate on the transaction is not changed. |
|
|
Transactions that have been included on a pre-bill or final statement cannot be transferred using this utility. You must undo the pre-bill or unbill
the final statement if you want to transfer them, or drill down to the transaction from the Pre-Bill Information window and use the Transfer Transaction action.
|
|
|
Information cannot be transferred to inactive clients. If you need to transfer payments or credit transactions to an inactive client, change the To client from inactive to active, transfer the transactions and then change the client back to inactive. |
|
|
Tabs3 Billing will not allow you to transfer billable fees and costs to a non-billable client. However, you can transfer accounts receivable information and non-billable transactions to a non-billable client. Therefore, you are allowed to select a non-billable client as the To client. |
|
|
If the user transferring transactions is assigned Tabs3 Timekeepers, only transactions for assigned timekeepers will be transferred. |
|
|
If you transfer a work-in-process payment, any allocations for the payment
will be cleared. The payment can be re-allocated to accounts receivable by accessing the payment in the
Payment Entry window and clicking the |
|
|
When integrating with General Ledger (GL), transferring a work-in-process payment will post reversing journal entries for the prior allocations and new journal entries to the Unapplied Payments account, even if the payment has been reconciled. You will be prompted to enter the date to use for the GL adjusting journal entries. |
|
|
If you attempt to transfer a work-in-process payment created by a client funds Payment to Firm without transferring client funds transactions, a message will be displayed and the payment transaction will not be transferred. Similarly, attempting to transfer client funds transactions that have linked work-in-process payments without transferring payment transactions will display a message and the work-in-process payments will be transferred as well. Client funds transactions and linked payments must remain linked. |
|
|
Transferring a linked credit card transaction will not create adjusting information on the Tabs3 Pay®, LawPay®, or LexCharge® website. You must visit the processor’s website to make the appropriate changes. Alternatively, you can delete or adjust the payment from Tabs3 Billing as necessary and reenter it. This will prompt the processor to create the necessary void/credit transactions. |
|
|
When undoing an updated statement, keep in mind that only the most recently updated statement can be unupdated. The most recently updated statement is based on the largest Reference Number shown in the Statement Ledger Lookup window (i.e., not the Statement Date or Statement Number). When transferring A/R, Ledger, and Client Funds, statements for the transferred client may have an older Statement Date with a larger reference number, or a newer Statement Date with a smaller reference number. For example, a statement was updated for the original client with a Reference Number of 12. Later that day, you transfer A/R, Ledger, and Client Funds for a client with Reference Numbers of 13 and 14 dated last month. The next day, you need to undo the statement with a Reference Number of 12, but you must first undo the transferred statements numbered 13 and 14. |
| If fee or cost records are transferred from a non-Task Based Billing matter to a Task Based Billing matter, no Phase/Task and Activity Code will be assigned, which will cause DFIC Error 81 until those transactions are edited. The Change WIP Transactions utility can also be used to convert transaction codes to task based billing codes for existing work-in-process transactions. |