ALIS

Detail

Y

Y

Y

Resident billing data should be loading in the following manner: Last Name,First Name. Payer Type will always be Private. Last Name,First Name is the billing ID.

AMSI

Detail

Y

Y

Y

Resident billing data should be loaded in the following manner. Building-Unit-Resident Billing Id

AOD

Summary, Summary By Date, Summary by Date Hour, Detail

Y

Y

Y

When user imports the file, they will need to select Delimited and have ^ as the delimiter.

Accountmate

Detail, Summary

N

Y

Y

Sales tax as separate line is required to be Yes for the file as sales tax is displayed for each customer as part of the invoice created.

Achieve Pathlinks

Summary

Y

N

N

American HealthTech

Summary, Summary by Date, Summary by Date Hour

Y

N

Summary By Date and Date-Hour Only

These formats can be run with the quantity field included or excluded.

Cantata Health

Summary By Date

N

Y

Y

Item billing data should be loaded in as GL#-Description.

Cross Tab (Excel Report)

Summary

N

N

N

This is an excel report format to be used if communities do not have a billing system that accepts an export.

Cross Tab with Customer Details

Summary

N

N

N

This is an excel report format with customer details to be used if communities do not have a billing system that accepts an export.

CYMA

Detail

N

N

Y

Billing id data should be loaded in as Customer Id-Ship To Id.

Eldermark

Summary

N

Y

N

Entrata

Summary by Date

Y

N

Y

Financial Edge

Summary

N

Y

Y

Item billing data should be loading in as Billing Item Id~Charge Distribution Credit Account Number^Description.

Great Plains

Summary by Order, Bill Code (Sales Order), Detail (Receiveables Transactions), Summary (Receiveables Transactions)

N

N

N

Additional setup is typically needed with Great Plains to import a file. Please contact Diann Fariss <DiannF@expressinfo.com> and Express Info Support <support@expressinfo.com> to confirm import is setup.

There are two different types of imports in Great Plains. One is for sales orders. The other is for receiveables transactions. Confirm with the community which process in Great Plains they would like to import into. To use summarization by order, bill code, Item Description in Billing File for the community must be set to Order (Great Plains/Straco). For the Receiveables Transactions file, a grouping column can be included by setting the item bill code as Bill Code^Grouping Column.

JD Edwards (Vi Living)

Summary

Y

Y

Y

This file is primarily to be utilized with Vi Living for JD Edwards.It may work with other communities, but this should be vetted first.

LTC

Detail

N

N

Y

This format creates an Excel spreadsheet with one tab per bill code.

Keane Care

Summary

Y

N

Y

Mas 90

Summary

N

N

N

Matrix (Also called MDI Achieve or MatrixCare)

XML (Summary, Detail), Tab Delimited (Summary by Date Hour, Summary by Date Hour (with modifier columns), Detail)

N

N

All except Detail (tab delimited)

Some versions of Matrix require the modifier columns. Check with community to see if that is true in their case. Some communities may have to pay an additional fee to be able to load the tab delimited files.

Microsoft Dynamics

Summary, Summary by Order

N

Y

Y

If utilizing mutiple descriptions, Item billing data should be loaded in as BillCode-Description. The Summary by Order file format was developed specifically for communities managed by Era Living and will likely not work for other communities. The summary (and all other future options) should be utilized by communities not managed by Era Living.

Move N

Detail

Y

Y

N/A (See notes)

Bill codes should be loaded in as BillCode^GL Code to parse properly on the file. Sales tax is a field on the billing file, so the sales tax on separate line field is not applicable.

myUnity

Summary, Summary by Description, Summary by Date, Summary by Date Hour, Summary by Date Hour (Resident Id), Summary by Date Hour (Unit Price), Summary by Date Time, Detail, Detail (Resident Id and Facility Id)

N

Y

Y

User will need to select semi colon (;) as the delimiter for the file. Most communities will use Admission Id for their billing id. This is the default for our myUnity billing files and used unless stated in the billing file name. The file formats including Resident Id in the name import using myUnity's Resident Id field. There are also several options for version 8.5+ if a community is having issues uploading the other billing files. Payor code can now be included in the non-summary billing files by appending "~" and the payor code in the customer's billing id. This software was formerly known as Vision.

NTT Data

Summary

Y

N

N

Facility ID must be filled in, but it can be any value.

OneSite

Summary

N

N

N

Peachtree

Summary

N

N

N

Item billing data should be loaded in as BillCode-GL Account

Point Click Care

Summary, Summary by Date, Summary by Date Hour (Unit Price), Detail

Optional

Y

Y

Patient ID should be used for Billing ID. The client will need to be sure to set PCC to "Use amount from file". Otherwise it will charge the base price assigned to the bill code instead of the total  being sent over. For PCC, if the customer wants to have the description field populated per bill code, it can be put in the bill code field as BillCode^Description.

PropertyBoss

Summary

Y

N/A

Y

PropertyBoss requires lease start date. We are using the resident's effective start date for the lease start date field.

Quick Care

Summary

N

N

N

Real Page / One Site

Summary, Detail (CSV or XML)

Y

N

CSV Only

Resident billing data should be loaded in as Resident Id-Lease Id. Bill code data should be loaded in as Trans Name^Trans Description. XML file format should only be used when the customer has the sde-convergent module.

Rent Manager

Summary

N

N

Y

Sage

Summary

N

N

N

Sage Intacct

Summary, Summary by Date-Hour

Y

N/A

Y (see notes)

Sales tax as separate line uses the taxable field in the Sage Intacct billing file and does not create a separate line.

SOS

Summary, Summary by Date, Detail

Y

Y

Detail Only

SLS

Detail

N

Y

N

Description in the billing file format will only be used when bill code is BillCode-Description.

Straco

Detail

N

N

Y

Item Description in Billing File for the community must be set to Order (Great Plains/Straco).

Transaction Pro Importer

Detail

N

N

Y

This billing file includes first name and last name of the resident for reference only.

UltraCare

Summary, Detail

N

Y

N

Vitals

Summary, Detail

Y

Y

Y

Vitals requires that biling information be sent via web service using an XML format. This requires set up on the ADT tab under the Setup button to enter information to connect to the webservice with. Information for connection to the web service will be provided by Vitals on a per community basis.

VMS

Summary

N

Y

N

WellSky

Summary

Y

N

Y

Yardi Core

Summary, Detail

Y

N/A for summary

Y

Resident billing data should be loaded in as Facility Code-Resident Billing Id. Facility Code on the billing id level is optional and does not need to be loaded in if they are not being used. If Facility Code is not defined at the resident level, the community level attribute will be used. Please note that the Yardi Core import is different than their senior living solution. Most of our communities are using the senior living solution.

Yardi Senior Living

Summary, Summary by Date, Summary by Date-Time, Detail

Y

Y

Summary by Date Only

Resident billing data should be loaded in as Facility Code^Resident Billing Id-Payor Code~EFT. Facility Code on the billing id level,Payor Code, and EFT are optional and do not need to be loaded in if they are not being used. If Facility Code is not defined at the resident level, the community level attribute will be used. The detail file makes use of the Taxable (Y/N) attribute in Yardi and will bill the non-taxed amount and set the Taxable (Y/N) column to be Y if the transaction was taxed.