Payer details
Know who is submitting the payment.
Collect the payer's name and contact. When someone pays for another person, distinguish the payer from the account holder.
- Payer name and email.
- Phone for questions.
- Relationship to account holder.
Free bill pay form builder
Free AI Bill Pay Form Generator
Describe your bills and matching references. Makeform creates a bill pay form with payer details, account number, billing period, amount, payment choice, and confirmation.
- Unlimited free forms and responses
- Editable before publishing
- Account and payment fields
- Built for utilities and service businesses
31129+ makers build faster
Used by tools like ChatGPT, Perplexity & ClaudeRoute payment records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your workflow, or send it to the Makeform builder. Every example is editable.
Prompt ready4 formats
Audience
Residential customers paying water or energy bills
Format
Account lookup and payment form
Prompt size
245 chars
Brief qualitySends to builder
Example form structure
Account lookup and payment form
Prompt exampleEditable in builder
Customer and service address
Short answerFirst ask
2
Account and invoice number
Short answer
3
Billing period
Dropdown
4
Amount to pay
Currency
5
Payment method
Multiple choice
Suggested routing tags
Payment received
Needs account match
Follow-up required
Request the billing period and show only a masked account hint in confirmations.
Step 1
Identify
customer, account, invoice, and billing period
Step 2
Review
amount and payment choice confirmed
Step 3
Submit
authorization captured with the payment record
Step 4
Reconcile
billing team matches and follows exceptions
Why use a bill pay form
A payment is only useful when it reaches the right account.
A generic payment link may collect an amount but leave staff guessing which invoice it belongs to. A focused bill pay form collects the matching references before submission.
Match the customer first
Require the account number, service address, invoice reference, or another identifier your billing team already uses before asking for an amount.
Handle payment exceptions
Reveal partial-payment reasons, multiple invoice references, or billing questions only when they apply.
Confirm the submitted details
Confirm submission and route the account, invoice, and amount to the reconciliation team.
Built around real billing flows
One starting point for four payment situations.
Choose the workflow closest to yours, then replace example labels and references with the terms customers recognize on your own bills.
Utility accounts
Service address, account number, billing period, current amount, and contact details for household bills.
Business invoices
Customer ID, one or more invoice numbers, payer contact, remittance note, and amount allocation.
Property charges
Property address, unit, charge type, account reference, and partial-payment explanation.
Staff-assisted payments
A short link with a support case reference so the payment returns to the conversation that started it.
Bill payment workflow
Build a form that billing staff can reconcile.
Start with fields printed on the invoice, then shape follow-up around how your team posts payments.
01
Describe the bill and payer
Describe what customers pay, the bill references, and whether one submission can cover multiple invoices.
02
Edit fields and instructions
Reuse statement labels, show an account format, and require every field needed for matching.
03
Add exception paths
Show follow-up fields for partial payments, disputed amounts, several invoices, or a payer acting for another account holder.
04
Route and reconcile
Send submissions to billing, tag records needing review, and confirm receipt.
Form vs email vs generic link
Choose a collection method that preserves payment context.
Compare how consistently each method delivers account, invoice, amount, and payer details.
Approach
What the team receives
Best fit
ApproachPayment details by email
What the team receivesReferences vary and key information may be missing.
Best fitAn unusual one-off billing question.
ApproachGeneric payment link
What the team receivesAn amount may arrive without account context.
Best fitA transaction matched somewhere else.
Approach
Generated bill pay form
What the team receivesConsistent account, invoice, amount, exception, and contact fields.
Best fitRecurring payments needing reconciliation.
Field guide
What a useful bill pay form should include.
Build the form around account matching, clear payment intent, and exception handling. Use these six field groups as a practical checklist.
Account matching
Ask for references customers can find.
Use identifiers and labels printed on the bill. Show format guidance without using real customer data.
- Account number.
- Service address or unit.
- Invoice and billing period.
Bill details
Capture what the payment covers.
Ask for the invoice, charge type, or billing month. Allow several references when combined payments are accepted.
- Charge category.
- Invoice date and balance.
- One or multiple invoices.
Payment intent
Make the amount easy to verify.
Separate the balance from the payment amount. Use currency fields and require review before submission.
- Bill balance.
- Payment amount.
- Reason when amounts differ.
Payment handling
Keep card data out of ordinary text fields.
Use a purpose-built connection or hosted step for card details. Keep matching references in the form, not card numbers in ordinary response fields.
- Payment method.
- Transaction reference.
- No card number in text fields.
Confirmation and support
Explain what happens after submission.
Confirm what was received and which reference to keep. Route exceptions to a billing queue.
- Amount and account hint.
- Confirmation reference.
- Support contact and next step.
Related tools
Build the rest of the billing workflow.
Connect bill payment intake with invoice requests, payment requests, disputes, card payments, and processor-specific forms.
Payment Form Generator
Start from a broad payment form when the workflow is not tied to a recurring bill.
Open toolAI Invoice Request Form Generator
Collect the details staff need before creating or sending an invoice.
Open toolAI Payment Request Form Generator
Organize internal or customer-facing requests for a payment to be initiated.
Open toolAI Billing Dispute Form Generator
Route questions about charges and disputed amounts into a review queue.
Open toolAI Credit Card Payment Form Generator
Design a payment flow specifically around credit card transactions and references.
Open toolStripe Payment Form Generator
Create a payment form for a workflow that uses Stripe as its payment route.
Open toolFAQ
Bill pay form questions
Practical answers for billing teams creating an online customer payment route.
What is a bill pay form?
A bill pay form lets customers identify an account and state what they are paying. It collects payer contact, account and invoice references, billing period, amount, method, and review acknowledgment for matching.
What fields should a bill pay form include?
Include payer contact, account and property reference, invoice, billing period, balance, payment amount, and method. Add conditional fields for partial payments, several invoices, billing questions, or third-party payers.
Can customers pay several invoices in one submission?
Yes. Ask whether it covers one invoice or several, then reveal a repeatable reference field. Request allocation amounts when billing staff must divide the total and explain the accepted format.
How should a bill pay form handle partial payments?
Separate the stated balance from the payment amount. When they differ, require a reason or billing question and tag the submission for review so the exception is immediately visible.
Should I ask customers to type card details into the form?
Do not use ordinary response fields for a full card number or security code. Use a purpose-built connection or hosted step, while keeping account, invoice, amount, and transaction references together.
Is this bill pay form generator free?
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and collect submissions without a response cap; the paid tier removes the Makeform badge.
Can the billing team receive payment notifications?
Yes. Route submissions to an inbox, Google Sheets, Slack, or Zapier. Include the account hint, invoice, amount, and exception status so staff can triage the record.
What should the confirmation message say?
Confirm submission, repeat the amount and a masked account or invoice hint, provide a reference, and explain the next step for questions. Do not display payment details or a full account number.
Turn a payment link into a complete billing record.
Generate a bill pay form customers can complete with confidence.
Unlimited free forms and responsesAccount and invoice matchingEditable payment workflow