# Credits and Billing Source: https://www.digiparser.com/docs/guides/troubleshooting/credits-and-billing Common Problems # Credits and Billing Calculate credit usage for processing, AI features, document type rules, classifiers, and reprocessing Copy MarkdownOpen # [Credits and Billing](#credits-and-billing) Feedback DigiParser uses credits to process documents. Most charges are based on the number of pages processed. Document type rules and document classifiers use a smaller, per-document charge. Feedback Credits belong to the team, so documents processed by any team member, parser, classifier, inbox, or integration use the same team balance. ## [How credits work](#how-credits-work) Action or setting Credit cost Standard document processing **1 credit per page** Email conversation **At least 1 page per visible message**; messages longer than 5,000 visible characters continue onto additional pages Calculate confidence scores **+1 credit per processed page** Markdown parsing **+1 credit per processed page** Critical data extraction mode **+2 credits per processed page** Split with AI **+1 credit per selected page being split** Document type rules **0.1 credit per document checked** Document classifier **0.1 credit per document classified** Reprocess a document Charged again using the parser's current settings Feedback **Fast** and **Accurate** extraction use the standard 1 credit per page. **Critical** uses 3 credits per page before any other optional features are added. Feedback These costs add together when the same document uses more than one feature. ## [Common calculations](#common-calculations) ### [Email bodies](#email-bodies) Feedback Each visible message in an email conversation uses at least one processing page: Feedback * Three one-line messages = 3 pages * One message containing 5,001 visible characters = 2 pages * A three-message conversation where one message needs two pages = 4 pages Feedback Page 1 is the newest message. Use **Limit which pages to parse** to select conversation pages; for example, `1-3` processes the three newest pages. HTML markup, scripts, styles, and repeated whitespace do not increase the visible-character count. Feedback Email attachments are separate documents and keep their normal page counts. For example, a short email body with a 27-page PDF attachment uses 1 processing page for the body and 27 processing pages for the PDF. Any enabled confidence or Critical-mode multiplier applies to both documents in the usual way. ### [Standard processing](#standard-processing) Feedback A 10-page document processed with standard settings uses: Feedback `10 pages x 1 credit = 10 credits` ### [Confidence scores](#confidence-scores) Feedback A 10-page document with confidence scores enabled uses: Feedback `10 pages x (1 standard + 1 confidence) = 20 credits` ### [Critical mode with confidence scores](#critical-mode-with-confidence-scores) Feedback A 10-page document using Critical mode and confidence scores uses: Feedback `10 pages x (1 standard + 2 Critical + 1 confidence) = 40 credits` ### [Markdown parsing](#markdown-parsing) Feedback A 10-page document with Markdown parsing enabled uses: Feedback `10 pages x (1 standard + 1 Markdown) = 20 credits` Feedback The Markdown charge is separate from the structured extraction charge. It still uses 1 DigiParser credit per page when a team uses its own AI provider key for structured extraction. ### [Split with AI](#split-with-ai) Feedback A 20-page PDF split with AI uses 20 extra credits for the AI split. The resulting documents then use their normal processing credits. Feedback For example, if the 20 pages are split into four 5-page documents and processed with standard settings: Feedback `20 AI split credits + 20 standard processing credits = 40 credits` Feedback Splitting every X pages or splitting by page ranges does not add an AI splitting charge. The resulting documents still use their normal page-processing credits. ### [Pages to be parsed with splitting](#pages-to-be-parsed-with-splitting) Feedback If **Pages to be parsed** is enabled, DigiParser selects those pages before splitting or extraction. All per-page credit calculations use the selected pages, not the full uploaded PDF. Feedback For example, a 1,000-page PDF limited to `1-6` with Split with AI and standard extraction uses: Feedback `6 selected pages x (1 AI split + 1 standard processing) = 12 credits` Feedback The remaining 994 pages are not split, extracted, or included in the per-page credit calculation. ### [Document type rules](#document-type-rules) Feedback Document type rules cost **0.1 credit for every incoming document checked**, whether DigiParser processes or skips it. Feedback * A skipped document uses **0.1 credit** because it was checked, but it does not use page-processing credits. * An accepted 5-page document with standard settings uses **5.1 credits**: 0.1 for the check and 5 for extraction. * Clicking **Process anyway** on a skipped document bypasses the document type rule for that run and uses the normal processing credits. ### [Document classifiers](#document-classifiers) Feedback A document classifier costs **0.1 credit per document classified**. Feedback * A document that is not routed uses **0.1 credit** for classification. * A routed 5-page document with standard target-parser settings uses **5.1 credits**: 0.1 for classification and 5 for extraction. * If the target parser also has document type rules enabled, its 0.1-credit document check is added as well. Feedback If **Split Before Routing** creates several documents, the classifier checks and charges for each split document separately. Split with AI also adds its per-page AI splitting charge. ## [What does not change the calculation](#what-does-not-change-the-calculation) Feedback The way a document arrives does not change its processing cost. Uploads, email attachments, upload pages, embeds, API imports, cloud imports, and automation platforms use the same credit rules. Feedback Fixed-page and page-range splitting do not duplicate pages. For example, splitting one 20-page PDF into four 5-page documents still results in 20 processed pages. ## [Reprocessing uses credits again](#reprocessing-uses-credits-again) Feedback Reprocessing starts a new processing run. DigiParser charges for the pages again using the parser settings that are active when you reprocess the document. Feedback For example, reprocessing a 5-page document with confidence scores enabled uses another 10 credits. Reprocessing a 5-page document with Markdown parsing enabled also uses another 10 credits, even when DigiParser reuses the existing Markdown file. ## [Checking your team credits](#checking-your-team-credits) Feedback 1. Open the team menu. 2. Click **Billing** to see your current credits. app.digiparser.com![Team settings Billing tab showing the available credit balance](https://documents.digiparser.com/docs/screenshots/2026-07-27/billing-credits.png?sig=ed1a7039803b96d4d45fa8b8e94a5c3ce707ce243f00630f192a6dc728b81263) ## [Checking credits used by a document](#checking-credits-used-by-a-document) Feedback 1. Open the **Document Inbox**. 2. Open the document you want to check. 3. After the document uses credits, find the coin icon beside its status. The number beside it is the total credits used by that document. 4. Open the **History** tab to see each recorded credit charge, such as processing, reprocessing, Split with AI, document type rules, or classifier checks. Feedback The document total is available for documents added on or after **July 29, 2026 at 8:00 PM IST**. Older documents do not show a total because their earlier credit history may be incomplete. ## [What happens when credits run out](#what-happens-when-credits-run-out) Feedback If you don't have enough credits to process a document: Feedback * **The document is saved** but **not processed** * You'll see an error message: "You don't have enough page credits available. Required: X, Available: Y" * **Low credit email notifications** are sent (rate limited to once per day) * **Documents can be reprocessed** once you add credits Feedback **Example**: If you try to process a 10-page document but only have 5 credits, the document is saved and marked **Failed** with the credit error. Add credits, then reprocess it. ## [Adding credits](#adding-credits) Feedback To add credits: Feedback 1. Open the team menu and click **Billing**. 2. **Upgrade your plan** or **purchase additional credits** (depending on your plan). 3. Once credits are added, you can **re-process** documents that failed due to low credits. Feedback Monthly plan credits are used first. Extra credits purchased separately are used after the monthly balance and are valid for one year from purchase. ## [Reprocessing after adding credits](#reprocessing-after-adding-credits) Feedback After adding credits, documents that failed due to low credits can be reprocessed: Feedback 1. Go to the **Document Inbox**. 2. Find documents with **Failed** status. 3. Click **More (⋮) -> Re-process document** on each document. ## [Tips](#tips) Feedback * **Monitor credits**: Check your credits regularly, especially before processing large batches * **Include every enabled feature**: Add page charges and per-document checks when estimating a batch * **Plan for reprocessing**: Testing or reprocessing a document creates another charged processing run * **Use extra features where they help**: Turn off confidence scores, Markdown parsing, Critical mode, or Split with AI when the additional processing is not needed * **Watch for notifications**: You'll get email notifications when credits are low ## [Next steps](#next-steps) Feedback * [Manage Billing and Credits](/docs/guides/advanced-features/billing-and-credits) - Change plans, payment details, and extra credits * [Document Type Rules](/docs/guides/parsers/parser-settings/document-type-rules) - Check or skip incoming document types * [Document Classifiers](/docs/guides/document-classifiers) - Route mixed documents to the correct parser * [Split Documents](/docs/guides/parsers/parser-settings/split-documents) - Compare fixed and AI splitting * [Processing Failures](/docs/guides/troubleshooting/processing-failures) - What to do when processing fails How is this guide? GoodBad [ Troubleshoot Integrations Check why a connected import or export did not run ](/docs/guides/troubleshooting/integration-problems)