How to automate sales tax for WordPress memberships

Before changing WordPress, confirm whether your membership or course is taxable in each jurisdiction where you have an obligation to collect tax. Sales tax treatment for memberships, software, courses, and subscriptions varies by location, and economic-nexus thresholds also differ.

Decide whether prices include tax or whether tax is added at checkout. Record the jurisdictions where you are registered, the tax treatment for each membership level, and whether any customers qualify for exemption. Paid Memberships Pro recommends checking with your accountant or regional tax office before setting rates.

For a simple US setup, go to Memberships > Settings > Payments. Set the site currency, then configure the sales-tax state and rate. Paid Memberships Pro applies the flat rate when the member’s billing address is in that state; its documentation gives .06 as the format for a 6% rate.

This manual route is fine when you collect tax in one state with one straightforward rate. It breaks down when local rates differ, several states require collection, membership levels have different tax treatments, or rates change regularly.

If the built-in setting cannot express your rules, a developer can use Paid Memberships Pro’s confirmed pmpro_tax filter to alter the tax amount on an order. Put the code in a small custom plugin or a maintained code-snippet tool rather than editing the membership plugin’s files.

Custom code gives you control over regions, membership levels, and billing-address checks, but it does not maintain tax rates or decide whether your business should be registered. You must update and retest it when tax rules change.

For changing rates across multiple jurisdictions, connect tax calculation to the payment flow instead of maintaining a spreadsheet of rates. Paid Memberships Pro documents Stripe Tax through Stripe Checkout: enable the Stripe Checkout payment flow, collect a billing address, and choose whether tax is included in the membership price or calculated on top.

Stripe also requires business information, registrations, and threshold settings in its tax account. Do not enable two tax calculators for the same checkout, or the member may be charged twice.

If you use the Paid Memberships Pro AvaTax integration, install it from Memberships > Add Ons, activate it, then open Memberships > AvaTax. Enter the credentials and company details from your AvaTax account and save the page. A successful save validates the connection; incorrect account numbers, licence keys, or company codes prevent the API connection.

Set whether documents are recorded, add a unique site prefix when several sites use the same AvaTax account, and assign the appropriate tax category to each membership level. Check the current support position first: the official add-on page says this integration is deprecated and receives only minor updates and bug fixes.

Test in a sandbox or otherwise controlled environment with billing addresses inside and outside your taxable jurisdictions. Check the amount shown at checkout, the order tax field, confirmation emails, refunds, exempt customers, and a recurring renewal.

This is the Friday problem to avoid: the AvaTax integration sends recurring orders to AvaTax, but says the recurring tax rate remains the rate from the original checkout rather than being recalculated after a later rate change. It also cannot currently calculate tax on top of the membership price. Review this behaviour with your accountant before going live.

Fast way: use Paid Memberships Pro with a supported automated tax route, such as Stripe Tax through Stripe Checkout. If your existing setup specifically depends on AvaTax, configure the PMPro AvaTax integration only after confirming its deprecated status and recurring-tax limitations.