PandaDoc Usage Credits Explained: What Consumes Them, What They Cost, and How to Budget
PandaDoc usage credits are a metered allowance that is consumed each time a document is created through an automated channel: the API, Zapier, Make and similar workflow tools, web forms, or bulk send. Documents your team creates by hand in the PandaDoc editor do not consume credits; on the Starter and Business plans, it is only automation volume that draws down the pool, and API document creation pauses entirely when the pool hits zero.
That one sentence answers the question most teams type into Google after their first surprise invoice or paused integration. The rest of this guide covers the detail that actually matters for budgeting: exactly which actions burn a credit and which do not, the different out-of-credit behaviour for the API versus every other channel, how trial credits and recurring credit packs work, a worked method for estimating your monthly burn before you commit to a plan, and the point at which metered credits make Enterprise custom pricing the cheaper deal. Everything here was verified against pandadoc.com in November 2026; PandaDoc adjusts packaging periodically, so treat the pricing page as the final word.
Key takeaways
- A usage credit is consumed when a new document is created through an integration or automated workflow: the API, Zapier, Make, web forms, or bulk send. Manual creation in the editor is unmetered on paid per-seat plans
- The Free plan works differently: its 5 documents per month are shared across the UI, API and automations alike
- First-time Starter and Business customers get trial credits; after those run out you buy a recurring usage credit pack, priced on your order form rather than published publicly
- Out-of-credit behaviour is not uniform: the API pauses document creation at zero and only resumes with more credits or an upgrade, while Zapier, Make, forms and bulk send fall back to pay-per-document overage, at your order form’s per-unit price or up to $5 per document where none is set
- Unused monthly credits do not roll over; annual plans can draw on the full yearly allocation at any point in the year, which suits seasonal senders
- Credit burn is a volume forecast: count the documents each automated channel will create per month, because every one of them is a credit, including test documents and regenerated drafts
- High automation volume changes the plan maths: at hundreds of automated documents a month, Enterprise custom pricing (per seat or per document) is often cheaper than Business plus credit packs
- A clean implementation reduces credit waste directly: templates and mappings that produce the right document first time mean you stop paying for the regenerated ones
What a usage credit is, and what it is not
PandaDoc’s 2026 packaging separates two kinds of document creation. A person opening the app, picking a template and building a document is seat usage: that is what the per-seat price covers ($19 per seat per month for Starter, $49 for Business, billed annually). A system creating a document with no human in the loop is metered usage: that is what credits cover.
The official definition is that a usage credit is consumed when a new document is created through an integration or automated workflow. In practice that means five channels on Starter and Business:
| Channel | Consumes credits? | Typical use |
|---|---|---|
| Manual creation in the editor | No | A rep builds a proposal from a template |
| API | Yes | Your product or CRM middleware generates documents programmatically |
| Zapier, Make and similar tools | Yes | A deal stage change triggers document creation |
| Web forms | Yes | A prospect fills a form and a document is generated |
| Bulk send | Yes | One template sent to a large recipient list, one document each |
| Native CRM integrations (rep clicks “create document” in HubSpot) | No, this is a manual creation initiated by a seat holder | A rep creates a proposal from inside the CRM record |
Two clarifications worth making, because they are the usual sources of confusion. First, the native CRM integrations are not metered when a person initiates the document: a rep creating a proposal from a HubSpot deal via the PandaDoc HubSpot integration is manual creation with CRM data merged in. It is unattended creation, where no one clicks anything, that burns credits. Second, sending, signing, tracking and payments do not consume credits. The meter runs on document creation only.
The Free plan sits outside this model entirely: its 5 documents per month are a single shared cap across the UI, the API and every automation. If you are evaluating PandaDoc’s API on the Free plan, those 5 documents are the whole sandbox.
What happens when you run out
This is where the packaging has real teeth, and the behaviour differs by channel.
The API pauses. When the credit pool hits zero, API document creation stops and returns errors until you add credits or upgrade. The API does not support pay-as-you-go overage: it is credit-pack only. If your quoting flow, customer portal or CRM middleware creates documents through the API, an empty credit pool is an outage for that flow. Anyone building on the API should read our PandaDoc API guide with this constraint in mind and set alerts well before zero.
Everything else falls back to overage billing. Zapier, Make, web forms and bulk send keep working after the pool empties, and each document beyond your credits is billed as pay-per-document overage: at the per-unit price on your order form if one is set, and up to $5 per document where none is. That default matters. A runaway Zap or an unexpectedly successful web form can create a lot of $5 documents before anyone notices.
PandaDoc does surface warnings: in-product notifications and emails to the account owner as you approach the limit. Treat those as operational alerts, not marketing. The teams that get surprised are the ones where the account owner’s inbox is not the person who owns the automation.
One more rule that shapes budgeting: unused credits do not roll over month to month. Annual plans soften this by letting you draw on the full yearly allocation at any time during the year, which is the right shape for seasonal businesses: an accounting firm bulk-sending engagement letters every January, or an events company whose quoting peaks in two quarters, can spend most of a year’s credits in the busy months rather than losing the quiet months’ share.
Trial credits and credit packs: how you actually buy this
First-time Starter and Business customers get trial credits included, enough to prove out an automation without a separate purchase. After those are consumed, continued automation volume means buying a recurring usage credit pack.
PandaDoc does not publish credit pack prices or per-plan credit counts on the public pricing page; packs are priced on your order form, and the included trial amounts are stated in-product. That is worth knowing before a renewal conversation, because it means two things. One: your effective per-document automation cost is negotiable, and worth negotiating if your volume is growing. Two: you cannot fully budget PandaDoc from the public pricing page alone if automation is central to your setup; get the credit pack line onto the order form during the sales conversation, not after go-live.
If you are still choosing between tiers, our PandaDoc Essentials vs Business vs Enterprise comparison covers the feature splits; this guide’s job is the metered layer that sits on top of whichever tier you pick.
How to estimate your monthly credit burn
Credit burn is a forecast of unattended document creation. The method is counting, channel by channel:
- API: how many documents will your systems create per month? If you are generating a quote per inbound order, that is your order volume. Include retries and regenerations: a document created twice because the first had the wrong pricing table is two credits.
- Workflow tools: count the Zaps or Make scenarios that end in “create PandaDoc document” and multiply by their monthly trigger volume. Our PandaDoc Zapier integration guide covers the common recipes; each run of one of those recipes is a credit.
- Web forms: every completed form that generates a document is a credit. Use your form conversion volume, not your traffic.
- Bulk send: the big one for seasonal senders. A bulk send to 400 recipients is 400 documents. The bulk send guide covers the mechanics; for budgeting, just multiply list size by sends per year and spread it across your allocation.
- Add a waste factor. Test documents, duplicate triggers, and regenerations after template fixes all burn real credits. On a new implementation, 10 to 20 percent on top of the clean forecast is realistic until the setup settles.
Worked example: a 6-seat team on Business at $49 per seat per month, with a web form producing 30 documents a month, a HubSpot-triggered Zap producing 60, and a quarterly bulk send of 300. That is roughly 90 automated documents in an ordinary month and 390 in a bulk-send month, about 1,380 a year. At the $5 no-contract overage ceiling, a year of that volume left unbudgeted could cost more than the seats themselves: which is exactly why the credit pack belongs on the order form from day one.
Run the forecast before the sales call and you can compare three prices for the same volume: a negotiated credit pack on Business, pay-per-document overage, and an Enterprise quote.
When Enterprise pricing becomes the cheaper option
Enterprise is quoted per seat or per document, and automation volume on Enterprise is custom: negotiated with sales rather than drawn from the standard metered pool. That changes the arithmetic at scale.
The crossover logic is straightforward. On Business, your total cost is seats plus credit packs, and the packs scale linearly with automation volume. On Enterprise, document volume is part of one negotiated number. As your unattended volume climbs into the hundreds per month, the credit-pack line item grows until the Enterprise quote, which typically also carries SSO, advanced workflow features and custom integration support, stops looking like a premium and starts looking like a volume discount.
There is no public threshold, because neither credit packs nor Enterprise quotes are public. The practical rule we use: if your forecast says 300 or more automated documents a month sustained, or your API flow is revenue-critical enough that a paused integration is unacceptable, get the Enterprise quote and compare it against Business plus packs for the same volume. Teams sending at volume through the API (we have scoped setups discussed at around 80 documents a day) are firmly in Enterprise territory, and treating that as a credits problem on Business is the expensive way to find out.
Where credit waste actually comes from, and how an implementation removes it
Most credit waste is not volume you did not predict. It is documents created more than once because the setup produces wrong documents first.
The pattern is familiar from the implementation work we do. A team wires up a CRM trigger or an API flow against templates that were never properly built: variables that do not map, pricing tables that need hand-fixing, conditional content that shows the wrong sections. Every document the automation creates needs checking, many need regenerating after a fix, and each regeneration is a credit. Across 105 sales calls we ran over 16 months, 82 of 129 companies named manual document creation time as a top pain; the teams that then automate on top of a broken template stack convert that time cost into a metered cash cost, and pay twice.
A proper PandaDoc implementation attacks the waste at its source: templates with variables mapped end to end from the CRM, pricing tables that pull current catalog data instead of stale numbers, and automation triggers tested against edge cases before they run on live deals. Right-first-time documents mean the credit forecast and the credit spend actually match. The same discipline shortens the human side too: teams we work with typically start from 45 to 50 minutes per manually built proposal, and the point of automating is to spend credits on documents that go out, not on drafts that get thrown away.
If your credits are draining faster than your document output grows, that gap is the diagnostic: it is template and mapping debt, and it is fixable. Our ongoing support retainers exist largely to keep that gap at zero as catalogs, pricing and templates change.
Frequently asked questions
Do manually created documents use credits? No. On Starter and Business, documents a seat holder creates in the editor, including from inside a native CRM integration, are covered by the per-seat subscription. Credits meter unattended creation only: API, Zapier, Make, web forms and bulk send. The Free plan is the exception, where all 5 monthly documents share one cap.
What happens to my API integration when credits hit zero? It stops creating documents until you add a credit pack or upgrade. The API has no pay-as-you-go fallback, so set the in-product alerts, watch the account owner emails, and buy ahead of the burn rate rather than after the outage.
How much does a credit pack cost? PandaDoc prices recurring credit packs on your order form rather than publicly. First-time customers get trial credits to start. Negotiate the pack price against your forecast volume during the sales conversation, and reprice it at renewal if your automation has grown.
Do unused credits roll over? Not between monthly periods. On annual plans you can use the full yearly allocation at any time during the year, which effectively lets seasonal volume borrow from quiet months.
Is there a point where credits make PandaDoc too expensive? At sustained volume, Business plus credit packs can cost more than an Enterprise agreement that bundles custom document volume. Forecast your monthly automated document count first; at roughly 300 or more a month, or with a revenue-critical API flow, compare an Enterprise quote before defaulting to packs.