Square invoice limits cover partial payments, automatic send times, additional recipients, and attachments; check all four before sending a client bill. Square makes sending easy. That speed is useful for a firm that bills many clients every month, but it also means a bad setting can reach a client before anyone on your team notices. Many billing problems start with a setting nobody reviewed, not with the software itself.
Square's invoice help page describes the feature this way: "With invoices, you can request payments for goods or services by sending an unlimited number of digital invoices, estimates, or recurring invoices." So the limits in this article are not about how many bills you can send. They are about what each bill can do once it leaves your hands.
Accounting firms have a particular version of this problem. A bookkeeping client on a monthly retainer, a tax preparer billing a one-time return, and an advisory partner collecting a payment on a project may all use the same invoice screen. A setting that fits one of them can cause a problem for the other two. Before any bill goes out, the person sending it should be able to answer four questions, and each one corresponds to a section below.
The questions are simple. How can the client pay in pieces? Will this bill repeat without anyone pressing send? Who else will receive it and get reminders? What is attached? Your firm should decide each answer on purpose and write it into its billing procedure, so the next person who sends a bill does not have to guess.
No technical background is required. You need access to the invoice settings, a current list of active clients, and time with whoever runs billing day to day. The advice here is written for partners and operations leads who set up or approve bills rather than for the staff who send them.
The limits matter most in the first few weeks with a new setup. Early bills set the pattern clients expect, and fixing a bill after a client has already seen it creates more work than getting it right the first time. That is why each check below is framed as a decision to make before sending, not a repair to make afterward.
Decide how partial payments fit each engagement
The first limit is about partial payments. Square's help page says, "Your customer will make partial payments of up to $50,000 toward the invoice balance." Plan for that rather than assuming the full balance will arrive in one payment. A client who cannot pay everything at once may split the balance into several payments over time.
Partial payments change what "paid" means in your records. An invoice can stay open while money comes in piece by piece. If your team marks the invoice closed as soon as the first payment lands, the records will show a balance that is wrong. If they wait for the full amount, a client who has already paid most of the bill may receive a reminder that makes the relationship harder than it needs to be. Neither outcome is hard to avoid, but both require someone to decide in advance what the record should show.
Picture a partner whose client pays a project fee in two installments over a few weeks. If the staff member who records payments has not been told about the installments, the invoice can look unpaid for weeks while most of the money has already arrived. A short note on the invoice record, saying the balance is being paid in pieces, helps someone understand the remaining balance before following up.
Ask the partner who owns each client which of three situations applies: the client usually pays in full, the client sometimes pays in parts, or the client has agreed in writing to a payment plan. Each answer changes what the staff member should do when money arrives, and the answer should be written down where the staff member can see it.
Where your engagement letter sets payment terms, make sure the invoice wording matches it. If the letter calls for payment in full, a partial payment option on the invoice may contradict what the client signed. If the letter says nothing about installments, add a short clarification at the next renewal rather than relying on an invoice note to settle the question.
Think about who picks up the file when a client pays in parts. If billing staff hand an invoice to a collections contact, that handoff note should say how much has been paid and what the client agreed to. Without it, the next person to open the invoice starts from scratch, and the client may be asked the same question twice.
Write a short rule for this and keep it with your other billing procedures. It should name who checks partial payments, how often they check, and what they do when a client stops paying partway through. The last part is a judgment call for the partner, not the staff member, because it affects the client relationship. A staff member can record a payment; a partner should decide whether to chase the remainder.
Think about the size of any single engagement too. A client who sees a large balance, a split schedule, and a partial payment option for the first time in one message is likely to have questions.
Recurring invoices: know exactly when the bill leaves
Recurring invoices are where a setup error turns into a repeated one. Square's help page states, "Scheduled recurring invoices will be automatically sent to your customer at 10 a.m." For a monthly bookkeeping retainer, that is the whole point. For a client whose contact has left the company, whose scope has changed, or whose fee was wrong from the start, it means the error goes out again on the next cycle.
Before you set a schedule, be clear about its frequency. A monthly retainer and a quarterly review fee need different schedules, and a mismatch means either a bill goes out too often or a fee is missed.
Before you schedule anything, check four things: the amount, the client, the recipient list, and the attachments. Treat the first automatic send as a live event rather than a draft. Open the scheduled invoice, read it the way the client will, and only then let it run. If the bill depends on a figure that changes during the year, such as a rate or a headcount, decide how you will update the schedule before the next send, and check that the update happened.
Tell the client in writing when an amount is going to change, and give them the date the new figure will first appear. A client who learns about a new fee from a bill has every reason to feel surprised.
Consider a monthly retainer that ends in the middle of the year because the client sold the business. If the schedule was never reviewed, the bill keeps going until someone notices, and the client is left to ask why. A standing review on the operations calendar gives someone a chance to catch that. Assign one person to own the review, and give them a written list of what to look for.
One practical test is to ask whether the client will need the same service on the same terms next period. If the answer is yes, a schedule may fit. If the answer depends on what happens in a meeting, send each bill by hand after the meeting.
Keep recurring schedules for ongoing work only. A one-time return, a valuation, or a project with a defined end date should be a single invoice. A schedule that outlives the engagement keeps billing for work that has already finished, and the client will be right to question it. Put a review date on every schedule, so that each renewal or quarter-end forces a check on whether the schedule still matches the engagement.
Also confirm the applicable time zone with Square support before you plan around the automatic send time. If a client expects a bill at the start of their working day and it arrives later, or the reverse, the difference will show up in their questions.
Recipients and reminders: decide who sees the bill
The third limit controls who else sees the bill. Square's help page says you can add up to 8 additional recipients and set automatic reminders when sharing a link by email. Settle the recipient list and the reminder plan together, so you know both before the first email goes out.
Many small firm bills have a natural audience of one or two people: the owner who approves the spend and the person who pays it. Accounts payable teams, office managers, and other staff are often added out of habit. Treat each added name as someone who may see the amount, the service description, and any attachment. Only add people who need to see the bill, and remove anyone whose role has changed.
| Setting | Decide before you send | Check on every send |
|---|---|---|
| Partial payments | Who records a partial payment, and when an invoice counts as settled | The open balance matches your records |
| Recurring invoices | Which engagements are ongoing, and when each schedule gets reviewed | The amount, client, and recipients are still correct |
| Recipients and reminders | Who needs to see the bill, and who gets reminders | Each name matches the client's current contact sheet |
| Attachments | Which support documents belong with each bill | The files fit within the total size limit and each file opens |
Read the table as a pre-send checklist. It covers the four settings this article is about. It does not list every option Square offers, so check the help page for anything beyond these.
The cap is also a useful discipline. If you find yourself wanting to add every name on the client's org chart, the bill is probably doing a job that a conversation should do. A bill is a request for payment, and sending it to a long list turns that request into a discussion among people who have no role in it.
A simple monthly routine keeps this manageable. The operations lead reviews the active recurring invoices, compares each recipient against the contact sheet, and removes any name that has left the client's company. New approvers get added at the same time. The routine is likely to take less time than one follow-up email about a bill that went to the wrong person.
Keep a short contact sheet for each client. Record the primary contact, the person who pays, and any approved billing addresses. Old addresses are an easy way for a bill to land in the wrong inbox, and with a cap on recipients, every slot should go to a person you have confirmed.
Reminders deserve the same care. A reminder is a message the client receives on your behalf, so its timing and tone reflect on the firm. Decide, for each client type, whether reminders should run at all, and whether a partner should review the first reminder before it goes out. That review can be quick, and it can prevent a reminder for a payment the client already made in another way.
Train everyone who sends bills on these four settings, and keep the training short enough that people will read it. A one-page sheet that names the owner of each setting is more useful than a long manual that nobody opens.
Attachments: keep support files under the cap
The fourth limit is about files. Square's help page says, "If applicable, you can attach up to 10 files totaling 25 MB." The phrase "if applicable" matters. Many bills need no attachment at all, and the simplest bill is often the easiest one to approve. Check the combined size as well as the file count; fewer files can still exceed the size cap.
Scanned documents are the most likely source of a size problem. A high-resolution scan of a multi-page statement can be large on its own, and a handful of them can use up the available space quickly. Check each file's size before you attach it. Lower the scan resolution to one that is still readable, then check the total again.
Open each file on a phone as well as a computer before you rely on it. Some clients will read invoices on a phone, and a document that looks fine on a large monitor can be hard to read on a small screen. The check takes little time and catches problems the client would otherwise report to you.
Think about what the client actually needs. A bill usually needs enough support for the client to understand the charge and approve payment. It rarely needs the full working papers behind an engagement. Internal workpapers belong in your own file system. Sending them with an invoice gives the client material they did not ask for, and it may expose details your engagement letter never meant to share. A short summary or fee schedule usually does the job better.
If a file contains bank details, payroll figures, or information about other clients, remove those pages before you attach it. The recipient list and the attachment list should be checked together for this reason.
Set a naming convention so files are easy to find and check: client name, period, and document type, in that order. Then, before you send, open each attachment and confirm it is the right file for this client and this period. A wrong attachment is hard to pull back once the client has it, and the check takes far less time than the apology would.
Decide now how you will handle a bill that went out with the wrong file. Know who the client should contact, what you will say, and whether a corrected invoice should replace the original. Having that answer ready keeps a small error from becoming a long email thread.
None of these four settings is complicated on its own. The risk comes from leaving them at whatever the last person chose. A partner who can answer those four questions before a bill goes out is much less likely to answer a client's question about it afterward.
Start with the bill that goes out next. Run the four checks on it, note what you changed, and repeat the process with the next one. For a broader review, use the invoice checks before sending a client bill. A procedure built from real bills will serve your team better than one drafted from a list.