FAQs

Frequently asked questions about the Affinda platform.

Account and Security

Does Affinda support MFA?

Yes. Users can configure MFA by navigating to their Profile Settings (click the user icon in the top left corner) and clicking “Set up MFA”. Affinda supports both email and authenticator apps.

If you would like to require MFA for all users in your organisation, reach out to the Affinda team, and we can enable this security requirement.

How many users can I add to my organization?

Affinda doesn’t limit the number of users you can add to your organization

Capabilities

What languages do you support?

Affinda supports over 50 languages, including the following:

Language Code	Language
En	English
De	German
Ja	Japanese
Es	Spanish
Fr	French
It	Italian
Pt	Portuguese
Zh-tw	Chinese (Taiwan)
Zh-cn	Chinese (PRC)
Nl	Dutch
Pl	Polish
Sv	Swedish
Cs	Czech
Ru	Russian
Da	Danish
Ro	Romanian
No	Norwegian
Id	Bahasa Indonesian
Hu	Hungarian
Tr	Turkish
Hr	Croatian
Sk	Slovak
Fi	Finnish
Vi	Vietnamese
Th	Thai
Sl	Slovenian
El	Greek
Et	Estonian
Ar	Arabic
Ko	Korean
Lt	Lithuanian
Fa	Persian
Bg	Bulgarian
He	Hebrew
Uk	Ukrainian
Tl	Tagalog
Mk	Macedonian
So	Somali
Lv	Latvian, Lettish
Sq	Albanian
Af	Afrikaans
Sw	Swahili
Bn	Bengali
Hi	Hindi
Ur	Urdu
Mr	Marathi
Gu	Gujarati
Ta	Tamil
Ne	Nepali
Ml	Malayalam
Te	Telugu
Kn	Kannada
Pa	Punjabi

Can Affinda handle multi-lingual documents?

Yes, Affinda supports multilingual documents.

How do I increase the page limit in my organisation?

The default page limit in Affinda is 15 pages per document. If you need to increase this to fit your use case, get in contact with the Affinda team.

Can I get the raw data off my document from Affinda?

All data exports include a rawText field containing the full, unstructured text extracted from the document.

For every field Affinda extracts, you’ll get two values:

• raw — the value exactly as it appears on the document.
• parsed — the value after data-type processing and text transformations (e.g., date/number normalization).

If I enable splitting, can I still see the whole file?

After splitting is enabled, the original multi-document file remains available as the “parent” record, and each piece of it becomes a “child” document. The parent–child relationship means you can still access the full set of pages and see which children were created. In practice, when a file is split Affinda creates new files with suffixes on the filename (e.g., [filename]_1, [filename]_2).

In the app, you can use the “Edit Pages” function to split or combine pages again.

Is the fingerprinting solely based on the document layout?

Affinda’s fingerprinting algorithm uses both textual and visual content to construct a representative embedding of the document’s meaning and layout. This includes not just the physical aspects (layout, text location, formatting) but also analyzes the semantic meaning of the text itself.

Configuration

Can I add custom fields in Affinda?

Yes, Affinda is completely configurable, so you can add custom fields as you like. See Field Configuration to see how to add custom fields to your document types in Affinda.

Can I create calculated fields in Affinda?

Affinda does not currently support creating calculated fields within the app; however, we are working towards it on our product roadmap. For the time being, Affinda can support your calculated fields by automating the extraction of the source fields in a structured and usable format, so you can build calculated fields in your own systems.

Can I write my own validation rules in Affinda?

Absolutely - Affinda’s allows customers to create validation rules using a natural language description of the logic that they would like to implement:

1. Type your rule in plain language, referencing any extracted field with @field_name.
2. Click Generate to create the rule and view the underlying code.

The prompt can handle a broad range of validations.

If you require more specific logic, Affinda doesn’t support uploading custom code directly. Instead, you can:

• Pull the extracted data via the API,
• Run your own checks locally, and
• Push the results back to Affinda through our Create Validation Result API so the outcomes appear in the app and flag documents for review.

When should I add a new document type?

Affinda document types are built to handle multiple layouts and templates. If the information you’re extracting follows the same schema (i.e., the same fields and structure), you don’t need a new document type for each template.

However, our models perform best with simpler schemas. If the extraction schema differs significantly across templates, consider splitting them into separate document types.

What happens to documents in Affinda that aren't classified?

By default, documents that the model doesn’t match to one of the document types linked to your workspace will remain in “For Review” as unclassified. Users can review and manually classify these documents as they like.

Alternatively, users can configure their workspace so documents that are left unclassified are automatically rejected. To do this, navigate to the Workflow settings → Configure Classification and enable “Reject Documents”.

Performance & Troubleshooting

What are Affinda's end-to-end latency expectations?

Typical parse times (simple bill ≈ 5–15 s; complex multi-page ≈ 10–30 s)

I got an error when trying to parse my document, how do I fix it?

Documents uploaded to Affinda might cause an error for a number of reasons. Review our Error Glossary to understand the error and how you can fix it.

Affinda misclassified two of my document types. How do I improve?

If Affinda models are repeatedly mixing up two of your document types in classification, there are a few steps you can take to improve performance.

Firstly, ensure there are adequate examples in your model memory of both document types. Check that you have not confirmed any documents that are labelled as the wrong document type.

Secondly, check that the name and description of each document type are clear and relevant. The models use these to predict classifications. Add disambiguation hints (unique keywords, fields, or layout cues) to help the model tell similar types apart.

Show Example

Document type: Broker Invoice

Description: An invoice for brokerage/origination/referral fees. Line items typically include the keywords “brokerage”, “origination”, or “referral.”

I got an error message saying 'Something went wrong;' - what did I do?

From time to time, users may hit an unexpected error when taking action in the Affinda app. If this occurs, try refreshing the page and trying again. If problems persist, get in touch with Affinda Support.

About Us and Contact

How do I contact Affinda?

Fill out the form here, and our team will get back to you.

What is Affinda?

_Affinda specialises in enterprise AI transformations in business process automation, enabling intelligent document processing. Affinda’s AI platform, and customised solutions, automate end-to-end processes for faster, smarter operations and real productivity gains.  _

_Affinda’s document AI technology combines 10+ years of IP in document reconstruction, with the latest advancements in computer vision, natural language processing and deep learning.  _

_Our technology is used by enterprises globally across a wide range of industries to automate their document processing workflows. _

_We are headquartered in Melbourne, Australia, with a global team across Asia Pacific, North America and Europe. _

_For more information _head to our website.

What is Affinda's pricing?

Affinda offers flexible and scalable pricing plans to meet businesses’ needs. For full pricing details, please head to our website pricing pages.

• Affinda Platform pricing
• Resume Parser pricing