Tables Associated with Chargeslips
There are numerous tables assosciated with Chargeslips. Below is a list the 3 major tables that are used when processing Chargeslips and a brief description of how the data in the tables is created and some of the data field names. These can be used when researching possible issues with Billing Transactions.The tables are: BIL_Chargeslips - contains basic information for chargeslips that were entered when the creating the chargeslip. Fields - Chargekey, clientkey, staffkey, OP__Docid, DateSvc, Inspolicykey, admissionkey, ContractRate and PrimDiagkey. BIL_Chargetranslog – contains the information created from the chargeslips after it has been Final Saved and again after the Chargeslips have been processed. Fields - Chargekey, clientkey, staffkey, OP__Docid, DateSvc, Inspolicykey, admissionkey, DoWaterfall, PrimDiagkey, TransTypeLU, DisplayAmount,Delta, Descr and Chargetranslogkey. BIL_ARtranslog - contains the information created from the chargeslips that have been Final Saved and after the Chargeslips have been processed. These records are created by a trigger on the BIL_Chargetranslog table, except for requests for payments, but also includes the records of the Client Deposits that are created, and the waterfalls from one policy to another Fields - Chargekey, clientkey, staffkey, OP__Docid, DateSvc, Inspolicykey, admissionkey, ContractRate and PrimDiagkey, TransTypeLU, PayorPlanKey, InitialCharge, Balance, Delta, DateTrans, ctlkey and ARDesc.The main way of linking these 3 tables is by using the ChargekeyThese are the main tables which are used on the Chargeslip processing. But, they are by no means the only tables used for Billing. There are also tables that contain the insurance information and payor information. **Whenever making corrections to improper postings, it is important that ALL of the tables affected by the type of transaction being corrected are checked.(see attached pdf for entire Tidbit and accompanying screen shots)
