How to connect WordPress forms to accounting software

Decide what should happen after a form is submitted. A contact form may only need to create or update a customer. A quote form may need an estimate. A paid order may need an invoice, a payment record or both.

Do not send every submission straight into accounting by default. Set a condition such as a selected service, a completed payment or an approved enquiry. This prevents test entries, spam and incomplete forms from creating accounting records.

Add separate fields for the customer’s name, email address, company, billing address, currency, product or service, quantity, tax status and payment reference where those details are required. Use consistent field types rather than putting several values into one paragraph field.

Decide whether the form collects payment. A payment gateway may confirm a transaction, but it does not automatically mean that an accounting invoice has been created or marked as paid.

Check your form plugin’s add-on or integration settings, then connect the accounting account and create a feed for the specific form. In Gravity Forms, feeds are configured from the form’s add-on settings and map submitted fields to the external service.

Map the client fields first, then configure the invoice, estimate, line items, discount, notes and conditional logic. Save the feed and keep invoices in draft until you have confirmed the mapping. FreshBooks invoices created through its API begin as drafts unless they are sent or marked as sent.

If there is no native accounting add-on, connect the form plugin to an automation service or webhook. The form submission is the trigger; the accounting platform is the action. Map the customer fields, line-item description, quantity, unit price, tax and payment status in the action step.

For example, a Gravity Forms connection through Zapier requires the site to be publicly reachable over HTTPS, the relevant add-on and REST API credentials.

Use a filter before the accounting action. Otherwise a visitor refreshing the confirmation page, submitting twice or failing payment can create duplicate clients or invoices.

Use custom code only when the native integration and automation route cannot handle your accounting rules. You will need to authenticate with the accounting service, receive the form submission on the server, validate and sanitise the values, find or create the customer, then create the invoice or estimate.

FreshBooks uses OAuth2 for API authentication and provides separate operations for clients and invoices. Its invoice API also requires the correct authorisation scopes, and invoice creation can return a draft that still needs to be sent.

Keep API credentials out of form fields and theme files. Store them in protected configuration, log failures without recording sensitive payment data and add a way to retry failed submissions without creating a second invoice.

Submit the form with a clearly marked test customer and check the accounting account. Confirm the customer, address, currency, tax treatment, line-item totals, invoice status and payment reference. Test both the success and failure paths.

Check what happens when the same email address submits twice, when a required accounting field is empty and when the form payment fails. The common Friday problem is a successful form confirmation paired with a failed accounting request, so make sure the site reports or records that failure for follow-up.

The quickest route is a supported native add-on for your form plugin and accounting platform. For Gravity Forms and FreshBooks, the named Gravity Forms Freshbooks Addon is intended to create clients, invoices and estimates from submissions, but confirm that the download supports the current FreshBooks service before installing it.

Gravity Forms’ own documentation says its FreshBooks Classic add-on and Classic API were discontinued in mid-2022, so do not assume an add-on labelled FreshBooks will work with a current account. If it is not current, use an automation bridge or the FreshBooks API instead.