My team handled the FUTA filings for a PEO client a few years back, and the first time we saw Schedule R, it was attached to a 940 with 47 client-level rows – all handwritten on a supplemental spreadsheet instead of the actual form. We spent two days reformatting that data before we could even begin a review. Building a proper Schedule R template into our aggregate payroll workflow saved us dozens of hours the following January.
Download Form 940 (Schedule R) PDF
Key Takeaways
- Schedule R is an allocation schedule required for aggregate Form 940 filers – organizations such as PEOs, CPEOs, and reporting agents that file a single Form 940 on behalf of multiple clients.
- The schedule breaks down the total FUTA taxable wages, FUTA tax, and credit reduction amounts by each underlying client (identified by EIN).
- Only employers authorized to file aggregate returns – specifically those who have received IRS approval or operate under IRC §3504 agent authority – use Schedule R.
- Due date follows Form 940: January 31 for the prior calendar year, or February 10 if all FUTA deposits were timely made.
- The most common error is failing to match the sum of all Schedule R rows exactly to the totals on Form 940 – any discrepancy triggers an IRS notice.
- Quick rule you can copy into your SOP: reconcile the Schedule R column totals to Form 940 Lines 3, 7, 10, and 11 before any partner review begins.
What Form 940 Schedule R Is and When to Use It
Form 940 Schedule R – “Allocation Schedule for Aggregate Form 940 Filers” – is used by organizations that file a single Form 940 covering multiple employer-clients. It is an attachment to the aggregate Form 940 and provides a client-by-client breakdown of the FUTA data that rolls up into the consolidated return.
The IRS requires Schedule R to maintain transparency in aggregate filing arrangements. Without it, there is no way for the IRS to verify that the aggregate return accurately reflects each underlying employer’s liability. Schedule R is the audit trail that makes aggregate 940 filing legally sound.
From my side of the desk, the form is straightforward in structure but demanding in precision. Every row must tie exactly to payroll records for that client, and the column totals must equal the Form 940 totals to the dollar. There is no rounding grace here.
Who Must File Schedule R
Schedule R is only for organizations that have been authorized or designated to file aggregate Form 940 returns. This includes: (1) agents filing under the authority of IRC §3504, designated by employer-clients via Form 2678; (2) Certified Professional Employer Organizations (CPEOs) approved by the IRS under IRC §7705; and (3) other IRS-approved aggregate filers. Standard payroll companies and CPA firms do not file aggregate 940s for clients – they file separate returns per client EIN.
How Schedule R Relates to Form 940
The aggregate Form 940 is the summary-level return. Schedule R is the supporting detail. The Form 940 totals represent the combined FUTA obligation for all clients, while each row on Schedule R represents one client’s share of that obligation. Think of it as a subsidiary ledger – the sum of all subsidiary balances must equal the control account (Form 940).
When You Do Not Need Schedule R
If you file a separate Form 940 for each employer you serve, Schedule R is not required. Schedule R is only triggered when a single Form 940 is filed aggregating multiple employer EINs. If you are uncertain whether your filing arrangement qualifies as aggregate, review the Instructions for Form 940 and confirm your agent or CPEO authorization status with the IRS.
How to Complete Form 940 Schedule R
Schedule R is a columnar form. Each row represents one employer-client identified by EIN and legal name. The columns collect FUTA data that must reconcile to the aggregate Form 940. Here is the column-by-column breakdown.
| Column | Data Required | Ties to Form 940 |
|---|---|---|
| (a) Client EIN | Employer Identification Number of each client | Must match IRS records for each client |
| (b) Total payments | All wages paid to employees during the year | Feeds into Form 940 Line 3 |
| (c) Exempt payments | Wages excluded from FUTA (e.g., fringe benefits, dependent care) | Feeds into Form 940 Lines 4–6 |
| (d) FUTA taxable wages | Total payments minus exempt payments, capped at $7,000/employee | Feeds into Form 940 Line 7 |
| (e) FUTA tax before adjustments | Column (d) × 0.6% | Feeds into Form 940 Line 8 |
| (f) Credit reductions | Schedule A amounts for this client’s credit reduction states | Feeds into Form 940 Line 11 |
| (g) Total FUTA tax | Column (e) plus column (f) | Feeds into Form 940 Line 12 |
Completing the Header Section
Before the client rows, the schedule requires the aggregate filer’s own EIN, name, and the calendar year being reported. The aggregate filer’s name is the entity filing the Form 940, not the individual clients. Enter the tax year in the space provided and verify the aggregate filer’s EIN matches the Form 940.
Adding Client Rows
Enter one row per client. If you have more clients than the form has rows, continue on additional pages and number them sequentially. The IRS allows continuation pages with the same column structure. I recommend numbering pages in the header to make it easy to reference during any IRS inquiry.
Completing the Totals Row
The final row on Schedule R sums all client-level data. These column totals must match the corresponding lines on Form 940 exactly. Run a reconciliation macro or formula before printing – catching a mismatch at this stage is far easier than explaining it to the IRS after filing.
Deadlines, Penalties, and Filing Requirements
| Filing Event | Deadline | Notes |
|---|---|---|
| Aggregate Form 940 with Schedule R | January 31 | For prior calendar year |
| Extended deadline if deposits were timely | February 10 | All required FUTA deposits must have been made on schedule |
| Quarterly FUTA deposits (if over $500) | April 30, July 31, October 31, January 31 | Applies to aggregate liability for all clients combined |
Penalty Structure for Aggregate Filers
Aggregate filers are held to the same penalty standards as individual employers. Late filing attracts a 5% per month penalty on unpaid FUTA tax, up to 25%. Failure-to-deposit penalties range from 2% to 15% depending on days late. Because aggregate filers often handle significant combined FUTA liabilities, the penalty exposure per missed deposit can be substantial. Small errors create big cleanup.
Electronic Filing for Aggregate Returns
The IRS requires electronic filing for all aggregate Form 940 returns filed by agents and CPEOs. These filers typically use IRS-approved payroll software or an authorized e-file provider. Paper filing of aggregate 940s is generally not accepted. Confirm your software vendor’s support for Schedule R before the January deadline.
Who Qualifies as an Aggregate Filer
The IRS restricts aggregate Form 940 filing to specific categories of entities. Filing an aggregate 940 without proper authorization is a compliance violation, so understanding the threshold is critical before adopting this approach for any client.
IRC §3504 Agents
Under IRC §3504, an employer can designate an agent to file returns and pay taxes on its behalf. The agent files Form 2678 (Employer/Payer Appointment of Agent) to obtain the designation. Once approved, the agent may file aggregate 940s covering all clients for whom they have agent authority. Each client employer-client retains ultimate liability for its own FUTA obligations.
Certified Professional Employer Organizations (CPEOs)
CPEOs are certified by the IRS under IRC §7705 and have specific rights to file aggregate employment tax returns, including Form 940. CPEOs go through an IRS approval process and must maintain certification requirements annually. The CPEO’s aggregate return covers clients in the CPEO arrangement, and each client’s data is allocated on Schedule R.
Standard Payroll Agents and CPA Firms
A CPA firm or payroll company that prepares and files 940s for clients without a §3504 or CPEO designation must file a separate Form 940 for each client EIN. They cannot aggregate those returns into a single 940. This distinction is important – I have seen firms try to file a single 940 for a group of related entities without proper authorization, which creates significant compliance exposure.
Allocation Mechanics and Credit Reductions on Schedule R
The credit reduction dimension of Schedule R adds complexity beyond simple FUTA wage allocation. If any of your aggregate clients operated in credit reduction states, each affected client must show the credit reduction amount on their Schedule R row.
How Credit Reductions Flow Through Schedule R
If Client A had 20 employees in California (a historical credit reduction state) and Client B had no California employees, only Client A’s row on Schedule R carries a credit reduction amount in column (f). The aggregate Form 940 Line 11 then shows the sum of all client credit reductions. This allocation requires you to track not just aggregate FUTA wages but the state-level breakdown for each client – effectively maintaining the data from Schedule A at the individual client level.
Multi-State Clients on Schedule R
If a client has employees in multiple states, you still report that client as a single row on Schedule R, but the credit reduction amount in column (f) must account for all credit reduction states applicable to that client. Keep workpapers showing the state-level breakdown behind each Schedule R row. This is your audit defense if the IRS ever questions the credit reduction calculation.
Year-End Reconciliation Protocol
My standard practice is to build a reconciliation workpaper before finalizing the aggregate 940. The workpaper maps each Schedule R column total to the corresponding Form 940 line, shows any credit reduction detail by state and client, and confirms that the sum of all client FUTA deposits equals the aggregate return balance due. This takes about 90 minutes for a 20-client aggregate but catches errors that would otherwise generate IRS notices three months later.
Common Mistakes That Slow Things Down
- Column totals not matching Form 940 – The IRS immediately flags any mismatch between Schedule R totals and Form 940 lines. Build a reconciliation formula that auto-checks this before you submit.
- Filing aggregate 940s without proper authorization – Unless you hold §3504 agent designation or CPEO status, you cannot file aggregate returns. Filing without authorization exposes both the agent and the clients to compliance risk.
- Missing credit reduction allocations on client rows – Failing to carry state credit reductions through to individual Schedule R rows creates a mismatch at the aggregate level. Track credit reduction data by client, not just in aggregate.
- Using incorrect client EINs – An EIN error on Schedule R triggers an IRS notice. Verify all client EINs against the IRS-issued confirmation letters or prior filed returns before entering them on the form.
- Applying the wrong FUTA taxable wage cap – The $7,000 per-employee FUTA wage cap applies separately for each client. An employee who transferred from one CPEO client to another during the year may have FUTA wages restarted for the new client depending on the arrangement.
- Losing track of continuation pages – If the client list spans multiple Schedule R pages, the totals on all pages must be combined and verified against the Form 940. Failing to include continuation pages causes a systematic underreporting problem.
- Not confirming e-file support for Schedule R – Some payroll software platforms support aggregate Form 940 but do not properly generate or attach Schedule R in the e-file transmission. Confirm with your software vendor before the January deadline.
Practical Checklists You Can Reuse
Copy these into your internal wiki or SOP.
Schedule R Pre-Filing Checklist
- Confirm §3504 or CPEO authorization is current for the filing year
- Pull FUTA taxable wage reports for every client by EIN
- Identify any clients in credit reduction states and calculate credit reduction amounts
- Enter all client rows on Schedule R with correct EINs, names, and data
- Sum all column totals on Schedule R
- Reconcile column totals to Form 940 Lines 3, 7, 8, 11, and 12
- Confirm aggregate FUTA deposit amounts match the liability shown on Form 940
- Verify e-file software properly attaches Schedule R to Form 940 submission
Client-Level Data Review Checklist
- Verify FUTA taxable wages for each client do not exceed $7,000 per employee
- Check for mid-year employee transfers between clients and apply wage cap rules correctly
- Confirm state-level FUTA data for each multi-state client
- Verify credit reduction allocations match the underlying Schedule A data for each client
- Cross-reference each client’s FUTA wages to the quarterly FUTA deposit records
Year-End Aggregate Reconciliation Checklist
- Compile final FUTA wage reports from payroll system for all clients
- Review IRS credit reduction state announcement for the tax year
- Update credit reduction data for any clients in affected states
- Prepare Schedule R draft and run column reconciliation to Form 940
- Review prior year Schedule R to confirm no new clients were added or dropped without updating the aggregate EIN list
- Confirm all FUTA deposits made throughout the year are credited and accounted for in the balance due calculation
For Accounting Firms – Keep Delivery Smooth While You Scale
Aggregate payroll compliance – managing Schedule R for 30, 40, or 80 clients simultaneously – is the kind of high-precision work that cannot afford interruptions during January filing season. Firms that support PEO clients or have §3504 agent arrangements often find that the Schedule R preparation workload is one of the most time-intensive items in the entire payroll compliance calendar. Adding structured offshore support for data preparation, reconciliation workpapers, and draft review can materially reduce the partner and manager hours absorbed by this work.
Accountably supports CPA and EA firms with payroll compliance work at scale – including FUTA allocation schedules, state unemployment reconciliations, and aggregate return support – through trained offshore teams embedded in your existing workflow. We keep this mention brief on purpose, your process comes first.
FAQs About Form 940 Schedule R
What is Form 940 Schedule R used for?
Schedule R is used by aggregate Form 940 filers – such as §3504 agents and CPEOs – to allocate the FUTA tax information on the aggregate Form 940 back to each individual employer-client. It provides the IRS with a client-by-client breakdown of FUTA taxable wages, credit reductions, and total FUTA tax liability. The column totals on Schedule R must equal the corresponding lines on the aggregate Form 940.
Who is required to file Schedule R?
Only organizations authorized to file aggregate Form 940 returns are required to attach Schedule R. This includes agents designated under IRC §3504 via Form 2678, and Certified Professional Employer Organizations (CPEOs) approved under IRC §7705. Standard payroll service providers and CPA firms that file individual 940s per client are not aggregate filers and do not use Schedule R.
What information appears on each row of Schedule R?
Each row represents one employer-client and shows: the client’s EIN, total wages paid, exempt payments, FUTA taxable wages (capped at $7,000 per employee), FUTA tax before adjustments, any credit reduction amounts, and total FUTA tax for that client. The row totals for all clients must reconcile to the aggregate Form 940.
When is Schedule R due?
Schedule R is filed as an attachment to the aggregate Form 940 and follows the same deadline: January 31 for the prior calendar year. The deadline extends to February 10 if all required FUTA deposits were made on time. Aggregate filers are generally required to file electronically.
What happens if Schedule R totals do not match Form 940?
A mismatch between Schedule R column totals and Form 940 lines will generate an IRS notice requesting reconciliation or adjustment. The IRS uses Schedule R as the verification mechanism for aggregate returns, so any discrepancy triggers a compliance inquiry. Always reconcile Schedule R to Form 940 before submission.
This article is educational, not tax advice. Rules change, and states differ. Confirm thresholds, deadlines, and elections against the current IRS instructions for your year and facts.