©2003 Remettra, Inc. Page 1 Transactions and Code Sets: Strategies in Implementing the 835...

©2003 Remettra, Inc. Page 1

Transactions and Code Transactions and Code Sets: Strategies in Sets: Strategies in

Implementing the 835 Implementing the 835 TransactionTransaction

Brett Hacker, CIOBrett Hacker, CIO

Remettra, Inc.Remettra, Inc.


Simple ConceptSimple Concept

Plans have been paying providers since providers Plans have been paying providers since providers started filing claimsstarted filing claims

Providers need to know what was paid, rejected, Providers need to know what was paid, rejected, or adjusted (remittance)or adjusted (remittance)

HIPAA just wants to get that remittance HIPAA just wants to get that remittance standardized, and available electronically so standardized, and available electronically so providers can eventually auto-post receivables providers can eventually auto-post receivables


Complex IssuesComplex Issues

Health care industry has little experience with Health care industry has little experience with banking beyond cutting a check and reconciling banking beyond cutting a check and reconciling statementsstatements

Banking industry as a whole has little experience Banking industry as a whole has little experience with health care and is generally unaware of with health care and is generally unaware of HIPAAHIPAA


Driving Factors - PayersDriving Factors - Payers

HIPAA Compliance - OctoberHIPAA Compliance - October Reduced print/mail costs - over timeReduced print/mail costs - over time Increased efficiency – immediateIncreased efficiency – immediate Declined importance of float (although likely to Declined importance of float (although likely to

rebound eventually)rebound eventually) Reduced check fraud (if implementing EFT)Reduced check fraud (if implementing EFT)


Driving Factors - ProvidersDriving Factors - Providers

HIPAA Compliance - OctoberHIPAA Compliance - October Automatic receivables posting – eventuallyAutomatic receivables posting – eventually More timely payment receipt (if implementing More timely payment receipt (if implementing

EFT)EFT)


What’s The Problem?What’s The Problem?

IG Scenarios/Prescribed Strategies:IG Scenarios/Prescribed Strategies: 2.1.2.1: ERA w/Payment by Check2.1.2.1: ERA w/Payment by Check 2.1.2.2: ERA and EFT through DFI2.1.2.2: ERA and EFT through DFI 2.1.2.3: ERA with Payment by Separate EFT2.1.2.3: ERA with Payment by Separate EFT 2.1.2.4: ERA and Payment Delivered Separately 2.1.2.4: ERA and Payment Delivered Separately

but Processed by a Value-Added Bank (VAB)but Processed by a Value-Added Bank (VAB) 2.1.2.5: ERA with Debit EFT2.1.2.5: ERA with Debit EFT


ERA with Payment by CheckERA with Payment by Check

Payer sends $ via check through the mailPayer sends $ via check through the mail Payer sends ERA directly to the PayeePayer sends ERA directly to the Payee

Payee deposits the check and reconciles the ERAPayee deposits the check and reconciles the ERA Requires reassociationRequires reassociation

““Gotchas”:Gotchas”: Legacy Approach: keep same old process, tack on electronic Legacy Approach: keep same old process, tack on electronic

delivery of ERAdelivery of ERA Payer (or Payer’s clearinghouse) responsible for ERA delivery, Payer (or Payer’s clearinghouse) responsible for ERA delivery,

which becomes an additional process (still stuffing and mailing which becomes an additional process (still stuffing and mailing an envelope for the check)an envelope for the check)

Payer Payee835 ERA

Check


ACH PrimerACH Primer TermsTerms::

DFIDFI: Depository Financial Institution: Depository Financial Institution Electronic Funds Transfer (EFT)Electronic Funds Transfer (EFT): The electronic mechanism that payers use : The electronic mechanism that payers use

to instruct one DFI to move money from one account to another account at to instruct one DFI to move money from one account to another account at the same or at another DFI. Fund transfers may utilize ACH, FedWire, Swift, the same or at another DFI. Fund transfers may utilize ACH, FedWire, Swift, or other authorized electronic payment system.or other authorized electronic payment system.

Originating DFI (ODFI)Originating DFI (ODFI): bank which initiates EFT instructions: bank which initiates EFT instructions Receiving DFI (RDFI)Receiving DFI (RDFI): bank which receives EFT instructions: bank which receives EFT instructions NACHANACHA: NACHA is a not-for-profit trade association that develops operating : NACHA is a not-for-profit trade association that develops operating

rules and business practices for the Automated Clearinghouse (ACH) rules and business practices for the Automated Clearinghouse (ACH) network and for other areas of electronic payments (network and for other areas of electronic payments (http://www.nacha.orghttp://www.nacha.org).).

ACH (Automated Clearinghouse)ACH (Automated Clearinghouse): The most popular and widely used : The most popular and widely used clearinghouse of electronic fund transfers (i.e. direct deposit of payroll, clearinghouse of electronic fund transfers (i.e. direct deposit of payroll, corporate payments, travel/expense reimbursements, state/federal, tax corporate payments, travel/expense reimbursements, state/federal, tax payments, consumer/business related transactions). Common ACH payments, consumer/business related transactions). Common ACH computer formats (NACHA formats) include CTX, CCD, and CCD+.computer formats (NACHA formats) include CTX, CCD, and CCD+.

FloatFloat: Refers to both the time delay related to exchange of funds (i.e. : Refers to both the time delay related to exchange of funds (i.e. check, mail, processing) and the associated interest that may accrue during check, mail, processing) and the associated interest that may accrue during that delay.that delay.


ACH Primer, ContinuedACH Primer, Continued More Terms:More Terms:

Financially EDI capable/Value Added bank (VAB)Financially EDI capable/Value Added bank (VAB): DFI that can successfully : DFI that can successfully process and deliver incoming/outgoing EDI data, including translation, and process and deliver incoming/outgoing EDI data, including translation, and store-and-forward mailboxing between bank customers and their trading store-and-forward mailboxing between bank customers and their trading partners. Lockbox-capable.partners. Lockbox-capable.

Value added network (VAN)Value added network (VAN): A third party service provider of secure : A third party service provider of secure networking services such as secure store-and forward mailbox delivery of networking services such as secure store-and forward mailbox delivery of EDI documents, EDI and proprietary in-network translation, and access to EDI documents, EDI and proprietary in-network translation, and access to audit and reporting data on activity.audit and reporting data on activity.

Advance Notification of FundsAdvance Notification of Funds: The receipt of payment related detailed : The receipt of payment related detailed information in advance of payment.information in advance of payment.

Dollars and Data TogetherDollars and Data Together: When the payment and remittance are kept : When the payment and remittance are kept together through the entire data flow process, with the receiver also together through the entire data flow process, with the receiver also receiving the information together.receiving the information together.

Dollars and Data SeparateDollars and Data Separate: The transfer and receipt of payment and related : The transfer and receipt of payment and related data separately (usually split to accommodate the advance notification of data separately (usually split to accommodate the advance notification of funds, requiring reassociation of both payment and remittance by receiver funds, requiring reassociation of both payment and remittance by receiver of information).of information).


ACH Primer, ContinuedACH Primer, Continued More Terms:More Terms:

ACH OperatorsACH Operators Federal Reserve System, New York Clearing House Association, Federal Reserve System, New York Clearing House Association,

VisaNet ACH Services, and the American Clearing House VisaNet ACH Services, and the American Clearing House Association Association

ACH FormatsACH Formats CCD: “Cash Concentration and Disbursement”CCD: “Cash Concentration and Disbursement”

B2B EFT formatB2B EFT format 1 payment record, no addenda1 payment record, no addenda

CCD+: “Cash Concentration and Disbursement with Addenda”CCD+: “Cash Concentration and Disbursement with Addenda” 1 payment record, 1 addenda record of 80 bytes1 payment record, 1 addenda record of 80 bytes Suitable for transmission of payment order and 835 TRN segmentSuitable for transmission of payment order and 835 TRN segment

CTX: “Corporate Trade eXchange”CTX: “Corporate Trade eXchange” 1 payment record, up to 9,999 addenda records of 80 bytes each1 payment record, up to 9,999 addenda records of 80 bytes each


CTXCTX


CCD+CCD+


ERA and EFT through DFIERA and EFT through DFI

Payer sends $ and ERA in an 835 to the Payer’s DFIPayer sends $ and ERA in an 835 to the Payer’s DFI Payer’s DFI sends $ and ERA to Payee’s DFIPayer’s DFI sends $ and ERA to Payee’s DFI

Payee’s DFI notified Payee of the $ via FDN (Funds Deposit Payee’s DFI notified Payee of the $ via FDN (Funds Deposit Notification) and delivers the ERANotification) and delivers the ERA

Reassociation not necessaryReassociation not necessary

PayerPayer DFI

ERA

EFT

Payee DFI

ERA

EFTPayee

ERA

FDN



““Gotchas”:Gotchas”: Payer must maintain Account/Routing info for payees Payer must maintain Account/Routing info for payees

(information not available in 837)(information not available in 837) Since ODFI and RDFI will have access to PHI via the Since ODFI and RDFI will have access to PHI via the

remittance portion of the 835, BA agreements will need remittance portion of the 835, BA agreements will need to be in place (between Payer and ODFI, and Payee and to be in place (between Payer and ODFI, and Payee and RDFI)RDFI)

PayerPayer DFI

ERA

EFT

Payee DFI

ERA

EFTPayee

ERA

FDN



More “Gotchas”:More “Gotchas”: 835 is “enveloped” into a NACHA CTX format by Originating 835 is “enveloped” into a NACHA CTX format by Originating

bank (ODFI) – BAA required between Payer and ODFIbank (ODFI) – BAA required between Payer and ODFI CTX is transmitted to ACH (Federal Reserve, other CH) – in CTX is transmitted to ACH (Federal Reserve, other CH) – in

clear text over private connectionclear text over private connection CH forwards to Receiving bank (RDFI) – based on routing CH forwards to Receiving bank (RDFI) – based on routing

number (if correct: if not, NACK is sent back to ODFI)number (if correct: if not, NACK is sent back to ODFI)

PayerPayer DFI

ERA

EFT

Payee DFI

ERA

EFTPayee

ERA

FDN



More “Gotchas”:More “Gotchas”: RDFI extracts 835 from CTX and re-assembles – if RDFI is EDI-RDFI extracts 835 from CTX and re-assembles – if RDFI is EDI-

capablecapable RDFI delivers 835 to Provider – if RDFI has electronic delivery RDFI delivers 835 to Provider – if RDFI has electronic delivery

mechanismmechanism

PayerPayer DFI

ERA

EFT

Payee DFI

ERA

EFTPayee

ERA

FDN



NACHA ACH Rules (page OG99): “If the addenda record NACHA ACH Rules (page OG99): “If the addenda record information will be provided in human-readable format, the RDFI information will be provided in human-readable format, the RDFI must ensure that the addenda information is translated from ANSI must ensure that the addenda information is translated from ANSI ASC X12 syntax…and provided to the Receiver in human-readable ASC X12 syntax…and provided to the Receiver in human-readable text. If the addenda record information will be provided in text. If the addenda record information will be provided in machine-readable, electronic file format…the RDFI and Receiver machine-readable, electronic file format…the RDFI and Receiver will need to determine whether the information will be (1) will need to determine whether the information will be (1) transmitted to the Receiver as a pass-through of the electronic file transmitted to the Receiver as a pass-through of the electronic file format (i.e., …835), (2) translated into a proprietary format agreed format (i.e., …835), (2) translated into a proprietary format agreed to by the RDFI and Receiver, or (3) merged with the Receiver’s to by the RDFI and Receiver, or (3) merged with the Receiver’s lockbox data.”lockbox data.”

PayerPayer DFI

ERA

EFT

Payee DFI

ERA

EFTPayee

ERA

FDN



More “Gotchas”:More “Gotchas”: CTX format consists of (1) payment record (the “6” record in CTX format consists of (1) payment record (the “6” record in

ACH format) and up to 9,999 “addenda” records (“7” records), ACH format) and up to 9,999 “addenda” records (“7” records), each sequenced and related to the “6” recordeach sequenced and related to the “6” record

The ACH format allows 94-characters per line, and the The ACH format allows 94-characters per line, and the addenda record allows an 80-character payload (plus 14 addenda record allows an 80-character payload (plus 14 characters of ACH control information)characters of ACH control information)

The maximum “payload” or remittance data capable of being The maximum “payload” or remittance data capable of being transmitted per payment record is just at 800ktransmitted per payment record is just at 800k

The data cannot be compressed, except to make “…one The data cannot be compressed, except to make “…one segment immediately follow(s) the preceding segment”segment immediately follow(s) the preceding segment”

PayerPayer DFI

ERA

EFT

Payee DFI

ERA

EFTPayee

ERA

FDN


ERA with Payment by Separate EFTERA with Payment by Separate EFT

Payer sends $ via EFT instructions to the Payer’s DFIPayer sends $ via EFT instructions to the Payer’s DFI Payer sends ERA directly to PayeePayer sends ERA directly to Payee

Payer’s DFI sends $ to Payee’s DFIPayer’s DFI sends $ to Payee’s DFI Payee’s DFI notifies Payee of $Payee’s DFI notifies Payee of $

Payee reconciles ERA with $Payee reconciles ERA with $

PayerPayer DFI

EFT Payee DFI

EFT PayeeFDN

ERA


ERA with Payment by Separate ERA with Payment by Separate EFTEFT

““Gotchas”:Gotchas”: Payer must maintain account/routing numbers and payment Payer must maintain account/routing numbers and payment

preferences for payeespreferences for payees Payer must generate CCD+ file for ODFI, or establish BA with Payer must generate CCD+ file for ODFI, or establish BA with

ODFI before sending 835; ODFI must generate CCD+ from 835ODFI before sending 835; ODFI must generate CCD+ from 835 Payee must set up account/routing number and payment Payee must set up account/routing number and payment

preferences with each payer he transacts withpreferences with each payer he transacts with

PayerPayer DFI

EFT Payee DFI

EFT PayeeFDN

ERA


ERA and Payment Delivered Separately but ERA and Payment Delivered Separately but Processed by a Value-Added Bank (VAB)Processed by a Value-Added Bank (VAB)

Payer sends $ as appropriate for EFT or check to Payee’s Payer sends $ as appropriate for EFT or check to Payee’s DFI.DFI. Payer sends ERA to Payee’s DFIPayer sends ERA to Payee’s DFI

Payee’s DFI reconciles ERA and $ and notifies PayeePayee’s DFI reconciles ERA and $ and notifies Payee Reassociation performed by VABReassociation performed by VAB

PayerPayer DFI

Funds

ERA

Payee DFI

(VAB)

FundsPayee

FDN



““Gotchas”:Gotchas”: This is HHS legalese for “lockbox operations”. Provider’s bank This is HHS legalese for “lockbox operations”. Provider’s bank

(RDFI) receives payment and remittance, either electronically (RDFI) receives payment and remittance, either electronically or via paper, and processes the information for consolidated or via paper, and processes the information for consolidated delivery to provider. Inherently involves reformatting if delivery to provider. Inherently involves reformatting if received as a standard transaction and consolidated to paper, received as a standard transaction and consolidated to paper, or if received as paper and delivered as 835: RDFI would be a or if received as paper and delivered as 835: RDFI would be a covered entity.covered entity.

PayerPayer DFI

Funds

ERA

Payee DFI

(VAB)

FundsPayee

FDN



More “Gotchas”:More “Gotchas”: Payer separates dollars and data then delivers ERA to RDFI Payer separates dollars and data then delivers ERA to RDFI

(VAB)(VAB) Payer must have mechanism to communicate with each RDFI Payer must have mechanism to communicate with each RDFI

directly. With mailed remittance, this is not a problem, but for directly. With mailed remittance, this is not a problem, but for ERA either the payer or the payer’s clearinghouse would have ERA either the payer or the payer’s clearinghouse would have to electronically transmit the ERA to the receiving bank.to electronically transmit the ERA to the receiving bank.

The reassociation trace number (TRN segment) would still have The reassociation trace number (TRN segment) would still have to be transmitted through the ACH from ODFI to RDFI.to be transmitted through the ACH from ODFI to RDFI.

PayerPayer DFI

Funds

ERA

Payee DFI

(VAB)

FundsPayee

FDN


ERA with Debit EFTERA with Debit EFT

Payer sends 835 with ERA and debit authorization to PayeePayer sends 835 with ERA and debit authorization to Payee Payee instructs DFI to take funds from the Payer’s DFIPayee instructs DFI to take funds from the Payer’s DFI

Payee’s DFI gets funds from Payer’s DFI and notifies PayeePayee’s DFI gets funds from Payer’s DFI and notifies Payee Reassociation is necessaryReassociation is necessary

Payer Payee835

Debit Notice

Payee DFI

DebitRequest

Payer DFI

EFT/FDN

DebitRequest

Funds


ERA with Debit EFTERA with Debit EFT

““Gotchas”:Gotchas”: More risk for payer (operating account authorized for debits)More risk for payer (operating account authorized for debits) More complexity and effort for provider (provider must set up More complexity and effort for provider (provider must set up

with his RDFI as a debit originator)with his RDFI as a debit originator) Payer (or clearinghouse) must still deliver 835 directly to Payer (or clearinghouse) must still deliver 835 directly to

payeepayee

Payer Payee835

Debit Notice

Payee DFI

Payer DFI

EFT/FDN Funds

DebitRequest

DebitRequest


Other DFI IssuesOther DFI Issues

NACHA/ABA believe they should be exempt from NACHA/ABA believe they should be exempt from HIPAA rules due to privacy mandates of HIPAA rules due to privacy mandates of Graham/Leach/Bliley, and exemptions outlined in Graham/Leach/Bliley, and exemptions outlined in Section 1179.Section 1179.

GLB requires bank to restrict outside entities from GLB requires bank to restrict outside entities from access to collected data: no restrictions for internal access to collected data: no restrictions for internal use. HIPAA Privacy requires entities with access to PHI use. HIPAA Privacy requires entities with access to PHI to have measures in place to restrict access internally.to have measures in place to restrict access internally.

Section 1179 refers to exemption for “payment” Section 1179 refers to exemption for “payment” activities; remittance is not exempted.activities; remittance is not exempted.


Still a Problem?Still a Problem?

Alternate StrategiesAlternate Strategies ERA Delivered by Payer, Payment Delivered by 3ERA Delivered by Payer, Payment Delivered by 3rdrd-party -party

payment processorpayment processor ERA Delivered by a Healthcare Clearinghouse, Payment ERA Delivered by a Healthcare Clearinghouse, Payment

Delivered by 3Delivered by 3rdrd-party payment processor-party payment processor ERA and Payment Delivered Separately but Processed ERA and Payment Delivered Separately but Processed

by a Healthcare Clearinghouseby a Healthcare Clearinghouse


ERA Delivered by Payer, Payment Delivered ERA Delivered by Payer, Payment Delivered byby

33rdrd-party payment processor-party payment processor

Payer

Payer DFI

EFTOr

ERA Payee DFI

PayeeFDN

ERA

Payer sends $ via EFT instructions (via CCD+ ERA) to the Payer’s Payer sends $ via EFT instructions (via CCD+ ERA) to the Payer’s DFIDFI Payer sends ERA directly to PayeePayer sends ERA directly to Payee

Payer’s DFI sends $ to Payee’s DFIPayer’s DFI sends $ to Payee’s DFI Payee’s DFI notifies Payee of $Payee’s DFI notifies Payee of $

Payee reconciles ERA with $Payee reconciles ERA with $

Payment Processor

FundsEFT Order(CCD+) Funds


ERA Delivered by Payer, Payment Delivered ERA Delivered by Payer, Payment Delivered byby

33rdrd-party payment processor-party payment processor

““Gotchas”:Gotchas”: Payer still responsible for ensuring delivery of the ERA to the PayeePayer still responsible for ensuring delivery of the ERA to the Payee Depending on the policies of the 3Depending on the policies of the 3rdrd-party processor, Payer may need -party processor, Payer may need

to maintain payee account/routing numbers and payment prefsto maintain payee account/routing numbers and payment prefs If Payer maintains prefs, Payee must set up prefs with each payer he If Payer maintains prefs, Payee must set up prefs with each payer he

does business with (using a payment processor of this type)does business with (using a payment processor of this type) Due to state banking regulations, Payer must maintain control of funds Due to state banking regulations, Payer must maintain control of funds

before release to Payee (or keep equal amount on hand); CH must before release to Payee (or keep equal amount on hand); CH must access Payer account or a new account must be established by Payer access Payer account or a new account must be established by Payer for funds access by CH.for funds access by CH.

Payer

Payer DFI

EFTOr

ERA Payee DFI

PayeeFDN

ERA

Payment Processor

FundsEFT Order(CCD+) Funds


ERA Delivered by a Healthcare Clearinghouse, Payment ERA Delivered by a Healthcare Clearinghouse, Payment Delivered by 3Delivered by 3rdrd-party payment processor-party payment processor

Payer sends $ via EFT instructions (via CCD+ ERA) to the Payer’s Payer sends $ via EFT instructions (via CCD+ ERA) to the Payer’s DFIDFI Payer sends ERA to Clearinghouse; Clearinghouse delivers ERA Payer sends ERA to Clearinghouse; Clearinghouse delivers ERA

to Payeeto Payee Payer’s DFI sends $ to Payee’s DFIPayer’s DFI sends $ to Payee’s DFI

Payee’s DFI notifies Payee of $Payee’s DFI notifies Payee of $ Payee reconciles ERA with $Payee reconciles ERA with $

Payer

Payer DFI

EFTOr

ERA

Payee DFI

PayeeFDN

ERA

Payment Processor FundsEFT Order

(CCD+)Funds

CHERA


““Gotchas”:Gotchas”: Payer manages multiple relationships (CH, payment processor)Payer manages multiple relationships (CH, payment processor) Depending on the policies of the 3Depending on the policies of the 3rdrd-party processor, Payer may need -party processor, Payer may need

to maintain payee account/routing numbers and payment prefsto maintain payee account/routing numbers and payment prefs If Payer maintains prefs, Payee must set up prefs with each payer he If Payer maintains prefs, Payee must set up prefs with each payer he

does business with (using a payment processor of this type)does business with (using a payment processor of this type) Due to state banking regulations, Payer must maintain control of funds Due to state banking regulations, Payer must maintain control of funds

before release to Payee (or keep equal amount on hand); CH must before release to Payee (or keep equal amount on hand); CH must access Payer account or a new account must be established by Payer access Payer account or a new account must be established by Payer for funds access by CH.for funds access by CH.

ERA Delivered by a Healthcare Clearinghouse, Payment ERA Delivered by a Healthcare Clearinghouse, Payment Delivered by 3Delivered by 3rdrd-party payment processor-party payment processor

Payer

Payer DFI

EFTOr

ERA

Payee DFI

PayeeFDN

ERA

Payment Processor FundsEFT Order

(CCD+)Funds

CHERA


ERA and Payment Delivered Separately but ERA and Payment Delivered Separately but Processed by a Healthcare ClearinghouseProcessed by a Healthcare Clearinghouse

Payer Sends 835 to CHPayer Sends 835 to CH Payer Sends $ to ODFIPayer Sends $ to ODFI

CH creates CCD+ from 835 and transmits to ODFICH creates CCD+ from 835 and transmits to ODFI ODFI initiates funds transfer to RDFI via CCD+ ODFI initiates funds transfer to RDFI via CCD+

instructionsinstructions CH sends Funds Deposit Notification to PayeeCH sends Funds Deposit Notification to Payee

Payee retrieves ERA from CHPayee retrieves ERA from CH

Payer

Payer DFI

Funds

ERACH

EFT Order(CCD+)

Payee

FDN

Payee DFI

ERA

Funds Funds


““Gotchas”:Gotchas”: Due to state banking regulations (in most states), Payer must Due to state banking regulations (in most states), Payer must

maintain control of funds before releasing to Payee or keep maintain control of funds before releasing to Payee or keep equal amount on hand, so CH must have access to Payer equal amount on hand, so CH must have access to Payer account or a separate account must be established for payer account or a separate account must be established for payer to put funds into for access by CH.to put funds into for access by CH.

Many traditional clearinghouses have indicated they do not Many traditional clearinghouses have indicated they do not want to handle the EFT transaction.want to handle the EFT transaction.

ERA and Payment Delivered Separately but ERA and Payment Delivered Separately but Processed by a Healthcare ClearinghouseProcessed by a Healthcare Clearinghouse

Payer

Payer DFI

Funds

ERACH

EFT Order(CCD+)

Payee

FDN

Payee DFI

ERA

Funds Funds


SummarySummary

There are many issues, both unresolved and There are many issues, both unresolved and under debate, regarding utilizing the ACH under debate, regarding utilizing the ACH network for ERA delivery.network for ERA delivery.

Payers must carefully evaluate both strategy and Payers must carefully evaluate both strategy and partners when deciding on a remittance and EFT partners when deciding on a remittance and EFT delivery method.delivery method.

To fully realize HIPAA cost savings in the To fully realize HIPAA cost savings in the remittance process, both payment and remittance process, both payment and remittance must be delivered electronically or remittance must be delivered electronically or outsourced to a partner.outsourced to a partner.


Thank You!Thank You!

Brett Hacker, CIOBrett Hacker, CIO

Remettra, Inc.Remettra, Inc.

400 Hardin Rd., Ste. 140400 Hardin Rd., Ste. 140

Little Rock, AR 72211Little Rock, AR 72211

(866) 226-9641(866) 226-9641

http://http://www.remettra.comwww.remettra.com

Remettra, Inc. (reh-‘meh-truh) is a specialized Remettra, Inc. (reh-‘meh-truh) is a specialized healthcare clearinghouse providing healthcare clearinghouse providing remittance advices (electronic or paper) and remittance advices (electronic or paper) and payments (electronic or paper) to healthcare payments (electronic or paper) to healthcare providers for claims previously adjudicated. providers for claims previously adjudicated. Unlike most clearinghouses that provide an Unlike most clearinghouses that provide an array of services, Remettra has focused on array of services, Remettra has focused on services specifically tailored to meet payers' services specifically tailored to meet payers' accounts payable objectives. accounts payable objectives.

Remettra fills the role of a one-stop Remettra fills the role of a one-stop outsourcing solution for converting our outsourcing solution for converting our clients' paper-based accounts payable clients' paper-based accounts payable processes to fully automated electronic processes to fully automated electronic systems. We do this through our core systems. We do this through our core products, MedRemit and MedRing.products, MedRemit and MedRing.

Date post:	04-Jan-2016
Category:	Documents
Upload:	linda-holland
View:	218 times
Download:	0 times

©2003 Remettra, Inc. Page 1 Transactions and Code Sets: Strategies in Implementing the 835...

Documents