Validation issues around missing tag {1500} in incoming wires formatted with Fedwire extended format

[vishwasbabu]

Wire Version: v0.9.0

What were you trying to do? Parse incoming wires in the Fedwire extended format

What did you expect to see? Wires parsed successfully

What did you see? Validation error message since tag {1500} is not present in incoming Fedwire extended format files

How can we reproduce the problem? Parse a wire file with tag {1500}, ex

{1100}30P N{1110}06071654XXXX{1120}20220607XXXXXXXXXXXXXXXXXXXXXXXXXX{1510}1000{1520}20220607XXXXXXXX000002{2000}000000009000{3100}021004543Test Bank*{3320}158545637*{3400}123456789Test XXXXXXXXXXXXX*{3600}CTP{3620}3*752E9D0D-99B8-4DF4-87F2-XXXXXXXXXXXX*{3700}BUSD0,00*USD10,00*{3710}USD100,00*{4200}DXXXXXXXXXXXXXXXX*Test Bank*line1*line2*line3*{4320}WW22060755582563*{5000}DXXXXXXXXXXX*line1*line2*line3*{5100}BXXXXXXXXXXX*Test Bank*line1*line2*{6000}FFC: XXXXX*XXXXXXXXXXX*

[mfdeveloper508]

Mandatory Tags in Each Message At a minimum, the following tags are mandatory in each outgoing message sent from a DI to the Fedwire Funds Service (regardless of the business function code). Other tags are required depending on the business function code selected.

• {1500} Sender Supplied Information
• {1510} Type Code, Subtype Code
• {1520} IMAD
• {2000} Amount
• {3100} Sender DI
• {3400} Receiver DI
• {3600} Business Function Code (first element)

[zbruhnke]

OK FYI I've gone deep down this rabbit hole and here's what I have found out - we have also asked both the clearing house and the Fed to consider updating their FAIM documentation to better reflect this

{1500} IS required for OUTGOING files but it is stripped out when receiving INCOMING files and the same data is added to {1100}

This is exactly what @vishwasbabu is seeing above if you look - also of note the data in {1500} OR {1100} IS allowed to be spaces - it is 8 chars and spaces are allowed!

So I think we'd need a fix for that too

[mfdeveloper508]

Thanks for your note I will check this point again

[zbruhnke]

I am happy to provide the documentation if its helpful @mfdeveloper508

[zbruhnke]

@mfdeveloper508 is this something you have looked into yet? The docs have been provided to both @adamdecaf and @atonks2