Quick Verdict

Jotform + Make provides a reliable, low-cost invoice processing pipeline for small ops teams. Jotform handles intake and basic data capture. Make routes the invoice data to your accounting tool, Slack, or email. This combo works best for teams processing fewer than 100 invoices monthly. Beyond that, look at dedicated AP automation tools.

Overview

Invoice processing is a manual time sink for most small teams. Someone receives a PDF, enters data into accounting software, checks approvals, and files it. At 1-50 person companies, this often falls on ops leads who have enough on their plate. Jotform and Make together strip out most of the manual steps without heavy upfront costs or weeks of setup.

The workflow is straightforward: vendor submits an invoice through a Jotform form attached with the PDF. Jotform extracts key fields (invoice number, amount, date, vendor name, line items) and sends that structured data to Make. Make then routes the invoice for internal approval, posts a notification to Slack or email, and optionally pushes the record to your accounting tool like QuickBooks or Xero.

Neither tool is revolutionary. Jotform is a mature form builder with decent OCR for PDFs. Make is a solid automation platform. Together they solve a concrete problem: invoices stop being lost in email threads, and you don't manually copy-paste numbers into spreadsheets.

How the Workflow Works

Step 1: Invoice Intake via Jotform

Create a Jotform form with fields for vendor email, invoice number, total amount, invoice date, and a file upload for the PDF. Use Jotform's "PDF Extractor" widget (paid plan required) to automatically pull data from the uploaded PDF. Set up "Conditional Logic" to flag incomplete or out-of-range invoices (e.g., amounts over $5,000) for manual review before automation kicks in.

Strengths: Jotform's UI is drag-and-drop simple. Non-technical team members can build the form in under an hour. The PDF extraction works reliably for standard invoice templates. Weakness: OCR accuracy drops with handwritten entries, scanned documents, or multi-page invoices with non-standard layouts. You'll need fallback validation steps.

Step 2: Data Routing via Make

Connect Jotform to Make using the built-in Jotform module. Set a trigger: "New Submission" from your form. Build a scenario that receives the structured JSON from Jotform. Use Make's router module to split the flow:

  • Path A (Standard invoices under $5,000): Auto approve, send to accounting software (via QuickBooks or Xero module), log to Google Sheets, and notify the ops lead via Slack with a summary.
  • Path B (Invoices over $5,000 or missing fields): Route to a Slack approval channel with buttons. Wait for "approve" or "reject" response using Slack webhooks. On approval, proceed as Path A. On rejection, notify the vendor via email template.

Make also handles error states: if Jotform's extraction fails, route the invoice to a "manual review" folder and alert the team.

Step 3: Approval and Archiving

Use Make to store approved invoices in a Google Drive folder named by vendor/date, update a master spreadsheet with status, and send payment instructions to your accounting tool. You can also add a final step to email the vendor a confirmation.

Price Comparison

Here's the annual cost for a team processing ~50 invoices per month:

Tool Plan Needed Annual Cost Notes
Jotform Bronze ($34/mo) or Silver ($49/mo) $408 - $588 Bronze supports 100 forms and 1,000 submissions. PDF Extractor available on Silver and up.
Make Free (10k ops/mo) or Core ($9/mo, 10k ops) $0 - $108 Free tier is fine for low volume. Core plan needed for webhooks and multiple active scenarios.
QuickBooks Online Simple Start ($15/mo) or Essentials ($35/mo) $180 - $420 Already paid by most teams. Make's QuickBooks module works with both plans.

Total annual additional cost: $408 to $696. Compare that to dedicated AP tools like Bill.com ($399/mo baseline) or Stampli, which start around $200/mo for small teams. Jotform + Make is significantly cheaper for low-volume processing.

Who Each Is For

Jotform is best for:

  • Teams that already use Jotform for other intake processes (support tickets, lead gen, etc.).
  • Non-technical ops leads who need a visual form builder with no code.
  • Teams with mostly standard, single-page PDF invoices from known vendors.

Not for: Teams processing complex scanned documents or invoices with varying formats. Consider a dedicated OCR platform like Rossum or Hypatos with Make instead.

Make is best for:

  • Teams comfortable with visual workflow builders and basic conditional logic.
  • Ops leads who need to connect 5+ tools (Jotform, Slack, Google Drive, QuickBooks, Sheets).
  • Low-to-medium invoice volume (under 100/month). Make's free tier caps operations; at 100 invoices with multiple steps, you'll hit limits.

Not for: High-volume processing (500+ invoices/month). Make's operation limits and lack of built-in AP-specific features (like duplicate detection or 2-way matching) become liabilities.

Further Reading