Key Features
Specialized OCR
OCR trained specifically on purchase order layouts and field patterns
Pre-Configured Fields
Common PO fields ready for extraction with smart field detection
High Accuracy
Superior accuracy for purchase order processing compared to generic OCR
Procurement Ready
Designed for procurement workflows and vendor management systems
Purchase Order Fields
The Purchase Orders File Reader can extract standard PO fields automatically:Primary Purchase Order Fields
Vendor Information
Vendor Information
✅ Tax Payer ID - Vendor tax identification number
✅ Vendor Name - Company or individual vendor name
✅ Vendor Address - Complete vendor address
✅ Vendor Phone - Contact phone number
✅ Vendor URL - Website or online portal
Order Details
Order Details
✅ PO Number - Purchase order number
✅ Order Date - Date the order was placed
✅ Payment Terms - Payment conditions and terms
✅ Total - Total order amount
✅ Discount - Applied discount amount
Shipping Information
Shipping Information
✅ Receiver Name - Delivery recipient name
✅ Receiver Address - Delivery address
✅ Address - General address field
Additional Available Fields
Extended Invoice Fields
Extended Invoice Fields
- Invoice Receipt Date - When invoice was received
- Invoice Receipt ID - Internal invoice tracking number
- Customer Number - Customer identification
- Account Number - Account reference number
- Due Date - Payment due date
- Delivery Date - Expected delivery date
Financial Details
Financial Details
- Amount Due - Outstanding amount
- Amount Paid - Paid amount
- Subtotal - Pre-tax amount
- Tax - Tax amount
- Service Charge - Additional service fees
- Gratuity - Tip or gratuity amount
- Prior Balance - Previous account balance
- Shipping Handling Charge - Shipping costs
Vendor Details
Vendor Details
- Vendor ABN Number - Australian Business Number
- Vendor GST Number - Goods and Services Tax number
- Vendor PAN Number - Permanent Account Number
- Vendor VAT Number - Value Added Tax number
- Receiver ABN Number - Receiver’s ABN
- Receiver GST Number - Receiver’s GST number
- Receiver PAN Number - Receiver’s PAN
- Receiver VAT Number - Receiver’s VAT number
- Receiver Phone - Receiver contact information
Creating a Purchase Orders File Reader
1
Navigate to File Readers
In your application, go to File Readers section
2
Create New Reader
Click + File Reader and select Purchase Orders from the document type options
3
Configure Basic Settings
Name: Enter a descriptive name (e.g., “Vendor PO Processing”)Description: Optional description for your team
4
Select Required Fields
Choose the fields you need from the available Purchase Order fields:Core Fields: PO Number, Vendor Name, Total, Order Date
Optional Fields: Select additional fields based on your workflow needs
5
Test with Sample PO
Upload a sample purchase order to validate field extraction accuracy
Field Configuration
Essential PO Fields
Configure these core fields for most purchase order processing workflows:- Basic Configuration
- Complete Configuration
- Financial Focus
Required Fields:
- PO Number (Text) - Unique purchase order identifier
- Vendor Name (Text) - Supplier company name
- Total (Decimal) - Total order amount
- Order Date (Date) - When the order was placed
Using in Automations
Integration with Procurement Workflows
The Purchase Orders File Reader integrates with automation workflows for complete procurement processing:Common Automation Patterns
PO Processing Workflow
PO Processing Workflow
Trigger: Email Received (with PO attachment)
File Reader: Extract PO fields
Actions:
- Search Records to find vendor
- Create Record for purchase order
- Start Approval Process based on amount
- Send Email Notification to procurement team
Vendor Invoice Matching
Vendor Invoice Matching
Trigger: Attachment Added (invoice PDF)
File Reader: Extract invoice details
Actions:
- Search Records to match with existing PO
- Run Calculation to verify amounts
- Update Record Fields with invoice data
- Post Comment with matching results
Three-Way Matching
Three-Way Matching
Trigger: Record Updated (receipt confirmation)
File Reader: Process delivery receipt
Actions:
- Search Records for PO and invoice
- Run Calculation to compare quantities
- AI Classification to determine discrepancies
- Send Message to Teams for resolution
Approval Workflow Integration
Combine PO processing with approval workflows:- File Reader: Extract PO fields including Total
- IF Condition: Check if Total exceeds approval threshold
- Conditional Actions: Route to appropriate approval level
- Status Updates: Update PO status based on approval outcome
Best Practices
Field Selection
Choose only the fields you need to optimize processing speed and accuracy
Document Quality
Use clear, high-resolution PO documents for best extraction results
Validation Rules
Implement validation checks for critical fields like PO numbers and amounts
Error Handling
Plan for missing or incorrect field extraction in your automations
PO Document Preparation
For Optimal Results:- Use standard PO templates when possible
- Ensure clear printing or high-quality scans
- Avoid handwritten additions or corrections
- Keep consistent formatting across documents
- Use standard fonts and layouts
- PDF purchase orders
- Scanned PO documents
- Faxed purchase orders
- Email-embedded PO images
Advanced Features
Multi-Vendor Processing
Handle purchase orders from different vendors with varying formats:1
Vendor-Specific Configuration
Create separate PO readers for different vendor formats
2
Dynamic Field Mapping
Use AI Classification to determine vendor type and apply appropriate reader
3
Fallback Processing
Configure Text File Reader as fallback for unusual formats
Data Validation and Enrichment
Enhance extracted PO data with additional processing:- Verify vendor exists in approved vendor list
- Check PO number format and uniqueness
- Validate tax calculations
- Confirm delivery addresses
Integration with ERP Systems
Connect PO processing with enterprise systems:ERP Integration
ERP Integration
Send API Request: Post PO data to ERP system
Field Mapping: Match PO fields to ERP data structure
Status Updates: Sync approval status back to Elementum
Error Handling: Manage API failures and data conflicts
Vendor Management
Vendor Management
Search Records: Validate vendor in master data
Create Record: Add new vendors automatically
Update Record: Maintain vendor information
AI Classification: Assess vendor risk levels
Error Handling and Troubleshooting
Common Issues
Missing PO Fields
Missing PO Fields
Symptoms: Expected fields return empty valuesCauses:
- Non-standard PO format
- Poor document quality
- Unusual field placement
- Test with different PO formats
- Improve document quality
- Configure additional fields
- Consider Elementum Intelligence File Reader for complex formats
Incorrect Amount Extraction
Incorrect Amount Extraction
Symptoms: Financial amounts are wrong or missingCauses:
- Multiple currency symbols
- Unusual number formatting
- Tax calculations in different locations
- Standardize PO templates
- Use Transform Data to clean amounts
- Implement validation calculations
- Add manual review steps for large amounts
Vendor Information Errors
Vendor Information Errors
Symptoms: Vendor details extracted incorrectlyCauses:
- Multiple addresses on document
- Vendor name variations
- Address formatting differences
- Configure multiple address fields
- Use Search Records for vendor matching
- Implement fuzzy matching logic
- Maintain vendor master data
Validation Strategies
Implement validation checks in your automation workflows to ensure data accuracy before processing POs.
- PO number format and uniqueness
- Vendor exists in approved vendor list
- Amount fields are numeric and reasonable
- Dates are valid and logical
- Required fields are populated
Performance Optimization
Processing Speed
Optimization Techniques:- Select only required fields
- Use appropriate field types
- Implement caching for vendor lookups
- Process during off-peak hours for large volumes
Accuracy Improvements
Enhancement Methods:- Use high-quality source documents
- Implement data validation rules
- Configure fallback processing
- Regular testing with new PO formats
Integration Examples
Accounts Payable Workflow
- Email Received: Trigger on PO email
- Purchase Orders Reader: Extract PO fields
- Search Records: Validate vendor
- Create Record: Generate AP record
- Start Approval Process: Route based on amount
- Send API Request: Update ERP system
Procurement Analytics
- Attachment Added: Process uploaded PO
- Purchase Orders Reader: Extract all relevant fields
- Update Record: Store in procurement database
- Generate Report: Create procurement analytics
- Send Email: Distribute to procurement team
Comparison with Other File Readers
When to Use Purchase Orders Reader
Choose Purchase Orders Reader when:- Processing standard purchase order documents
- Need high accuracy for PO-specific fields
- Working with procurement workflows
- Handling vendor management processes
- Processing non-standard business documents (Elementum Intelligence Reader)
- Working with general text extraction (Text File Reader)
- Handling structured data files (Table File Reader)
Accuracy Comparison
Document Type | Purchase Orders Reader | Text File Reader | Elementum Intelligence |
---|---|---|---|
Standard POs | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐ |
Custom POs | ⭐⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐⭐ |
Multi-Format | ⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
Next Steps
Automation System
Learn how to integrate Purchase Orders Readers with procurement workflows
Approval Processes
Set up approval workflows for purchase order processing
Table File Reader
Process vendor catalogs and pricing spreadsheets
Elementum Intelligence Reader
Handle complex or non-standard purchase order formats
The Purchase Orders File Reader provides specialized OCR capabilities for procurement document processing. Use it for accurate, efficient purchase order handling in your automation workflows.