BN106 - 834 5010 File Format

We need to submit a 834 5010 file format to one of our vendors in a weekly basis. Lawson provides the program BN106 in order to generate this format file based on configuration. However, even the file format the vendor is requesting is the same 834 5010, there are some differences in what BN106 is generating. For example, at the end of each value, the vendor is requesting a * delimiter, BN106 does not generate that delimiter. Also, our vendor is requesting ending each record line with a ~, BN106 is neither producing that delimiter. There is anything that I'm missing on the BN106 parameters or do I need to configure anything in the plan code? Do I need to customize the deliver program? Thank you.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

marty

Hi Luis,

I had this come up a few weeks ago, and learned that the BN106 creates the information for an 834 file, but does not format it completely. Companies need an EDI translator tool to fully configure the file to vendor specifications. A lot of companies I talked to outsource that step, as the EDI translator tools are tricky. If you hear differently, I would be very interested to know about it as we are programming a flat file that our vendor will accept in place of the 834.

Jenn

slivak

Yep. We never used the 834 format file for any of our vendors when we were doing benefit feeds ourselves (we have since outprocessed all of our benefit administration.) We always created a custom .NET export program to match each vendor's preferred file format.

unknown

<rant> You know this is the kind of stuff that drives us nuts about Lawson. It doesn't finish the job. They say they have the 834 format... but.. not really, it's incomplete. We have similar issues with NACHA formats, W2's, 1099's, etc.. everything has to go to another vendor (or outsourced) to get it formatted. I guess I go leave an enhancement request that may get noticed 3-4 years from now.</rant>

d-wilcox

Hi Luis and Jenn, I have just gone through this nightmare. The BN106 does give the 834 information, however there are quirks in the program. I searched for a few months trying to find the right tool to convert the report but ended up hiring TEAMABSOLUTE to configure the information. The BN106 does not come with a tool that tells you exactly which line to complete if you want a specific segment. Info gives you the layout and that is it. I had to re-run the report in various ways to find out which field need to be completed for items such as for Ref 38, complete the BN01.1 , field Contract with the group number and division number if applicable or for Ref 38 1L, complete the field Contract on BN15.1. If you have vendors such as VSP who need the levels broken out, the report does not separate EE + 1. It lumps it into the family status which if left alone will cause your company more money. For the N1 - IN - F1 segment, this derives from the BN01.1 Entity ID. You must use the Federal ID, not the HIPPA ID for the ID classification. Anthem requires the Loop 2300 to be in a specific place. The BN106 will not put it in the order needed. You have to have it programmed. Hope this helps.

3579_4115_dEPM-450 - Managing Data Connections.mp4

slivak

That's the problem with the 834 "standard" -- it's not really a standard. Every vendor has different needs that require different data in different formats at different times. Trying to create One File Format to Rule Them All is an exercise in utter futility. That's why we've found that "rolling our own" from scratch always got us to the desired result far quicker than trying to figure out how to get myriads of various Lawson programs configured just right.

unknown

Does anyone know if this is easier in Global HR 11?

slivak

It's not a Lawson problem, so I'm guessing "No."

com_2010feb_proactive.pdf

Copyright © 2025 Infor. All rights reserved.