moov-io/irs

Internal Revenue Service (IRS) Filing Information Returns Electronically (FIRE)

irs's Issues

Create Record formats for IRS 1220

The IRS defines an electronic ASCII format for filling documents through their FIRE system. The FIRE system is used to automate the traditional paper process for paper or PDF forms. The Publication 1220 is the standard for IRS forms 1097,1098,1099,3921,3922,5498 and W-2g and their variations. Our initial efforts are focusing on 1099 specifically on 1099-MISC &1099-NEC, and 1099-INT & 1099-OID.

Our design goal is that irs.1099MISC datatype will have the ability to take a JSON representation as input and utilize the 1220 record types to output a 1099MISC ASCII file ready for upload to the FIRE server. The data types, record size, and formats for validation of publication are located in Part C | Record Format Specifications and Record Layouts. on page 45. Basic inputs represented in JSON format are in the Data folder of this project.

1099-INT and 1099-OID

Support 1099-INT and 1099-OID.
https://www.irs.gov/instructions/i1099int

• - Define data model in JSON for accepting a 1099-INT and 1099-OID.
• - Process JSON into ASCII format defined by 1220 specification.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

Add support for form 1120 family for Corporate income tax Modernized e-File

Support for IRS Modernized e-File Forms 1120, 1120S, and 1120-F for Tax Year 2020 and beyond.
Our design goal is primarily to extend moov-irs in such a way that given JSON representation as input it produces Modernized e-File compliant files for transmission to the IRS.
Modernized e-File(MeF) Overview

The Modernized e-File(MeF) approved file transmission format is XML and as such moov-irs will produce files compliant with IRS Business rules and all xml schema specifications for (MeF) for the various families of form 1120 starting with 1120.
Updates will be made to keep the system up to date with changes in subsequently released instructions from the IRS.

Create 1099-MISC example over HTTP

It would be really helpful for the project to have an example of creating a 1099-MISC file over the HTTP service. This will better explain what's involved from a user of the IRS project.

Included / linked on docs/RUNNING.md and the README.

Prior Year Data Indicator

"Prior Year Data Indicator" defined as required field.
but the field show allows blank value too

CLI for input file to output file

Develop and CLI (Command Line Interface) such as that created for Metro2 to allow for an input file type and an output file type:

As an example but not prescriptive of the solution:

moov-irs -t 1099MISC input-file.json --output output-file.ascii

Filing 1099

Hi,

First of all, thank you for the project! It's very useful to generate documents for 1099.

I assume it's out of scope of this project, but I'm asking this question here.
I'm wondering if there's a way to submit 1099 programatically. 1099 documents can be submitted through FIRE https://fire.irs.gov/ but it requires manual process to upload the files. I'm wondering if there's a way to do it.

I know some companies provide API for submitting documents(perhaps moov.io has that too?), I want to know how they are achieving that.

Add support for form 8949

Add support for IRS form 8949. Documentation for Form 8949 can be found on the IRS website:

https://www.irs.gov/forms-pubs/about-form-8949

Error during container run: unable to load config file

I was trying to run the container today and saw the following error pop up each time. I then tried building the image locally and ended up with the same issue. I don't think it's a permissions thing as I've checked all permissions for the file and they seem to be fine:

ts=2021-10-14T21:49:13Z msg="loading config file" level=info app=irs component=Service file=/configs/config.default.yml
ts=2021-10-14T21:49:13Z msg="pkger unable to load /configs/config.default.yml: open /configs/config.default.yml: no such file or directory" component=Service file=/configs/config.default.yml level=info app=irs errored=true
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xa1dd82]

goroutine 1 [running]:
main.glob..func1(0x1157280, {0xc02599, 0x0, 0x0})
/src/cmd/irs/main.go:45 +0x122
github.com/spf13/cobra.(*Command).execute(0x1157280, {0x11e98b0, 0x0, 0x0})
/go/pkg/mod/github.com/spf13/[email protected]/command.go:856 +0x60e
github.com/spf13/cobra.(*Command).ExecuteC(0x1157c80)
/go/pkg/mod/github.com/spf13/[email protected]/command.go:974 +0x3bc
github.com/spf13/cobra.(*Command).Execute(...)
/go/pkg/mod/github.com/spf13/[email protected]/command.go:902
main.main()
/src/cmd/irs/main.go:215 +0x25

replace moov-io/identity with moov-io/base/log package

moov-io/identity is an outdated package and we should be using the log, database, etc from our moov-io/base library.

spike: data / file storage

Once we have files created they'll need to be stored for IRS regulations. These will need to be encrypted as well. A good candidate for storage would be compatible cloud services.

Metadata (key/value pairs) will likely need to be searchable / stored alongside this.

What does this process look like? Does it live in this service? How would these be referenced by the Customers service?

handle IRS "b notice" / cp2100 (backup withholding for TIN mismatch)?

Any plans to handle the "sad path" of 1099 filing, cp2100(a) (aka B notice), when TINs and names on 1099s you generate don't match IRS records?

https://www.irs.gov/pub/irs-pdf/p1281.pdf

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore(deps): update all (major) (actions/checkout, actions/setup-go, github/codeql-action)
• chore(deps): update github artifact actions to v4 (major) (actions/download-artifact, actions/upload-artifact)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update all (github.com/moov-io/base, github.com/spf13/cobra, golang.org/x/oauth2)

Detected dependencies

docker-compose

docker-compose.yml

• mysql 8-oracle

dockerfile

Dockerfile

• golang 1.22
• debian stable

github-actions

.github/workflows/codeql.yaml

• actions/checkout v2
• github/codeql-action v2
• github/codeql-action v2

.github/workflows/go.yml

• actions/setup-go v4
• actions/checkout v2

.github/workflows/release.yml

• actions/setup-go v4
• actions/checkout v2
• actions/create-release v1
• actions/upload-artifact v1
• actions/setup-go v4
• actions/checkout v2
• actions/download-artifact v1
• actions/upload-release-asset v1
• actions/upload-release-asset v1
• actions/upload-release-asset v1
• actions/setup-go v4
• actions/checkout v2

gomod

go.mod

• go 1.20
• github.com/antihax/optional v1.0.0
• github.com/go-kit/log v0.2.1
• github.com/gorilla/mux v1.8.1
• github.com/moov-io/base v0.48.5
• github.com/spf13/cobra v1.8.0
• github.com/stretchr/testify v1.9.0
• golang.org/x/oauth2 v0.19.0
• gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c@10cb98267c6c

---

• Check this box to trigger a request for Renovate to run again on this repository

Add support for form 3921

Spec can be found in publication 1120.

The only complicated bit I can see is if the foreign field is set then the address fields are treated differently.

Does this tool support union typed fields?

api: include example values in schemas

Recently I setup this project to serve API docs from GitHub Pages. This means we have a pretty view of API endpoints, however the examples aren't fully displayed. This is because there are no example values for the viewer to include.

Example values also help to show what to provide when making requests for people who are new to the 1099 files.

See: https://moov-io.github.io/irs/api/

Data JSON examples should be Camel Case

Example files are currently using underscores(_) and should follow the other projects and use camel case.

Create 1099-INT example over HTTP

It would be really helpful for the project to have an example of creating a 1099-INT file over the HTTP service. This will better explain what's involved from a user of the IRS project.

Included / linked on docs/RUNNING.md and the README.

1099-MISC &1099-NEC support

Support 1099-MISC & 1099-NEC.
https://www.irs.gov/instructions/i1099msc

• - Define data model in JSON for accepting a 1099-MISC and 1099-NEC.
• - Process JSON into ASCII format defined by 1220 specification.