Templates

Templates are the fastest way to get started when your document is similar to a common format already available in the library.

What templates are

A template is a shared parser starter.

It usually includes:

• a predefined field structure
• a configured processor
• a sample document
• sample output
• template-specific notes or limitations

Templates help you understand the shape of a working parser without starting from an empty schema.

Important behavior

You do not process production documents against the shared template directly.

When you click Use template, SimplyParse creates a private copy in your account. That private copy becomes your parser.

This matters because:

• your parser is editable
• your usage is scoped to your account
• your integrations stay private
• the original template remains unchanged

When to use a template

Templates are a good choice when:

• your document looks similar to a common business format
• you want to get a first result quickly
• you want to learn the platform by example
• you expect to make only light adjustments after starting

When not to use a template

Create a parser from scratch instead when:

• your document layout is very custom
• the fields you need are unusual or deeply nested
• the template is only loosely related to your actual documents
• you already know you will need a highly specific schema

How to evaluate a template

Before adopting a template, review:

• the template name and purpose
• extracted fields
• sample document
• sample output
• listed limitations

Ask these questions:

1. Does this look like my document family?
2. Are the main fields already close to what I need?
3. Would editing this be easier than starting over?

If the answer to most of these is yes, start from the template.

How to use a template

Step 1: Open the Library

Browse or search the available templates.

Step 2: Open the details

Inspect the template and confirm that it is close to your document type.

Step 3: Click Use template

This creates a private parser in your account.

The app then opens your new parser on the Test Parser tab.

Step 4: Run the sample document

Start by running the built-in sample.

This tells you whether the template is functioning as expected before you introduce your own files.

Step 5: Upload your own document

Use your own document next.

This is the real test of whether the template matches your workflow closely enough.

Step 6: Edit the private copy

If needed, adjust:

• field names
• field types
• nested structures
• validation rules
• parser settings
• integrations

Best way to test a template

Use this progression:

1. Run the provided sample document.
2. Upload one of your own documents.
3. Compare the output against your expected values.
4. Make the smallest field changes needed.
5. Test again before moving to batch processing.

Common outcomes after adopting a template

Usually one of three things happens:

It works well immediately

Great. Keep the parser, test a few more documents, and move into production usage.

It is close, but needs edits

This is the most common outcome. Adjust the private copy and keep iterating.

It is not a good fit

If the document structure is too different, stop forcing the template and create a parser from scratch instead.

Good template usage habits

• Start with the template that is closest, not just the first one that looks related.
• Test on one real document before processing a batch.
• Keep changes small and intentional.
• Rename fields to match your downstream systems if needed.
• Add validation only after the extraction shape is stable.

Limitations to keep in mind

• A template is a starting point, not a guarantee of perfect extraction.
• Shared templates are not your production endpoint until you clone them.
• Integrations belong on your private parser, not on the template itself.

Next steps

• If you need a custom schema, read Create a parser.
• If your parser is already working and you want stronger quality checks, read Validation rules.
• If you are ready to run more files, read Test and process documents.