Upload Documents in Microsoft Forms: Limits and Workarounds

Microsoft Forms can collevt files, but two limits trip up accounting firms: how large each upload can be, and whether the client has to sign in to send it. Clients outside your tenant feel both. If you only need files from staff, Forms is fine. For clients who just want to send a bank statement, use a form that accepts files from anyone with the link.

Where Microsoft Forms stops being convenient

Microsoft Forms is free with a Microsoft account and part of Microsoft 365, and it works best inside Microsoft tools. That is a good fit for internal requests: an employee signs in, answers questions, attaches a file, and the response lands in your tenant.

Client intake is a different job. The person on the other end is a business owner with a phone, a folder of PDFs and no reason to know which account your firm uses. Two things go wrong:

• Sign-in. A file upload question usually ties the respondent to a signed-in account. A client who is not in your organization gets a login prompt instead of an upload button, and many of them reply by email with the files attached instead.
• File size. A scanned year of statements, a phone video of a receipt pile or a large export from accpunting software can exceed the per-file cap on an upload question.

I am deliberately not quoting numbers for either limit. Microsoft changes the rules by plan and by tenant settings, so read the current Forms support page for your plan before you pick a design. The shape of the problem stays the same: uploads are built for people inside the Microsoft boundary.

Your options for taking documents without a client login

Two honest notes on that table. Tally is a good product with a large community, and if your clients only send small PDFs, the 10 MB free cap may never matter. Qwenvo is the one we build (our team makes it), and it launched in October 2026, so it has far fewer public reviews than the others. Judge it on a test form with your real documents before you move your whole intake over.

Build your client intake form free

Set up a no-login document intake in Qwenvo

Qwenvo is a completely free form builder: no paid plans, no card, and every feature is on for every account. Here is the setup we use as a starting point for accounting clients.

1. Create the form. Start from the client intake template, or describe the form to Create with AI. Type / to add blocks.
2. Add a hidden field for the client ID. Put the ID in the link you email each client (?client_id=...) so you never ask them to type it. The hidden fields help page covers the syntax.
3. Ask for structure before files. Add dropdowns for document type and period, then the File upload block. Because each file can be up to 1 GB, a client can send a large scan in one go.
4. Verify the email. Turn on respondent email verification (a one-time code). Clients prove they own the address without creating an account.
5. Set the guardrails. Use password protection if you want one shared passcode, prevent duplicate submissions, and set data retention so uploads auto-delete after N days.
6. Switch off the badge. Turn off Qwenvo branding in the Settings drawer so the form looks like your firm's.
7. Put it on your domain. On the Domains page, add a subdomain such as docs.yourfirm.com, add the CNAME to qwenvo.com and the TXT record shown, click Verify, then pick it on the Share tab. The HTTPS certificate is issued on the first visit. Subdomains only, so a bare yourfirm.com will not work.
8. Send it. Share the link, or paste the Standard embed into your WordPress custom HTML block, Webflow, Framer or Wix page.

Notification emails go to you, and you can sennd a confirmation email to the client so they know the files arrived.

The fields that make the files usable later

A pile of uploads is only half a workflow. These fields decide whether the next step can run without a person opening every file.

Keep it short. Every extra question loses some clients, and you can check where people quit in the drop-off analytics. Partial submissions show up as incomplete rows, so you can chase a client who started and stopped.

Try the file upload guide

Where the form sits in an invoice and document pipeline

For most firms the form is the front door, not the whole system. In our AI Invoice & Document Processing system, documents arrive from an inbox or a form, an LLM plus OCR step extracts the fields, validation and matching run, and approved items push into QuickBooks, Xero or Zoho. Anything that fails a check goes to an exceptions queue for a person.

The form matters because it fixes the weakest part of the inbox rouet. Email attachments come with no metadata, so someone has to work out which client sent what. A form delivers the client ID, period and document type alongside the file, and the extraction step starts with context.

The handoff is a webhook. Qwenvo posts each submission to any URL, so Zapier, Make, n8n or your own endpoint can receive it. This is the shape we typically map to before extraction. It is illustrative, so check the webhooks help page for the exact fields yiur form sends.

{
  "client_id": "C-1042",
  "period": "2026-09",
  "document_type": "vendor_invoice",
  "email": "owner@clientco.example",
  "files": ["https://.../september-invoices.pdf"],
  "submitted_at": "2026-10-30T14:12:09Z"
}

Anything tat looks wrong at this stage, such as an unknown client ID or no files, should stop and alert someone rather than flow through.

Pitfalls we plan for

• Wrong file type for the job. A client sends a photo of a statement when you need a PDF. Say what is acceptable in the label, and let extraction flag unreadable images.
• One client, many submissions. Clients upload in several batches. Key your downstream records on client ID and period, not on the submission.
• Retention you did not choose. If documents sit forever, you hold more client data than you need. Set the retention window deliberately.
• Sensitive material. Qwenvo is hosted in the United States and has no HIPAA offering. If your engagement terms or local rules require data hosted elsewhere, take that into account. Tally is hosted in Europe.
• Per-submission PDFs. Exported PDFs of a submission cannot draw some scripts (Devanagari, Arabic) or emoji. CSV and XLSX exports can.

If your whole client base already lives in your Microsoft tneant, staying on Microsoft Forms is a reasonable call. The pain is specific to clients outside it.

Questions teams ask

Can clients upload to Qwenvo without any account?

Yes. The form is a public link, and respondents do not sign in. Email verification with a one-time code is optional, and it is the way to confirm who is sending without an account.

What happens to the files after they arrive?

They sit with the submission. You can export submissions as CSV, JSON or XLSX, or send the data on with a webhook. Set data retention so they auto-delete after the number of days you choose. We do not state a storage total, so if you expect very heavy volume, read the fair use policy.

Do I need the AI invoice system to use the form?

No. The form works alone as a cleaner replacement for email attachments. The system adds extraction, validation, matching and the ledger push once volume makes manual entry the bottleneck. It is priced at a $1,800 setup plus a $349/month care plan.

Can the form route urgent uploads to the right person?

Yes. AI triage gives each submission a category, priority, sentiment and a short summary. Routing rules can email up to 5 addresses or post to a Slack incoming webhook. A monthly AI usage allowance applies per account.

Next step

Take ten real documents your clients have sent you, including the largest one, and run them through a test form. Build it from the template, add the hidden client ID, and open the link on your phone as a client would. If it works there, put it on a subdomain and send it to your first five clients.

Open the client intake template