Turn on suggestions. Showing results for. Search instead for. Did you mean:. New Member. Who qualifies for assistance? In general, households meeting the following criteria will be eligible: Must be a renter in Georgia Must have a household income at or below 80 percent of the Area Median Income AMI Must have either qualified for unemployment benefits or experienced a reduction in household income, incurred significant costs, or experienced a financial hardship due to COVID; and Must demonstrate a risk of experiencing homelessness or housing instability through having an eviction notice, past due rent or utility notice; Are any applications given priority for assistance?
I have fallen behind on my rent — what can I do now until the program starts? What about the eviction moratorium? Verification of Renter Status Tenant Applicants must submit: Lease agreement that has been signed by both parties must be submitted in its entirety as part of the initial application OR Households without a current signed lease such as those renting under a month-to-month arrangement should provide a signed Statement of Delinquent Rent certification from the landlord must be provided stating that they still reside in the rental unit for which the assistance is being applied and confirmation of amount owed Mobile homes are eligible for rent arrearages on the unit being rented.
If the mobile home is owned by the applicant, rent arrearages may not be requested for the lot being rented. Note: If circumstances prevent applicant from providing the requested documentation, applicant may provide evidence of paying utilities for the residential unit, an attestation by a landlord who can be identified as the verified management agent of the unit, or other reasonable documentation as determined by DCA.
Verification of COVID Hardship Tenant Applicants must submit: To qualify for assistance one or more of the individuals within the household must either have qualified for unemployment benefits OR have experienced a reduction in household income, incurred significant costs, or experienced other financial hardship due, directly or indirectly, to COVID, which the applicant must document in writing.
Verification of Risk of Experiencing Homelessness or Housing Instability The household must also be able to demonstrate a risk of experiencing homelessness or housing instability to qualify.
Acceptable documentation for this can include the following: An eviction notice or A past due rent notice A past due utility bill Acceptable documentation of rent and utility arrears may include the most recent past due bill, an eviction or late notice, a PDF or screenshot of an online payment portal, or a letter or email from a landlord to a tenant.
Proof of Identity Must be provided by individual submitting application. How much rent can you pay? Who can I contact for more information? Georgia, USA gdecd. Explore Georgia ExploreGeorgia. On this VeteransDay , we want to thank all of those who have served our country. Great, I never checked half of it!
I received a deposit from the Georgia EDI Department this morning, but these are not my taxes, my taxes are very high. I do not know why! I paid DI Is this a file? Can anyone tell me what it is? I don't want to spend it if I have to take it out later. If records have been incorrectly identified by Master File, a control record is generated to assign count and amount to the correct file. It is determined during the initial balancing of a transmission that records in a batch have been incorrectly identified by Master File, a control record is generated to assign count and amount to the correct file.
The record may be created during initial validation for records that have been batched incorrectly. This control record is also generated for records that have been reclassified due to changes from the correction screen.
A separate control record is generated for error items within each batch. Repeat "loop" errors create separate control records each time the record is corrected and sent back to error. This control record contains the following:. Item count of 1 EFPPS validates payment records individually and creates a new control record each time the record is sent to error or corrected from error.
As each error record is corrected and returned to batch control status, an error correction control record is generated with the following:. Suspense status is used for items or batches that are being removed from normal processing to await deletion by Accounting or to await a generated offset from the financial agent. Suspended items are included on the New Suspense List and on the EFPPS Age Report until either a generated update or offset record is received from the financial agent or the record is manually deleted or corrected by Accounting.
Many of these conditions are identified immediately and cause the records to be rejected without the control record being created. Research the batch on the control file to identify the cause of the error.
Manually enter any control records that are necessary to suspend or delete the invalid record or batch. In some cases it may be necessary to suspend the batch so that the TEP can be completed while the error code is being researched. If a specific transaction is identified as the cause of the error code, the EFT number can be manually deleted.
Then the batch can be unsuspended to complete processing. If the transaction represents "real money" , the deleted record must be manually controlled on some other system, such as the Non-Master File or unidentified remittance file. Some error codes, such as error code "1" for a duplicate resubmitted batch number, require no corrective action.
Documentation on the control file must include sufficient information e. Include necessary information in the "Remarks" field on the manual record or on a supplemental Manual Remarks record.
Then select Control Menu tab. Each of the Control Menu input screens display the same fields. Depending on the screen selected, some of the fields will require input, some have optional input, some have generated value, and some must be blank.
Credit amounts are not signed. Omit commas and leading zeros. Enter as follows:. The Manual Delete screen is used to remove records from active status on the control file and the data file. The batch number, item count, amount, remarks and from code must be entered.
The bottom of the screen shows the cursor field and data that has been entered in the field. The from code is normally "4" to delete items that are in suspense status. From code "0" may also be used to delete an item in batch control. If from code "0" is used, the count must be 1 and the EFT number and amount must match an open item. A "0 - 2" control record is generated to delete the record. From code "4" may be used to delete single items from suspense or to delete all of the suspense items within the batch.
The count and amount must match the total count and amount of the suspense status items within the batch. In a rare case in which records for more than one Master File are in the batch being deleted, separate records are created for each Master File.
Follow local procedures to prepare and number Form , Payment Posting Voucher, for processing the transaction to another system. If you make a mistake and delete a record that should not have been deleted, the Manual Undelete screen can be used to retrieve the record on the same day only. Enter the batch number, amount, remarks and EFT number on the screen and commit.
Reverse the decision made by error correction that a record should be suspended. Bring a suspend "unidentified" or "offset" record transaction indicator 8, 9, A or B to unresolved status.
Use this option only when the missing information is known and can be added to the record. This allows time for a possible offset record. If Manual Suspense to Error is used for a record with transaction indicator "8" or "B" , the transaction indicator is changed to "0". Transaction indicator "9" or "A" is converted to "4".
This control record will send the payment transaction back to error status with the same invalid condition that was previously on the record. Advise error correction of your proposed corrective action. Use the Manual Suspend option to remove a batch or single record from active processing and to prevent the record from being passed to the TEP.
The system will generate a record with from-to-code "0 - 4" for items in batch control status and a separate "3 - 4" record for each item in error status. Use this option to prevent posting of any batch or record that is identified as a balancing error, duplicate record, or other potential balancing problem. Use the Manual Unsuspend option to send suspended records back to their previous status. Do not use this option to unsuspend records that were suspended by error correction or by initial validation by the EFPPS system.
This option generates a "4 - 0" control record and sends the payment records back for initial validation. If any records were in error, the same error condition will send the records back to error with separate "0 - 3" records. Use the Manual Remarks option to add an addenda record to the control file as an audit trail. If "1" is entered in the Remarks field, the system automatically fills it with "Unidentified to Error". The Remarks field contains 50 positions. If more information is needed, use additional Remarks records.
If the rejected batch contains a zero money amount, the batch is not controlled, and a replacement batch is not required. Each rejected batch is established on the control file with a "1 - 0" control record, for the Master File designated on the record from the financial agent.
The original batch number is shown in the remarks position on the "1 - 0" control record. If the original Master File is other than "7" miscellaneous , a "0 - 0" control record assigns the batch to Master File "7". The rejected batch is suspended with a "0 - 4" control record to wait for the corrected batch to be submitted. The remarks field on the "0 - 4" record contains the literal "Rejected Batch". Do not attempt to manually delete the batch from suspense.
The batch will be deleted automatically when the replacement batch is received. During initial EFPPS validation, all payments are added by tax class and compared to the classification on the deposit ticket. When the corrected batch is received, the suspended batch or pseudo batch is deleted with a "4 - 2" control record and the replacement batch is established with a "1 - 0" record.
If the replacement batch has a different batch number, the Remarks field of the control file will include the cross reference batch number. If the replacement batch has the same batch number, both "1 - 0" records will be present on the control file. The second record will be error coded as a duplicate on the Control Record List CMS 25 , but no correction is necessary once it is determined that the original batch was deleted without any transactions being processed.
For each resubmitted batch, the payments are reclassified from tax class "9" to the tax classes of the resubmitted payments. If the resubmitted batch had the same tax class totals as the original batch and was received on the same day, the reclassifications will offset each other and not be shown on the Reclassification Summary CMS To suspend an entire batch, enter the batch number and the total count and amount of the batch.
Leave the EFT number blank. To suspend a single record, enter the batch number, EFT number, count of 1, and the amount of the payment record. In the remarks field, enter the reason for the suspend, plus any cross-reference information, such as the batch number of a duplicate batch. To unsuspend the records, use the Manual Unsuspend option, and the records will be returned to their previous status.
Records without error conditions will be selected for the next TEP. To ensure consistent reports, the TEP should be run with the same date as the validation and correction activity.
That is, if the TEP is run at a. Accounting and Enterprise Operations will establish a schedule for nightly shutdown and TEP that will permit the TEP to be balanced without adversely affecting error correction or the loading and validation of new files from the financial agent. Blocks are not linked to batches.
The payment records assigned to a block could have originated in several different batches. The EFT number is the unique number used for payment research and audit trails and is included in the revenue receipts record. Revenue receipts are accumulated by fiscal year of the settlement date. The dates are from the beginning of the fiscal year to the last day of the current month. The "Current" field of the report shows the inclusive dates included as current revenue.
When the weekly RRCS is received, add the daily tax classes and balance the sum of the daily tax classes to the weekly tax classes. The final report for the date must be balanced to sum of the transaction records for all TEPs for the date. Journals are posted based on the month in which the activity occurred. For month end processing, deposit tickets and debit vouchers with settlement dates in the following month must be journalized separately. The automated journal is number The printed deposit ticket lists all of the batch numbers that have been included on the deposit.
The deposit ticket does not identify user fees and non-revenue items. Non-revenue deposit items are classified into account , then reclassified.
RRACS uses the printed debit voucher as the source for journalization. If a manual journal is required, prepare journal to debit the appropriate suspense accounts and credit the tax class accounts. Any record that was changed to a different tax class or Master File as a result of an auto correction during load and validate.
The payments are reclassified to Master File "7" , until a corrected batch is resubmitted. Special fund payments that were classified as tax class "9" , revenue suspense by the financial agent, but were assigned tax type codes that EFPPS is able to further classify.
These include:. Tax class "9" must equal Master File "7" Miscellaneous Account Part 1 is the Tax Class Reclassification, containing the net change in tax classes, as identified by a comparison between the tax type codes and the deposit ticket, and by changes in tax types made by error correction or auto correction.
Part 2 is the Master File Reclassification, based on a comparison between the tax type codes and the Master File in the batch header, plus Master File changes created by auto correction and error correction.
Both parts include a Net Change column that can easily be used to create a reclassification journal. Deposit ticket or debit voucher reclassifications list the batch number, EFT number, amount, from and to tax class and tax type code for all items that are identified as tax class "9" , a special fund alpha tax class , and are identified as "load and validate".
Auto corrections or error corrections that change the Master File or tax class include the batch number, EFT number, from and to tax class, from and to Master File, from and to tax type and a source of "load and validate" , "resubmitted" or "error correction".
Batch reclassifications, from a comparison to the batch header that do not also affect the deposit ticket , contain the batch number, EFT number, from and to Master File and source "batch re-class". Prepare a manual reclassification journal or for items not included in the reclassification summary. Be sure to document the changes with a manual reclassification list with the EFT numbers used in the reclassification and retain the list or worksheet as permanent documentation for the reclassification journal.
A manual reclassification journal is only necessary for items not included on the Reclassification Summary, if the automated journal fails, or it contains an error. At the bottom right corner of CMS 24, page 1, write DR, the appropriate account , and the amount for the account s that have a bracket around the money amount in the manual adjustment field of the Daily Trial Balance.
Write CR, the appropriate account , and the amount for the accounts that do not have a bracket around the money amount in the manual adjustment field of the Daily Trial Balance. These figures must net to zero. Run an add tape or excel spreadsheet if needed.
Do a pen and ink adjustment to the Tax class 9 suspense net change figure. Once the manual journal has been done, make two photocopies. Staple them together and put in the Reclass file in the cabinet. Only the tax class will be used. There will be an Out of Balance on one of the accounts if a Manual Delete was input on the previous day. Input a manual adjustment for the amount of the deleted payment. The correction screens allow the user to view a complete EFT transaction containing invalid elements and to identify and correct the invalid condition s causing the error.
Financial agent validation - The financial agent compares the TIN and tax type of the incoming payment to the enrollment database.
If the TIN does not match an enrolled taxpayer, the payment may be rejected back to the taxpayer's financial institution immediately depending on the type of payment. If the tax type is inconsistent with the enrollment filing requirements or an accepted payment is for a non-enrolled taxpayer, an indicator is generated by the financial agent so that the record will be re-validated on CFOL by IRS.
For FTD payment types, the tax period is automatically corrected to match a valid year or quarter ending month. Form ES, Estimated Tax for Individuals, payments are changed to subsequent payments if the current date is more than 8 months later than the tax period.
Auto corrected records are not sent to error correction. However, other types of errors are identified by the EFPPS program prior to the records being auto corrected. While correcting another error, you may notice that a tax period is incorrect. You must make sure all data fields are correct on the correction screen before you commit the record, any changes committed from the correction screen will no longer be auto-corrected. The Correction Screen appears showing the following options.
After the payment is worked click on the Get Next Unassigned Payment button or press the Control and backslash keys at the same time to access the next unassigned unresolved payment. When there are no more unassigned unresolved payments to correct, you will receive an error message stating,"There are no more Unresolved Records not Assigned".
The Assigned Unresolved option will always be displayed. To select a previously assigned error record:. Click on the drop down arrow, use the scroll bar to locate the EFT number you wish to work.
Click on the EFT number then submit. When a change is made you must click outside the box to continue or select Submit twice. Correction Entry Commit — To correct a field in error, enter the correction data in the text entry box. If the correction should be transmitted, select the "Yes" button.
You will receive the information message indicating the record was successfully committed. If the correction entered is invalid, an error message appears across the top of the screen. Reenter the correction data and repeat the steps above. If the correction should not be transmitted, click on the No button to return to the record. If no change is necessary for an unresolved element click the commit button at the bottom of the screen, select "Yes" when the pop-up window asks: "Do you wish to commit record?
Select "Yes" if the correction must be re-sequenced for two cycles at the Master File to wait for an entity change to post. If an incorrect entry has been committed, see IRM 3. If an unresolved payment needs further research before it can be worked, click the abort button at the bottom of the screen. Upon execution of the Abort key, the record will appear in the Assigned Unresolved drop down menu. The error record will remain in the unresolved inventory assigned to the employee that performed the Abort command.
Only that employee can retrieve and continue work on the error correction record, unless reassigned. Certain situations, such as an item waiting for an offset, require records flagged for error to be removed from the error correction inventory and placed in suspense status on the control file.
Click on the "Suspend" button at the bottom of the screen. Figure 3. Select yes or no in the pop up box. Research the FTCS database Single Point for taxpayer information or information about the bank at which the payment was initiated.
If you are unable to get into Single Point or the current day payment information has not been uploaded, call Commercial Services at You will need to provide the TIN. Based on information provided from the FTCS, it may be necessary to contact either the taxpayer or the taxpayer's financial institution. If sufficient taxpayer information is provided but a discrepancy is still present, contact the taxpayer to secure the correct information.
If a telephone number or the taxpayer's identity is not available, contact US Bank Customer Service via a service message to contact the taxpayer's financial institution to secure the correct information. To send a service message, complete the Service Message Request Form. All fields are required. They include the name of the employee sending the request, their work phone number, the date of the wire, the dollar amount, the TIN last four digits only , the EFT Number if available , and a message to the originator explain what information is needed in this field.
Send the completed spreadsheet to: customer. Suspend case for ten business days waiting for response, after ten business days and no response then send a second request and suspend an additional ten business days. If still no response after the second request, follow procedures to have the payment applied to the Unidentified Remittance File URF. If additional research is necessary for bulk provider payments, contact the bulk provider. Positions 8 and 9 of the EFT number will identify the bulk provider.
See "Bulk Provider Number" in the glossary. When a valid TIN for the taxpayer has been secured, retrieve the transaction record from the Assigned Unresolved status. If a record is committed and does not match CFOL, it will return as unresolved and be assigned to the same employee who worked the original unresolved record.
If an entity change is required, initiate the change and select "yes" for the resequence indicator. If a valid EIN is not located or needs verification, complete Form , Inquiry Referral, as follows and route to Entity per local procedures:.
Write along the top of Form "3 Day Expedite Process". If the EFT number begins with 23, research the FTCS database for taxpayer information or information about the bank at which the payment was initiated. Based on information provided by the FTCS Coordinator, it may be necessary to contact either the taxpayer or the taxpayer's financial institution.
When a valid Name Control for the taxpayer has been secured, retrieve the transaction record from the Assigned Unresolved status. Enter the correct Name Control in the Name Control element box and commit the entry.
Verify that the information is correct. If an entity change is not required, select "no" to the resequence indicator prompt. Once the record has been accessed, it remains assigned to the employee who worked the original error, unless reassigned by a manager. Description - The Origination Date is used to identify the date the payment amount was reported to the financial agent by the taxpayer. Do not count holidays and weekends. Description - The Payment Date is the date that the taxpayer will be credited with making the deposit.
On original validation, the Payment Date cannot be more than 30 days prior to the settlement date or days prior to the current processing date. Correction Procedures: Determine the correct payment date. Contact the financial agent if necessary. If the correct payment date is different from the payment date on the unresolved screen, enter the correct payment date in the Payment Date element box and Commit. If the correct payment date is more than 30 days prior to the settlement date or days prior to the current date, enter and commit the correct payment date.
The response is a warning message that the payment date exceeds the 30 day or day check. If the date is correct, select "Yes" to "Is this Correct? DO NOT change the payment date if the date on the check does not match. Description - The Original Payment Date will be blank, except for the following:. For returned payments transaction indicator "1" or "4" , the date must be present and will be sent to Master File as the transaction date.
If the date does not match the payment date of the original transaction, the record will unpost. For credit reversals transaction indicator "R" , the date is generated into this field from the payment date of the original transaction. For e-file debits payment method "0" , this date is the payment date requested by the taxpayer whenever the settlement is different from the requested date. If the field is blank on an Indicator "1" or "4" transaction, contact the Financial Agent to request the date.
The financial agent is responsible for providing this date on all reversals. Description - This code denotes the form number of the tax and the transaction code. In some instances, the tax period may also have to be changed. If necessary, enter the correct tax period in the Tax Period element box. If a change is required for both the Tax Type Code and the Tax Period, enter the corrected data in both element boxes before committing.
If a record is committed and it does not match CFOL, it will return as an unresolved. Set the Resequence Indicator, if appropriate. The tax period month does not equal one of the designated values for non-FTD tax types with Valid Months as shown in the same exhibit, or. For Tax Types with 6 and 7 the tax period must equal For current year tax periods, change the tax type code to the appropriate FTD tax type. EFPPS will then auto correct the tax period. If there are no prior liabilities, the tax type code may be changed to the FTD tax type.
For tax type Form ES if the tax period is changed to a date older than 8 months from the current date, a warning message is a reminder that the tax type will be changed to subsequent payment. If this is correct, select "Yes". If "No" , you will need to make another correction to the record. Working in compliance with "one stop processing " , every effort should be made to resolve an error using the Command Codes below. TXMOD: Use to access specific tax modules which contain pending and posted transactions, and to determine the status of an account.
See IRM 2. If the result of the EFTPS research is non-conclusive and appears out of line with the taxpayer payment history. To make a determination the technician will perform normal account and payment research procedures using IDRS command codes listed in IRM 3.
Will the payment full pay an account in Status 60 Installment status or an additional tax assessment? The EFPPS technicians will respond via password protected email within two business days of the request. The response should not contain specific account information, only respond suspicious or not suspicious.
Refer to the following IRM references for each element. Also, access the RS-PCC system to see an image of the check that was processed, for any information that may be noted on the check before it was imaged.
If you are able to determine the correction from this information, input the correct information on the correction screen and commit the correction to Master File. They will provide you with any backup information they received with the check.
Once Campus Support or the TAC offices respond to the backup request, review the information provided. Pull the error from the unresolved list and enter the correct element information. Commit the error to Master File. Entity will assign a new EIN to the taxpayer. Two additional days are allowed for errors requiring backup information from campus support or TAC offices. If you are unable to locate the correct taxpayer, review information received via UPS from the campus or TAC office or contact the appropriate campus for backup.
If you are still unable to locate the correct taxpayer, change the TIN to and commit the payment. You will have to commit the payment two times in order to push the payment through the system. Copy all backup showing exhausted research and route to the Unidentified lead for backup to associate with the unidentified payment file. This will cause the payment to go to Unpostables. Unpostables will "8" code the payment which will send the payment to Rejects.
Rejects will forward the payment to Unidentified. See 3. EFPPS is currently accepting these payments. Complete Form as follows:. On the Manual Delete screen, enter the batch number, item count, amount, remarks, from code, and EFT number.
Commit the changes. Be sure to print a copy of the screen when prompted. Provide the following information to the person that will make the payment:. Explanation — ex. ARRA surplus.
0コメント