Skip ahead to the main page
Partner Huddle
Pages

4 records a client may send with a payment

Partner Huddle Editorial Team · Published · 14 min read

The checked sources name four kinds of record: a return showing the tax due for a period, a copy of a federal notice of deposit status requested by the Minnesota commissioner, a remittance with its supporting documentation, and a third-party benefits disclosure that is a duty of the applicant, recipient, or legal representative under Fla. Stat. None of the four applies to every payment, because each depends on the agency and the type of payment.

The short answer for each payment

Intake staff usually ask one question about a payment: what does the agency want to see with it? The checked sources answer that question differently for each agency, and the wording of each rule tells you when the record is needed. The Minnesota statute is a clear example. It says that taxpayers must submit a copy of their federal notice of deposit status to the commissioner upon request by the commissioner. That sentence sets two conditions. The client must have the federal notice, and the commissioner must ask for it.

Read that way, the rule does not require the notice with every payment. It requires the notice when the commissioner asks. The practical step is to keep a current copy of the federal notice in the client file, so it can be sent quickly when a request arrives.

The other three record types work differently. The Ohio return is a document tied to a filing period, showing the tax due for that period. The Florida disclosure concerns third-party benefits, and the duty to report them falls on the applicant or recipient. A federal contract remittance goes to a Contracting Officer together with the supporting papers behind it.

Sorting each record by three questions gives intake staff a fast way to build a file: who receives it, what triggers it, and what it shows. The sections that follow take each record in turn, starting with the Ohio return, then compare the records side by side, before covering Ohio extensions, Form 941 language choices, Minnesota, Florida, and the federal contract.

What an Ohio return must show

The Ohio sales tax statute sets out what a return has to contain. Under section 5739.12 of the Ohio Revised Code, the return "shall show the amount of tax due from the vendor to the state for the period covered by the return and such other information as the commissioner deems necessary for the proper administration of this chapter." The sentence has two parts, and each one changes what intake staff should collect.

The first part is the amount of tax due for the period covered by the return. That makes the return a record of one specific period, not a general summary of the year. A client who files for several periods needs the figure for each one, and a file that mixes periods makes the match between return and payment harder to prove. Before a return goes into the file, check that the period on the return matches the period the payment is meant to cover, and that the amount shown is the amount of tax due from the vendor.

The second part is broader. The return must also include "such other information as the commissioner deems necessary." That phrase does not list the items. It leaves the list to the commissioner, which means the required information can change over time without a change to the statute's wording. For that reason, the file should hold the return itself along with the sales records that support the figure, not only the payment record.

Intake staff should also note who the statute names as the filer. The return shows tax due "from the vendor," which makes the vendor the party whose records matter. If a client operates more than one location or account, each vendor's return should be kept separate so that the amount due can be traced back to the right business. Keeping returns in one folder for each vendor and each period is a simple way to meet that standard in practice.

Comparing the record types side by side

The table compares the four records on the same measures: who receives the record, what triggers it, what it shows, and which source states the rule. Each row comes from a single checked source, so the table can be read as a set of separate rules rather than one general standard.

RecordWho receives itWhat triggers it What it showsSource
Ohio sales tax returnOhio commissionerEach filing period Tax due from the vendor for that period, plus other information the commissioner requires section 5739.12
Copy of federal notice of deposit statusMinnesota commissionerA request from the commissioner The taxpayer's federal notice of deposit statusMinn. Stat. 289A.20
Remittance and supporting documentationContracting OfficerParagraph (2) of the contract clauseA copy of the remittance and the documents behind it FAR 52.232-25
Third-party benefits disclosureFlorida agency The applicant's or recipient's rights to third-party benefitsThe name and address of any person liable to provide them Fla. Stat. 409.910

Only the Ohio return is tied to a regular filing period. The Minnesota record waits for a request, the federal contract record follows a specific clause, and the Florida record depends on whether the applicant or recipient has rights to third-party benefits. Sorting a client's files by the trigger column shows which records need to be ready in advance and which can wait for the agency.

For the federal contract row, the clause's paragraph (2) requires the contractor to provide "a copy of the remittance and supporting documentation." That wording covers two items, not one. Intake staff should keep the remittance and the supporting documents together in a single packet, so the copy goes out as one submission. Separate folders for the remittance and the support invite the common error of sending one without the other.

The Florida row differs in direction. The record is a disclosure the applicant or recipient makes to the agency, not a document the agency asks for after payment. The intake task is to gather the names and addresses of any liable person before the disclosure is written, because the statute asks for those details directly.

Ohio extensions and reconciliation returns

Ohio's statute gives the commissioner two related powers that affect the timing and content of a return. The commissioner "may extend the time for making and filing returns and paying the tax," and may require a reconciliation return for certain periods. The full wording, in section 5739.12, is that the commissioner "may require that the return for the last month of any annual or semiannual period, as determined by the commissioner, be a reconciliation return detailing the vendor's sales activity for the preceding annual or semiannual period."

The extension power changes the deadline, not the duty. Both the time for filing a return and the time for paying the tax are subject to the commissioner's extension. Because the statute uses the word "may," an extension is a decision the commissioner makes, not an automatic change. Intake staff should record the extended dates in the client file next to the original dates, so the period and payment can be matched later. Keeping the agency's notice of any extension in the same folder is a practical habit that makes the timing easy to explain.

The reconciliation power applies to one specific return: the return for the last month of an annual or semiannual period. The commissioner determines which periods count, so intake staff cannot assume every client has one. The task is to confirm, from the agency's determination, whether a client's period is annual or semiannual before preparing the reconciliation return.

A reconciliation return "details the vendor's sales activity for the preceding annual or semiannual period." That is a broader record than a single-month return. It covers the whole earlier period, so the file needs the sales records for that full span. A client who has kept monthly returns already has most of the detail, but the reconciliation will be easier to prepare if the monthly figures are gathered in one schedule before the return is due.

Federal payroll filings and Spanish-language forms

The IRS instructions for Form 941 address two points that affect intake: the form choice for employers in the U.S. territories, and which forms have Spanish-language versions. The version of the instructions checked for this post is the March 2026 revision. It states that employers in the U.S. territories file Form 941 or, if you prefer your form and instructions in Spanish, you can file Form 941 (sp). The choice of language is the filer's own preference, and the Spanish version is a legitimate filing option under that sentence.

The same instructions list examples of Spanish-language forms. According to the March 2026 revision of the Form 941 instructions, the examples include "Form 941 (sp), Form 944 (sp), Form SS-4 (sp), Form W-4 (sp), and Form W-9 (sp)." The word "examples" matters. The list shows forms that have Spanish versions, but it does not claim to be complete. Intake staff who serve Spanish-speaking clients should treat the list as a starting point and check each form the client needs.

Form 941 is the form at the center of the instructions, and the Spanish version is named alongside it. When a client's payroll filing is prepared, the form name in the file should match the version the client chose. Mixing a Spanish form with English instructions, or the reverse, creates a file that is hard to explain later. The intake sheet should record which language was used for the form and the instructions together.

The other forms on the list serve different purposes, and intake staff should keep each one in its own place in the file. Recording the form name and the language version for each one prevents confusion when a client asks which version was used.

Finding a Spanish-language version

The IRS instructions give a direct method for checking whether a form is available in Spanish. The instructions tell readers to "go to IRS.gov/SpanishForms to determine if a Spanish-language version is available." That is the step to take when a form is not on the examples list, or when a client asks about a form that was not named in the instructions.

A workable order for intake staff is to start with the examples list in the Form 941 instructions, since those forms are named directly. If the form the client needs is not on that list, go to the IRS Spanish forms page and check the form by name. Keep a dated note of the check in the client file, so there is a record of which version was available when the filing was prepared.

The client's preference governs the choice. The instructions say that employers who prefer their form and instructions in Spanish can file the Spanish version. Intake staff should ask the client which language they want before preparing the form, instead of choosing a version on the client's behalf. Recording that preference in the intake notes makes the choice clear to anyone who reviews the file later.

Once the form version is confirmed, the file should show the form name, the language, and the date the version was checked. A short line in the intake sheet, such as the form name followed by the language and the check date, is enough to make the file complete. This habit also helps with the earlier questions about timing and content, because every filing in the folder carries the same identifying details.

Minnesota deposit status on request

The Minnesota statute makes this record conditional, which changes how intake staff plan the file. Under Minnesota Statutes section 289A.20, "taxpayers must submit a copy of their federal notice of deposit status to the commissioner upon request by the commissioner." The duty begins when the commissioner asks. The sentence does not say the notice must accompany every payment.

That shapes the file in two ways. First, the client should keep a current copy of the federal notice on hand, because the state's request can arrive at any time and the quoted sentence does not state a deadline for gathering the notice. Second, the request itself should be logged. Write down the date the commissioner asked and what was sent in reply. That record shows compliance if the commissioner asks again.

Intake staff should also keep the federal notice apart from the Minnesota return and payment. As a practical choice rather than a statutory requirement, the notice belongs in a labeled section of the client file. Filing it with the payment papers makes it harder to find when a request arrives.

Third-party benefits disclosure in Florida

Florida's rule places a reporting duty on the people who receive or seek benefits. Subsection (5) of section 409.910 of the 2024 Florida Statutes says that "an applicant, recipient, or legal representative shall inform the agency of any rights the applicant or recipient has to third-party benefits and shall inform the agency of the name and address of any person that is or may be liable to provide third-party benefits."

The sentence contains two duties. The first is to tell the agency about any rights to third-party benefits. The second is to give the name and address of any person who is or may be liable to provide them. The word "may" widens the second duty, so a possible source must be reported, not only one who is certain to be liable. Intake staff should gather those names and addresses during the intake interview, before the disclosure is written.

The statute covers three people: the applicant, the recipient, and the legal representative. The statute also applies to a legal representative acting for the applicant or recipient. Before preparing a disclosure, confirm who is acting for the client and whether that person is the one submitting it.

Federal contract payments and remittance support

Federal contract payments follow a different rule from state tax filings. Under FAR 52.232-25, Prompt Payment, paragraph (2) requires the party to "provide a copy of the remittance and supporting documentation to the Contracting Officer." The recipient is the Contracting Officer named in the clause, not a tax agency. The record is proof of the payment together with the documents that back it.

The clause names two items, so the submission should contain both. The remittance and the supporting documentation travel together. Intake staff should assemble them in one packet with a cover index listing each document. That way the copy sent to the Contracting Officer is complete on the first submission, and no one has to chase a missing attachment.

Keep contract payment files separate from tax files. A remittance to a Contracting Officer answers a different question than a state return showing tax due, and mixing them makes both harder to locate. This post relies only on paragraph (2) of the clause, so any other requirements in the clause fall outside its scope.

Which one should you pick?

Intake staff often face a choice between options rather than a single record. The checked sources show that different parties make the choice in different situations. The table below lists each choice, who makes it, and what the source says.

ChoiceWho decidesWhat the source says Source
Reconciliation return for the last month of a periodThe commissioner May be required for an annual or semiannual period "as determined by the commissioner" section 5739.12
Extended time for filing and payingThe commissionerThe commissioner "may extend the time" section 5739.12
English or Spanish version of Form 941The filer An employer who prefers Spanish "can file Form 941 (sp)"IRS Form 941 instructions
Copy of federal notice of deposit statusThe Minnesota commissioner's requestSubmitted "upon request by the commissioner" Minn. Stat. 289A.20

The pattern is clear. For Ohio's reconciliation and extension options, the client has no choice, so the file should record the commissioner's decision as it arrives. For the Spanish form, the client picks the language, so intake staff should ask the client before preparing the form. The Minnesota notice is not a choice at all but a response to a request.

Matching payment-linked records to their payment type

The IRS instructions make language choice a matter of matching the form to the client's preference. They name five Spanish-language examples: "Form 941 (sp), Form 944 (sp), Form SS-4 (sp), Form W-4 (sp), and Form W-9 (sp)." The word "examples" means the list is not complete, so a form missing from it may still have a Spanish version.

The instructions tell readers to "go to IRS.gov/SpanishForms to determine if a Spanish-language version is available." Intake staff should use that page for any form that is not on the list. Matching works best when it starts from the payment or filing type, then identifies the record that goes with it.

Payment or filingRecord to matchWhere to check
Ohio sales tax paymentReturn for the same period showing the tax due section 5739.12
Minnesota commissioner's request Copy of the federal notice of deposit statusMinn. Stat. 289A.20
Federal contract paymentRemittance and supporting documentationFAR 52.232-25
Federal payroll filing (Form 941 family)Form and instructions in the language the client chose IRS Form 941 instructions

Each row starts from a payment or filing and ends at the record the source requires. Before the file is closed, check that the record matches the payment type and that any language choice is noted beside the form.

Not legal or tax advice.

Related guides: Client tax payments: compare 3 percentage floors · Client disengagement checklist: 9 final file checks · 2 checks before a firm bills a client for file copies.

Sources