Send clean data to your tools every time
Post processing cleans and standardizes extracted values before export, so your team spends less time fixing data in spreadsheets.
Before and after transformation
No more messy exports
Remove symbols, fix formatting, and normalize values before they leave DigiParser.
Same format everywhere
Keep dates, totals, and key fields consistent across suppliers and teams.
Less manual correction
Apply rules once and stop fixing the same output issues file by file.
Ready for your tools
Send cleaner output to sheets, accounting apps, and APIs without extra cleanup.
How post processing fits your workflow
A simple four-step flow from extraction to clean export.
1Extract
DigiParser captures values from your document as usual.
2Transform
Data transformations clean text, numbers, and date formats.
3Enrich
Lookup tables map names to IDs and add missing business context.
4Export
Integrations and exports receive the transformed output automatically.
Choose the method that fits your team
Start with simple transformations, then use lookup tables or custom rules as needed.
Data Transformations
Use built-in actions to clean and format values automatically.
- Remove currency symbols
- Convert text to numbers
- Normalize date formats
Lookup Tables
Match extracted values with your reference data before export.
- Map vendor names to vendor IDs
- Standardize location or category values
- Apply consistent internal codes
Custom Code
Use JavaScript rules for advanced transformations your team needs.
- Build custom field logic
- Create conditional output values
- Handle complex edge cases
Where teams use it most
AP team month-end close
Invoices from different vendors arrive in mixed formats. Post processing standardizes date and amount fields before export.
Vendor mapping to ERP IDs
Supplier names from documents are matched with your vendor master so exports always carry the correct internal ID.
Ops reporting consistency
Teams create consistent calculated fields for reports so dashboards stay clean and comparable every week.
When and how it runs
Post processing runs right after extraction and before every export or integration push.
The transformed output is what your downstream tools receive, so teams don’t need to clean values again in spreadsheets.
Once configured, it runs automatically for every processed document without extra manual steps.
Cut weekly cleanup work for finance teams
Weekly operations effort
Manual cleanup vs automated post processing
Accounts team example
Teams save cleanup time and review more documents each week because exports are cleaner by default.
Frequently asked questions
What is post processing in DigiParser?
Post Processing runs after extraction. It helps you clean, transform, and enrich values before data is exported to your tools.
Do I need to run post processing manually each time?
No. Once set up, post processing runs automatically for every matching document.
Can I map supplier names to internal IDs?
Yes. Use lookup tables to match extracted values like supplier names to your internal IDs.
Can I use custom logic for complex rules?
Yes. DigiParser supports custom code so your team can apply advanced transformations when needed.
Set up advanced post processing quickly
Clean, map, and standardize document data automatically before it reaches your systems.